Red Canary · Vulnerability Disclosure

Red Canary Vulnerability Disclosure

Vulnerability disclosure

Red Canary publishes a vulnerability disclosure policy for reporting security issues. A machine-readable /.well-known/security.txt is served. A dedicated security contact is published.

CompanySecurityCybersecurityManaged Detection and ResponseThreat DetectionThreat IntelligenceEndpoint SecurityIncident ResponseSecurity OperationsAutomation

Program: security.txt present

Disclosure Policy

Policy

https://redcanary.com/responsible-disclosure/

Security Contact

Contact

security@redcanary.com

Contact

grc@redcanary.com

Source

Vulnerability Disclosure

generated: '2026-08-05'
method: searched
probe: true
source: https://redcanary.com/responsible-disclosure/
policy:
- https://redcanary.com/responsible-disclosure/
contact:
- security@redcanary.com
- grc@redcanary.com
bug_bounty:
  present: false
  platform: null
  paid: false
  statement: >-
    "While we appreciate reports, we do not have a formal bug bounty at this time, and
    do not provide financial compensation for vulnerability reports."
program:
  name: Red Canary Vulnerability Disclosure Program
  safe_harbor: >-
    Not explicit. The policy sets researcher obligations (comply with applicable law,
    avoid privacy violations, do not destroy or modify data, do not degrade availability)
    but does not contain explicit legal safe-harbor language indemnifying researchers.
  commitments:
  - prompt acknowledgement of receipt
  - transparent coordination and open dialogue
  - confirmation of the vulnerability where feasible
  - updates on remediation progress including obstacles
  disclosure: coordinated — Red Canary requests non-disclosure until the issue is resolved
  required_report_fields:
  - name
  - email
  - phone
  - vulnerability description
  - vulnerability category
  - steps to validate
  - affected parameters
  - attack payload
  pgp_key: null
security_txt:
  present: false
  note: >-
    Red Canary serves no /.well-known/security.txt on redcanary.com,
    docs.redcanary.com or support.redcanary.com (all 404). The 200 at
    status.redcanary.com/.well-known/security.txt is Atlassian's Statuspage platform
    file (Canonical: https://www.atlassian.com/.well-known/security.txt) and is not
    attributable to Red Canary. Publishing an RFC 9116 security.txt pointing at
    https://redcanary.com/responsible-disclosure/ would be a one-line win for a company
    whose business is security.
evidence:
- source: https://redcanary.com/responsible-disclosure/
  kind: disclosure page
  http_status: 200
  keywords:
  - responsible disclosure
  - security@redcanary.com
- source: https://redcanary.com/trust-center/
  kind: trust-center link to VDP
  http_status: 200
- source: https://redcanary.com/.well-known/security.txt
  kind: security.txt
  http_status: 404
x-evidence:
  fetched: '2026-08-05'

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/red-canary-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 form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

GitHub Google LinkedIn

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