Markdown Editor

Stage 2 Audit Evidence Index Template (ISO/IEC 27001)

Stage 2 audit workbook: evidence index per clause and Annex A theme, sampling populations, interview schedule, evidence rules, debrief log, closing notes

ISMS und ISO/IEC 27001VollständigISO/IEC 27001:2022 + Amd 1:2024 clauses 4 to 10 and Annex A (cited only); ISO/IEC 17021-1:2015; ISO/IEC 27006-1:2024stageauditevidenceindex

Anleitung: Use it between Stage 1 and Stage 2 and live during the audit week. Fill the clause index and the sampling populations first. The main pitfall is pointing to policies instead of dated records that show the ISMS operates.

Vorschau

Stage 2 Audit Evidence Index: [Organization name]

Evidence index and audit-week workbook for the Stage 2 certification audit of the information security management system (ISMS) of [Organization name] against ISO/IEC 27001:2022 + Amd 1:2024. It lists where the evidence for each clause (4 to 10) and each Annex A theme sits, prepares the populations auditors sample from, sets the interview schedule and the rules for the audit room and for remote evidence, and keeps the daily debrief log and the closing meeting notes. Stage 2 is run by the certification body (CB) under ISO/IEC 17021-1:2015 and ISO/IEC 27006-1:2024. Replace every [bracketed] value and every row marked Example.

Document control

FieldValue
Document IDDOC-ISMS-092
Version[1.0]
Status[Draft / In review / In use during audit / Final]
Owner[@isms-manager]
Approvers/reviewers[@ciso], [@ceo]
Last updatedYYYY-MM-DD
Classification[Confidential]
Standard and editionISO/IEC 27001:2022 + Amd 1:2024; CB rules ISO/IEC 17021-1:2015 and ISO/IEC 27006-1:2024
Certification body and audit team[CB name], lead auditor [name], auditors [names], technical expert [name or none]
Audit dates and mode[YYYY-MM-DD to YYYY-MM-DD, on site / remote / mixed]
SoA version auditedDOC-ISMS-011, version [n]
Evidence period[YYYY-MM-DD to YYYY-MM-DD]
Next scheduled review[Before first surveillance audit, YYYY-MM-DD]

Approvals

RoleNameDecisionDate
ISMS manager[@isms-manager][Index complete]YYYY-MM-DD
Top management[@ceo][Ready for Stage 2]YYYY-MM-DD

Revision history

VersionDateAuthorChange
0.1 (Example)2027-04-19[@isms-manager]Clause and Annex A index built from DOC-ISMS-033
1.0 (Example)2027-05-07[@isms-manager]Populations refreshed to 2027-05-07, interview schedule confirmed
1.1 (Example)2027-05-12[@isms-manager]Debrief log and closing meeting notes added

Contents

  1. Purpose and how to use
  2. Audit team, roles and evidence flow
  3. Audit room and remote evidence rules
  4. Evidence index by clause
  5. Evidence index by Annex A theme
  6. Sampling readiness
  7. Interview schedule
  8. Daily debrief log
  9. Findings raised during the audit
  10. Closing meeting notes
  11. Size tiers
  12. Records and evidence
  13. References

1. Purpose and how to use

Stage 2 evaluates the implementation and effectiveness of the ISMS: that the processes in clauses 4 to 10 run as documented, that the applicable controls in the Statement of Applicability operate, and that the ISMS achieves its objectives. The audit team follows its own audit plan and samples records; this index lets the audit guide find any piece of evidence within minutes and shows the team exactly what was shown.

How to use it:

  1. Build sections 4 and 5 from DOC-ISMS-033 (control evidence matrix) and check each link opens the current record.
  2. Refresh section 6 populations to a cut-off date shortly before Stage 2.
  3. Confirm section 7 with every interviewee and a deputy.
  4. During the audit, log each request and what was shown (section 2 flow), and fill section 8 at the end of each day.
  5. After the closing meeting, move findings to isms/certification-findings-action-plan and keep this file as the audit record.

