Framework · Information security · Certifiable

ISO 27001 requirements, controls and certification

ISO/IEC 27001 is the international standard for an information security management system (ISMS). Clauses 4 to 10 set the management requirements, and Annex A lists 93 reference controls. An accredited certification body audits you in two stages. The certificate lasts three years, with surveillance audits in years one and two.

Key takeaways

What you need to know about ISO 27001

Risk-basedYou pick controls from your own risk assessment. No organisation has to apply all 93.
SoAThe Statement of Applicability records each control's status and justifies any you exclude.
2 stagesStage 1 reviews your design and documents. Stage 2 tests whether controls actually operate.
Not a lawIt's voluntary, but customers, regulators and tenders often ask for it.
ReusableOne ISMS evidence set supports SOC 2, NIST CSF 2.0, ISO 27701 and more.

Who needs ISO 27001?

No law requires it, but these situations usually make it a requirement in practice.

SaaS and cloud providersEnterprise buyers ask for the certificate during vendor due diligence, often before a contract.
IT and outsourcing firmsClients put ISO 27001 into master service agreements and RFPs.
Fintech and paymentsBanks and regulators look for a recognised ISMS behind sector rules.
Healthtech and data processorsShows that personal and health data sit inside a governed security system.
Public-sector suppliersGovernment tenders often score or require certification.

QULDEX helps here first: the readiness check shows how far you are from Stage 1 before you commit budget.

Clauses 4–10

What does ISO 27001 require?

ISO 27001 requires you to run an ISMS: define its scope, assess information security risk, treat that risk with controls, and keep checking that it works. Clauses 4 to 10 are mandatory for certification and follow the Plan-Do-Check-Act cycle.

Clause 4 Plan

Context

Issues, interested parties, ISMS scope. Since Amd 1:2024, whether climate change is relevant.

In QULDEX: Scope, interested parties and the climate question set up once per programme
Clause 5 Plan

Leadership

Top-management commitment, security policy, roles and authorities.

In QULDEX: Policy approvals with named owners and full sign-off history
Clause 6 Plan

Planning

Risk assessment, risk treatment, Statement of Applicability, objectives.

In QULDEX: Risk register decisions generate the Statement of Applicability
Clause 7 Plan

Support

Resources, competence, awareness, communication, documented information.

In QULDEX: Training and competence records kept in the evidence vault
Clause 8 Do

Operation

Run the risk treatment plan and control planned changes.

In QULDEX: Control tasks run on schedule with evidence attached
Clause 9 Check

Evaluation

Monitoring and measurement, internal audit, management review.

In QULDEX: Internal audit workspace and management review packs
Clause 10 Act

Improvement

Nonconformity, corrective action, continual improvement.

In QULDEX: Findings flow into CAPA with owners, due dates and verification
Annex A · 93 controls

What are the ISO 27001 Annex A controls?

Annex A of ISO/IEC 27001:2022 lists 93 information security controls in four themes: organisational (37), people (8), physical (14) and technological (34). You choose the controls your risk assessment needs and record each decision in the Statement of Applicability.

114 → 93controls, 2013 to 2022
14 → 4domains became themes
11new controls in 2022
0controls changed by Amd 1:2024

Showing all 93 controls. Select a control to see what it requires.

