Compliance, Mapped to Your Cloud

Assess your AWS, Azure, and Google Cloud environments against the industry frameworks and regulations your auditors expect.

56
Frameworks Supported
18
Standards Families
3
Cloud Providers
5 min
To First Results
ASecureCloud compliance report preview
Google Cloud logo

NIST CSF v2.0

96 controls
129 checks mapped

The NIST Cybersecurity Framework (CSF) organizes security activities around its core functions — Identify, Protect, Detect, Respond, and Recover.

Controls assessed

ID.AM-01 - Inventories of hardware managed by the organization are maintained.9

Inventories of hardware managed by the organization are maintained.

ID.AM-02 - Inventories of software, services, and systems managed by the organization are maintained.5

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

ID.AM-03 - Representations of authorized network communication and data flows are maintained.5

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

ID.AM-04 - Inventories of services provided by suppliers are maintained.2

Inventories of services provided by suppliers are maintained.

ID.AM-05 - Assets are prioritized based on classification, criticality, resources, and impact on the mission.1

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

ID.AM-07 - Inventories of data and corresponding metadata for designated data types are maintained.5

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

ID.AM-08 - Systems, hardware, software, services, and data are managed throughout their life cycles.5

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

ID.IM-01 - Improvements are identified from evaluations.3

Improvements are identified from evaluations.

ID.IM-02 - Improvements are identified from security tests and exercises.3

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

ID.IM-03 - Improvements are identified from execution of operational processes.4

Improvements are identified from execution of operational processes, procedures, and activities.

ID.IM-04 - Incident response and cybersecurity plans are established, maintained, and improved.1

Incident response plans and other cybersecurity plans that affect operations are established, communicated, maintained, and improved.

ID.RA-01 - Vulnerabilities in assets are identified, validated, and recorded.1

Vulnerabilities in assets are identified, validated, and recorded.

ID.RA-02 - Cyber threat intelligence is received.10

Cyber threat intelligence is received from information sharing forums and sources.

ID.RA-03 - Internal and external threats are identified and recorded.9

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

ID.RA-04 - Potential impacts and likelihoods are identified and recorded.9

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

ID.RA-05 - Inherent risk informs response prioritization.9

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

ID.RA-06 - Risk responses are chosen, prioritized, planned, tracked, and communicated.9

Risk responses are chosen, prioritized, planned, tracked, and communicated.

ID.RA-07 - Changes and exceptions are managed and assessed for risk impact.9

Changes and exceptions are managed, assessed for risk impact, recorded, and tracked.

ID.RA-08 - Vulnerability disclosure processes are established.10

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

ID.RA-09 - Authenticity and integrity of hardware and software are assessed prior to use.6

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

ID.RA-10 - Critical suppliers are assessed prior to acquisition.2

Critical suppliers are assessed prior to acquisition.

PR.AA-01 - Identities and credentials are managed by the organization.15

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

PR.AA-02 - Identities are proofed and bound to credentials based on context.5

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

PR.AA-03 - Users, services, and hardware are authenticated.10

Users, services, and hardware are authenticated.

PR.AA-04 - Identity assertions are protected, conveyed, and verified.8

Identity assertions are protected, conveyed, and verified.

PR.AA-05 - Access permissions, entitlements, and authorizations are managed.12

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

PR.AA-06 - Physical access to assets is managed, monitored, and enforced.1

Physical access to assets is managed, monitored, and enforced commensurate with risk.

PR.DS-01 - Confidentiality, integrity, and availability of data-at-rest are protected.13

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

PR.DS-02 - Confidentiality, integrity, and availability of data-in-transit are protected.5

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

PR.DS-10 - Confidentiality, integrity, and availability of data-in-use are protected.2

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

PR.DS-11 - Backups of data are created, protected, maintained, and tested.5

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

PR.IR-01 - Networks and environments are protected from unauthorized logical access and usage.54

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