2. Audit team, roles and evidence flow

RoleNameResponsibility
Audit guide[@isms-manager]Accompanies the audit team, introduces interviewees, keeps time
Evidence runner[@name]Retrieves records from systems and the document store
Scribe[@name]Logs each request, the evidence shown and any open request in the request log
Process owners[@owners]Answer questions on their process and show records
Top management representative[@ceo]Leadership interview, opening and closing meetings

Request log format:

Req IDTimeAuditorRequestClause or controlEvidence shownShown byOpen follow-up
REQ-001 (Example)2027-05-10 10:40Lead auditorLast access review of production cloud accountsA.5.18, A.8.2Q2 access review record, 3 removals with tickets[@head-of-engineering-ops]None
REQ-002 (Example)2027-05-10 11:15Lead auditorTraining record for two persons flagged at Stage 17.3Completion records dated 2027-05-03[@hr-lead]None
[REQ-NNN][time][auditor][request][ref][record][@name][follow-up]

3. Audit room and remote evidence rules

On-site audit room

  • Room booked for all audit days, with a screen, power and guest network only; no access to internal networks for auditor devices.
  • Visitors signed in, badged and escorted outside the audit room (DOC-ISMS-055 physical security policy).
  • A clean desk in the room: only the evidence being discussed is on the table or the screen (DOC-ISMS-056).
  • Printed evidence is collected and shredded at the end of each day, unless the auditor needs a copy under the CB's confidentiality terms.

Remote evidence

  • Show evidence by screen share from the live system or the document store by default.
  • Files are shared only when the auditor needs a copy for the audit file, through the channel agreed in the CB contract, under DOC-ISMS-043 (information transfer policy).
  • Personal data, secrets, full vulnerability details and customer data are shown, not sent; redact where a copy is unavoidable.
  • No recording of sessions unless both parties agree in writing.
  • Confirm the identity of every participant at the start of each call.
Evidence classShow on screenProvide a copyCondition
Policies and proceduresYesYesRead-only export with version
Records with no personal data (for example change tickets)YesOn requestThrough agreed channel
Records with personal data (for example HR screening)YesNoShow a sample, no copies
Security configuration and vulnerability dataYesNoShow live or redacted
Customer contractsExtracts onlyNoCommercial terms hidden

4. Evidence index by clause

