Australian Energy Sector Cyber Security Framework...

What does THREAT-2h require?

Threat information is exchanged with stakeholders, for example executives, operations staff, government, connected organisations, vendors, sector organisations, regulators and ISACs, according to what may or must be shared.

Maintained by Gerard BlokdykVerified against the published standard 31 May 2026Control text last updated 21 May 2026

Other controls in Threat and vulnerability management (THREAT) – Australian Energy Sector Cyber Security Framework (AESCSF)

THREAT-1a THREAT-1a: Vulnerability information sources identified
THREAT-1b THREAT-1b: Vulnerability information gathered and interpreted
THREAT-1c THREAT-1c: Vulnerability assessments performed
THREAT-1d THREAT-1d: Relevant vulnerabilities mitigated
THREAT-1e THREAT-1e: Sources covering higher priority assets monitored
THREAT-1f THREAT-1f: Vulnerability assessments periodic and triggered
THREAT-1g THREAT-1g: Vulnerabilities analysed, prioritised and addressed
THREAT-1h THREAT-1h: Operational impact evaluated before patching

Query this from an agent

The graph holds this control, the 0 it maps to, and the evidence behind each claim, over MCP and REST.

MCP endpoint All Australian Energy Sector Cyber Security Framework (AESCSF) controls