Australia

Australian Energy Sector Cyber Security Framework (AESCSF)

393 controls. 13 other frameworks in our corpus share controls with it. Here is all of it, and how much of it you are already doing.

Page built . This page is derived from the framework corpus, which changes when the corpus is extended rather than daily.

393 controls 13 frameworks share controls with it Australia verified against its source document

Every control below is one this framework asks for. The right hand column counts how many other frameworks in our corpus carry the same control, which is the difference between doing this work once and doing it again for the next standard.

AESCSF Australian Energy Sector Cyber Security Evidence & Implementation Kit

393 controls is the documentation set somebody has to write. This is that set, already written: an adopt-ready artifact for every control in policy and procedure text you edit rather than draft, and the evidence checklist an auditor asks for against each.

See what is in it, $249

The same set every buyer of this kit receives. Nothing here is produced on request.

What you already have

Frameworks whose controls overlap this one, most first. If you run any of them, the count is roughly what you have already evidenced.

Every control

CodeControlAlso in
AESCSF-ACM-1Asset inventory2
AESCSF-ACM-2Configuration management4
AESCSF-ACM-3Change management5
AESCSF-APM-1Australian privacy management1
AESCSF-APM-2Privacy breach management1
AESCSF-CPM-1Cyber security program management1
AESCSF-CPM-2Cyber security governance and strategy1
AESCSF-CPM-3Cyber security architecture0
AESCSF-EDM-1Supply chain risk management1
AESCSF-EDM-2External dependency assessment0
AESCSF-EDM-3Dependency resilience0
AESCSF-IAM-1Identity management3
AESCSF-IAM-2Access control5
AESCSF-IAM-3Multi-factor authentication2
AESCSF-IR-1Incident response plan1
AESCSF-IR-2Incident detection and handling0
AESCSF-IR-3Continuity of operations and recovery1
AESCSF-IR-4Incident reporting1
AESCSF-ISC-1Cyber security information sharing1
AESCSF-ISC-2Stakeholder communications0
AESCSF-RM-1Establish cyber security risk management strategy1
AESCSF-RM-2Identify and assess cyber risks2
AESCSF-RM-3Manage and treat cyber risks0
AESCSF-SA-1Logging and monitoring5
AESCSF-SA-2Anomaly and event detection1
AESCSF-SA-3Common operating picture0
AESCSF-TVM-1Vulnerability management2
AESCSF-TVM-2Threat management1
AESCSF-TVM-3Patch and remediation management2
AESCSF-WM-1Cyber security workforce management0
AESCSF-WM-2Training and awareness3
AESCSF-WM-3Personnel security0
ACCESS-1aACCESS-1a: Identities created for people, services and devices needing access0
ACCESS-1bACCESS-1b: Credentials issued to those needing access0
ACCESS-1cACCESS-1c: Identities removed when no longer needed0
ACCESS-1dACCESS-1d: Password strength and reuse rules set and enforced0
ACCESS-1eACCESS-1e: Identity repositories reviewed on a schedule and on triggers0
ACCESS-1fACCESS-1f: Deprovisioning within defined time limits0
ACCESS-1gACCESS-1g: Privileged credentials used only where needed0
ACCESS-1hACCESS-1h: Stronger authentication for higher risk access0
ACCESS-1iACCESS-1i: Multifactor authentication for all access where feasible0
ACCESS-1jACCESS-1j: Inactive identities disabled after a set period0
ACCESS-2aACCESS-2a: Logical access controls in place0
ACCESS-2bACCESS-2b: Logical access revoked when no longer needed0
ACCESS-2cACCESS-2c: Logical access requirements defined and maintained0
ACCESS-2dACCESS-2d: Least privilege built into logical access rules0
ACCESS-2eACCESS-2e: Separation of duties built into logical access rules0
ACCESS-2fACCESS-2f: Asset owners approve logical access requests0
ACCESS-2gACCESS-2g: Extra scrutiny and monitoring for higher risk logical access0
ACCESS-2hACCESS-2h: Logical access reviewed on schedule, triggers and after elevation0
ACCESS-2iACCESS-2i: Anomalous logical access attempts monitored0
ACCESS-3aACCESS-3a: Physical access controls in place0
ACCESS-3bACCESS-3b: Physical access revoked when no longer needed0
ACCESS-3cACCESS-3c: Physical access logs kept0
ACCESS-3dACCESS-3d: Physical access requirements defined and maintained0
ACCESS-3eACCESS-3e: Least privilege applied to physical access0
ACCESS-3fACCESS-3f: Separation of duties applied to physical access0
ACCESS-3gACCESS-3g: Asset owners approve physical access requests0
ACCESS-3hACCESS-3h: Extra scrutiny and monitoring for higher risk physical access0
ACCESS-3iACCESS-3i: Physical access privileges reviewed and updated0
ACCESS-3jACCESS-3j: Physical access monitored for cybersecurity events0
ACCESS-AP1ACCESS-AP1: Anti-pattern: access provisioned before need is confirmed0
ACCESS-AP10ACCESS-AP10: Anti-pattern: access reviews do not test continued need0
ACCESS-AP11ACCESS-AP11: Anti-pattern: no policy ban on unauthorised devices reaching critical assets0
ACCESS-AP2ACCESS-AP2: Anti-pattern: no complete register of privileged users0
ACCESS-AP3ACCESS-AP3: Anti-pattern: deprovisioning ignores risk criteria0
ACCESS-AP4ACCESS-AP4: Anti-pattern: single-factor access to non-public internet-facing assets0
ACCESS-AP5ACCESS-AP5: Anti-pattern: privileged access granted by default0
ACCESS-AP6ACCESS-AP6: Anti-pattern: access that breaches segregation of duties0
ACCESS-AP7ACCESS-AP7: Anti-pattern: users not individually attributable0
ACCESS-AP8ACCESS-AP8: Anti-pattern: unusual access not monitored0
ACCESS-AP9ACCESS-AP9: Anti-pattern: unknown users or devices can connect to known assets0
ARCHITECTURE-1aARCHITECTURE-1a: A cybersecurity architecture strategy exists0
ARCHITECTURE-1bARCHITECTURE-1b: Architecture strategy aligned with the program strategy and enterprise architecture0
ARCHITECTURE-1cARCHITECTURE-1c: Documented architecture covering IT and OT0
ARCHITECTURE-1dARCHITECTURE-1d: Architecture governance with periodic reviews and exceptions0
ARCHITECTURE-1eARCHITECTURE-1e: Visible senior sponsorship for the architecture program0
ARCHITECTURE-1fARCHITECTURE-1f: Architecture sets cybersecurity requirements for assets0
ARCHITECTURE-1gARCHITECTURE-1g: Controls chosen and implemented to meet requirements0
ARCHITECTURE-1hARCHITECTURE-1h: Security architecture aligned with enterprise architecture0
ARCHITECTURE-1iARCHITECTURE-1i: Conformance to the architecture evaluated periodically and on triggers0
ARCHITECTURE-1jARCHITECTURE-1j: Architecture guided by risk analysis and threat profile0
ARCHITECTURE-1kARCHITECTURE-1k: Architecture supports predefined states of operation0
ARCHITECTURE-2aARCHITECTURE-2a: Network protections in place0
ARCHITECTURE-2bARCHITECTURE-2b: IT separated from OT0
ARCHITECTURE-2cARCHITECTURE-2c: Network protections per asset type by risk and priority0
ARCHITECTURE-2dARCHITECTURE-2d: Important assets segmented into security zones0
ARCHITECTURE-2eARCHITECTURE-2e: Least privilege and least functionality in network protections0
ARCHITECTURE-2fARCHITECTURE-2f: Traffic monitored, analysed and controlled for selected zones0
ARCHITECTURE-2gARCHITECTURE-2g: Web and email traffic monitored and controlled0
ARCHITECTURE-2hARCHITECTURE-2h: All assets segmented into security zones0
ARCHITECTURE-2iARCHITECTURE-2i: Separate networks with independent authentication where warranted0
ARCHITECTURE-2jARCHITECTURE-2j: OT can run through an IT outage0
ARCHITECTURE-2kARCHITECTURE-2k: Only authorised devices can connect0
ARCHITECTURE-2lARCHITECTURE-2l: Architecture allows isolation of compromised assets0
ARCHITECTURE-3aARCHITECTURE-3a: Access controls protecting important assets0
ARCHITECTURE-3bARCHITECTURE-3b: Endpoint protections for important assets0
ARCHITECTURE-3cARCHITECTURE-3c: Least privilege enforced on assets0
ARCHITECTURE-3dARCHITECTURE-3d: Least functionality enforced on assets0
ARCHITECTURE-3eARCHITECTURE-3e: Secure configuration at deployment0
ARCHITECTURE-3fARCHITECTURE-3f: Security applications required in device configuration0
ARCHITECTURE-3gARCHITECTURE-3g: Removable media controlled0
ARCHITECTURE-3hARCHITECTURE-3h: Controls on all assets or compensating controls0
ARCHITECTURE-3iARCHITECTURE-3i: Maintenance and capacity management for all assets0
ARCHITECTURE-3jARCHITECTURE-3j: Physical operating environment controlled0
ARCHITECTURE-3kARCHITECTURE-3k: More rigorous controls for higher priority assets0
ARCHITECTURE-3lARCHITECTURE-3l: Firmware configuration and changes controlled across the lifecycle0
ARCHITECTURE-3mARCHITECTURE-3m: Unauthorised code prevented from running0
ARCHITECTURE-4aARCHITECTURE-4a: Secure development for in-house software on higher priority assets0
ARCHITECTURE-4bARCHITECTURE-4b: Vendor secure development considered for higher priority assets0
ARCHITECTURE-4cARCHITECTURE-4c: Secure configuration required at software deployment0
ARCHITECTURE-4dARCHITECTURE-4d: Secure development for all in-house software0
ARCHITECTURE-4eARCHITECTURE-4e: Vendor secure development considered for all procured software0
ARCHITECTURE-4fARCHITECTURE-4f: Architecture review of new and revised applications0
ARCHITECTURE-4gARCHITECTURE-4g: Authenticity of software and firmware validated0
ARCHITECTURE-4hARCHITECTURE-4h: Security testing of in-house applications0
ARCHITECTURE-5aARCHITECTURE-5a: Sensitive data protected at rest0
ARCHITECTURE-5bARCHITECTURE-5b: All data at rest protected for selected categories0
ARCHITECTURE-5cARCHITECTURE-5c: All data in transit protected for selected categories0
ARCHITECTURE-5dARCHITECTURE-5d: Encryption controls for data at rest and in transit0
ARCHITECTURE-5eARCHITECTURE-5e: Key management infrastructure in place0
ARCHITECTURE-5fARCHITECTURE-5f: Controls restrict data exfiltration0
ARCHITECTURE-5gARCHITECTURE-5g: Protection for data on assets that may be lost or stolen0
ARCHITECTURE-5hARCHITECTURE-5h: Protection against unauthorised changes to software, firmware and data0
ARCHITECTURE-AP1ARCHITECTURE-AP1: Anti-pattern: operational assets can reach the internet directly0
ARCHITECTURE-AP2ARCHITECTURE-AP2: Anti-pattern: remote or third-party access bypasses network controls0
ARCHITECTURE-AP3ARCHITECTURE-AP3: Anti-pattern: critical assets cannot be isolated0
ASSET-1aASSET-1a: Important IT and OT assets inventoried0
ASSET-1bASSET-1b: Inventory includes assets a threat actor could leverage0
ASSET-1cASSET-1c: Inventoried assets prioritised by defined criteria0
ASSET-1dASSET-1d: Prioritisation considers leverage by threat actors0
ASSET-1eASSET-1e: Inventory holds attributes that support security work0
ASSET-1fASSET-1f: IT and OT inventory complete0
ASSET-1gASSET-1g: IT and OT inventory kept current0
ASSET-1hASSET-1h: Data removed from assets before redeployment and at end of life0
ASSET-2aASSET-2a: Important information assets inventoried0
ASSET-2bASSET-2b: Information inventory includes assets a threat actor could leverage0
ASSET-2cASSET-2c: Information assets categorised by defined criteria0
ASSET-2dASSET-2d: Information categorisation considers threat leverage0
ASSET-2eASSET-2e: Information inventory holds security attributes0
ASSET-2fASSET-2f: Information inventory complete0
ASSET-2gASSET-2g: Information inventory kept current0
ASSET-2hASSET-2h: Information sanitised or destroyed at end of life0
ASSET-3aASSET-3a: Configuration baselines established0
ASSET-3bASSET-3b: Baselines used at deployment and restoration0
ASSET-3cASSET-3c: Baselines incorporate architecture requirements0
ASSET-3dASSET-3d: Baselines reviewed periodically and on triggers0
ASSET-3eASSET-3e: Configurations monitored against baselines0
ASSET-4aASSET-4a: Changes evaluated and approved before implementation0
ASSET-4bASSET-4b: Changes documented0
ASSET-4cASSET-4c: Change documentation requirements defined0
ASSET-4dASSET-4d: Changes to higher priority assets tested before deployment0
ASSET-4eASSET-4e: Changes and updates made securely0
ASSET-4fASSET-4f: Ability to reverse changes for important assets0
ASSET-4gASSET-4g: Change management covers the full asset lifecycle0
ASSET-4hASSET-4h: Changes to higher priority assets tested for cybersecurity impact0
ASSET-4iASSET-4i: Change logs record effects on cybersecurity requirements0
ASSET-AP1ASSET-AP1: Anti-pattern: internet-facing changes not assessed for vulnerabilities0
ASSET-AP2ASSET-AP2: Anti-pattern: inventories not linked to data governance or impact assessment0
ASSET-AP3ASSET-AP3: Anti-pattern: inventories not updated in 24 months0
HOLDINGSOfficial text0
MILMaturity Indicator Levels and how maturity is scored0
PRIVACY-1APRIVACY-1A: Applicable privacy requirements identified0
PRIVACY-1BPRIVACY-1B: Personal information defined for the business0
PRIVACY-1CPRIVACY-1C: Point of contact for privacy issues0
PRIVACY-1DPRIVACY-1D: Activities handling personal information identified0
PRIVACY-1EPRIVACY-1E: Personal information holdings documented0
PRIVACY-1FPRIVACY-1F: Privacy policy documented and communicated0
PRIVACY-1GPRIVACY-1G: Handling requirements defined in the privacy policy0
PRIVACY-1HPRIVACY-1H: Privacy roles and accountabilities assigned0
PRIVACY-1IPRIVACY-1I: Privacy management plan implemented0
PRIVACY-1JPRIVACY-1J: Privacy risks recorded in a risk register0
PRIVACY-1KPRIVACY-1K: Process for privacy enquiries, complaints and corrections0
PRIVACY-1LPRIVACY-1L: Privacy training for staff handling personal information0
PRIVACY-1MPRIVACY-1M: Response plans cover personal information breaches0
PRIVACY-1NPRIVACY-1N: Data breach plans tested and improved0
PRIVACY-1OPRIVACY-1O: Privacy compliance assessed and reported to senior management0
PRIVACY-1PPRIVACY-1P: Privacy management plan updated for changing threats and regulation0
PRIVACY-AP1PRIVACY-AP1: Anti-pattern: unaware whether personal information is collected0
PROGRAM-1aPROGRAM-1a: A cybersecurity program strategy exists0
PROGRAM-1bPROGRAM-1b: Strategy sets goals and objectives for cybersecurity activities0
PROGRAM-1cPROGRAM-1c: Strategy documented and aligned with mission, objectives and critical infrastructure risk0
PROGRAM-1dPROGRAM-1d: Strategy defines oversight and governance0
PROGRAM-1ePROGRAM-1e: Strategy defines the program's structure0
PROGRAM-1fPROGRAM-1f: Strategy names the standards and guidelines to follow0
PROGRAM-1gPROGRAM-1g: Strategy identifies compliance requirements0
PROGRAM-1hPROGRAM-1h: Strategy updated periodically and on triggers0
PROGRAM-2aPROGRAM-2a: Senior management supports the program0
PROGRAM-2bPROGRAM-2b: Program established according to the strategy0
PROGRAM-2cPROGRAM-2c: Visible, active senior sponsorship of the program0
PROGRAM-2dPROGRAM-2d: Senior sponsorship of cybersecurity policies0
PROGRAM-2ePROGRAM-2e: Program responsibility assigned to a role with authority0
PROGRAM-2fPROGRAM-2f: Program stakeholders identified and involved0
PROGRAM-2gPROGRAM-2g: Program activities reviewed against the strategy0
PROGRAM-2hPROGRAM-2h: Independent review of conformance with policies0
PROGRAM-2iPROGRAM-2i: Program enables legal and regulatory compliance0
PROGRAM-2jPROGRAM-2j: Collaboration on standards, practices and emerging technology0
REGULATORYRegulatory use: SOCI Act risk management programs and the National Electricity Rules0
RESPONSE-1aRESPONSE-1a: Detected events reported to a named role and recorded0
RESPONSE-1bRESPONSE-1b: Event detection criteria defined0
RESPONSE-1cRESPONSE-1c: Events documented against the criteria0
RESPONSE-1dRESPONSE-1d: Event information correlated for patterns0
RESPONSE-1eRESPONSE-1e: Detection tuned to risks and threat profile0
RESPONSE-1fRESPONSE-1f: Situational awareness monitored to identify events0
RESPONSE-2aRESPONSE-2a: Incident declaration criteria set0
RESPONSE-2bRESPONSE-2b: Events analysed to support declaration0
RESPONSE-2cRESPONSE-2c: Declaration criteria formally based on impact to the function0
RESPONSE-2dRESPONSE-2d: Events declared incidents according to the criteria0
RESPONSE-2eRESPONSE-2e: Declaration criteria updated periodically and on triggers0
RESPONSE-2fRESPONSE-2f: Repository tracks events and incidents to closure0
RESPONSE-2gRESPONSE-2g: Stakeholders identified and notified of incidents0
RESPONSE-2hRESPONSE-2h: Declaration criteria aligned with risk prioritisation0
RESPONSE-2iRESPONSE-2i: Incidents correlated across multiple incidents0
RESPONSE-3aRESPONSE-3a: Response personnel identified and roles assigned0
RESPONSE-3bRESPONSE-3b: Incident responses executed to limit impact and restore operations0
RESPONSE-3cRESPONSE-3c: Incidents reported internally and externally0
RESPONSE-3dRESPONSE-3d: Incident response plans cover the whole lifecycle0
RESPONSE-3eRESPONSE-3e: Response follows defined plans and procedures0
RESPONSE-3fRESPONSE-3f: Response plans include a stakeholder communications plan0
RESPONSE-3gRESPONSE-3g: Response plan exercises held periodically and on triggers0
RESPONSE-3hRESPONSE-3h: Lessons learned captured and acted on0
RESPONSE-3iRESPONSE-3i: Root-cause analysis performed and acted on0
RESPONSE-3jRESPONSE-3j: Response coordinated with external entities including evidence handling0
RESPONSE-3kRESPONSE-3k: Responders take part in joint exercises with other organisations0
RESPONSE-3lRESPONSE-3l: Responses use and trigger predefined states of operation0
RESPONSE-4aRESPONSE-4a: Continuity plans to sustain and restore the function0
RESPONSE-4bRESPONSE-4b: Backups available and tested0
RESPONSE-4cRESPONSE-4c: Assets needing spares identified0
RESPONSE-4dRESPONSE-4d: Continuity plans address cyber incident impacts0
RESPONSE-4eRESPONSE-4e: Assets and activities for minimum operations documented0
RESPONSE-4fRESPONSE-4f: Plans cover important assets, backups and spares0
RESPONSE-4gRESPONSE-4g: RTOs and RPOs in continuity plans0
RESPONSE-4hRESPONSE-4h: Incident criteria triggering continuity plans set and communicated0
RESPONSE-4iRESPONSE-4i: Continuity plans tested periodically and on triggers0
RESPONSE-4jRESPONSE-4j: Backup controls at least as strong as source0
RESPONSE-4kRESPONSE-4k: Backups separated from source data0
RESPONSE-4lRESPONSE-4l: Spares available for selected assets0
RESPONSE-4mRESPONSE-4m: Continuity plans aligned with risks and threat profile0
RESPONSE-4nRESPONSE-4n: Continuity exercises address higher priority risks0
RESPONSE-4oRESPONSE-4o: Test and activation results compared with recovery objectives0
RESPONSE-4pRESPONSE-4p: Continuity plans reviewed and updated periodically0
RESPONSE-AP1RESPONSE-AP1: Anti-pattern: critical functions not identified0
RESPONSE-AP2RESPONSE-AP2: Anti-pattern: services and assets supporting critical functions not identified0
RESPONSE-AP3RESPONSE-AP3: Anti-pattern: responders do not know which authorities to contact0
RISK-1aRISK-1a: A cyber risk management strategy exists0
RISK-1bRISK-1b: Risk strategy aligned with program strategy and enterprise architecture0
RISK-1cRISK-1c: Risk management program operates per the strategy0
RISK-1dRISK-1d: Risk information communicated to stakeholders0
RISK-1eRISK-1e: Risk program governance in place0
RISK-1fRISK-1f: Visible senior sponsorship of risk program0
RISK-1gRISK-1g: Risk program aligned with mission and objectives0
RISK-1hRISK-1h: Cyber risk coordinated with enterprise risk management0
RISK-2aRISK-2a: Cyber risks identified0
RISK-2bRISK-2b: Defined method used to identify risks0
RISK-2cRISK-2c: Operations and business stakeholders take part in risk identification0
RISK-2dRISK-2d: Risks consolidated into categories0
RISK-2eRISK-2e: Risks recorded in a register0
RISK-2fRISK-2f: Risks assigned to owners0
RISK-2gRISK-2g: Risk identification repeated periodically and on triggers0
RISK-2hRISK-2h: Risk identification uses asset inventory and priority data0
RISK-2iRISK-2i: Vulnerability information updates risks0
RISK-2jRISK-2j: Threat information updates risks0
RISK-2kRISK-2k: Third-party information updates risks0
RISK-2lRISK-2l: Architecture gaps update risks0
RISK-2mRISK-2m: Risks from and to critical infrastructure and interdependencies considered0
RISK-3aRISK-3a: Risks prioritised by estimated impact0
RISK-3bRISK-3b: Defined criteria used to prioritise risks0
RISK-3cRISK-3c: Defined method estimates impact of higher priority risks0
RISK-3dRISK-3d: Defined methods analyse higher priority risks0
RISK-3eRISK-3e: Stakeholders take part in analysing higher priority risks0
RISK-3fRISK-3f: Risks removed from register when no longer needed0
RISK-3gRISK-3g: Risk analyses updated periodically and on triggers0
RISK-4aRISK-4a: Risk responses implemented0
RISK-4bRISK-4b: Defined method selects and implements responses0
RISK-4cRISK-4c: Controls evaluated for design and operation0
RISK-4dRISK-4d: Leadership reviews impact analyses with control evaluations0
RISK-4eRISK-4e: Leadership periodically reviews risk responses0
RISK-AP1RISK-AP1: Anti-pattern: identified risks not periodically reviewed0
RISK-AP2RISK-AP2: Anti-pattern: risks left untreated for long periods0
RISK-AP3RISK-AP3: Anti-pattern: assets risk-assessed in isolation0
RISK-AP4RISK-AP4: Anti-pattern: risk activities not guided by risk criteria0
SCOPEWho assesses, what is in scope and the Lite framework0
SITUATION-1aSITUATION-1a: Logging on important assets0
SITUATION-1bSITUATION-1b: Logging on assets a threat actor could leverage0
SITUATION-1cSITUATION-1c: Logging requirements set for important and leverageable assets0
SITUATION-1dSITUATION-1d: Logging requirements set for monitoring infrastructure0
SITUATION-1eSITUATION-1e: Log data aggregated0
SITUATION-1fSITUATION-1f: More rigorous logging for higher priority assets0
SITUATION-2aSITUATION-2a: Log data and monitoring reviewed periodically0
SITUATION-2bSITUATION-2b: Monitoring infrastructure data and alerts reviewed0
SITUATION-2cSITUATION-2c: Monitoring and analysis requirements set for timely review0
SITUATION-2dSITUATION-2d: Indicators of anomalous activity defined and monitored across IT and OT0
SITUATION-2eSITUATION-2e: Alarms and alerts configured for cybersecurity events0
SITUATION-2fSITUATION-2f: Monitoring aligned with the threat profile0
SITUATION-2gSITUATION-2g: More rigorous monitoring for higher priority assets0
SITUATION-2hSITUATION-2h: Risk analysis used to identify anomaly indicators0
SITUATION-2iSITUATION-2i: Indicators reviewed periodically and on triggers0
SITUATION-3aSITUATION-3a: Methods to communicate the current cybersecurity state0
SITUATION-3bSITUATION-3b: Monitoring data aggregated to show operational state0
SITUATION-3cSITUATION-3c: Information from across the organisation enhances awareness0
SITUATION-3dSITUATION-3d: Situational awareness reporting requirements defined0
SITUATION-3eSITUATION-3e: External information collected and shared internally0
SITUATION-3fSITUATION-3f: Near-real-time capability to aggregate, correlate and analyse monitoring0
SITUATION-3gSITUATION-3g: Predefined states of operation documented0
SITUATION-AP1SITUATION-AP1: Anti-pattern: operational assets monitored only for performance0
SITUATION-AP10SITUATION-AP10: Anti-pattern: logs of impacted assets cannot be inspected0
SITUATION-AP11SITUATION-AP11: Anti-pattern: IOCs cannot be added to monitoring of critical assets0
SITUATION-AP2SITUATION-AP2: Anti-pattern: logs monitored only during incidents0
SITUATION-AP3SITUATION-AP3: Anti-pattern: normal operation not baselined0
SITUATION-AP4SITUATION-AP4: Anti-pattern: alerts exclude security events0
SITUATION-AP5SITUATION-AP5: Anti-pattern: logs not time synchronised0
SITUATION-AP6SITUATION-AP6: Anti-pattern: critical asset logs stored only on the asset0
SITUATION-AP7SITUATION-AP7: Anti-pattern: unnecessary write access to central logs0
SITUATION-AP8SITUATION-AP8: Anti-pattern: third-party privileged access not logged0
SITUATION-AP9SITUATION-AP9: Anti-pattern: IOCs considered only during or after incidents0
SPSecurity Profiles, priority practices and target state0
STRUCTUREHow the AESCSF V2 Framework Core is built0
THIRD-PARTIES-1aTHIRD-PARTIES-1a: Important third-party dependencies identified0
THIRD-PARTIES-1bTHIRD-PARTIES-1b: Third parties with access, control or custody identified0
THIRD-PARTIES-1cTHIRD-PARTIES-1c: Defined method identifies third-party risks0
THIRD-PARTIES-1dTHIRD-PARTIES-1d: Third parties prioritised by established criteria0
THIRD-PARTIES-1eTHIRD-PARTIES-1e: Escalated priority for high-consequence third parties0
THIRD-PARTIES-1fTHIRD-PARTIES-1f: Third-party prioritisation updated periodically and on triggers0
THIRD-PARTIES-2aTHIRD-PARTIES-2a: Supplier selection considers cybersecurity qualifications0
THIRD-PARTIES-2bTHIRD-PARTIES-2b: Product and service selection considers security capabilities0
THIRD-PARTIES-2cTHIRD-PARTIES-2c: Defined method sets third-party security requirements and controls0
THIRD-PARTIES-2dTHIRD-PARTIES-2d: Defined method evaluates and selects third parties0
THIRD-PARTIES-2eTHIRD-PARTIES-2e: More rigorous controls for higher priority third parties0
THIRD-PARTIES-2fTHIRD-PARTIES-2f: Security requirements formalised in agreements0
THIRD-PARTIES-2gTHIRD-PARTIES-2g: Third parties periodically attest to requirements0
THIRD-PARTIES-2hTHIRD-PARTIES-2h: Secure development requirements for suppliers0
THIRD-PARTIES-2iTHIRD-PARTIES-2i: Product selection considers end of life and support0
THIRD-PARTIES-2jTHIRD-PARTIES-2j: Selection considers safeguards against counterfeit or compromised items0
THIRD-PARTIES-2kTHIRD-PARTIES-2k: Bills of material evaluated for higher priority assets0
THIRD-PARTIES-2lTHIRD-PARTIES-2l: Hosting environments and source data evaluated for higher priority assets0
THIRD-PARTIES-2mTHIRD-PARTIES-2m: Acceptance testing includes security requirements0
THREAT-1aTHREAT-1a: Vulnerability information sources identified0
THREAT-1bTHREAT-1b: Vulnerability information gathered and interpreted0
THREAT-1cTHREAT-1c: Vulnerability assessments performed0
THREAT-1dTHREAT-1d: Relevant vulnerabilities mitigated0
THREAT-1eTHREAT-1e: Sources covering higher priority assets monitored0
THREAT-1fTHREAT-1f: Vulnerability assessments periodic and triggered0
THREAT-1gTHREAT-1g: Vulnerabilities analysed, prioritised and addressed0
THREAT-1hTHREAT-1h: Operational impact evaluated before patching0
THREAT-1iTHREAT-1i: Vulnerability information shared with defined stakeholders0
THREAT-1jTHREAT-1j: Sources covering all IT and OT assets monitored0
THREAT-1kTHREAT-1k: Independent vulnerability assessments0
THREAT-1lTHREAT-1l: Vulnerability responses checked for effectiveness0
THREAT-1mTHREAT-1m: Mechanism to receive external vulnerability reports0
THREAT-2aTHREAT-2a: Threat information sources identified0
THREAT-2bTHREAT-2b: Threat information gathered and interpreted0
THREAT-2cTHREAT-2c: Threat objectives identified0
THREAT-2dTHREAT-2d: Relevant threats addressed0
THREAT-2eTHREAT-2e: Threat profile established0
THREAT-2fTHREAT-2f: Sources covering the whole threat profile prioritised and monitored0
THREAT-2gTHREAT-2g: Threats analysed, prioritised and addressed0
THREAT-2hTHREAT-2h: Threat information exchanged with stakeholders0
THREAT-2iTHREAT-2i: Threat profile updated periodically and on triggers0
THREAT-2jTHREAT-2j: Threat activities use and trigger predefined states of operation0
THREAT-2kTHREAT-2k: Secure near-real-time threat sharing methods0
THREAT-AP1THREAT-AP1: Anti-pattern: no compensating controls where remediation is blocked0
THREAT-AP2THREAT-AP2: Anti-pattern: internet-facing assets not periodically assessed0
THREAT-AP3THREAT-AP3: Anti-pattern: controls not updated for new high-priority threats0
VERSIONSVersions: V1 (2018, 282 items) and V2 (2023, 354 items)0
WORKFORCE-1aWORKFORCE-1a: Vetting at hire0
WORKFORCE-1bWORKFORCE-1b: Separation procedures address cybersecurity0
WORKFORCE-1cWORKFORCE-1c: Periodic vetting for positions with access to important assets0
WORKFORCE-1dWORKFORCE-1d: Separation and transfer procedures address cybersecurity with supplementary vetting0
WORKFORCE-1eWORKFORCE-1e: Personnel aware of protection and acceptable use responsibilities0
WORKFORCE-1fWORKFORCE-1f: Vetting for all positions by position risk0
WORKFORCE-1gWORKFORCE-1g: Formal accountability and disciplinary process0
WORKFORCE-2aWORKFORCE-2a: Awareness activities occur0
WORKFORCE-2bWORKFORCE-2b: Awareness objectives set0
WORKFORCE-2cWORKFORCE-2c: Awareness objectives aligned with the threat profile0
WORKFORCE-2dWORKFORCE-2d: Awareness activities periodic0
WORKFORCE-2eWORKFORCE-2e: Awareness tailored to job role0
WORKFORCE-2fWORKFORCE-2f: Awareness covers predefined states of operation0
WORKFORCE-2gWORKFORCE-2g: Awareness effectiveness evaluated and improved0
WORKFORCE-3aWORKFORCE-3a: Cybersecurity responsibilities identified0
WORKFORCE-3bWORKFORCE-3b: Responsibilities assigned to specific people0
WORKFORCE-3cWORKFORCE-3c: Responsibilities assigned to roles including service providers0
WORKFORCE-3dWORKFORCE-3d: Responsibilities documented0
WORKFORCE-3eWORKFORCE-3e: Responsibilities reviewed periodically and on triggers0
WORKFORCE-3fWORKFORCE-3f: Coverage, redundancy and succession managed0
WORKFORCE-4aWORKFORCE-4a: Training available for people with cybersecurity responsibilities0
WORKFORCE-4bWORKFORCE-4b: Knowledge, skill and ability gaps identified0
WORKFORCE-4cWORKFORCE-4c: Gaps addressed by training, recruiting and retention0
WORKFORCE-4dWORKFORCE-4d: Training required before access to important assets0
WORKFORCE-4eWORKFORCE-4e: Training effectiveness evaluated and improved0
WORKFORCE-4fWORKFORCE-4f: Continuing education for significant cybersecurity roles0
WORKFORCE-AP1WORKFORCE-AP1: Anti-pattern: capability depends on one or two people with no succession0
WORKFORCE-AP2WORKFORCE-AP2: Anti-pattern: people working with critical assets lack added responsibilities0
WORKFORCE-AP3WORKFORCE-AP3: Anti-pattern: people unaware of their added responsibilities0

Tell me when Australian Energy Sector Cyber Security Framework (AESCSF) files something new

One email when a public company newly discloses something this framework governs, naming the company and what our corpus says it puts in scope. Nothing else, and one click to stop.

What an auditor will ask you to produce

The artefacts named on the failure modes this framework speaks to.

  • Role inventory + RACI
  • Metrics + management review
  • Annual cycle documentation
  • Supervisory dialogue records
  • Role inventory + RACI + DPO designation
  • Operational controls + tooling investment
  • security charter
  • board reporting pack
  • risk register
  • policy library

How programmes fail on this

Failure modes named by this framework and others. Each opens the full record.

What this page is

A control-level reference for Australian Energy Sector Cyber Security Framework (AESCSF), drawn from our framework corpus. Control codes and titles are references to the standard, not reproductions of it. The overlap counts and the auditor artefacts are our own work and are the part you will not find elsewhere.

Measure this against what you already run · All frameworks · Today's edition