ClauseWhat the auditor typically checksEvidence (record, ID, location)OwnerStatus
4.1Internal and external issues identified, including the climate change decision (Amd 1:2024)DOC-ISMS-003, steering minute approving it[@isms-manager][Ready / Gap]
4.2Interested parties and their relevant requirements, including any climate-related onesDOC-ISMS-003, DOC-ISMS-014[@isms-manager][Ready / Gap]
4.3Scope boundaries, interfaces and dependencies match realityDOC-ISMS-002, network and cloud diagrams[@isms-manager][Ready / Gap]
4.4ISMS processes and their interactions establishedDOC-ISMS-004 process map[@isms-manager][Ready / Gap]
5.1Top management leadership shown in practiceSteering committee minutes (DOC-ISMS-007), budget approval, interview[@ceo][Ready / Gap]
5.2Policy approved, communicated and availableDOC-ISMS-001, communication record, intranet page[@ceo][Ready / Gap]
5.3Roles and authorities assigned and communicatedDOC-ISMS-006, appointment records[@ceo][Ready / Gap]
6.1.1Risks and opportunities for the ISMS consideredDOC-ISMS-017[@isms-manager][Ready / Gap]
6.1.2Risk assessment performed with defined criteria, repeatable resultsDOC-ISMS-010, DOC-ISMS-015, DOC-ISMS-016[@isms-manager][Ready / Gap]
6.1.3Treatment selected, SoA justified, plan approved, residual risk accepted by risk ownersDOC-ISMS-011, DOC-ISMS-013, DOC-ISMS-019Risk owners[Ready / Gap]
6.2Objectives measurable, planned, monitoredDOC-ISMS-024, measurement results[@ciso][Ready / Gap]
6.3Changes to the ISMS plannedDOC-ISMS-025 change plan, change records[@isms-manager][Ready / Gap]
7.1Resources providedDOC-ISMS-031 budget and resource plan[@cfo][Ready / Gap]
7.2Competence determined and evidencedDOC-ISMS-026, certificates, training records[@hr-lead][Ready / Gap]
7.3Awareness of policy, contribution and consequencesAwareness completion records, interviews with staff[@hr-lead][Ready / Gap]
7.4Communication planned and doneDOC-ISMS-027, communication log[@isms-manager][Ready / Gap]
7.5Documented information controlledDOC-ISMS-028, version history samples[@isms-manager][Ready / Gap]
8.1Processes planned and controlled, outsourced processes controlledDOC-ISMS-032 calendar, operating procedures, supplier reviews[@isms-manager][Ready / Gap]
8.2Risk assessments at planned intervals and on changeDated risk assessment results[@isms-manager][Ready / Gap]
8.3Risk treatment plan implementedDOC-ISMS-013 status with completed actionsRisk owners[Ready / Gap]
9.1Monitoring and measurement results analysedDOC-ISMS-080, DOC-ISMS-081[@isms-manager][Ready / Gap]
9.2Internal audit programme run by objective, competent auditorsDOC-ISMS-082, DOC-ISMS-084, auditor competence[@internal-auditor][Ready / Gap]
9.3Management review covers all inputs and records decisionsDOC-ISMS-085[@ceo][Ready / Gap]
10.1Continual improvement shownDOC-ISMS-088 continual improvement register[@isms-manager][Ready / Gap]
10.2Nonconformities handled, root cause, effectiveness checkedDOC-ISMS-087, DOC-ISMS-086[@isms-manager][Ready / Gap]

5. Evidence index by Annex A theme

5.1 A.5 Organizational controls (37)

ControlsTopicEvidence (record, ID, location)OwnerStatus
A.5.1 to A.5.4Policies, roles, segregation of duties, management responsibilityDOC-ISMS-005 policy index with review dates, DOC-ISMS-006[@ciso][Ready / Gap]
A.5.5, A.5.6Contacts with authorities and special interest groupsDOC-ISMS-069[@ciso][Ready / Gap]
A.5.7Threat intelligence (new in 2022)DOC-ISMS-045, monthly triage log[@security-lead][Ready / Gap]
A.5.8Security in projectsDOC-ISMS-046 completed checklists for sampled projects[@pmo-lead][Ready / Gap]
A.5.9 to A.5.14Assets, acceptable use, return, classification, labelling, transferDOC-ISMS-012, DOC-ISMS-040, DOC-ISMS-042, DOC-ISMS-043, leaver asset returns[@it-lead][Ready / Gap]
A.5.15 to A.5.18Access rules, identities, authentication, access rightsDOC-ISMS-041, joiner and leaver tickets, quarterly access reviews[@it-lead][Ready / Gap]
A.5.19 to A.5.23Suppliers, agreements, ICT supply chain, monitoring, cloud services (A.5.23 new in 2022)DOC-ISMS-066, DOC-ISMS-067 assessments, DOC-ISMS-068, DOC-ISMS-044[@procurement-lead][Ready / Gap]
A.5.24 to A.5.28Incident management and evidenceDOC-ISMS-020, DOC-ISMS-021 entries, DOC-ISMS-022 reviews[@security-lead][Ready / Gap]
A.5.29, A.5.30Security during disruption, ICT readiness (A.5.30 new in 2022)DOC-ISMS-121, DOC-ISMS-047, DR test report[@head-of-engineering-ops][Ready / Gap]
A.5.31 to A.5.34Legal requirements, intellectual property, records, privacyDOC-ISMS-014, licence inventory, retention schedule, records of processing[@legal-lead], [@dpo][Ready / Gap]
A.5.35 to A.5.37Independent review, compliance checks, operating proceduresDOC-ISMS-048, compliance check records, DOC-ISMS-049[@isms-manager][Ready / Gap]