5 · Organisational controls 37

  1. A.5.1Policies for information security

    Define, approve, publish and regularly review an information security policy and topic-specific policies.

    In QULDEXQULDEX gives this control an owner, a review cycle and an evidence request, and maps it to every framework you run.

  2. A.5.2Information security roles and responsibilities

    Define and assign information security roles and responsibilities.

    In QULDEXQULDEX gives this control an owner, a review cycle and an evidence request, and maps it to every framework you run.

  3. A.5.3Segregation of duties

    Separate conflicting duties and areas of responsibility.

    In QULDEXQULDEX gives this control an owner, a review cycle and an evidence request, and maps it to every framework you run.

  4. A.5.4Management responsibilities

    Management requires all personnel to apply security in line with policies and procedures.

    In QULDEXQULDEX gives this control an owner, a review cycle and an evidence request, and maps it to every framework you run.

  5. A.5.5Contact with authorities

    Establish and maintain contact with relevant authorities.

    In QULDEXQULDEX gives this control an owner, a review cycle and an evidence request, and maps it to every framework you run.

  6. A.5.6Contact with special interest groups

    Maintain contact with security forums and professional associations.

    In QULDEXQULDEX gives this control an owner, a review cycle and an evidence request, and maps it to every framework you run.

  7. A.5.7Threat intelligenceNew

    Collect and analyse information about threats to produce threat intelligence.

    In QULDEXQULDEX gives this control an owner, a review cycle and an evidence request, and maps it to every framework you run.

    Typical evidence
    Threat intelligence sources, analysis notes, actions taken
    Maps to
    SOC 2 CC3.2NIST ID.RA-02

  8. A.5.8Information security in project management

    Integrate information security into project management.

    In QULDEXQULDEX gives this control an owner, a review cycle and an evidence request, and maps it to every framework you run.

  9. A.5.9Inventory of information and other associated assets

    Keep an inventory of information and associated assets, each with an owner.

    In QULDEXQULDEX gives this control an owner, a review cycle and an evidence request, and maps it to every framework you run.

  10. A.5.10Acceptable use of information and other associated assets

    Document and apply rules for acceptable use and handling of assets.

    In QULDEXQULDEX gives this control an owner, a review cycle and an evidence request, and maps it to every framework you run.

  11. A.5.11Return of assets

    Get organisational assets back when employment, a contract or an agreement changes or ends.

    In QULDEXQULDEX gives this control an owner, a review cycle and an evidence request, and maps it to every framework you run.

  12. A.5.12Classification of information

    Classify information by confidentiality, integrity, availability and stakeholder needs.

    In QULDEXQULDEX gives this control an owner, a review cycle and an evidence request, and maps it to every framework you run.

  13. A.5.13Labelling of information

    Label information according to the classification scheme.

    In QULDEXQULDEX gives this control an owner, a review cycle and an evidence request, and maps it to every framework you run.

  14. A.5.14Information transfer

    Apply transfer rules, procedures or agreements for every type of transfer facility.

    In QULDEXQULDEX gives this control an owner, a review cycle and an evidence request, and maps it to every framework you run.

  15. A.5.15Access control

    Set rules for physical and logical access based on business and security requirements.

    In QULDEXAccess reviews run as recurring tasks. Reviewers sign off in QULDEX and every revocation becomes a tracked action.

    Typical evidence
    Access control policy, role-to-permission matrix, approval records
    Maps to
    SOC 2 CC6.1CC6.3NIST PR.AA-05PCI Req 7

    A.5.15 explained on the blog →

  16. A.5.16Identity management

    Manage the full life cycle of identities.

    In QULDEXAccess reviews run as recurring tasks. Reviewers sign off in QULDEX and every revocation becomes a tracked action.

  17. A.5.17Authentication information

    Control how authentication information such as passwords is issued and managed.

    In QULDEXQULDEX gives this control an owner, a review cycle and an evidence request, and maps it to every framework you run.

  18. A.5.18Access rights

    Provision, review, change and remove access rights in line with policy.

    In QULDEXAccess reviews run as recurring tasks. Reviewers sign off in QULDEX and every revocation becomes a tracked action.

    Typical evidence
    Quarterly access review export with sign-off and revocation tickets
    Maps to
    SOC 2 CC6.2NIST PR.AA-05PCI Req 7.2

    A.5.18 explained on the blog →

  19. A.5.19Information security in supplier relationships

    Manage the security risks of using suppliers' products and services.

    In QULDEXEach supplier gets one record with its assessment, contract clauses and renewal date, and renewals trigger review tasks.

    Typical evidence
    Supplier inventory, risk assessments, security clauses in contracts
    Maps to
    SOC 2 CC9.2NIST GV.SC-07PCI Req 12.8

  20. A.5.20Addressing information security within supplier agreements

    Agree security requirements with each supplier in the contract.

    In QULDEXEach supplier gets one record with its assessment, contract clauses and renewal date, and renewals trigger review tasks.

  21. A.5.21Managing information security in the ICT supply chain

    Manage security risks in the ICT product and service supply chain.

    In QULDEXEach supplier gets one record with its assessment, contract clauses and renewal date, and renewals trigger review tasks.

  22. A.5.22Monitoring, review and change management of supplier services

    Monitor and review supplier security practices and manage changes to them.

    In QULDEXEach supplier gets one record with its assessment, contract clauses and renewal date, and renewals trigger review tasks.

  23. A.5.23Information security for use of cloud servicesNew

    Set processes for acquiring, using, managing and exiting cloud services.

    In QULDEXEach supplier gets one record with its assessment, contract clauses and renewal date, and renewals trigger review tasks.

    Typical evidence
    Cloud service register, shared-responsibility matrix, exit plan
    Maps to
    SOC 2 CC9.2NIST GV.SC-07

  24. A.5.24Information security incident management planning and preparation

    Plan incident management with defined processes, roles and responsibilities.

    In QULDEXIncidents are logged with root cause and evidence, and lessons learned feed straight into CAPA.

    Typical evidence
    Incident response plan, roles, contact lists, test exercise record
    Maps to
    SOC 2 CC7.3NIST RS.MA-01PCI Req 12.10

  25. A.5.25Assessment and decision on information security events

    Assess security events and decide whether they count as incidents.

    In QULDEXIncidents are logged with root cause and evidence, and lessons learned feed straight into CAPA.

  26. A.5.26Response to information security incidents

    Respond to incidents according to documented procedures.

    In QULDEXIncidents are logged with root cause and evidence, and lessons learned feed straight into CAPA.

  27. A.5.27Learning from information security incidents

    Use what incidents teach you to strengthen controls.

    In QULDEXIncidents are logged with root cause and evidence, and lessons learned feed straight into CAPA.

  28. A.5.28Collection of evidence

    Identify, collect and preserve evidence related to security events.

    In QULDEXIncidents are logged with root cause and evidence, and lessons learned feed straight into CAPA.

  29. A.5.29Information security during disruption

    Keep information security at an appropriate level during disruption.

    In QULDEXRestore and continuity tests are scheduled, and results are attached as evidence for the auditor to sample.

  30. A.5.30ICT readiness for business continuityNew

    Plan, implement and test ICT readiness against continuity objectives.

    In QULDEXRestore and continuity tests are scheduled, and results are attached as evidence for the auditor to sample.

    Typical evidence
    ICT continuity plan, recovery objectives, test results
    Maps to
    SOC 2 A1.2NIST RC.RP-01

  31. A.5.31Legal, statutory, regulatory and contractual requirements

    Identify and meet the legal, regulatory and contractual requirements that apply to security.

    In QULDEXLegal and privacy obligations map once and also count toward ISO 27701, GDPR and DPDP programmes.

  32. A.5.32Intellectual property rights

    Protect intellectual property rights.

    In QULDEXQULDEX gives this control an owner, a review cycle and an evidence request, and maps it to every framework you run.

  33. A.5.33Protection of records

    Protect records from loss, destruction, falsification and unauthorised access.

    In QULDEXQULDEX gives this control an owner, a review cycle and an evidence request, and maps it to every framework you run.

  34. A.5.34Privacy and protection of PII

    Meet the requirements for privacy and protection of personal data.

    In QULDEXLegal and privacy obligations map once and also count toward ISO 27701, GDPR and DPDP programmes.

  35. A.5.35Independent review of information security

    Have the approach to information security reviewed independently at planned intervals.

    In QULDEXQULDEX gives this control an owner, a review cycle and an evidence request, and maps it to every framework you run.

  36. A.5.36Compliance with policies, rules and standards for information security

    Check compliance with security policies and standards regularly.

    In QULDEXQULDEX gives this control an owner, a review cycle and an evidence request, and maps it to every framework you run.

  37. A.5.37Documented operating procedures

    Document operating procedures and make them available to the people who need them.

    In QULDEXQULDEX gives this control an owner, a review cycle and an evidence request, and maps it to every framework you run.

