Ladder · Vulnerability Disclosure

Ladder Vulnerability Disclosure

Vulnerability disclosure

Ladder publishes an RFC 9116 security.txt at https://www.ladderlife.com/.well-known/security.txt whose Policy field points at a full responsible-disclosure policy at https://www.ladderlife.com/security. It is a coordinated-disclosure program with published response commitments and safe-harbor language for good-faith researchers — not a paid bug bounty, and not run on HackerOne, Bugcrowd, or Intigriti.

Ladder runs a coordinated vulnerability disclosure program on Hackerone. A machine-readable /.well-known/security.txt is served. A dedicated security contact is published.

CompanyInsuranceInsurtechLife InsuranceEmbedded FinanceEmbedded InsuranceFinancial-ServicesFintechQuoting
Program: Hackerone security.txt present

Disclosure Policy

Policy

Security Contact

Contact
mailto:security@ladderlife.com

Source

Vulnerability Disclosure

ladder-vulnerability-disclosure.yml Raw ↑
generated: '2026-07-19'
method: searched
probe: true
source: well-known/ladder-security.txt
docs: https://www.ladderlife.com/security
policy:
- https://ladderlife.com/security
contact:
- mailto:security@ladderlife.com
program_type: responsible-disclosure
bug_bounty: false
safe_harbor: true
description: >-
  Ladder publishes an RFC 9116 security.txt at
  https://www.ladderlife.com/.well-known/security.txt whose Policy field points at
  a full responsible-disclosure policy at https://www.ladderlife.com/security. It
  is a coordinated-disclosure program with published response commitments and
  safe-harbor language for good-faith researchers — not a paid bug bounty, and
  not run on HackerOne, Bugcrowd, or Intigriti.
response_commitments:
  acknowledgement: within 48 hours of receipt
  triage: 3-5 business days
  remediation_target:
    critical: 7 days
    high: 30 days
  researcher_confidentiality: 90 days after acknowledgement
rules_of_engagement:
- Non-destructive testing only
- Testing limited to accounts the researcher owns
- No automated scanning without prior coordination
- Cease testing once a vulnerability is confirmed
out_of_scope:
- Third-party services
- Denial-of-service testing
- Social engineering
- Physical security testing
security_txt:
  expires: 'Thu, 31 Mar 2027 10:00:00 -0700'
  canonical: https://www.ladderlife.com/.well-known/security.txt
  preferred_languages: en
evidence:
- source: well-known/ladder-security.txt
  kind: security.txt
- source: https://www.ladderlife.com/security
  kind: responsible-disclosure policy page

Work with this as data

Every security artifact here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for security posture

4 MCP tools reach this
  • find_securityBrowse and filter every security artifact in the catalog.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This security artifact
curl "https://apis.io/api/v1/security/ladder-vulnerability-disclosure"
All security posture
curl "https://apis.io/api/v1/security?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no email required.

A second provider on the same verified email joins the account you already have.