5.2 A.6 People controls (8)

ControlsTopicEvidenceOwnerStatus
A.6.1, A.6.2Screening and employment termsDOC-ISMS-050, sample of screening records (shown, not copied), contract template[@hr-lead][Ready / Gap]
A.6.3Awareness and trainingTraining completion report for the evidence period[@hr-lead][Ready / Gap]
A.6.4, A.6.5Disciplinary process, duties after leavingDOC-ISMS-052, DOC-ISMS-053 completed checklists[@hr-lead][Ready / Gap]
A.6.6Confidentiality agreementsDOC-ISMS-051 signed samples[@legal-lead][Ready / Gap]
A.6.7Remote workingDOC-ISMS-054, device compliance report[@it-lead][Ready / Gap]
A.6.8Event reportingDOC-ISMS-023, reports received in the incident register[@security-lead][Ready / Gap]

5.3 A.7 Physical controls (14)

ControlsTopicEvidenceOwnerStatus
A.7.1 to A.7.6Perimeters, entry, secure areas, monitoring (A.7.4 new in 2022), environmental threatsDOC-ISMS-055, badge access logs, visitor log, colocation provider assurance (DOC-ISMS-079)[@facilities-lead][Ready / Gap]
A.7.7Clear desk and clear screenDOC-ISMS-056, walk-round check records[@facilities-lead][Ready / Gap]
A.7.8 to A.7.13Equipment, off-site assets, media, utilities, cabling, maintenanceAsset records, maintenance logs, cloud provider assurance for hosted equipment[@it-lead][Ready / Gap]
A.7.14Disposal and reuseDOC-ISMS-057 disposal records and certificates[@it-lead][Ready / Gap]

5.4 A.8 Technological controls (34)

ControlsTopicEvidenceOwnerStatus
A.8.1Endpoint devicesDOC-ISMS-058, MDM compliance report[@it-lead][Ready / Gap]
A.8.2 to A.8.5Privileged access, access restriction, source code access, authenticationPrivileged account list and review, MFA coverage report, repository permissions[@head-of-engineering-ops][Ready / Gap]
A.8.6CapacityCapacity reviews, monitoring dashboards[@head-of-engineering-ops][Ready / Gap]
A.8.7, A.8.8Malware, vulnerabilitiesDOC-ISMS-059, EDR coverage report, DOC-ISMS-072 remediation tracker with SLA results[@security-lead][Ready / Gap]
A.8.9 to A.8.12Configuration, deletion, masking, leakage prevention (all new in 2022)DOC-ISMS-060 baseline with drift report, deletion records, DOC-ISMS-062[@security-lead][Ready / Gap]
A.8.13, A.8.14Backup, redundancyDOC-ISMS-061, DOC-ISMS-071 restore test log, region failover test[@head-of-engineering-ops][Ready / Gap]
A.8.15 to A.8.17Logging, monitoring (A.8.16 new in 2022), clock synchronisationLogging standard, DOC-ISMS-064 alert triage records, time source configuration[@security-lead][Ready / Gap]
A.8.18, A.8.19Privileged utilities, software installationAllow-list configuration, change records[@it-lead][Ready / Gap]
A.8.20 to A.8.23Network security, network services, segregation, web filtering (A.8.23 new in 2022)DOC-ISMS-063, firewall rule review, filtering policy report[@head-of-engineering-ops][Ready / Gap]
A.8.24CryptographyCryptography standard, DOC-ISMS-070 key register[@security-lead][Ready / Gap]
A.8.25 to A.8.31Secure development, requirements, architecture, secure coding (A.8.28 new in 2022), testing, outsourced development, environment separationDOC-ISMS-065, pull request reviews, SAST and dependency scan results, DOC-ISMS-077[@engineering-lead][Ready / Gap]
A.8.32Change managementSample of change tickets with approvals[@head-of-engineering-ops][Ready / Gap]
A.8.33, A.8.34Test information, protection during audit testingTest data rules, approval for any audit testing on production[@engineering-lead][Ready / Gap]