6 · People controls 8

  1. A.6.1Screening

    Run background checks on candidates before they join and on an ongoing basis, in proportion to risk.

    In QULDEXHR evidence is requested from owners on schedule and stored once for all frameworks.

  2. A.6.2Terms and conditions of employment

    State security responsibilities in employment contracts.

    In QULDEXHR evidence is requested from owners on schedule and stored once for all frameworks.

  3. A.6.3Information security awareness, education and training

    Give personnel security awareness, education and training.

    In QULDEXTraining completion is imported as evidence and checked against headcount in scope.

    Typical evidence
    Training plan, completion records, phishing test results
    Maps to
    SOC 2 CC1.4CC2.2NIST PR.AT-01PCI Req 12.6

  4. A.6.4Disciplinary process

    Formalise a disciplinary process for policy violations.

    In QULDEXHR evidence is requested from owners on schedule and stored once for all frameworks.

  5. A.6.5Responsibilities after termination or change of employment

    Define the security duties that remain after someone leaves or changes role.

    In QULDEXHR evidence is requested from owners on schedule and stored once for all frameworks.

  6. A.6.6Confidentiality or non-disclosure agreements

    Use confidentiality or non-disclosure agreements that reflect your needs.

    In QULDEXHR evidence is requested from owners on schedule and stored once for all frameworks.

  7. A.6.7Remote working

    Protect information accessed, processed or stored while working remotely.

    In QULDEXHR evidence is requested from owners on schedule and stored once for all frameworks.

  8. A.6.8Information security event reporting

    Give personnel a way to report observed or suspected security events promptly.

    In QULDEXIncidents are logged with root cause and evidence, and lessons learned feed straight into CAPA.

