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.
What you need to know about ISO 27001
Who needs ISO 27001?
No law requires it, but these situations usually make it a requirement in practice.
QULDEX helps here first: the readiness check shows how far you are from Stage 1 before you commit budget.
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.
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 programmeLeadership
Top-management commitment, security policy, roles and authorities.
In QULDEX: Policy approvals with named owners and full sign-off historyPlanning
Risk assessment, risk treatment, Statement of Applicability, objectives.
In QULDEX: Risk register decisions generate the Statement of ApplicabilitySupport
Resources, competence, awareness, communication, documented information.
In QULDEX: Training and competence records kept in the evidence vaultOperation
Run the risk treatment plan and control planned changes.
In QULDEX: Control tasks run on schedule with evidence attachedEvaluation
Monitoring and measurement, internal audit, management review.
In QULDEX: Internal audit workspace and management review packsImprovement
Nonconformity, corrective action, continual improvement.
In QULDEX: Findings flow into CAPA with owners, due dates and verificationWhat 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.
Showing all 93 controls. Select a control to see what it requires.
5 · Organisational controls 37
A.5.1Policies for information securityDefine, 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.
A.5.2Information security roles and responsibilitiesDefine 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.
A.5.3Segregation of dutiesSeparate 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.
A.5.4Management responsibilitiesManagement 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.
A.5.5Contact with authoritiesEstablish 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.
A.5.6Contact with special interest groupsMaintain 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.
A.5.7Threat intelligenceNewCollect 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
A.5.8Information security in project managementIntegrate 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.
A.5.9Inventory of information and other associated assetsKeep 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.
A.5.10Acceptable use of information and other associated assetsDocument 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.
A.5.11Return of assetsGet 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.
A.5.12Classification of informationClassify 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.
A.5.13Labelling of informationLabel 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.
A.5.14Information transferApply 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.
A.5.15Access controlSet 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.16Identity managementManage 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.
A.5.17Authentication informationControl 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.
A.5.18Access rightsProvision, 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.19Information security in supplier relationshipsManage 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
A.5.20Addressing information security within supplier agreementsAgree 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.
A.5.21Managing information security in the ICT supply chainManage 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.
A.5.22Monitoring, review and change management of supplier servicesMonitor 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.
A.5.23Information security for use of cloud servicesNewSet 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
A.5.24Information security incident management planning and preparationPlan 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
A.5.25Assessment and decision on information security eventsAssess 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.
A.5.26Response to information security incidentsRespond to incidents according to documented procedures.
In QULDEXIncidents are logged with root cause and evidence, and lessons learned feed straight into CAPA.
A.5.27Learning from information security incidentsUse what incidents teach you to strengthen controls.
In QULDEXIncidents are logged with root cause and evidence, and lessons learned feed straight into CAPA.
A.5.28Collection of evidenceIdentify, collect and preserve evidence related to security events.
In QULDEXIncidents are logged with root cause and evidence, and lessons learned feed straight into CAPA.
A.5.29Information security during disruptionKeep 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.
A.5.30ICT readiness for business continuityNewPlan, 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
A.5.31Legal, statutory, regulatory and contractual requirementsIdentify 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.
A.5.32Intellectual property rightsProtect 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.
A.5.33Protection of recordsProtect 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.
A.5.34Privacy and protection of PIIMeet 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.
A.5.35Independent review of information securityHave 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.
A.5.36Compliance with policies, rules and standards for information securityCheck 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.
A.5.37Documented operating proceduresDocument 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
A.6.1ScreeningRun 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.
A.6.2Terms and conditions of employmentState security responsibilities in employment contracts.
In QULDEXHR evidence is requested from owners on schedule and stored once for all frameworks.
A.6.3Information security awareness, education and trainingGive 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
A.6.4Disciplinary processFormalise a disciplinary process for policy violations.
In QULDEXHR evidence is requested from owners on schedule and stored once for all frameworks.
A.6.5Responsibilities after termination or change of employmentDefine 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.
A.6.6Confidentiality or non-disclosure agreementsUse confidentiality or non-disclosure agreements that reflect your needs.
In QULDEXHR evidence is requested from owners on schedule and stored once for all frameworks.
A.6.7Remote workingProtect information accessed, processed or stored while working remotely.
In QULDEXHR evidence is requested from owners on schedule and stored once for all frameworks.
A.6.8Information security event reportingGive 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
A.7.1Physical security perimetersDefine and use security perimeters around areas holding information assets.
In QULDEXInspection records and photos attach to the control, per site for multi-site scopes.
A.7.2Physical entryProtect secure areas with entry controls and access points.
In QULDEXInspection records and photos attach to the control, per site for multi-site scopes.
A.7.3Securing offices, rooms and facilitiesDesign and apply physical security for offices, rooms and facilities.
In QULDEXInspection records and photos attach to the control, per site for multi-site scopes.
A.7.4Physical security monitoringNewMonitor 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
A.7.5Protecting against physical and environmental threatsProtect against natural disasters and other physical and environmental threats.
In QULDEXInspection records and photos attach to the control, per site for multi-site scopes.
A.7.6Working in secure areasApply security measures for working in secure areas.
In QULDEXInspection records and photos attach to the control, per site for multi-site scopes.
A.7.7Clear desk and clear screenEnforce 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.
A.7.8Equipment siting and protectionSite equipment securely and protect it.
In QULDEXInspection records and photos attach to the control, per site for multi-site scopes.
A.7.9Security of assets off-premisesProtect assets used off-site.
In QULDEXInspection records and photos attach to the control, per site for multi-site scopes.
A.7.10Storage mediaManage storage media through acquisition, use, transport and disposal.
In QULDEXInspection records and photos attach to the control, per site for multi-site scopes.
A.7.11Supporting utilitiesProtect facilities from power failures and other utility disruptions.
In QULDEXInspection records and photos attach to the control, per site for multi-site scopes.
A.7.12Cabling securityProtect power and data cables from interception, interference or damage.
In QULDEXInspection records and photos attach to the control, per site for multi-site scopes.
A.7.13Equipment maintenanceMaintain equipment correctly so it stays available and secure.
In QULDEXInspection records and photos attach to the control, per site for multi-site scopes.
A.7.14Secure disposal or re-use of equipmentRemove 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
A.8.1User endpoint devicesProtect 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.
A.8.2Privileged access rightsRestrict 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.
A.8.3Information access restrictionRestrict 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.
A.8.4Access to source codeManage 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.
A.8.5Secure authenticationImplement 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
A.8.6Capacity managementMonitor 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.
A.8.7Protection against malwareImplement protection against malware, backed by user awareness.
In QULDEXExports from your systems attach as evidence, and each test result is kept for auditor sampling.
A.8.8Management of technical vulnerabilitiesIdentify 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.9Configuration managementNewEstablish, 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
A.8.10Information deletionNewDelete 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
A.8.11Data maskingNewMask 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
A.8.12Data leakage preventionNewApply 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
A.8.13Information backupKeep 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.14Redundancy of information processing facilitiesBuild 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.
A.8.15LoggingProduce, 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.16Monitoring activitiesNewMonitor 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
A.8.17Clock synchronizationSynchronise system clocks to approved time sources.
In QULDEXExports from your systems attach as evidence, and each test result is kept for auditor sampling.
A.8.18Use of privileged utility programsRestrict 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.
A.8.19Installation of software on operational systemsManage software installation on operational systems securely.
In QULDEXExports from your systems attach as evidence, and each test result is kept for auditor sampling.
A.8.20Networks securitySecure, manage and control networks and network devices.
In QULDEXExports from your systems attach as evidence, and each test result is kept for auditor sampling.
A.8.21Security of network servicesIdentify, 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.
A.8.22Segregation of networksSegregate 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.
A.8.23Web filteringNewManage 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
A.8.24Use of cryptographyDefine 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.
A.8.25Secure development life cycleSet 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.
A.8.26Application security requirementsIdentify, 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.
A.8.27Secure system architecture and engineering principlesEstablish and apply principles for engineering secure systems.
In QULDEXExports from your systems attach as evidence, and each test result is kept for auditor sampling.
A.8.28Secure codingNewApply 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
A.8.29Security testing in development and acceptanceDefine 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.
A.8.30Outsourced developmentDirect, monitor and review outsourced system development.
In QULDEXExports from your systems attach as evidence, and each test result is kept for auditor sampling.
A.8.31Separation of development, test and production environmentsSeparate and secure development, test and production environments.
In QULDEXExports from your systems attach as evidence, and each test result is kept for auditor sampling.
A.8.32Change managementPut 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.
A.8.33Test informationSelect, protect and manage test information appropriately.
In QULDEXExports from your systems attach as evidence, and each test result is kept for auditor sampling.
A.8.34Protection of information systems during audit testingPlan 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.
No control matches that search.
Control numbers and titles follow ISO/IEC 27002:2022. Summaries are QULDEX paraphrases; the standard's text is the authority.
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.
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.
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.
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.
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.
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.
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.
Keep it running for three years
Year 1Surveillance auditYear 2Surveillance auditYear 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.
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 record | Clause | Where it lives in QULDEX |
|---|---|---|
| ISMS scope | 4.3 | Program setup |
| Information security policy | 5.2 | Evidence vault · policy library |
| Risk assessment and risk treatment process | 6.1.2 · 6.1.3 | Risk register |
| Statement of Applicability | 6.1.3 d | Control library (generated) |
| Information security objectives | 6.2 | Program dashboard |
| Evidence of competence | 7.2 | Evidence vault · training records |
| Operational planning and control records | 8.1 | Control workflows |
| Risk assessment and risk treatment results | 8.2 · 8.3 | Risk register |
| Monitoring and measurement results | 9.1 | Readiness reports |
| Internal audit programme and results | 9.2 | Audit workspace |
| Management review results | 9.3 | Audit workspace |
| Nonconformities and corrective actions | 10.2 | CAPA 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.
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
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
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.
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 27001 | SOC 2 | |
|---|---|---|
| What it is | International management-system standard | Attestation report on controls (AICPA) |
| Who issues it | Accredited certification body | Licensed CPA firm |
| What you get | Public certificate | Restricted-use report, Type I or Type II |
| Validity | 3 years, annual surveillance audits | Covers a set period; usually renewed yearly |
| Where it's asked for | Worldwide; strongest in Europe, the Middle East and Asia | Mostly North America |
| Scope | The ISMS plus Annex A controls chosen by risk | Trust services criteria you select; Security is always in |
| In QULDEX | One control set and one evidence vault serve both. Test a control once and it counts toward both reports. | |
Control crosswalk
| ISO 27001:2022 | SOC 2 (TSC 2017) | NIST CSF 2.0 | PCI DSS v4.0.1 | Shared evidence |
|---|---|---|---|---|
| A.5.15 Access control | CC6.1 · CC6.3 | PR.AA-05 | Req 7 | Access policy, role matrix |
| A.5.18 Access rights | CC6.2 · CC6.3 | PR.AA-05 | Req 7.2 | Quarterly access review export |
| A.8.5 Secure authentication | CC6.1 | PR.AA-03 | Req 8 | MFA configuration, IdP settings |
| A.8.8 Technical vulnerabilities | CC7.1 | ID.RA-01 | Req 6.3 · 11.3 | Scan reports, patch tickets |
| A.8.15 Logging | CC7.2 | PR.PS-04 | Req 10 | SIEM retention settings, log review |
| A.5.24–5.26 Incident management | CC7.3–CC7.5 | RS.MA-01 | Req 12.10 | Incident plan, post-incident reviews |
| A.5.19–5.22 Supplier security | CC9.2 | GV.SC-07 | Req 12.8 | Supplier risk assessments, contracts |
| A.6.3 Awareness training | CC1.4 · CC2.2 | PR.AT-01 | Req 12.6 | Training completion records |
Indicative mapping for planning. The full crosswalk, aligned to NIST's published informative references, is in the QULDEX control library.
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.
- Scope and riskDecide the scope and accept the risksGuided scope setup, a risk register, and the SoA generated from your decisions
- Implement controlsRun the controls day to dayAll 93 controls pre-loaded with owners, due dates and reminders
- Collect evidenceUpload files or export from your toolsEvidence linked to controls once and reused for SOC 2, ISO 27701 and ISO 42001
- Internal auditYour internal auditor tests the ISMSTest sheets, sampling and findings that flow into CAPA
- Certification auditThe certification body audits youControlled, logged evidence sharing with the auditor, with no zip files over email
- Surveillance yearsKeep the ISMS runningA live readiness view, so surveillance prep takes days, not weeks
For advisors and audit teams running ISO 27001 for several clients or business units.
- Scope and riskRun the gap assessmentOne gap-assessment template reused for every client
- Implement controlsGuide the client teamYour methodology saved as a reusable control set
- Collect evidenceChase and review evidenceEvidence requests with review and approval states, so nothing lives in inboxes
- Internal auditTest and reportAudit programme, sampling, findings and CAPA follow-up in one place
- Certification auditPrepare the clientAn audit-ready pack the client can share with the certification body
- Surveillance yearsStay on retainerOne dashboard across all clients and their next audit dates
For accredited bodies and external auditors running Stage 1, Stage 2 and surveillance audits.
- Audit planningPlan audit days and the teamScope and SoA received in a standard format, with a multi-auditor workspace
- Stage 1Review documents and readinessDocument review with comments tied to clauses
- Stage 2Sample evidence and test controlsView-only evidence access with download control and a full access log
- FindingsGrade nonconformitiesMajor and minor findings recorded against clauses and controls
- DecisionIssue or withhold the certificateA complete, traceable audit record for the certification decision
- Surveillance and recertificationReturn each yearHistory across the 3-year cycle kept in one workspace
Pre-mapped control library
All 93 Annex A controls with owners, test steps and the crosswalk to 50+ frameworks.
Explore → EvidenceSecure evidence vault
Evidence linked to controls and findings, with upload, review and approval history.
Explore → RiskRisk register
Clause 6 risk assessment and treatment, with the SoA generated from decisions.
Explore → FindingsCAPA remediation
Nonconformities from internal and certification audits tracked to closure.
Explore →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.
Go deeper on ISO 27001
ISO 27001:2022 transition: what changed
The 11 new controls, the restructured Annex A, and what auditors check now.
blog.quldex.comISO 27001 nonconformities: major vs minor, with worked examples
How auditors grade findings and what each one does to your certificate.
blog.quldex.comAudit evidence naming convention
A file-naming scheme that lets auditors sample evidence without asking.
blog.quldex.comAudit sampling size for compliance
How many samples auditors pull per control, and why.
More on the blog: all ISO 27001 articles · Annex A control explainers
References
- ISO/IEC 27001:2022, Information security, cybersecurity and privacy protection: Information security management systems: Requirements. iso.org
- ISO/IEC 27001:2022/Amd 1:2024, Climate action changes. iso.org
- ISO/IEC 27002:2022, Information security controls. iso.org
- ISO/IEC 27006-1:2024, Requirements for bodies providing audit and certification of ISMS. iso.org
- IAF MD 26:2023, Transition requirements for ISO/IEC 27001:2022. iaf.nu
- NIST Cybersecurity Framework 2.0 and informative references. nist.gov
- AICPA 2017 Trust Services Criteria (revised points of focus, 2022). aicpa-cima.com
Reviewed by
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.