Aemo Vulnerability Disclosure
AEMO publishes an RFC 9116 security.txt at https://www.aemo.com.au/.well-known/security.txt naming its Cyber Security Team as the reporting channel. There is no public bug bounty (no HackerOne / Bugcrowd / Intigriti program was found) and no published safe-harbour or coordinated-disclosure policy document; the security.txt carries a Contact and a Hiring field only — no Policy, Encryption, Preferred-Languages or Expires field.
AEMO runs a coordinated vulnerability disclosure program on Hackerone. A machine-readable /.well-known/security.txt is served. A dedicated security contact is published.
Disclosure Policy
Security Contact
Source
Vulnerability Disclosure
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.
Call it yourself
curl for this page
curl "https://apis.io/api/v1/security/aemo-vulnerability-disclosure"
curl "https://apis.io/api/v1/security?limit=25"
Discovery needs no key. Ratings and market analysis are Pro.