7 · Physical controls 14

  1. A.7.1Physical security perimeters

    Define and use security perimeters around areas holding information assets.

    In QULDEXInspection records and photos attach to the control, per site for multi-site scopes.

  2. A.7.2Physical entry

    Protect secure areas with entry controls and access points.

    In QULDEXInspection records and photos attach to the control, per site for multi-site scopes.

  3. A.7.3Securing offices, rooms and facilities

    Design and apply physical security for offices, rooms and facilities.

    In QULDEXInspection records and photos attach to the control, per site for multi-site scopes.

  4. A.7.4Physical security monitoringNew

    Monitor premises continuously for unauthorised physical access.

    In QULDEXInspection records and photos attach to the control, per site for multi-site scopes.

    Typical evidence
    CCTV or alarm coverage map, monitoring logs, retention settings
    Maps to
    NIST DE.CM-02PCI Req 9.4

  5. A.7.5Protecting against physical and environmental threats

    Protect against natural disasters and other physical and environmental threats.

    In QULDEXInspection records and photos attach to the control, per site for multi-site scopes.

  6. A.7.6Working in secure areas

    Apply security measures for working in secure areas.

    In QULDEXInspection records and photos attach to the control, per site for multi-site scopes.

  7. A.7.7Clear desk and clear screen

    Enforce clear desk rules for papers and media, and clear screen rules for devices.

    In QULDEXInspection records and photos attach to the control, per site for multi-site scopes.

  8. A.7.8Equipment siting and protection

    Site equipment securely and protect it.

    In QULDEXInspection records and photos attach to the control, per site for multi-site scopes.

  9. A.7.9Security of assets off-premises

    Protect assets used off-site.

    In QULDEXInspection records and photos attach to the control, per site for multi-site scopes.

  10. A.7.10Storage media

    Manage storage media through acquisition, use, transport and disposal.

    In QULDEXInspection records and photos attach to the control, per site for multi-site scopes.

  11. A.7.11Supporting utilities

    Protect facilities from power failures and other utility disruptions.

    In QULDEXInspection records and photos attach to the control, per site for multi-site scopes.

  12. A.7.12Cabling security

    Protect power and data cables from interception, interference or damage.

    In QULDEXInspection records and photos attach to the control, per site for multi-site scopes.

  13. A.7.13Equipment maintenance

    Maintain equipment correctly so it stays available and secure.

    In QULDEXInspection records and photos attach to the control, per site for multi-site scopes.

  14. A.7.14Secure disposal or re-use of equipment

    Remove sensitive data and licensed software before equipment is disposed of or re-used.

    In QULDEXInspection records and photos attach to the control, per site for multi-site scopes.