PR.IR-02 - Technology assets are protected from environmental threats.8

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

PR.IR-03 - Mechanisms are implemented to achieve resilience requirements.12

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

PR.IR-04 - Adequate resource capacity is maintained.7

Adequate resource capacity to ensure availability is maintained.

PR.PS-01 - Configuration management practices are established and applied.7

Configuration management practices are established and applied.

PR.PS-02 - Software is maintained, replaced, and removed commensurate with risk.3

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

PR.PS-03 - Hardware is maintained, replaced, and removed commensurate with risk.3

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

PR.PS-04 - Log records are generated and made available for continuous monitoring.20

Log records are generated and made available for continuous monitoring.

PR.PS-05 - Installation and execution of unauthorized software are prevented.3

Installation and execution of unauthorized software are prevented.

PR.PS-06 - Secure software development practices are integrated.2

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

DE.AE-2 - Detected events are analyzed to understand attack targets and methods.2

Detected events are analyzed to understand attack targets and methods.

DE.AE-3 - Event data are collected and correlated from multiple sources and sensors.20

Event data are collected and correlated from multiple sources and sensors.

DE.CM-1 - The network is monitored to detect potential cybersecurity events.11

The network is monitored to detect potential cybersecurity events.

RS.AN-03 - Analysis is performed to establish what has taken place and root cause.9

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

RS.AN-06 - Actions performed during an investigation are recorded.2

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

RS.AN-07 - Incident data and metadata are collected with integrity preserved.2

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

RS.AN-08 - Incident magnitude is estimated and validated.9

An incident's magnitude is estimated and validated.

RS.CO-02 - Internal and external stakeholders are notified of incidents.1

Internal and external stakeholders are notified of incidents.

RS.CO-03 - Information is shared with designated stakeholders.1

Information is shared with designated internal and external stakeholders.

RS.MA-01 - Incident response plan is executed with third parties once declared.1

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

RS.MA-02 - Incident reports are triaged and validated.9

Incident reports are triaged and validated.

RS.MA-03 - Incidents are categorized and prioritized.9

Incidents are categorized and prioritized.

RS.MA-04 - Incidents are escalated or elevated as needed.9

Incidents are escalated or elevated as needed.

RS.MA-05 - Criteria for initiating incident recovery are applied.9

The criteria for initiating incident recovery are applied.

RS.MI-01 - Incidents are contained.9

Incidents are contained.

RS.MI-02 - Incidents are eradicated.9

Incidents are eradicated.

RC.CO-03 - Recovery activities and progress are communicated to stakeholders.1

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

RC.CO-04 - Public updates on incident recovery are shared using approved methods.1

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

RC.RP-01 - Recovery portion of incident response plan is executed.1

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

RC.RP-02 - Recovery actions are selected, scoped, prioritized, and performed.3

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

RC.RP-03 - Integrity of backups and restoration assets is verified before use.3

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

RC.RP-04 - Post-incident operational norms are established.2

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

RC.RP-05 - Integrity of restored assets is verified and normal status confirmed.3

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

RC.RP-06 - End of incident recovery is declared and documentation completed.2

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

GV.OC-01 - Organizational mission informs cybersecurity risk management.6

The organizational mission is understood and informs cybersecurity risk management.

GV.OC-02 - Stakeholder needs and expectations are considered.1

Internal and external stakeholders are understood, and their needs and expectations are considered.

GV.OC-03 - Legal, regulatory, and contractual requirements are managed.11

Legal, regulatory, and contractual requirements regarding cybersecurity are understood and managed.

GV.OC-04 - Critical objectives and capabilities are understood and communicated.2

Critical objectives, capabilities, and services that external stakeholders depend on are understood and communicated.

GV.OC-05 - Dependencies are understood and communicated.2

Outcomes, capabilities, and services that the organization depends on are understood and communicated.

GV.OV-01 - Risk management strategy outcomes are reviewed.11

