Compliance, Mapped to Your Cloud

Networks and network services are monitored to find potentially adverse events.

The physical environment is monitored to find potentially adverse events.

Personnel activity and technology usage are monitored to find potentially adverse events.

External service provider activities and services are monitored to find potentially adverse events.

Computing hardware and software, runtime environments, and their data are monitored to find potentially adverse events.

Potentially adverse events are analyzed to better understand associated activities.

Information is correlated from multiple sources.

The estimated impact and scope of adverse events are understood.

Information on adverse events is provided to authorized staff and tools.

Cyber threat intelligence and other contextual information are integrated into the analysis.

Incidents are declared when adverse events meet the defined incident criteria.

Internal and external stakeholders are understood, and their needs and expectations regarding cybersecurity risk management are understood and considered.

Legal, regulatory, and contractual requirements regarding cybersecurity — including privacy and civil liberties obligations — are understood and managed.

Cybersecurity risk management activities and outcomes are included in enterprise risk management processes.

Organizational leadership is responsible and accountable for cybersecurity risk and fosters a culture that is risk-aware, ethical, and continually improving.

Roles, responsibilities, and authorities related to cybersecurity risk management are established, communicated, understood, and enforced.

Cybersecurity is included in human resources practices.

Cybersecurity roles and responsibilities for suppliers, customers, and partners are established, communicated, and coordinated internally and externally.

Inventories of hardware managed by the organization are maintained.

Inventories of software, services, and systems managed by the organization are maintained.

Representations of the organization's authorized network communication and internal and external network data flows are maintained.

Assets are prioritized based on classification, criticality, resources, and impact on the mission.

Inventories of data and corresponding metadata for designated data types are maintained.

Systems, hardware, software, services, and data are managed throughout their life cycles.

Vulnerabilities in assets are identified, validated, and recorded.

Internal and external threats to the organization are identified and recorded.

Potential impacts and likelihoods of threats exploiting vulnerabilities are identified and recorded.

Threats, vulnerabilities, likelihoods, and impacts are used to understand inherent risk and inform risk response prioritization.

Processes for receiving, analyzing, and responding to vulnerability disclosures are established.

The authenticity and integrity of hardware and software are assessed prior to acquisition and use.

Improvements are identified from evaluations.

Improvements are identified from security tests and exercises, including those done in coordination with suppliers and relevant third parties.

Identities and credentials for authorized users, services, and hardware are managed by the organization.

Identities are proofed and bound to credentials based on the context of interactions.

Users, services, and hardware are authenticated.

Identity assertions are protected, conveyed, and verified.

Access permissions, entitlements, and authorizations are defined in a policy, managed, enforced, and reviewed, and incorporate the principles of least privilege and separation of duties.

The confidentiality, integrity, and availability of data-at-rest are protected.

The confidentiality, integrity, and availability of data-in-transit are protected.

Backups of data are created, protected, maintained, and tested.

Configuration management practices are established and applied.

Software is maintained, replaced, and removed commensurate with risk.

Hardware is maintained, replaced, and removed commensurate with risk.

Log records are generated and made available for continuous monitoring.

Installation and execution of unauthorized software are prevented.

Secure software development practices are integrated, and their performance is monitored throughout the software development life cycle.

Networks and environments are protected from unauthorized logical access and usage.

The organization’s technology assets are protected from environmental threats.

Mechanisms are implemented to achieve resilience requirements in normal and adverse situations.

Adequate resource capacity to ensure availability is maintained.

The recovery portion of the incident response plan is executed once initiated from the incident response process.

Recovery actions are selected, scoped, prioritized, and performed.

The integrity of backups and other restoration assets is verified before using them for restoration.

Critical mission functions and cybersecurity risk management are considered to establish post-incident operational norms.

The integrity of restored assets is verified, systems and services are restored, and normal operating status is confirmed.

The end of incident recovery is declared based on criteria, and incident-related documentation is completed.

Recovery activities and progress in restoring operational capabilities are communicated to designated internal and external stakeholders.

Public updates on incident recovery are shared using approved methods and messaging.

The incident response plan is executed in coordination with relevant third parties once an incident is declared.

Incident reports are triaged and validated.

Incidents are categorized and prioritized.

Incidents are escalated or elevated as needed.

The criteria for initiating incident recovery are applied.

Analysis is performed to establish what has taken place during an incident and the root cause of the incident.

Actions performed during an investigation are recorded, and the records' integrity and provenance are preserved.

Incident data and metadata are collected, and their integrity and provenance are preserved.

An incident's magnitude is estimated and validated.

Internal and external stakeholders are notified of incidents.

Information is shared with designated internal and external stakeholders.

Incidents are contained.

Incidents are eradicated.