8 · Technological controls 34

  1. A.8.1User endpoint devices

    Protect information stored on, processed by or reached through user endpoint devices.

    In QULDEXExports from your systems attach as evidence, and each test result is kept for auditor sampling.

  2. A.8.2Privileged access rights

    Restrict and manage the allocation of privileged access rights.

    In QULDEXAccess reviews run as recurring tasks. Reviewers sign off in QULDEX and every revocation becomes a tracked action.

  3. A.8.3Information access restriction

    Restrict access to information and applications according to the access control policy.

    In QULDEXExports from your systems attach as evidence, and each test result is kept for auditor sampling.

  4. A.8.4Access to source code

    Manage read and write access to source code, development tools and libraries.

    In QULDEXExports from your systems attach as evidence, and each test result is kept for auditor sampling.

  5. A.8.5Secure authentication

    Implement secure authentication technologies and procedures, such as MFA.

    In QULDEXExports from your systems attach as evidence, and each test result is kept for auditor sampling.

    Typical evidence
    MFA configuration, identity provider policy screenshots
    Maps to
    SOC 2 CC6.1NIST PR.AA-03PCI Req 8

  6. A.8.6Capacity management

    Monitor and adjust resource use to meet current and expected capacity needs.

    In QULDEXExports from your systems attach as evidence, and each test result is kept for auditor sampling.

  7. A.8.7Protection against malware

    Implement protection against malware, backed by user awareness.

    In QULDEXExports from your systems attach as evidence, and each test result is kept for auditor sampling.

  8. A.8.8Management of technical vulnerabilities

    Identify technical vulnerabilities, evaluate your exposure and act on it.

    In QULDEXScan reports attach each cycle, and overdue vulnerabilities become CAPA items with owners.

    Typical evidence
    Vulnerability scan reports, patch SLAs, remediation tickets
    Maps to
    SOC 2 CC7.1NIST ID.RA-01PCI Req 6.311.3

    A.8.8 explained on the blog →

  9. A.8.9Configuration managementNew

    Establish, document, monitor and review configurations, including security settings.

    In QULDEXExports from your systems attach as evidence, and each test result is kept for auditor sampling.

    Typical evidence
    Hardening baselines, configuration drift reports
    Maps to
    SOC 2 CC8.1NIST PR.PS-01PCI Req 2.2

  10. A.8.10Information deletionNew

    Delete information when it is no longer needed.

    In QULDEXExports from your systems attach as evidence, and each test result is kept for auditor sampling.

    Typical evidence
    Retention schedule, deletion logs, disposal certificates
    Maps to
    SOC 2 C1.2NIST PR.DS-01

  11. A.8.11Data maskingNew

    Mask data in line with the access control policy and legal requirements.

    In QULDEXExports from your systems attach as evidence, and each test result is kept for auditor sampling.

    Typical evidence
    Masking rules, test-data procedure, screenshots of masked fields
    Maps to
    SOC 2 C1.1NIST PR.DS-01PCI Req 3.4

  12. A.8.12Data leakage preventionNew

    Apply data leakage prevention to systems, networks and devices that hold sensitive information.

    In QULDEXExports from your systems attach as evidence, and each test result is kept for auditor sampling.

    Typical evidence
    DLP policy, rule set, alert review records
    Maps to
    SOC 2 CC6.7NIST PR.DS-01

  13. A.8.13Information backup

    Keep backups of information, software and systems, and test them regularly.

    In QULDEXRestore and continuity tests are scheduled, and results are attached as evidence for the auditor to sample.

    Typical evidence
    Backup schedule, job logs, restore test results
    Maps to
    SOC 2 A1.2NIST PR.DS-11

    A.8.13 explained on the blog →

  14. A.8.14Redundancy of information processing facilities

    Build in enough redundancy to meet availability requirements.

    In QULDEXRestore and continuity tests are scheduled, and results are attached as evidence for the auditor to sample.

  15. A.8.15Logging

    Produce, store, protect and analyse logs of activities, exceptions and faults.

    In QULDEXLog review evidence is collected on schedule and sampled by auditors in the same workspace.

    Typical evidence
    Logging standard, SIEM retention settings, log review records
    Maps to
    SOC 2 CC7.2NIST PR.PS-04PCI Req 10

    A.8.15 explained on the blog →

  16. A.8.16Monitoring activitiesNew

    Monitor networks, systems and applications for anomalous behaviour and act on it.

    In QULDEXLog review evidence is collected on schedule and sampled by auditors in the same workspace.

    Typical evidence
    Monitoring use cases, alert triage records
    Maps to
    SOC 2 CC7.2NIST DE.CM-01PCI Req 10.4

  17. A.8.17Clock synchronization

    Synchronise system clocks to approved time sources.

    In QULDEXExports from your systems attach as evidence, and each test result is kept for auditor sampling.

  18. A.8.18Use of privileged utility programs

    Restrict and tightly control utility programs that can override system controls.

    In QULDEXExports from your systems attach as evidence, and each test result is kept for auditor sampling.

  19. A.8.19Installation of software on operational systems

    Manage software installation on operational systems securely.

    In QULDEXExports from your systems attach as evidence, and each test result is kept for auditor sampling.

  20. A.8.20Networks security

    Secure, manage and control networks and network devices.

    In QULDEXExports from your systems attach as evidence, and each test result is kept for auditor sampling.

  21. A.8.21Security of network services

    Identify, implement and monitor security mechanisms and service levels for network services.

    In QULDEXExports from your systems attach as evidence, and each test result is kept for auditor sampling.

  22. A.8.22Segregation of networks

    Segregate groups of information services, users and systems on networks.

    In QULDEXExports from your systems attach as evidence, and each test result is kept for auditor sampling.

  23. A.8.23Web filteringNew

    Manage access to external websites to reduce exposure to malicious content.

    In QULDEXExports from your systems attach as evidence, and each test result is kept for auditor sampling.

    Typical evidence
    Web filter policy, category blocks, exception approvals
    Maps to
    NIST PR.IR-01

  24. A.8.24Use of cryptography

    Define and apply rules for using cryptography, including key management.

    In QULDEXExports from your systems attach as evidence, and each test result is kept for auditor sampling.

  25. A.8.25Secure development life cycle

    Set rules for the secure development of software and systems.

    In QULDEXExports from your systems attach as evidence, and each test result is kept for auditor sampling.

  26. A.8.26Application security requirements

    Identify, specify and approve security requirements when developing or buying applications.

    In QULDEXExports from your systems attach as evidence, and each test result is kept for auditor sampling.

  27. A.8.27Secure system architecture and engineering principles

    Establish and apply principles for engineering secure systems.

    In QULDEXExports from your systems attach as evidence, and each test result is kept for auditor sampling.

  28. A.8.28Secure codingNew

    Apply secure coding principles to software development.

    In QULDEXExports from your systems attach as evidence, and each test result is kept for auditor sampling.

    Typical evidence
    Secure coding standard, code review records, SAST results
    Maps to
    SOC 2 CC8.1NIST PR.PS-06PCI Req 6.2

  29. A.8.29Security testing in development and acceptance

    Define and run security testing during development and acceptance.

    In QULDEXExports from your systems attach as evidence, and each test result is kept for auditor sampling.

  30. A.8.30Outsourced development

    Direct, monitor and review outsourced system development.

    In QULDEXExports from your systems attach as evidence, and each test result is kept for auditor sampling.

  31. A.8.31Separation of development, test and production environments

    Separate and secure development, test and production environments.

    In QULDEXExports from your systems attach as evidence, and each test result is kept for auditor sampling.

  32. A.8.32Change management

    Put changes to systems and processing facilities through change management.

    In QULDEXExports from your systems attach as evidence, and each test result is kept for auditor sampling.

  33. A.8.33Test information

    Select, protect and manage test information appropriately.

    In QULDEXExports from your systems attach as evidence, and each test result is kept for auditor sampling.

  34. A.8.34Protection of information systems during audit testing

    Plan and agree audit tests on operational systems with management to limit disruption.

    In QULDEXExports from your systems attach as evidence, and each test result is kept for auditor sampling.