Cybersecurity risk management strategy outcomes are reviewed to inform and adjust strategy and direction.

GV.OV-02 - Risk management strategy is reviewed and adjusted.11

The cybersecurity risk management strategy is reviewed and adjusted to ensure coverage of organizational requirements and risks.

GV.OV-03 - Risk management performance is evaluated and reviewed.11

Organizational cybersecurity risk management performance is evaluated and reviewed for adjustments needed.

GV.PO-01 - Cybersecurity policy is established and enforced.10

Policy for managing cybersecurity risks is established, communicated, and enforced.

GV.PO-02 - Cybersecurity policy is reviewed and updated.11

Cybersecurity policy is reviewed, updated, communicated, and enforced to reflect changes in requirements, threats, technology, and mission.

GV.RM-01 - Risk management objectives are established and agreed to.5

Risk management objectives are established and agreed to by organizational stakeholders.

GV.RM-02 - Risk appetite and tolerance statements are established.6

Risk appetite and risk tolerance statements are established, communicated, and maintained.

GV.RM-03 - Cybersecurity RM activities included in ERM.5

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

GV.RM-04 - Strategic direction for risk response is established.6

Strategic direction that describes appropriate risk response options is established and communicated.

GV.RM-05 - Lines of communication across organization are established.10

Lines of communication across the organization are established for cybersecurity risks, including risks from suppliers and other third parties.

GV.RM-06 - Method for prioritizing cybersecurity risks is established.10

A standardized method for calculating, documenting, categorizing, and prioritizing cybersecurity risks is established and communicated.

GV.RM-07 - Strategic opportunities are characterized and discussed.10

Strategic opportunities (positive risks) are characterized and are included in organizational cybersecurity risk discussions.

GV.RR-01 - Leadership accountable for cybersecurity risk and culture.4

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

GV.RR-02 - Roles, responsibilities, and authorities are established and enforced.7

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

GV.RR-03 - Adequate resources are allocated for cybersecurity risk strategy.7

Adequate resources are allocated commensurate with the cybersecurity risk strategy, roles, responsibilities, and policies.

GV.RR-04 - Cybersecurity is included in human resources practices.5

Cybersecurity is included in human resources practices.

GV.SC-01 - Supply chain risk management program is established.7

A cybersecurity supply chain risk management program, strategy, objectives, policies, and processes are established and agreed to by organizational stakeholders.

GV.SC-02 - Roles and responsibilities for suppliers are established.6

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

GV.SC-03 - Supply chain RM integrated into cybersecurity and ERM.7

Cybersecurity supply chain risk management is integrated into cybersecurity and enterprise risk management, risk assessment, and improvement processes.

GV.SC-04 - Suppliers are known and prioritized by criticality.2

Suppliers are known and prioritized by criticality.

GV.SC-05 - Supply chain risk requirements are integrated into agreements.13

Requirements to address cybersecurity risks in supply chains are established, prioritized, and integrated into contracts and agreements.

GV.SC-06 - Due diligence is performed before supplier relationships.12

Planning and due diligence are performed to reduce risks before entering into supplier relationships.

GV.SC-07 - Supplier and third-party risks are managed and monitored.22

The risks posed by suppliers, their products and services, and third parties are understood, prioritized, responded to, and monitored over the relationship.

GV.SC-08 - Suppliers are included in incident planning, response, recovery.13

Relevant suppliers and third parties are included in incident planning, response, and recovery.

GV.SC-09 - Supply chain security practices are integrated and monitored.15

Supply chain security practices are integrated into cybersecurity and ERM programs, and their performance is monitored across the lifecycle.

GV.SC-10 - Supply chain RM plans include post-partnership activities.17

Supply chain risk management plans include provisions for activities after a partnership ends.

See where you stand against any framework

Connect an account and get a full compliance breakdown with mapped findings and remediation guidance — free to start.