6. Sampling readiness

Example populations (Example: Quillmere Analytics Ltd, evidence period 2027-01-04 to 2027-05-07; leavers over the 12 months to 2027-05-07):

Pop IDPopulationSource systemFields in the listCount (Example)Ready
POP-01Joiners (employees and contractors)HR system, supplier registerName, start date, role, screening date, NDA date, training date9[Yes / No]
POP-02Leavers (12 months)HR systemName, end date, account disable date per system, asset return date11[Yes / No]
POP-03Role changesHR systemName, date, old role, new role, access change ticket3[Yes / No]
POP-04Production changesChange and deployment toolID, date, approver, test evidence, rollback plan186[Yes / No]
POP-05Security events and incidentsDOC-ISMS-021ID, date, severity, status, closure date13[Yes / No]
POP-06Vulnerabilities rated high or criticalDOC-ISMS-072ID, discovered, fixed, SLA met27[Yes / No]
POP-07Privileged accountsIdentity provider, cloud consoleAccount, owner, last review14[Yes / No]
POP-08Critical suppliersDOC-ISMS-066Supplier, service, last assessment, contract clauses9[Yes / No]
POP-09Backup restore testsDOC-ISMS-071Date, system, result, time to restore6[Yes / No]
POP-10Endpoint devicesMDMDevice, owner, encryption, OS version, compliance state52[Yes / No]

Consistency checks before the audit:

  • POP-01 joiners plus existing staff minus POP-02 leavers equals the current scope headcount (46 persons: 38 employees, 8 contractors).
  • Every POP-05 incident has a matching entry in DOC-ISMS-022 where a post-incident review was required.
  • Every POP-06 item has a fix date or an approved exception (security/security-exception-request).

7. Interview schedule

Example schedule (Example: Quillmere Analytics Ltd, Stage 2 of 3.5 audit days over three calendar days, 2027-05-10 to 2027-05-12; a second auditor joins for half a day on day 2):

Day and timeSessionIntervieweeDeputyClauses and controls
Day 1, 09:00Opening meeting[@ceo], [@isms-manager][@ciso]Audit plan, scope confirmation
Day 1, 09:45Leadership, context, policy[@ceo][@coo]4.1 to 5.3
Day 1, 11:00Risk assessment and treatment[@isms-manager][@coo]6.1, 8.2, 8.3, SoA
Day 1, 14:00Objectives, measurement, resources[@isms-manager][@cfo]6.2, 7.1, 9.1
Day 2, 09:00People controls and HR[@hr-lead][@coo]7.2, 7.3, A.6
Day 2, 11:00Access, identities, endpoints[@it-lead][@head-of-engineering-ops]A.5.15 to A.5.18, A.8.1 to A.8.5
Day 2, 14:00Cloud operations, backup, logging[@head-of-engineering-ops][@engineering-lead]A.5.23, A.8.13 to A.8.17
Day 2, 14:00 (second auditor)Secure development and change[@engineering-lead][@head-of-engineering-ops]A.8.25 to A.8.32
Day 2, 16:00Office walk-round[@facilities-lead][@isms-manager]A.7
Day 3, 09:00Suppliers and legal[@procurement-lead], [@legal-lead][@coo]A.5.19 to A.5.22, A.5.31 to A.5.34
Day 3, 10:15Incidents, continuity, threat intelligence[@security-lead][@isms-manager]A.5.7, A.5.24 to A.5.30
Day 3, 11:30Internal audit, management review, improvement[@internal-auditor], [@ceo][@isms-manager]9.2, 9.3, 10
Day 3, 13:30Auditor preparation timeNoneNoneCB internal review
Day 3, 15:00Closing meeting[@ceo], [@isms-manager], process owners[@ciso]Findings, recommendation, next steps