Control numbers and titles follow ISO/IEC 27002:2022. Summaries are QULDEX paraphrases; the standard's text is the authority.

Certification path

How do you get ISO 27001 certified?

Build and run the ISMS first, then an accredited certification body audits it in two stages. Most organisations of 50–250 people take 6 to 12 months from scoping to certificate. The steps below are in the order auditors expect them.

  1. Define scope and run a gap assessment

    Decide which locations, teams, systems and services the ISMS covers (clause 4.3), then compare current practice with clauses 4–10 and Annex A.

  2. Assess risk and write the Statement of Applicability

    Identify risks to confidentiality, integrity and availability, choose treatments, and record every Annex A control as included or excluded with a reason.

  3. Implement controls and collect evidence

    Assign an owner to each control, put it into operation, and keep the records that prove it ran: access reviews, logs, training records, supplier assessments.

  4. Run an internal audit and management review

    Clause 9 must have operated at least once before certification. Fix what the internal audit finds and record the corrective actions.

  5. Stage 1 audit: design and documents

    The certification body checks that your scope, risk process, SoA and mandatory documents exist and that you're ready for Stage 2.

    1–3 days on site or remote
  6. Stage 2 audit: controls in operation

    Auditors sample evidence to confirm controls operate as designed. Major nonconformities must be closed before the certificate is issued; minor ones need an accepted action plan.

    Audit days set by headcountMajor vs minor nonconformity →
  7. Keep it running for three years

    Year 1Surveillance audit
    Year 2Surveillance audit
    Year 3Recertification audit

Durations are typical planning ranges from QULDEX audit delivery, not requirements of the standard. They vary with scope, headcount and how much of the ISMS already exists.

Documented information

Which documents does ISO 27001 require?

