Compliance, Mapped to Your Cloud

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

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

ISO/IEC 27001:2022 Annex A

34 controls
221 checks mapped

Assess AWS configurations against technical safeguards mapped to ISO/IEC 27001:2022 Annex A, covering organizational and technological controls. These automated checks provide supporting evidence for your information security management system (ISMS).

Controls assessed

A.5.1 Policies for information security1

Information security policy and topic-specific policies should be defined, approved by management, published, communicated to and acknowledged by relevant personnel and relevant interested parties, and reviewed at planned intervals and if significant changes occur.

A.5.5 Contact with authorities1

The organisation should establish and maintain contact with relevant authorities.

A.5.13 Labelling of information2

An appropriate set of procedures for information labelling should be developed and implemented in accordance with the information classification scheme adopted by the organisation.

A.5.15 Access control12

Rules to control physical and logical access to information and other associated assets should be established

A.5.16 Identity management1

The full lifecycle of identities should be managed.

A.5.17 Authentication information2

Allocation and management of authentication information should be controlled by a management process, including advising personnel on the appropriate handling of authentication information.

A.5.18 Access rights1

Access rights to information and other associated assets should be provisioned, reviewed, modified and removed in accordance with the organisation’s topic-specific policy on and rules for access control.

A.5.19 Information security in supplier relationships2

Processes and procedures should be defined and implemented to manage the information security risks associated with the use of supplier’s products or services.

A.5.21 Managing information security in the ICT supply chain2

Processes and procedures should be defined and implemented to manage the information security risks associated with the ICT products and services supply chain.

A.5.22 Monitoring, review and change management of supplier services1

The organisation should regularly monitor, review, evaluate and manage change in supplier information security practices and service delivery.

A.5.25 Assessment and decision on information security events3

The organisation should assess information security events and decide if they are to be categorised as information security incidents.

A.5.26 Response to information security incidents1

Information security incidents should be responded to in accordance with the documented procedures.

A.5.28 Collection of evidence3

The organisation should establish and implement procedures for the identification, collection, acquisition and preservation of evidence related to information security events.

A.5.29 Information security during disruption3

The organisation should plan how to maintain information security at an appropriate level during disruption.

A.8.1 User endpoint devices24

Information stored on, processed by or accessible via user endpoint devices should be protected.

A.8.2 Privileged access rights2

The allocation and use of privileged access rights should be restricted and managed.

A.8.3 Information access restriction5

Access to information and other associated assets should be restricted in accordance with the established topic-specific policy on access control.

A.8.4 Access to source code4

Read and write access to source code, development tools and software libraries should be appropriately managed.

A.8.5 Secure authentication7

Secure authentication technologies and procedures should be implemented based on information access restrictions and the topic-specific policy on access control.

A.8.7 Protection against malware2

Protection against malware should be implemented and supported by appropriate user awareness.

A.8.9 Configuration management2

Configurations, including security configurations, of hardware, software, services and networks should be established, documented, implemented, monitored and reviewed.

A.8.10 Information deletion2

Information stored in information systems, devices or in any other storage media should be deleted when no longer required.

A.8.11 Data masking33

Data masking should be used in accordance with the organisation’s topic-specific policy on access control and other related topic-specific policies, and business requirements, taking applicable legislation into consideration.

A.8.12 Data leakage prevention5

Data leakage prevention measures should be applied to systems, networks and any other devices that process, store or transmit sensitive information.

A.8.13 Information backup4

Backup copies of information, software and systems should be maintained and regularly tested in accordance with the agreed topic-specific policy on backup.

A.8.14 Redundancy of information processing facilities24

Information processing facilities should be implemented with redundancy sufficient to meet availability

A.8.15 Logging57

Logs that record activities, exceptions, faults and other relevant events should be produced, stored, protected and analysed.

A.8.16 Monitoring activities26

Networks, systems and applications should be monitored for anomalous behaviour and appropriate actions taken to evaluate potential information security incidents.

A.8.20 Networks security38

Networks and network devices should be secured, managed and controlled to protect information in systems and applications.

A.8.21 Security of network services39

Security mechanisms, service levels and service requirements of network services should be identified, implemented and monitored.

A.8.22 Segregation of networks39

Security mechanisms, service levels and service requirements of network services should be identified, implemented and monitored.

A.8.23 Web filtering3

Access to external websites should be managed to reduce exposure to malicious content.

A.8.24 Use of cryptography51

Rules for the effective use of cryptography, including cryptographic key management, should be defined and implemented.

A.8.27 Secure system architecture and engineering principles2

Principles for engineering secure systems should be established, documented, maintained and applied to any information system development activities.

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.