8. Daily debrief log

DayDateAreas coveredPotential findings raised by auditorOpen requestsOur actions overnightOwner
1 (Example)2027-05-104 to 6, 7.1, 9.1One objective has no result for April; no record of risk owner approval of the treatment plan DOC-ISMS-013 or of acceptance for the High residual risksREQ-007: risk acceptance for R-018Retrieve signed acceptance ACC-001 from DOC-ISMS-019, add April result with explanation, collect any approval records[@isms-manager]
2 (Example)2027-05-117.2, 7.3, A.6, A.5.15 to A.5.18, A.8.1 to A.8.5, A.5.23, A.8.13 to A.8.17, A.8.25 to A.8.32, A.71 of 10 sampled leavers kept access to the support ticketing tool for 9 days (target 1 business day)NonePrepare root cause and corrective action proposal[@it-lead]
[n]YYYY-MM-DD[areas][findings][REQ-NNN][actions][@owner]

9. Findings raised during the audit

IDCB refGrade (CB)RequirementFinding summaryObjective evidenceNext step
S2F-001 (Example)NC-01Major nonconformity6.1.3No record that risk owners approved the risk treatment plan or accepted residual risks; 14 High risks without acceptance (CBF-2027-01 in DOC-ISMS-093)DOC-ISMS-013 v0.9 unsigned, DOC-ISMS-016 exportCorrection, root cause and corrective action, with implementation verified by the CB before the decision, Example: evidence within 90 days as set by the CB
S2F-002 (Example)NC-02Minor nonconformityA.5.181 of 10 sampled leavers kept access to the support ticketing tool for 9 days after the leaving date (CBF-2027-02 in DOC-ISMS-093)POP-02 sample, ticketing tool audit logCorrection and corrective action plan in isms/certification-findings-action-plan, Example: submitted to CB within the period the CB sets (for example 30 days)
S2F-003 to S2F-008 (Example)NC-03, NC-04, OFI-01 to OFI-042 minor nonconformities, 4 opportunities for improvementA.5.19, 7.2, 9.1, A.8.16, A.5.7, 7.4See CBF-2027-03 to CBF-2027-08 in DOC-ISMS-093 section 4As recorded by the CBPlans for the minors; decisions recorded for each OFI
[S2F-NNN][ref][grade][ref][summary][evidence][step]

10. Closing meeting notes

FieldValue
Date and time[YYYY-MM-DD hh:mm]
Attendees[names and roles]
Scope confirmed[Yes / No, with changes]
Sampling statement by CB[The audit was based on samples; findings may exist that were not found]
Findings presentedExample: 1 major, 3 minor, 4 opportunities for improvement
Deadlines stated by CBExample: correction and corrective action plan for all nonconformities within 30 days (2027-06-11) and evidence for the major NC-01 within 90 days (2027-08-10), as set by the CB
Audit team recommendation[Recommended for certification subject to acceptance of corrective action plans / Not recommended / Follow-up visit needed]
Expected certification decision and certificate date[as stated by the CB]
First surveillance auditNo later than 12 months from the certification decision date; Example: planned for [month]
Questions raised by us and answers[notes]
Actions for usTransfer findings to DOC-ISMS-093, brief top management, update DOC-ISMS-094 certification cycle plan

11. Size tiers