ISO 27001 names the documented information you must keep. Auditors ask for these first in Stage 1, so they are the minimum set to have ready.

Document or recordClauseWhere it lives in QULDEX
ISMS scope4.3Program setup
Information security policy5.2Evidence vault · policy library
Risk assessment and risk treatment process6.1.2 · 6.1.3Risk register
Statement of Applicability6.1.3 dControl library (generated)
Information security objectives6.2Program dashboard
Evidence of competence7.2Evidence vault · training records
Operational planning and control records8.1Control workflows
Risk assessment and risk treatment results8.2 · 8.3Risk register
Monitoring and measurement results9.1Readiness reports
Internal audit programme and results9.2Audit workspace
Management review results9.3Audit workspace
Nonconformities and corrective actions10.2CAPA automation

Annex A controls add their own records (for example access reviews for 5.18 or logs for 8.15) where your SoA includes them. Start from the free Statement of Applicability template, read how to write the SoA, or see the forum answer on justifying excluded controls.

Time and cost

How long does ISO 27001 take and what drives the cost?

First certification usually takes 6 to 12 months. Cost depends mostly on scope and headcount, because ISO/IEC 27006 sets the minimum number of auditor days by the number of people working in the ISMS scope.

Where the months go

Scope and gap2–4 wk
Risk and SoA3–6 wk
Implement controls2–6 mo
Internal audit, review3–6 wk
Stage 1 + Stage 24–8 wk

Bars show the upper end of each range on one scale (6 months = full width).

What changes the effort

  • People in scope: the main driver of certification-body audit days
  • Number of sites: multi-site programmes need sampling plans
  • Existing frameworks: SOC 2 or ISO 9001 evidence cuts implementation time
  • Cloud and suppliers: controls 5.19–5.23 grow with each critical provider
  • Evidence maturity: scattered evidence is the most common cause of delay
Readiness check · 2 minutes

Are you ready for an ISO 27001 Stage 1 audit?

Stage 1 auditors look for eight things before anything else. Answer them to see where you stand and which gaps to close first. Nothing you enter leaves this page.

4.3Is your ISMS scope written down and approved?
5.2Do you have an approved information security policy?
6.1.2Have you run a documented risk assessment in the last 12 months?
6.1.3Do you have a Statement of Applicability covering all 93 controls?
A.5.2Does every control you apply have a named owner?
7.5Is your evidence stored in one place and linked to controls?
9.2Have you completed an internal audit of the ISMS?
9.3Has top management held a documented management review?
Crosswalk

How ISO 27001 maps to SOC 2, NIST CSF 2.0 and PCI DSS

Most ISO 27001 controls have a direct counterpart in other frameworks, so one tested control and one evidence item can satisfy several audits. QULDEX keeps this mapping in its pre-mapped control library.

ISO 27001 vs SOC 2 at a glance

ISO 27001SOC 2
What it isInternational management-system standardAttestation report on controls (AICPA)
Who issues itAccredited certification bodyLicensed CPA firm
What you getPublic certificateRestricted-use report, Type I or Type II
Validity3 years, annual surveillance auditsCovers a set period; usually renewed yearly
Where it's asked forWorldwide; strongest in Europe, the Middle East and AsiaMostly North America
ScopeThe ISMS plus Annex A controls chosen by riskTrust services criteria you select; Security is always in
In QULDEXOne control set and one evidence vault serve both. Test a control once and it counts toward both reports.

Control crosswalk

ISO 27001:2022SOC 2 (TSC 2017)NIST CSF 2.0PCI DSS v4.0.1Shared evidence
A.5.15 Access controlCC6.1 · CC6.3PR.AA-05Req 7Access policy, role matrix
A.5.18 Access rightsCC6.2 · CC6.3PR.AA-05Req 7.2Quarterly access review export
A.8.5 Secure authenticationCC6.1PR.AA-03Req 8MFA configuration, IdP settings
A.8.8 Technical vulnerabilitiesCC7.1ID.RA-01Req 6.3 · 11.3Scan reports, patch tickets
A.8.15 LoggingCC7.2PR.PS-04Req 10SIEM retention settings, log review
A.5.24–5.26 Incident managementCC7.3–CC7.5RS.MA-01Req 12.10Incident plan, post-incident reviews
A.5.19–5.22 Supplier securityCC9.2GV.SC-07Req 12.8Supplier risk assessments, contracts
A.6.3 Awareness trainingCC1.4 · CC2.2PR.AT-01Req 12.6Training completion records

