AESCSF-ACM-1 | Asset inventory | 2 |
AESCSF-ACM-2 | Configuration management | 4 |
AESCSF-ACM-3 | Change management | 5 |
AESCSF-APM-1 | Australian privacy management | 1 |
AESCSF-APM-2 | Privacy breach management | 1 |
AESCSF-CPM-1 | Cyber security program management | 1 |
AESCSF-CPM-2 | Cyber security governance and strategy | 1 |
AESCSF-CPM-3 | Cyber security architecture | 0 |
AESCSF-EDM-1 | Supply chain risk management | 1 |
AESCSF-EDM-2 | External dependency assessment | 0 |
AESCSF-EDM-3 | Dependency resilience | 0 |
AESCSF-IAM-1 | Identity management | 3 |
AESCSF-IAM-2 | Access control | 5 |
AESCSF-IAM-3 | Multi-factor authentication | 2 |
AESCSF-IR-1 | Incident response plan | 1 |
AESCSF-IR-2 | Incident detection and handling | 0 |
AESCSF-IR-3 | Continuity of operations and recovery | 1 |
AESCSF-IR-4 | Incident reporting | 1 |
AESCSF-ISC-1 | Cyber security information sharing | 1 |
AESCSF-ISC-2 | Stakeholder communications | 0 |
AESCSF-RM-1 | Establish cyber security risk management strategy | 1 |
AESCSF-RM-2 | Identify and assess cyber risks | 2 |
AESCSF-RM-3 | Manage and treat cyber risks | 0 |
AESCSF-SA-1 | Logging and monitoring | 5 |
AESCSF-SA-2 | Anomaly and event detection | 1 |
AESCSF-SA-3 | Common operating picture | 0 |
AESCSF-TVM-1 | Vulnerability management | 2 |
AESCSF-TVM-2 | Threat management | 1 |
AESCSF-TVM-3 | Patch and remediation management | 2 |
AESCSF-WM-1 | Cyber security workforce management | 0 |
AESCSF-WM-2 | Training and awareness | 3 |
AESCSF-WM-3 | Personnel security | 0 |
ACCESS-1a | ACCESS-1a: Identities created for people, services and devices needing access | 0 |
ACCESS-1b | ACCESS-1b: Credentials issued to those needing access | 0 |
ACCESS-1c | ACCESS-1c: Identities removed when no longer needed | 0 |
ACCESS-1d | ACCESS-1d: Password strength and reuse rules set and enforced | 0 |
ACCESS-1e | ACCESS-1e: Identity repositories reviewed on a schedule and on triggers | 0 |
ACCESS-1f | ACCESS-1f: Deprovisioning within defined time limits | 0 |
ACCESS-1g | ACCESS-1g: Privileged credentials used only where needed | 0 |
ACCESS-1h | ACCESS-1h: Stronger authentication for higher risk access | 0 |
ACCESS-1i | ACCESS-1i: Multifactor authentication for all access where feasible | 0 |
ACCESS-1j | ACCESS-1j: Inactive identities disabled after a set period | 0 |
ACCESS-2a | ACCESS-2a: Logical access controls in place | 0 |
ACCESS-2b | ACCESS-2b: Logical access revoked when no longer needed | 0 |
ACCESS-2c | ACCESS-2c: Logical access requirements defined and maintained | 0 |
ACCESS-2d | ACCESS-2d: Least privilege built into logical access rules | 0 |
ACCESS-2e | ACCESS-2e: Separation of duties built into logical access rules | 0 |
ACCESS-2f | ACCESS-2f: Asset owners approve logical access requests | 0 |
ACCESS-2g | ACCESS-2g: Extra scrutiny and monitoring for higher risk logical access | 0 |
ACCESS-2h | ACCESS-2h: Logical access reviewed on schedule, triggers and after elevation | 0 |
ACCESS-2i | ACCESS-2i: Anomalous logical access attempts monitored | 0 |
ACCESS-3a | ACCESS-3a: Physical access controls in place | 0 |
ACCESS-3b | ACCESS-3b: Physical access revoked when no longer needed | 0 |
ACCESS-3c | ACCESS-3c: Physical access logs kept | 0 |
ACCESS-3d | ACCESS-3d: Physical access requirements defined and maintained | 0 |
ACCESS-3e | ACCESS-3e: Least privilege applied to physical access | 0 |
ACCESS-3f | ACCESS-3f: Separation of duties applied to physical access | 0 |
ACCESS-3g | ACCESS-3g: Asset owners approve physical access requests | 0 |
ACCESS-3h | ACCESS-3h: Extra scrutiny and monitoring for higher risk physical access | 0 |
ACCESS-3i | ACCESS-3i: Physical access privileges reviewed and updated | 0 |
ACCESS-3j | ACCESS-3j: Physical access monitored for cybersecurity events | 0 |
ACCESS-AP1 | ACCESS-AP1: Anti-pattern: access provisioned before need is confirmed | 0 |
ACCESS-AP10 | ACCESS-AP10: Anti-pattern: access reviews do not test continued need | 0 |
ACCESS-AP11 | ACCESS-AP11: Anti-pattern: no policy ban on unauthorised devices reaching critical assets | 0 |
ACCESS-AP2 | ACCESS-AP2: Anti-pattern: no complete register of privileged users | 0 |
ACCESS-AP3 | ACCESS-AP3: Anti-pattern: deprovisioning ignores risk criteria | 0 |
ACCESS-AP4 | ACCESS-AP4: Anti-pattern: single-factor access to non-public internet-facing assets | 0 |
ACCESS-AP5 | ACCESS-AP5: Anti-pattern: privileged access granted by default | 0 |
ACCESS-AP6 | ACCESS-AP6: Anti-pattern: access that breaches segregation of duties | 0 |
ACCESS-AP7 | ACCESS-AP7: Anti-pattern: users not individually attributable | 0 |
ACCESS-AP8 | ACCESS-AP8: Anti-pattern: unusual access not monitored | 0 |
ACCESS-AP9 | ACCESS-AP9: Anti-pattern: unknown users or devices can connect to known assets | 0 |
ARCHITECTURE-1a | ARCHITECTURE-1a: A cybersecurity architecture strategy exists | 0 |
ARCHITECTURE-1b | ARCHITECTURE-1b: Architecture strategy aligned with the program strategy and enterprise architecture | 0 |
ARCHITECTURE-1c | ARCHITECTURE-1c: Documented architecture covering IT and OT | 0 |
ARCHITECTURE-1d | ARCHITECTURE-1d: Architecture governance with periodic reviews and exceptions | 0 |
ARCHITECTURE-1e | ARCHITECTURE-1e: Visible senior sponsorship for the architecture program | 0 |
ARCHITECTURE-1f | ARCHITECTURE-1f: Architecture sets cybersecurity requirements for assets | 0 |
ARCHITECTURE-1g | ARCHITECTURE-1g: Controls chosen and implemented to meet requirements | 0 |
ARCHITECTURE-1h | ARCHITECTURE-1h: Security architecture aligned with enterprise architecture | 0 |
ARCHITECTURE-1i | ARCHITECTURE-1i: Conformance to the architecture evaluated periodically and on triggers | 0 |
ARCHITECTURE-1j | ARCHITECTURE-1j: Architecture guided by risk analysis and threat profile | 0 |
ARCHITECTURE-1k | ARCHITECTURE-1k: Architecture supports predefined states of operation | 0 |
ARCHITECTURE-2a | ARCHITECTURE-2a: Network protections in place | 0 |
ARCHITECTURE-2b | ARCHITECTURE-2b: IT separated from OT | 0 |
ARCHITECTURE-2c | ARCHITECTURE-2c: Network protections per asset type by risk and priority | 0 |
ARCHITECTURE-2d | ARCHITECTURE-2d: Important assets segmented into security zones | 0 |
ARCHITECTURE-2e | ARCHITECTURE-2e: Least privilege and least functionality in network protections | 0 |
ARCHITECTURE-2f | ARCHITECTURE-2f: Traffic monitored, analysed and controlled for selected zones | 0 |
ARCHITECTURE-2g | ARCHITECTURE-2g: Web and email traffic monitored and controlled | 0 |
ARCHITECTURE-2h | ARCHITECTURE-2h: All assets segmented into security zones | 0 |
ARCHITECTURE-2i | ARCHITECTURE-2i: Separate networks with independent authentication where warranted | 0 |
ARCHITECTURE-2j | ARCHITECTURE-2j: OT can run through an IT outage | 0 |
ARCHITECTURE-2k | ARCHITECTURE-2k: Only authorised devices can connect | 0 |
ARCHITECTURE-2l | ARCHITECTURE-2l: Architecture allows isolation of compromised assets | 0 |
ARCHITECTURE-3a | ARCHITECTURE-3a: Access controls protecting important assets | 0 |
ARCHITECTURE-3b | ARCHITECTURE-3b: Endpoint protections for important assets | 0 |
ARCHITECTURE-3c | ARCHITECTURE-3c: Least privilege enforced on assets | 0 |
ARCHITECTURE-3d | ARCHITECTURE-3d: Least functionality enforced on assets | 0 |
ARCHITECTURE-3e | ARCHITECTURE-3e: Secure configuration at deployment | 0 |
ARCHITECTURE-3f | ARCHITECTURE-3f: Security applications required in device configuration | 0 |
ARCHITECTURE-3g | ARCHITECTURE-3g: Removable media controlled | 0 |
ARCHITECTURE-3h | ARCHITECTURE-3h: Controls on all assets or compensating controls | 0 |
ARCHITECTURE-3i | ARCHITECTURE-3i: Maintenance and capacity management for all assets | 0 |
ARCHITECTURE-3j | ARCHITECTURE-3j: Physical operating environment controlled | 0 |
ARCHITECTURE-3k | ARCHITECTURE-3k: More rigorous controls for higher priority assets | 0 |
ARCHITECTURE-3l | ARCHITECTURE-3l: Firmware configuration and changes controlled across the lifecycle | 0 |
ARCHITECTURE-3m | ARCHITECTURE-3m: Unauthorised code prevented from running | 0 |
ARCHITECTURE-4a | ARCHITECTURE-4a: Secure development for in-house software on higher priority assets | 0 |
ARCHITECTURE-4b | ARCHITECTURE-4b: Vendor secure development considered for higher priority assets | 0 |
ARCHITECTURE-4c | ARCHITECTURE-4c: Secure configuration required at software deployment | 0 |
ARCHITECTURE-4d | ARCHITECTURE-4d: Secure development for all in-house software | 0 |
ARCHITECTURE-4e | ARCHITECTURE-4e: Vendor secure development considered for all procured software | 0 |
ARCHITECTURE-4f | ARCHITECTURE-4f: Architecture review of new and revised applications | 0 |
ARCHITECTURE-4g | ARCHITECTURE-4g: Authenticity of software and firmware validated | 0 |
ARCHITECTURE-4h | ARCHITECTURE-4h: Security testing of in-house applications | 0 |
ARCHITECTURE-5a | ARCHITECTURE-5a: Sensitive data protected at rest | 0 |
ARCHITECTURE-5b | ARCHITECTURE-5b: All data at rest protected for selected categories | 0 |
ARCHITECTURE-5c | ARCHITECTURE-5c: All data in transit protected for selected categories | 0 |
ARCHITECTURE-5d | ARCHITECTURE-5d: Encryption controls for data at rest and in transit | 0 |
ARCHITECTURE-5e | ARCHITECTURE-5e: Key management infrastructure in place | 0 |
ARCHITECTURE-5f | ARCHITECTURE-5f: Controls restrict data exfiltration | 0 |
ARCHITECTURE-5g | ARCHITECTURE-5g: Protection for data on assets that may be lost or stolen | 0 |
ARCHITECTURE-5h | ARCHITECTURE-5h: Protection against unauthorised changes to software, firmware and data | 0 |
ARCHITECTURE-AP1 | ARCHITECTURE-AP1: Anti-pattern: operational assets can reach the internet directly | 0 |
ARCHITECTURE-AP2 | ARCHITECTURE-AP2: Anti-pattern: remote or third-party access bypasses network controls | 0 |
ARCHITECTURE-AP3 | ARCHITECTURE-AP3: Anti-pattern: critical assets cannot be isolated | 0 |
ASSET-1a | ASSET-1a: Important IT and OT assets inventoried | 0 |
ASSET-1b | ASSET-1b: Inventory includes assets a threat actor could leverage | 0 |
ASSET-1c | ASSET-1c: Inventoried assets prioritised by defined criteria | 0 |
ASSET-1d | ASSET-1d: Prioritisation considers leverage by threat actors | 0 |
ASSET-1e | ASSET-1e: Inventory holds attributes that support security work | 0 |
ASSET-1f | ASSET-1f: IT and OT inventory complete | 0 |
ASSET-1g | ASSET-1g: IT and OT inventory kept current | 0 |
ASSET-1h | ASSET-1h: Data removed from assets before redeployment and at end of life | 0 |
ASSET-2a | ASSET-2a: Important information assets inventoried | 0 |
ASSET-2b | ASSET-2b: Information inventory includes assets a threat actor could leverage | 0 |
ASSET-2c | ASSET-2c: Information assets categorised by defined criteria | 0 |
ASSET-2d | ASSET-2d: Information categorisation considers threat leverage | 0 |
ASSET-2e | ASSET-2e: Information inventory holds security attributes | 0 |
ASSET-2f | ASSET-2f: Information inventory complete | 0 |
ASSET-2g | ASSET-2g: Information inventory kept current | 0 |
ASSET-2h | ASSET-2h: Information sanitised or destroyed at end of life | 0 |
ASSET-3a | ASSET-3a: Configuration baselines established | 0 |
ASSET-3b | ASSET-3b: Baselines used at deployment and restoration | 0 |
ASSET-3c | ASSET-3c: Baselines incorporate architecture requirements | 0 |
ASSET-3d | ASSET-3d: Baselines reviewed periodically and on triggers | 0 |
ASSET-3e | ASSET-3e: Configurations monitored against baselines | 0 |
ASSET-4a | ASSET-4a: Changes evaluated and approved before implementation | 0 |
ASSET-4b | ASSET-4b: Changes documented | 0 |
ASSET-4c | ASSET-4c: Change documentation requirements defined | 0 |
ASSET-4d | ASSET-4d: Changes to higher priority assets tested before deployment | 0 |
ASSET-4e | ASSET-4e: Changes and updates made securely | 0 |
ASSET-4f | ASSET-4f: Ability to reverse changes for important assets | 0 |
ASSET-4g | ASSET-4g: Change management covers the full asset lifecycle | 0 |
ASSET-4h | ASSET-4h: Changes to higher priority assets tested for cybersecurity impact | 0 |
ASSET-4i | ASSET-4i: Change logs record effects on cybersecurity requirements | 0 |
ASSET-AP1 | ASSET-AP1: Anti-pattern: internet-facing changes not assessed for vulnerabilities | 0 |
ASSET-AP2 | ASSET-AP2: Anti-pattern: inventories not linked to data governance or impact assessment | 0 |
ASSET-AP3 | ASSET-AP3: Anti-pattern: inventories not updated in 24 months | 0 |
HOLDINGS | Official text | 0 |
MIL | Maturity Indicator Levels and how maturity is scored | 0 |
PRIVACY-1A | PRIVACY-1A: Applicable privacy requirements identified | 0 |
PRIVACY-1B | PRIVACY-1B: Personal information defined for the business | 0 |
PRIVACY-1C | PRIVACY-1C: Point of contact for privacy issues | 0 |
PRIVACY-1D | PRIVACY-1D: Activities handling personal information identified | 0 |
PRIVACY-1E | PRIVACY-1E: Personal information holdings documented | 0 |
PRIVACY-1F | PRIVACY-1F: Privacy policy documented and communicated | 0 |
PRIVACY-1G | PRIVACY-1G: Handling requirements defined in the privacy policy | 0 |
PRIVACY-1H | PRIVACY-1H: Privacy roles and accountabilities assigned | 0 |
PRIVACY-1I | PRIVACY-1I: Privacy management plan implemented | 0 |
PRIVACY-1J | PRIVACY-1J: Privacy risks recorded in a risk register | 0 |
PRIVACY-1K | PRIVACY-1K: Process for privacy enquiries, complaints and corrections | 0 |
PRIVACY-1L | PRIVACY-1L: Privacy training for staff handling personal information | 0 |
PRIVACY-1M | PRIVACY-1M: Response plans cover personal information breaches | 0 |
PRIVACY-1N | PRIVACY-1N: Data breach plans tested and improved | 0 |
PRIVACY-1O | PRIVACY-1O: Privacy compliance assessed and reported to senior management | 0 |
PRIVACY-1P | PRIVACY-1P: Privacy management plan updated for changing threats and regulation | 0 |
PRIVACY-AP1 | PRIVACY-AP1: Anti-pattern: unaware whether personal information is collected | 0 |
PROGRAM-1a | PROGRAM-1a: A cybersecurity program strategy exists | 0 |
PROGRAM-1b | PROGRAM-1b: Strategy sets goals and objectives for cybersecurity activities | 0 |
PROGRAM-1c | PROGRAM-1c: Strategy documented and aligned with mission, objectives and critical infrastructure risk | 0 |
PROGRAM-1d | PROGRAM-1d: Strategy defines oversight and governance | 0 |
PROGRAM-1e | PROGRAM-1e: Strategy defines the program's structure | 0 |
PROGRAM-1f | PROGRAM-1f: Strategy names the standards and guidelines to follow | 0 |
PROGRAM-1g | PROGRAM-1g: Strategy identifies compliance requirements | 0 |
PROGRAM-1h | PROGRAM-1h: Strategy updated periodically and on triggers | 0 |
PROGRAM-2a | PROGRAM-2a: Senior management supports the program | 0 |
PROGRAM-2b | PROGRAM-2b: Program established according to the strategy | 0 |
PROGRAM-2c | PROGRAM-2c: Visible, active senior sponsorship of the program | 0 |
PROGRAM-2d | PROGRAM-2d: Senior sponsorship of cybersecurity policies | 0 |
PROGRAM-2e | PROGRAM-2e: Program responsibility assigned to a role with authority | 0 |
PROGRAM-2f | PROGRAM-2f: Program stakeholders identified and involved | 0 |
PROGRAM-2g | PROGRAM-2g: Program activities reviewed against the strategy | 0 |
PROGRAM-2h | PROGRAM-2h: Independent review of conformance with policies | 0 |
PROGRAM-2i | PROGRAM-2i: Program enables legal and regulatory compliance | 0 |
PROGRAM-2j | PROGRAM-2j: Collaboration on standards, practices and emerging technology | 0 |
REGULATORY | Regulatory use: SOCI Act risk management programs and the National Electricity Rules | 0 |
RESPONSE-1a | RESPONSE-1a: Detected events reported to a named role and recorded | 0 |
RESPONSE-1b | RESPONSE-1b: Event detection criteria defined | 0 |
RESPONSE-1c | RESPONSE-1c: Events documented against the criteria | 0 |
RESPONSE-1d | RESPONSE-1d: Event information correlated for patterns | 0 |
RESPONSE-1e | RESPONSE-1e: Detection tuned to risks and threat profile | 0 |
RESPONSE-1f | RESPONSE-1f: Situational awareness monitored to identify events | 0 |
RESPONSE-2a | RESPONSE-2a: Incident declaration criteria set | 0 |
RESPONSE-2b | RESPONSE-2b: Events analysed to support declaration | 0 |
RESPONSE-2c | RESPONSE-2c: Declaration criteria formally based on impact to the function | 0 |
RESPONSE-2d | RESPONSE-2d: Events declared incidents according to the criteria | 0 |
RESPONSE-2e | RESPONSE-2e: Declaration criteria updated periodically and on triggers | 0 |
RESPONSE-2f | RESPONSE-2f: Repository tracks events and incidents to closure | 0 |
RESPONSE-2g | RESPONSE-2g: Stakeholders identified and notified of incidents | 0 |
RESPONSE-2h | RESPONSE-2h: Declaration criteria aligned with risk prioritisation | 0 |
RESPONSE-2i | RESPONSE-2i: Incidents correlated across multiple incidents | 0 |
RESPONSE-3a | RESPONSE-3a: Response personnel identified and roles assigned | 0 |
RESPONSE-3b | RESPONSE-3b: Incident responses executed to limit impact and restore operations | 0 |
RESPONSE-3c | RESPONSE-3c: Incidents reported internally and externally | 0 |
RESPONSE-3d | RESPONSE-3d: Incident response plans cover the whole lifecycle | 0 |
RESPONSE-3e | RESPONSE-3e: Response follows defined plans and procedures | 0 |
RESPONSE-3f | RESPONSE-3f: Response plans include a stakeholder communications plan | 0 |
RESPONSE-3g | RESPONSE-3g: Response plan exercises held periodically and on triggers | 0 |
RESPONSE-3h | RESPONSE-3h: Lessons learned captured and acted on | 0 |
RESPONSE-3i | RESPONSE-3i: Root-cause analysis performed and acted on | 0 |
RESPONSE-3j | RESPONSE-3j: Response coordinated with external entities including evidence handling | 0 |
RESPONSE-3k | RESPONSE-3k: Responders take part in joint exercises with other organisations | 0 |
RESPONSE-3l | RESPONSE-3l: Responses use and trigger predefined states of operation | 0 |
RESPONSE-4a | RESPONSE-4a: Continuity plans to sustain and restore the function | 0 |
RESPONSE-4b | RESPONSE-4b: Backups available and tested | 0 |
RESPONSE-4c | RESPONSE-4c: Assets needing spares identified | 0 |
RESPONSE-4d | RESPONSE-4d: Continuity plans address cyber incident impacts | 0 |
RESPONSE-4e | RESPONSE-4e: Assets and activities for minimum operations documented | 0 |
RESPONSE-4f | RESPONSE-4f: Plans cover important assets, backups and spares | 0 |
RESPONSE-4g | RESPONSE-4g: RTOs and RPOs in continuity plans | 0 |
RESPONSE-4h | RESPONSE-4h: Incident criteria triggering continuity plans set and communicated | 0 |
RESPONSE-4i | RESPONSE-4i: Continuity plans tested periodically and on triggers | 0 |
RESPONSE-4j | RESPONSE-4j: Backup controls at least as strong as source | 0 |
RESPONSE-4k | RESPONSE-4k: Backups separated from source data | 0 |
RESPONSE-4l | RESPONSE-4l: Spares available for selected assets | 0 |
RESPONSE-4m | RESPONSE-4m: Continuity plans aligned with risks and threat profile | 0 |
RESPONSE-4n | RESPONSE-4n: Continuity exercises address higher priority risks | 0 |
RESPONSE-4o | RESPONSE-4o: Test and activation results compared with recovery objectives | 0 |
RESPONSE-4p | RESPONSE-4p: Continuity plans reviewed and updated periodically | 0 |
RESPONSE-AP1 | RESPONSE-AP1: Anti-pattern: critical functions not identified | 0 |
RESPONSE-AP2 | RESPONSE-AP2: Anti-pattern: services and assets supporting critical functions not identified | 0 |
RESPONSE-AP3 | RESPONSE-AP3: Anti-pattern: responders do not know which authorities to contact | 0 |
RISK-1a | RISK-1a: A cyber risk management strategy exists | 0 |
RISK-1b | RISK-1b: Risk strategy aligned with program strategy and enterprise architecture | 0 |
RISK-1c | RISK-1c: Risk management program operates per the strategy | 0 |
RISK-1d | RISK-1d: Risk information communicated to stakeholders | 0 |
RISK-1e | RISK-1e: Risk program governance in place | 0 |
RISK-1f | RISK-1f: Visible senior sponsorship of risk program | 0 |
RISK-1g | RISK-1g: Risk program aligned with mission and objectives | 0 |
RISK-1h | RISK-1h: Cyber risk coordinated with enterprise risk management | 0 |
RISK-2a | RISK-2a: Cyber risks identified | 0 |
RISK-2b | RISK-2b: Defined method used to identify risks | 0 |
RISK-2c | RISK-2c: Operations and business stakeholders take part in risk identification | 0 |
RISK-2d | RISK-2d: Risks consolidated into categories | 0 |
RISK-2e | RISK-2e: Risks recorded in a register | 0 |
RISK-2f | RISK-2f: Risks assigned to owners | 0 |
RISK-2g | RISK-2g: Risk identification repeated periodically and on triggers | 0 |
RISK-2h | RISK-2h: Risk identification uses asset inventory and priority data | 0 |
RISK-2i | RISK-2i: Vulnerability information updates risks | 0 |
RISK-2j | RISK-2j: Threat information updates risks | 0 |
RISK-2k | RISK-2k: Third-party information updates risks | 0 |
RISK-2l | RISK-2l: Architecture gaps update risks | 0 |
RISK-2m | RISK-2m: Risks from and to critical infrastructure and interdependencies considered | 0 |
RISK-3a | RISK-3a: Risks prioritised by estimated impact | 0 |
RISK-3b | RISK-3b: Defined criteria used to prioritise risks | 0 |
RISK-3c | RISK-3c: Defined method estimates impact of higher priority risks | 0 |
RISK-3d | RISK-3d: Defined methods analyse higher priority risks | 0 |
RISK-3e | RISK-3e: Stakeholders take part in analysing higher priority risks | 0 |
RISK-3f | RISK-3f: Risks removed from register when no longer needed | 0 |
RISK-3g | RISK-3g: Risk analyses updated periodically and on triggers | 0 |
RISK-4a | RISK-4a: Risk responses implemented | 0 |
RISK-4b | RISK-4b: Defined method selects and implements responses | 0 |
RISK-4c | RISK-4c: Controls evaluated for design and operation | 0 |
RISK-4d | RISK-4d: Leadership reviews impact analyses with control evaluations | 0 |
RISK-4e | RISK-4e: Leadership periodically reviews risk responses | 0 |
RISK-AP1 | RISK-AP1: Anti-pattern: identified risks not periodically reviewed | 0 |
RISK-AP2 | RISK-AP2: Anti-pattern: risks left untreated for long periods | 0 |
RISK-AP3 | RISK-AP3: Anti-pattern: assets risk-assessed in isolation | 0 |
RISK-AP4 | RISK-AP4: Anti-pattern: risk activities not guided by risk criteria | 0 |
SCOPE | Who assesses, what is in scope and the Lite framework | 0 |
SITUATION-1a | SITUATION-1a: Logging on important assets | 0 |
SITUATION-1b | SITUATION-1b: Logging on assets a threat actor could leverage | 0 |
SITUATION-1c | SITUATION-1c: Logging requirements set for important and leverageable assets | 0 |
SITUATION-1d | SITUATION-1d: Logging requirements set for monitoring infrastructure | 0 |
SITUATION-1e | SITUATION-1e: Log data aggregated | 0 |
SITUATION-1f | SITUATION-1f: More rigorous logging for higher priority assets | 0 |
SITUATION-2a | SITUATION-2a: Log data and monitoring reviewed periodically | 0 |
SITUATION-2b | SITUATION-2b: Monitoring infrastructure data and alerts reviewed | 0 |
SITUATION-2c | SITUATION-2c: Monitoring and analysis requirements set for timely review | 0 |
SITUATION-2d | SITUATION-2d: Indicators of anomalous activity defined and monitored across IT and OT | 0 |
SITUATION-2e | SITUATION-2e: Alarms and alerts configured for cybersecurity events | 0 |
SITUATION-2f | SITUATION-2f: Monitoring aligned with the threat profile | 0 |
SITUATION-2g | SITUATION-2g: More rigorous monitoring for higher priority assets | 0 |
SITUATION-2h | SITUATION-2h: Risk analysis used to identify anomaly indicators | 0 |
SITUATION-2i | SITUATION-2i: Indicators reviewed periodically and on triggers | 0 |
SITUATION-3a | SITUATION-3a: Methods to communicate the current cybersecurity state | 0 |
SITUATION-3b | SITUATION-3b: Monitoring data aggregated to show operational state | 0 |
SITUATION-3c | SITUATION-3c: Information from across the organisation enhances awareness | 0 |
SITUATION-3d | SITUATION-3d: Situational awareness reporting requirements defined | 0 |
SITUATION-3e | SITUATION-3e: External information collected and shared internally | 0 |
SITUATION-3f | SITUATION-3f: Near-real-time capability to aggregate, correlate and analyse monitoring | 0 |
SITUATION-3g | SITUATION-3g: Predefined states of operation documented | 0 |
SITUATION-AP1 | SITUATION-AP1: Anti-pattern: operational assets monitored only for performance | 0 |
SITUATION-AP10 | SITUATION-AP10: Anti-pattern: logs of impacted assets cannot be inspected | 0 |
SITUATION-AP11 | SITUATION-AP11: Anti-pattern: IOCs cannot be added to monitoring of critical assets | 0 |
SITUATION-AP2 | SITUATION-AP2: Anti-pattern: logs monitored only during incidents | 0 |
SITUATION-AP3 | SITUATION-AP3: Anti-pattern: normal operation not baselined | 0 |
SITUATION-AP4 | SITUATION-AP4: Anti-pattern: alerts exclude security events | 0 |
SITUATION-AP5 | SITUATION-AP5: Anti-pattern: logs not time synchronised | 0 |
SITUATION-AP6 | SITUATION-AP6: Anti-pattern: critical asset logs stored only on the asset | 0 |
SITUATION-AP7 | SITUATION-AP7: Anti-pattern: unnecessary write access to central logs | 0 |
SITUATION-AP8 | SITUATION-AP8: Anti-pattern: third-party privileged access not logged | 0 |
SITUATION-AP9 | SITUATION-AP9: Anti-pattern: IOCs considered only during or after incidents | 0 |
SP | Security Profiles, priority practices and target state | 0 |
STRUCTURE | How the AESCSF V2 Framework Core is built | 0 |
THIRD-PARTIES-1a | THIRD-PARTIES-1a: Important third-party dependencies identified | 0 |
THIRD-PARTIES-1b | THIRD-PARTIES-1b: Third parties with access, control or custody identified | 0 |
THIRD-PARTIES-1c | THIRD-PARTIES-1c: Defined method identifies third-party risks | 0 |
THIRD-PARTIES-1d | THIRD-PARTIES-1d: Third parties prioritised by established criteria | 0 |
THIRD-PARTIES-1e | THIRD-PARTIES-1e: Escalated priority for high-consequence third parties | 0 |
THIRD-PARTIES-1f | THIRD-PARTIES-1f: Third-party prioritisation updated periodically and on triggers | 0 |
THIRD-PARTIES-2a | THIRD-PARTIES-2a: Supplier selection considers cybersecurity qualifications | 0 |
THIRD-PARTIES-2b | THIRD-PARTIES-2b: Product and service selection considers security capabilities | 0 |
THIRD-PARTIES-2c | THIRD-PARTIES-2c: Defined method sets third-party security requirements and controls | 0 |
THIRD-PARTIES-2d | THIRD-PARTIES-2d: Defined method evaluates and selects third parties | 0 |
THIRD-PARTIES-2e | THIRD-PARTIES-2e: More rigorous controls for higher priority third parties | 0 |
THIRD-PARTIES-2f | THIRD-PARTIES-2f: Security requirements formalised in agreements | 0 |
THIRD-PARTIES-2g | THIRD-PARTIES-2g: Third parties periodically attest to requirements | 0 |
THIRD-PARTIES-2h | THIRD-PARTIES-2h: Secure development requirements for suppliers | 0 |
THIRD-PARTIES-2i | THIRD-PARTIES-2i: Product selection considers end of life and support | 0 |
THIRD-PARTIES-2j | THIRD-PARTIES-2j: Selection considers safeguards against counterfeit or compromised items | 0 |
THIRD-PARTIES-2k | THIRD-PARTIES-2k: Bills of material evaluated for higher priority assets | 0 |
THIRD-PARTIES-2l | THIRD-PARTIES-2l: Hosting environments and source data evaluated for higher priority assets | 0 |
THIRD-PARTIES-2m | THIRD-PARTIES-2m: Acceptance testing includes security requirements | 0 |
THREAT-1a | THREAT-1a: Vulnerability information sources identified | 0 |
THREAT-1b | THREAT-1b: Vulnerability information gathered and interpreted | 0 |
THREAT-1c | THREAT-1c: Vulnerability assessments performed | 0 |
THREAT-1d | THREAT-1d: Relevant vulnerabilities mitigated | 0 |
THREAT-1e | THREAT-1e: Sources covering higher priority assets monitored | 0 |
THREAT-1f | THREAT-1f: Vulnerability assessments periodic and triggered | 0 |
THREAT-1g | THREAT-1g: Vulnerabilities analysed, prioritised and addressed | 0 |
THREAT-1h | THREAT-1h: Operational impact evaluated before patching | 0 |
THREAT-1i | THREAT-1i: Vulnerability information shared with defined stakeholders | 0 |
THREAT-1j | THREAT-1j: Sources covering all IT and OT assets monitored | 0 |
THREAT-1k | THREAT-1k: Independent vulnerability assessments | 0 |
THREAT-1l | THREAT-1l: Vulnerability responses checked for effectiveness | 0 |
THREAT-1m | THREAT-1m: Mechanism to receive external vulnerability reports | 0 |
THREAT-2a | THREAT-2a: Threat information sources identified | 0 |
THREAT-2b | THREAT-2b: Threat information gathered and interpreted | 0 |
THREAT-2c | THREAT-2c: Threat objectives identified | 0 |
THREAT-2d | THREAT-2d: Relevant threats addressed | 0 |
THREAT-2e | THREAT-2e: Threat profile established | 0 |
THREAT-2f | THREAT-2f: Sources covering the whole threat profile prioritised and monitored | 0 |
THREAT-2g | THREAT-2g: Threats analysed, prioritised and addressed | 0 |
THREAT-2h | THREAT-2h: Threat information exchanged with stakeholders | 0 |
THREAT-2i | THREAT-2i: Threat profile updated periodically and on triggers | 0 |
THREAT-2j | THREAT-2j: Threat activities use and trigger predefined states of operation | 0 |
THREAT-2k | THREAT-2k: Secure near-real-time threat sharing methods | 0 |
THREAT-AP1 | THREAT-AP1: Anti-pattern: no compensating controls where remediation is blocked | 0 |
THREAT-AP2 | THREAT-AP2: Anti-pattern: internet-facing assets not periodically assessed | 0 |
THREAT-AP3 | THREAT-AP3: Anti-pattern: controls not updated for new high-priority threats | 0 |
VERSIONS | Versions: V1 (2018, 282 items) and V2 (2023, 354 items) | 0 |
WORKFORCE-1a | WORKFORCE-1a: Vetting at hire | 0 |
WORKFORCE-1b | WORKFORCE-1b: Separation procedures address cybersecurity | 0 |
WORKFORCE-1c | WORKFORCE-1c: Periodic vetting for positions with access to important assets | 0 |
WORKFORCE-1d | WORKFORCE-1d: Separation and transfer procedures address cybersecurity with supplementary vetting | 0 |
WORKFORCE-1e | WORKFORCE-1e: Personnel aware of protection and acceptable use responsibilities | 0 |
WORKFORCE-1f | WORKFORCE-1f: Vetting for all positions by position risk | 0 |
WORKFORCE-1g | WORKFORCE-1g: Formal accountability and disciplinary process | 0 |
WORKFORCE-2a | WORKFORCE-2a: Awareness activities occur | 0 |
WORKFORCE-2b | WORKFORCE-2b: Awareness objectives set | 0 |
WORKFORCE-2c | WORKFORCE-2c: Awareness objectives aligned with the threat profile | 0 |
WORKFORCE-2d | WORKFORCE-2d: Awareness activities periodic | 0 |
WORKFORCE-2e | WORKFORCE-2e: Awareness tailored to job role | 0 |
WORKFORCE-2f | WORKFORCE-2f: Awareness covers predefined states of operation | 0 |
WORKFORCE-2g | WORKFORCE-2g: Awareness effectiveness evaluated and improved | 0 |
WORKFORCE-3a | WORKFORCE-3a: Cybersecurity responsibilities identified | 0 |
WORKFORCE-3b | WORKFORCE-3b: Responsibilities assigned to specific people | 0 |
WORKFORCE-3c | WORKFORCE-3c: Responsibilities assigned to roles including service providers | 0 |
WORKFORCE-3d | WORKFORCE-3d: Responsibilities documented | 0 |
WORKFORCE-3e | WORKFORCE-3e: Responsibilities reviewed periodically and on triggers | 0 |
WORKFORCE-3f | WORKFORCE-3f: Coverage, redundancy and succession managed | 0 |
WORKFORCE-4a | WORKFORCE-4a: Training available for people with cybersecurity responsibilities | 0 |
WORKFORCE-4b | WORKFORCE-4b: Knowledge, skill and ability gaps identified | 0 |
WORKFORCE-4c | WORKFORCE-4c: Gaps addressed by training, recruiting and retention | 0 |
WORKFORCE-4d | WORKFORCE-4d: Training required before access to important assets | 0 |
WORKFORCE-4e | WORKFORCE-4e: Training effectiveness evaluated and improved | 0 |
WORKFORCE-4f | WORKFORCE-4f: Continuing education for significant cybersecurity roles | 0 |
WORKFORCE-AP1 | WORKFORCE-AP1: Anti-pattern: capability depends on one or two people with no succession | 0 |
WORKFORCE-AP2 | WORKFORCE-AP2: Anti-pattern: people working with critical assets lack added responsibilities | 0 |
WORKFORCE-AP3 | WORKFORCE-AP3: Anti-pattern: people unaware of their added responsibilities | 0 |