AspectSmall: Quillmere Analytics Ltd (Example)Medium: Quillmere Health Systems (Example)Large: Quillmere Group (Example)
Profile46 persons, one office plus remote staff, one cloud provider in two regions320 staff, two offices, one colocation suite2,400 staff, 6 sites in 4 countries, OT and IT, ISO 9001 and ISO 22301 certified
Audit teamOne lead auditorLead auditor plus one auditor, possibly a health-sector technical expertSeveral auditors in parallel tracks, site visits by sample under ISO/IEC 27006-1 and IAF MD 1:2023 (Global ACI-TECH-3-001)
Evidence coordinationISMS manager (0.5 FTE) as guide, one runnerISMS manager as guide, security team as runners, one scribeCentral evidence desk in the CISO office, site coordinators, shared request log across sites
PopulationsAbout 10, small countsAbout 15, including colocation access and clinical customer contractsPer site and per function, including OT change and remote access populations
Audit roomRemote with office walk-roundOne office as audit base, visit to the colocation suiteAudit room at each visited site, daily cross-site debrief
Integrated auditNoneISO/IEC 27701:2025 extension planned for next yearCombined with ISO 9001 and ISO 22301 under IAF MD 11:2023 (Global ACI-TECH-3-008) if the CB agrees

12. Records and evidence

RecordOwnerLocationRetention
This evidence index, final version[@isms-manager][ISMS document store, restricted]Certification cycle + 3 years (Example)
Request log (section 2)Scribe[ISMS document store, restricted]Certification cycle + 3 years
Copies given to the CB, with redaction notes[@isms-manager][ISMS document store, restricted]Certification cycle + 3 years
Daily debrief log and closing meeting notes[@isms-manager][ISMS document store]Certification cycle + 3 years
CB audit plan and audit report[@isms-manager][ISMS document store]Certification cycle + 3 years
Findings and corrective action records[@isms-manager]DOC-ISMS-093, DOC-ISMS-086, DOC-ISMS-087Certification cycle + 3 years

Keep the permanent control-to-evidence links in isms/control-evidence-matrix (DOC-ISMS-033) and register these records in DOC-ISMS-028.

13. References

ReferenceEditionUse
ISO/IEC 27001:2022 (https://www.iso.org/standard/82875.html)2022Clauses 4 to 10 and Annex A
ISO/IEC 27001:2022/Amd 1:2024 (https://www.iso.org/standard/88435.html)2024-02-23Climate change in 4.1 and 4.2
ISO/IEC 27002:2022 (https://www.iso.org/standard/75652.html)2022Control guidance
ISO/IEC 17021-1:2015 (https://www.iso.org/standard/61651.html)2015Stage 2, findings, certification decision
ISO/IEC 27006-1:2024 (https://www.iso.org/standard/82908.html)2024ISMS audit requirements, multi-site
ISO/IEC 27007:2020 (https://www.iso.org/standard/77802.html)2020, under revisionISMS auditing guidance
ISO 19011:2026 (https://www.iso.org/standard/88984.html)2026Auditing management systems
IAF MD 1:2023 and IAF MD 4:2025, re-issued as Global ACI-TECH-3-001 and Global ACI-TECH-3-003Issue 3 each; Global ACI v1.0 in force 28 Aug 2026 (check the current issue)Multi-site sampling, remote audit techniques

Related templates: isms/stage-1-readiness-pack, isms/certification-findings-action-plan, isms/certification-cycle-plan, isms/control-evidence-matrix, isms/audit-findings-register, isms/surveillance-readiness-health-check, compliance/statement-of-applicability, compliance/capa-nonconformity, isms/certification-audit-explained.

Standard and licence note

Structure aligned with ISO/IEC 27001:2022 + Amd 1:2024 (clauses 4 to 10 and Annex A themes) and with the Stage 2 requirements for certification bodies in ISO/IEC 17021-1:2015 and ISO/IEC 27006-1:2024. The index, audit focus summaries, rules and examples are original; control labels are short descriptions written for this library, and no ISO/IEC text is reproduced. ISO and IEC standards are copyrighted: obtain the official text from ISO (https://www.iso.org/standard/82875.html) or your national standards body. Check the current editions and your certification body's audit plan and rules before use. Using this index does not guarantee certification; the certification decision belongs to the certification body. Template licence: MIT.

Ähnliche Vorlagen