Indicative mapping for planning. The full crosswalk, aligned to NIST's published informative references, is in the QULDEX control library.

Where QULDEX fits

How QULDEX runs ISO 27001 from scope to certificate

QULDEX is ISO 27001 compliance and audit management software built from EGV Group's audit delivery. It's used on both sides of the audit: by the organisation getting certified, and by the auditors who test it. Pick your role to see who does what.

For companies building their first ISMS or renewing a certificate.

  1. Scope and riskDecide the scope and accept the risksGuided scope setup, a risk register, and the SoA generated from your decisions
  2. Implement controlsRun the controls day to dayAll 93 controls pre-loaded with owners, due dates and reminders
  3. Collect evidenceUpload files or export from your toolsEvidence linked to controls once and reused for SOC 2, ISO 27701 and ISO 42001
  4. Internal auditYour internal auditor tests the ISMSTest sheets, sampling and findings that flow into CAPA
  5. Certification auditThe certification body audits youControlled, logged evidence sharing with the auditor, with no zip files over email
  6. Surveillance yearsKeep the ISMS runningA live readiness view, so surveillance prep takes days, not weeks
Without one systemWith QULDEX
Spreadsheets with unclear control ownersEvery control has an owner and an approval gate
Evidence scattered across drives and emailEvidence mapped to controls and review checkpoints
Readiness reports built by hand before auditsA live, traceable record auditors can sample
Separate effort for SOC 2 and ISO 27701Test once, report against each framework
10+years of audit delivery500+audits deliveredBoth sidesof the audit on one platformRBACand a full audit trail on every action
FAQ

ISO 27001 questions people ask

Is ISO 27001 certification mandatory?

No. ISO 27001 is voluntary. It becomes a practical requirement when customers, tenders or regulators ask for it, which is common in SaaS, financial services, healthcare and government supply chains.

Do we have to implement all 93 Annex A controls?

No. You include the controls your risk assessment needs and record each decision in the Statement of Applicability. Auditors accept exclusions that are justified and consistent with your risks.

What is the difference between ISO 27001 and ISO 27002?

ISO 27001 holds the requirements you are certified against. ISO 27002 is guidance that explains how to implement each Annex A control. You can't be certified to ISO 27002.

Is the 2013 version of ISO 27001 still valid?

No. The transition period ended on 31 October 2025, and certificates to ISO/IEC 27001:2013 are no longer valid. Organisations must hold a 2022 certificate.

What changed in ISO 27001 Amendment 1:2024?

The amendment adds climate change to clause 4. You now decide whether climate change is a relevant issue for the ISMS and whether interested parties have climate-related requirements. Annex A did not change.

What is the difference between ISO 27001 and SOC 2?

ISO 27001 certifies a management system against an international standard and results in a public certificate. SOC 2 is an attestation report by a CPA firm against AICPA trust services criteria, mostly requested in North America. Many controls overlap.

Can QULDEX run ISO 27001 alongside other frameworks?

Yes. Controls and evidence are mapped once in the control library, so the same work supports SOC 2, ISO 27701, ISO 42001, NIST CSF 2.0 and others, each with its own report.

Sources

References

  1. ISO/IEC 27001:2022, Information security, cybersecurity and privacy protection: Information security management systems: Requirements. iso.org
  2. ISO/IEC 27001:2022/Amd 1:2024, Climate action changes. iso.org
  3. ISO/IEC 27002:2022, Information security controls. iso.org
  4. ISO/IEC 27006-1:2024, Requirements for bodies providing audit and certification of ISMS. iso.org
  5. IAF MD 26:2023, Transition requirements for ISO/IEC 27001:2022. iaf.nu
  6. NIST Cybersecurity Framework 2.0 and informative references. nist.gov
  7. AICPA 2017 Trust Services Criteria (revised points of focus, 2022). aicpa-cima.com

Reviewed by

Abhishek Yadav

Lead Auditor · QULDEX

Reviewed this page against ISO/IEC 27001:2022 and Amendment 1:2024: requirements, Annex A summaries, certification path, mandatory documents and the crosswalk.

Page history
  • : Added Amendment 1:2024, Annex A summaries, readiness check and SOC 2 comparison. Reviewed by Abhishek Yadav
  • : Page first published

Find your ISO 27001 gaps in 15 minutes

Answer a short readiness check and get a gap summary by clause and Annex A theme. No sales call needed to see the result.

Schedule
Book a Demo