Free checklist
ISO 27001:2022 Annex A Checklist
This is a free interactive ISO 27001:2022 Annex A checklist covering all 93 controls: 37 organisational, 8 people, 14 physical and 34 technological. Tick controls off in your browser, then download the same checklist as an Excel or CSV file. No signup, no email address, no paywall. Every control links to a plain English guide with implementation and audit evidence tips.
The Excel and CSV versions are at controlstack.au on a computer.
Last updated: November 2026. Maintained against ISO/IEC 27001:2022 (Annex A as detailed in ISO/IEC 27002:2022).
How to use this checklist
- Work top to bottom, or jump to a theme: Organisational (37), People (8), Physical (14), Technological (34).
- Mark each control Implemented, In progress or Not applicable. Your progress saves in your browser automatically. Nothing is uploaded and no account is needed.
- Open any control name for plain English guidance, implementation tips and audit evidence tips.
- Download the Excel or CSV version to work offline or in your GRC tool, or export your current progress as a CSV gap summary.
Your progress
0 of 93 controls marked. Progress is saved in your browser.
Organisational controls (37)
All organisational controls- A.5.1Policies for information security
Define, publish and communicate management-approved security policies, have relevant personnel and interested parties acknowledge them, and review them at planned intervals and on significant change.
- A.5.2Information security roles and responsibilities
Define information security roles and responsibilities and allocate each one according to your organisation's needs, whether as dedicated roles or as duties added to existing jobs.
- A.5.3Segregation of duties
Segregate conflicting duties and conflicting areas of responsibility, so one person cannot carry out both sides of a sensitive task, such as requesting and approving the same access.
- A.5.4Management responsibilities
Management must require all personnel to apply information security as set out in the organisation's established information security policy, topic-specific policies and procedures.
- A.5.5Contact with authorities
Establish and maintain contact with the authorities relevant to your organisation, such as regulators, supervisory bodies and law enforcement, so you can reach them when needed.
- A.5.6Contact with special interest groups
Establish and maintain contact with special interest groups or other specialist security forums and professional associations, so security news and advice reach your organisation.
- A.5.7Threat intelligence
Collect information about information security threats and analyse it to produce threat intelligence, so that your organisation understands which threats apply to it.
- A.5.8Information security in project management
Integrate information security into project management, so that every project, not only IT ones, deals with its security risks and requirements from the early stages.
- A.5.9Inventory of information and other associated assets
Build an inventory of your information and the assets that hold, process or support it, record each item's owner, and keep the inventory up to date.
- A.5.10Acceptable use of information and other associated assets
Identify, document and implement acceptable use rules and handling procedures for information and other associated assets.
- A.5.11Return of assets
Personnel, and other interested parties as appropriate, must return all your organisation's assets they hold when their employment, contract or agreement changes or ends.
- A.5.12Classification of information
Classify information by how much its confidentiality, integrity and availability matter to your organisation, and by what relevant interested parties require.
- A.5.13Labelling of information
Develop and implement an appropriate set of information labelling procedures that follow the classification scheme your organisation has adopted.
- A.5.14Information transfer
Put a rule, procedure or agreement in place for every way information moves, such as email, courier or phone, inside your organisation and with other parties.
- A.5.15Access control
Set and apply rules for who and what may have physical and logical access to information and related assets, based on what the business needs and what information security requires.
- A.5.16Identity management
Manage the full life cycle of identities, from creation through changes to removal, for people and for non-human entities such as services and devices.
- A.5.17Authentication information
Control the allocation and management of authentication information through a management process, which must include advising personnel how to handle it appropriately.
- A.5.18Access rights
Provision, review, modify and remove access rights to information and other associated assets in line with your topic-specific policy on, and rules for, access control.
- A.5.19Information security in supplier relationships
Define and implement processes and procedures to manage the information security risks of using suppliers' products or services.
- A.5.20Addressing information security within supplier agreements
For each supplier, decide which information security requirements are relevant to the type of relationship you have, and agree them with that supplier.
- A.5.21Managing information security in the information and communication technology (ICT) supply chain
Define and implement processes and procedures to manage the information security risks in the ICT products and services supply chain, including parties behind your direct suppliers.
- A.5.22Monitoring, review and change management of supplier services
Regularly monitor, review and evaluate suppliers' information security practices and service delivery, and manage changes to them.
- A.5.23Information security for use of cloud services
Establish processes for acquiring, using, managing and exiting cloud services, each in accordance with your organisation's information security requirements.
- A.5.24Information security incident management planning and preparation
Before information security incidents happen, your organisation must decide how they will be managed and who does what, put that in place and make it known.
- A.5.25Assessment and decision on information security events
Assess each information security event and decide if it is to be categorised as an information security incident.
- A.5.26Response to information security incidents
Respond to information security incidents in accordance with your documented procedures, rather than deciding what to do as you go.
- A.5.27Learning from information security incidents
Use knowledge gained from information security incidents to strengthen and improve your information security controls, so lessons lead to actual changes.
- A.5.28Collection of evidence
Establish and implement procedures to identify, collect, acquire and preserve evidence related to information security events, even before an event is confirmed as an incident.
- A.5.29Information security during disruption
Plan how to maintain information security at an appropriate level during disruption, with your organisation deciding the level from its risks and context.
- A.5.30ICT readiness for business continuity
Plan, implement, maintain and test ICT readiness, based on your business continuity objectives and ICT continuity requirements.
- A.5.31Legal, statutory, regulatory and contractual requirements
Identify, document and keep up to date the legal, statutory, regulatory and contractual requirements relevant to information security, and your approach to meeting them.
- A.5.32Intellectual property rights
Implement appropriate procedures to protect intellectual property rights, such as copyright, patents and software licences, whether others hold them or your organisation does.
- A.5.33Protection of records
Protect records from loss, destruction, falsification, unauthorised access and unauthorised release, whatever their form.
- A.5.34Privacy and protection of personal identifiable information (PII)
Identify and meet the requirements for preserving privacy and protecting personally identifiable information (PII) under applicable laws, regulations and contractual requirements.
- A.5.35Independent review of information security
Have someone independent review how you manage information security and put it into practice, including people, processes and technologies, at planned intervals and after significant changes.
- A.5.36Compliance with policies, rules and standards for information security
Regularly review compliance with your information security policy, topic-specific policies, rules and standards, at a frequency your organisation sets.
- A.5.37Documented operating procedures
Document the operating procedures for information processing facilities and make them available to the personnel who need them.
People controls (8)
All people controls- A.6.1Screening
Check all candidates' backgrounds before they join and on an ongoing basis, within laws, regulations and ethics, proportional to business requirements, information classification and perceived risks.
- A.6.2Terms and conditions of employment
Employment agreements must state the information security responsibilities of both your personnel and your organisation.
- A.6.3Information security awareness, education and training
Personnel and relevant interested parties must receive appropriate information security awareness, education and training, and regular policy and procedure updates, as relevant for their job function.
- A.6.4Disciplinary process
Formalise and communicate a disciplinary process for taking action against personnel and other relevant interested parties who have committed an information security policy violation.
- A.6.5Responsibilities after termination or change of employment
Define, enforce and communicate the information security responsibilities and duties that remain valid after employment ends or changes, to relevant personnel and other interested parties.
- A.6.6Confidentiality or non-disclosure agreements
Identify, document and regularly review confidentiality or non-disclosure agreements that reflect your information protection needs, signed by personnel and other relevant interested parties.
- A.6.7Remote working
Implement security measures whenever personnel work remotely, to protect information accessed, processed or stored outside your premises.
- A.6.8Information security event reporting
Give personnel a way to report information security events they see or only suspect, promptly and through appropriate channels.
Physical controls (14)
All physical controls- A.7.1Physical security perimeters
Define security perimeters and use them to protect areas, such as server rooms, records stores and offices, that contain information and other associated assets.
- A.7.2Physical entry
Protect secure areas with appropriate entry controls and access points, chosen by your organisation based on its risks and context.
- A.7.3Securing offices, rooms and facilities
Design and implement physical security for your offices, rooms and facilities, so protection is planned for each space and then actually put in place.
- A.7.4Physical security monitoring
Monitor premises continuously for unauthorised physical access, at all hours and in unoccupied areas, whether by guards, alarms, video or a monitoring service.
- A.7.5Protecting against physical and environmental threats
Work out the protection your infrastructure needs against physical and environmental threats, whether natural, deliberate or accidental, and put it in place.
- A.7.6Working in secure areas
Design and implement security measures for working in secure areas, covering what people do once inside, not how they get in.
- A.7.7Clear desk and clear screen
Set rules for putting away papers and removable media and for locking or logging off unattended devices and systems, then enforce them appropriately.
- A.7.8Equipment siting and protection
Site equipment securely, and protect it where it sits from unauthorised access, damage, and physical and environmental threats.
- A.7.9Security of assets off-premises
Protect off-site assets, including privately owned devices used for work, against loss, damage, theft and compromise while they are outside your premises.
- A.7.10Storage media
Manage storage media through acquisition, use, transportation and disposal, following your classification scheme and handling requirements at every stage.
- A.7.11Supporting utilities
Protect information processing facilities from power failures and other disruptions caused by failures in supporting utilities, such as telecommunications, water and air conditioning.
- A.7.12Cabling security
Protect cables carrying power, data or supporting information services from interception, interference or damage, wherever they run.
- A.7.13Equipment maintenance
Maintain equipment correctly to ensure the availability, integrity and confidentiality of information, including during the maintenance itself.
- A.7.14Secure disposal or re-use of equipment
Before disposal or re-use, verify that any sensitive data and licensed software on equipment containing storage media has been removed or securely overwritten.
Technological controls (34)
All technological controls- A.8.1User end point devices
Protect information stored on, processed by or accessible via user endpoint devices, including privately owned devices used for work, even where it sits in a service and not on the device.
- A.8.2Privileged access rights
Restrict and manage both who is allocated privileged access rights and how those rights are used, including rights held by software components and services.
- A.8.3Information access restriction
Allow access to information and other associated assets, such as systems and devices, only as far as your established access control policy permits.
- A.8.4Access to source code
Appropriately manage read and write access to source code, development tools and software libraries, with your organisation deciding what appropriate means from its risks.
- A.8.5Secure authentication
Put secure authentication technology and procedures in place, matched to your access control policy and the limits on who may access which information.
- A.8.6Capacity management
Monitor the use of resources, including systems, people and facilities, and adjust it in line with current and expected capacity requirements.
- A.8.7Protection against malware
Implement protection against malware, and support it with appropriate user awareness so people know how to avoid malware and what to do if they meet it.
- A.8.8Management of technical vulnerabilities
Obtain information about technical vulnerabilities of information systems in use, evaluate your organisation's exposure to them and take appropriate measures.
- A.8.9Configuration management
Establish, document, implement, monitor and review configurations, including security configurations, of hardware, software, services and networks.
- A.8.10Information deletion
Delete information stored in information systems, devices or any other storage media when it is no longer required.
- A.8.11Data masking
Use data masking to hide sensitive values as your access control policy, other related policies and business needs require, considering the laws that apply.
- A.8.12Data leakage prevention
If a system, network or other device processes, stores or transmits sensitive information, apply data leakage prevention measures to it.
- A.8.13Information backup
Back up software and systems as well as information, keep the copies current and test them regularly, all as your agreed backup policy sets out.
- A.8.14Redundancy of information processing facilities
Implement information processing facilities with redundancy sufficient to meet availability requirements, which your organisation sets for its services and systems.
- A.8.15Logging
Produce, store, protect and analyse logs that record activities, exceptions, faults and other relevant events.
- A.8.16Monitoring activities
Watch networks, systems and applications for unusual activity, and take appropriate steps to check whether it may be an information security incident.
- A.8.17Clock synchronization
Synchronise the clocks of the information processing systems your organisation uses, whether it runs them or buys them as a service, to approved time sources.
- A.8.18Use of privileged utility programs
Restrict and tightly control the use of utility programs that can override system and application controls, such as debuggers and backup or diagnostic tools.
- A.8.19Installation of software on operational systems
Implement procedures and measures to securely manage software installation on operational systems, the live systems your organisation runs on.
- A.8.20Networks security
Secure, manage and control your networks and network devices, such as routers, switches, firewalls and wireless access points, to protect information in systems and applications.
- A.8.21Security of network services
Identify, implement and monitor the security mechanisms, service levels and service requirements of each network service, whether an internal team or an outside provider delivers it.
- A.8.22Segregation of networks
Segregate groups of information services, users and information systems in your organisation's networks, so they do not all share one open network.
- A.8.23Web filtering
Manage your organisation's access to external websites, for example by blocking known malicious sites, to reduce exposure to malicious content.
- A.8.24Use of cryptography
Define and implement rules for the effective use of cryptography, including key management: which methods protect which information, and how keys are handled through their life.
- A.8.25Secure development life cycle
Establish and apply rules for the secure development of software and systems, covering each stage from design to release, including scripts and outsourced work.
- A.8.26Application security requirements
Identify, specify and approve information security requirements when developing or acquiring applications, including paid or free cloud services, not after they go live.
- A.8.27Secure system architecture and engineering principles
Establish, document and maintain principles for engineering secure systems, and apply them to any information system development activities, in-house or outsourced.
- A.8.28Secure coding
Apply secure coding principles to software development, in-house or outsourced, to reduce flaws such as unchecked input and hard-coded passwords.
- A.8.29Security testing in development and acceptance
Define security testing processes and implement them in the development life cycle, so security requirements are checked before applications or code reach production.
- A.8.30Outsourced development
Direct, monitor and review the activities related to outsourced system development, so the security you require is set, checked during the work and confirmed on delivery.
- A.8.31Separation of development, test and production environments
Separate development, testing and production environments from one another and secure all three, so development and test work does not put live systems and data at risk.
- A.8.32Change management
Put changes to information processing facilities and information systems through change management procedures, whether software or infrastructure, planned or urgent.
- A.8.33Test information
Appropriately select, protect and manage test information, as your organisation decides from its risks, so tests are reliable and live data is not exposed.
- A.8.34Protection of information systems during audit testing
Plan audit tests and other assurance activities that assess operational systems, and agree them between the tester and appropriate management, before they start.
What this checklist is (and is not)
- It is a control by control tracker for Annex A of ISO/IEC 27001:2022, with the same 93 controls and four themes the standard uses.
- It is not a full certification project plan. The management system requirements in clauses 4 to 10 (scope, leadership, risk assessment, internal audit, management review) sit outside Annex A. For what each one requires, read ISO 27001 clauses 4 to 10 in plain English. For the project view, use the free ISO 27001 implementation checklist from our sister site Mindset Cyber.
- It is not a Statement of Applicability template, but the exported file gives you the control inventory and status columns an SoA is built on.
- For the mandatory documents themselves, PolicyMint drafts customised ISO 27001 documentation rather than leaving you to fight a boilerplate template.
- Running Essential Eight as well? See how the two frameworks line up in our ISO 27001 to Essential Eight mapping, or browse the full ISO 27001 Annex A controls library.
Clauses 4 to 10
Annex A is only part of ISO 27001. To be certified you must also run an information security management system (ISMS) that meets every requirement in clauses 4 to 10. You cannot exclude any of them. They cover:
- Clause 4, Context: your issues, interested parties, the ISMS scope and the ISMS itself.
- Clause 5, Leadership: top management commitment, the information security policy, and assigned roles and responsibilities.
- Clause 6, Planning: risks and opportunities, the risk assessment and treatment processes, the Statement of Applicability, objectives and planned changes.
- Clause 7, Support: resources, competence, awareness, communication and documented information.
- Clause 8, Operation: running your processes and carrying out risk assessment and risk treatment in practice.
- Clause 9, Performance evaluation: monitoring and measurement, internal audit and management review.
- Clause 10, Improvement: continual improvement, nonconformities and corrective action.
Read what each clause requires and what an auditor asks to see. The Excel download has a Clauses 4 to 10 sheet to track them.
Frequently asked questions
Is this ISO 27001 checklist really free?
Yes. The interactive checklist and the Excel and CSV downloads are completely free, with no signup, no email capture and no paywall. Progress is saved in your own browser and never uploaded.
How many controls are in ISO 27001:2022 Annex A?
ISO/IEC 27001:2022 Annex A contains 93 controls in four themes: 37 organisational controls (A.5), 8 people controls (A.6), 14 physical controls (A.7) and 34 technological controls (A.8). The 2013 edition had 114 controls in 14 domains; the 2022 revision consolidated them into 93.
Do we have to implement all 93 controls?
No. Annex A is a reference set, not a mandatory to do list. You select controls through your risk assessment and record what applies in your Statement of Applicability, with a justification for any control you exclude.
Is this the same as an ISO 27001 implementation checklist?
No. This checklist covers the Annex A controls only. An implementation checklist covers the whole certification project, including the clause 4 to 10 management system requirements such as scope, leadership, risk assessment and internal audit.
Can I use this checklist for a gap analysis or internal audit?
Yes. Mark each control as Implemented, In progress or Not applicable, use each control guide for audit evidence tips, and export your progress as a CSV gap summary.
What formats can I download?
Excel (.xlsx) with a status dropdown for every control, and plain CSV. Both list all 93 controls with theme, status, owner and evidence columns, and both are direct downloads with no signup.
Want help implementing the controls?
Control Stack keeps this checklist and the 93 control guides free. If you want formal training, our sister site Mindset Cyber sells official PECB ISO 27001 courses, including self paced Lead Implementer and Lead Auditor eLearning. Mindset Cyber provides training and exam vouchers; it is not a certification body and cannot certify your organisation.




