Markdown Editor

Control Evidence Matrix Template (ISO/IEC 27001 Clauses and 93 Controls)

Evidence register for clauses 4 to 10 and all 93 Annex A controls: owner, record, location, frequency, last collected, status, Stage 2 and surveillance use

SMSI & ISO/IEC 27001CompletISO/IEC 27001:2022 + Amd 1:2024 clauses 4 to 10, Annex A (cited only); ISO/IEC 27002:2022; ISO/IEC 17021-1:2015controlevidencematrix

Mode d'emploi: Use it from the first approved SoA to track who produces which record for every clause and control. Fill owner and evidence for each applicable control first, then the location codes. The main pitfall is citing a policy as evidence instead of a record that shows the control operated.

Aperçu

Control Evidence Matrix: [Organization name] ISMS

One register that shows, for every requirement of ISO/IEC 27001:2022 + Amd 1:2024 clauses 4 to 10 and every one of the 93 Annex A controls, who owns the evidence, which record proves the requirement or control operates, where that record is kept, how often it is produced, when it was last collected and its status. It is the working index behind the Statement of Applicability (DOC-ISMS-011), the Stage 2 audit evidence index (DOC-ISMS-092) and every surveillance audit. Control labels are short descriptions written for this library, not official titles. Replace every [bracketed] value and every row marked Example.

Document control

FieldValue
Document ID[DOC-ISMS-033]
Version[1.0]
Status[Draft / In review / Approved / Superseded]
Owner[@isms-manager]
Approvers/reviewers[@ciso], [@internal-audit]
Last updatedYYYY-MM-DD
Classification[Internal / Confidential]
Standard and editionISO/IEC 27001:2022 + Amd 1:2024 (clauses 4 to 10, Annex A); control guidance ISO/IEC 27002:2022
SoA version reflected[DOC-ISMS-011 version x.y, dated YYYY-MM-DD]
ISMS scope reference[DOC-ISMS-002]
Snapshot frozen for audit[Stage 2 / Surveillance YYYY, snapshot date YYYY-MM-DD]
Next scheduled reviewYYYY-MM-DD

Approvals

RoleNameDecisionDate
ISMS owner[@isms-manager][Prepared]YYYY-MM-DD
Chief information security officer[@ciso][Reviewed]YYYY-MM-DD
Internal audit[@internal-audit][Reviewed for completeness]YYYY-MM-DD

Revision history

VersionDateAuthorChange
1.0 (Example)YYYY-MM-DD[@isms-manager]First complete matrix aligned with SoA v1.0
1.1 (Example)YYYY-MM-DD[@isms-manager]Snapshot frozen for the Stage 2 audit; A.8.12 evidence changed to DLP alert review
[x.y]YYYY-MM-DD[@author][Change summary]

Contents

  1. Purpose and how the matrix works
  2. Status values and frequency codes
  3. Evidence locations
  4. Clauses 4 to 10
  5. Annex A organizational controls (A.5)
  6. Annex A people controls (A.6)
  7. Annex A physical controls (A.7)
  8. Annex A technological controls (A.8)
  9. Summary and health of the evidence
  10. Using the matrix for Stage 2 and surveillance audits
  11. Size tiers
  12. Records and maintenance of the matrix
  13. References

1. Purpose and how the matrix works

The matrix answers the question every auditor asks: "show me". For each requirement and control it records:

  • Owner: the role accountable for producing the evidence (usually the control owner named in DOC-ISMS-006).
  • Evidence: the record type that proves operation, not only design.
  • Location: where the record is kept, using the codes in section 3.
  • Frequency: how often a new record is produced (codes in section 2).
  • Last collected: date of the most recent record.
  • Status: whether the evidence is current (section 2).

2. Status values and frequency codes

StatusMeaning
CollectedA record exists for the current period and is stored in its location
DueThe next record is due within the next 30 days
OverdueThe record for the period was not produced on time
GapThe control is applicable but no record type is defined or produced yet
Not applicableExcluded in the SoA; the reason is in DOC-ISMS-011 section 5
CodeFrequency
CContinuous or per event (each joiner, change, incident)
MMonthly
QQuarterly
HHalf-yearly
AAnnual
EOn a trigger only (change of scope, new supplier, new project)

3. Evidence locations

CodeLocationOwnerTypical retention (Example)
DMSDocument management system (policies, procedures, minutes, reports)ISMS managerCurrent plus superseded versions for 3 years
GRCGRC tool or ISMS workbook (registers, risk, SoA, audit findings)ISMS manager3 years
IDPIdentity provider and access governance exportsIT operations lead1 year of logs, reviews 3 years
TKTTicketing system (changes, access requests, incidents, actions)IT operations lead3 years
HRHR system (screening, contracts, training, leavers)HR leadPer employment law, as in DOC-ISMS-028
LMSLearning platform (awareness, training completion)HR lead3 years
MDMEndpoint and device management consoleEndpoint leadMonthly reports kept 1 year
VULVulnerability scanner and remediation tracker (DOC-ISMS-072)Vulnerability lead3 years
SIEMLog management and security monitoring platformSecurity operations leadLogs [12 months], review records 3 years
CLDCloud provider consoles and posture tool reportsCloud lead1 year of reports
REPOSource code platform (reviews, pipelines, branch rules)Engineering leadLife of the repository
FACFacilities records (badges, visitor logs, CCTV retention, maintenance)Facilities leadPer local rules, CCTV [30 days]

4. Clauses 4 to 10

ClauseRequirement (short label)OwnerEvidenceLoc.Freq.Last collectedStatus
4.1 (Example)Internal and external issues, including whether climate change is relevantISMS managerContext register DOC-ISMS-003 with review record and climate change determinationDMSA2027-04-06Collected
4.2Interested parties and their requirementsISMS managerInterested parties table in DOC-ISMS-003DMSAYYYY-MM-DD[status]
4.3ISMS scopeISMS managerApproved scope DOC-ISMS-002DMSA, EYYYY-MM-DD[status]
4.4ISMS established and maintainedISMS managerProcess map DOC-ISMS-004, ISMS manual DOC-ISMS-008 (optional)DMSAYYYY-MM-DD[status]
5.1Leadership and commitmentTop managementSteering committee minutes, resource approvalsDMSQYYYY-MM-DD[status]
5.2 (Example)Information security policyTop managementApproved policy DOC-ISMS-001, publication and acknowledgement recordsDMS, LMSA2027-05-12Collected
5.3Roles, responsibilities and authoritiesTop managementRACI DOC-ISMS-006, appointment recordsDMSAYYYY-MM-DD[status]
6.1.1Actions to address risks and opportunitiesISMS managerRisk and opportunity entries in the registerGRCQYYYY-MM-DD[status]
6.1.2Risk assessment processISMS managerMethodology DOC-ISMS-010, risk criteria DOC-ISMS-015DMSAYYYY-MM-DD[status]
6.1.3Risk treatment process and SoAISMS managerTreatment plan DOC-ISMS-013, SoA DOC-ISMS-011, risk owner approvalsGRCA, EYYYY-MM-DD[status]
6.2Information security objectivesISMS managerObjectives register DOC-ISMS-024 with progressGRCQYYYY-MM-DD[status]
6.3Planning of changes to the ISMSISMS managerChange plan DOC-ISMS-025 (good practice; no record is mandated)DMSEYYYY-MM-DD[status]
7.1ResourcesTop managementBudget and resource plan DOC-ISMS-031DMSAYYYY-MM-DD[status]
7.2CompetenceHR leadCompetence matrix DOC-ISMS-026, certificates, training recordsHR, LMSAYYYY-MM-DD[status]
7.3AwarenessHR leadAwareness completion, policy acknowledgementsLMSA, CYYYY-MM-DD[status]
7.4CommunicationISMS managerCommunication plan DOC-ISMS-027 and sent communicationsDMSQYYYY-MM-DD[status]
7.5Documented informationISMS managerDocumented information register DOC-ISMS-028, version historyDMSQYYYY-MM-DD[status]
8.1Operational planning and controlISMS managerAnnual calendar DOC-ISMS-032, outsourced process controlsDMSAYYYY-MM-DD[status]
8.2Risk assessments performedISMS managerRisk assessment report DOC-ISMS-017, register snapshotGRCA, EYYYY-MM-DD[status]
8.3Risk treatment implementedISMS managerTreatment plan status, closure evidence per actionGRCQYYYY-MM-DD[status]
9.1 (Example)Monitoring, measurement, analysis and evaluationISMS managerMeasurement programme DOC-ISMS-080, performance report DOC-ISMS-081DMSQ2027-07-21Collected
9.2Internal auditInternal audit leadAudit programme DOC-ISMS-082, audit reports DOC-ISMS-084DMSAYYYY-MM-DD[status]
9.3Management reviewTop managementManagement review minutes DOC-ISMS-085DMSAYYYY-MM-DD[status]
10.1Continual improvementISMS managerImprovement register DOC-ISMS-088GRCQYYYY-MM-DD[status]
10.2Nonconformity and corrective actionISMS managerCAPA records DOC-ISMS-087, findings register DOC-ISMS-086GRCCYYYY-MM-DD[status]

5. Annex A organizational controls (A.5)

ControlShort label (not official title)OwnerEvidenceLoc.Freq.Last collectedStatus
A.5.1 (Example)Information security policiesISMS managerPolicy index DOC-ISMS-005 with review dates, approval recordsDMSA2027-05-12Collected
A.5.2Security roles and responsibilitiesISMS managerRACI DOC-ISMS-006, job descriptions with security dutiesDMS, HRAYYYY-MM-DD[status]
A.5.3Segregation of dutiesIT operations leadConflicting role matrix, access review exceptionsIDPQYYYY-MM-DD[status]
A.5.4Management responsibilities for securityTop managementSigned management commitments, briefing recordsDMSAYYYY-MM-DD[status]
A.5.5Contact with authoritiesISMS managerAuthority contact list DOC-ISMS-069, verification dateDMSAYYYY-MM-DD[status]
A.5.6Contact with special interest groupsSecurity leadMemberships and contact list in DOC-ISMS-069DMSAYYYY-MM-DD[status]
A.5.7 (Example)Threat intelligence (new in 2022)Security leadMonthly triage log and actions per DOC-ISMS-045GRCM2027-08-02Collected
A.5.8Security in project managementProject office leadCompleted project security checklists DOC-ISMS-046DMSCYYYY-MM-DD[status]
A.5.9Inventory of information and assetsIT operations leadAsset inventory DOC-ISMS-012, reconciliation reportGRCHYYYY-MM-DD[status]
A.5.10Acceptable use of information and assetsHR leadAUP DOC-ISMS-040 acknowledgementsLMSC, AYYYY-MM-DD[status]
A.5.11Return of assetsHR leadLeaver checklists DOC-ISMS-053 with returned asset listHRCYYYY-MM-DD[status]
A.5.12Information classificationData ownerClassification scheme, classified asset entriesDMS, GRCAYYYY-MM-DD[status]
A.5.13Information labellingData ownerLabelling procedure DOC-ISMS-042, label coverage sampleDMSAYYYY-MM-DD[status]
A.5.14Information transferSecurity leadTransfer agreements, secure transfer tool logs (DOC-ISMS-043)DMS, SIEMQYYYY-MM-DD[status]
A.5.15Access control rulesIAM leadAccess control policy DOC-ISMS-041, role definitionsDMSAYYYY-MM-DD[status]
A.5.16Identity lifecycle managementIAM leadJoiner, mover and leaver tickets reconciled with HRTKT, IDPMYYYY-MM-DD[status]
A.5.17Authentication information handlingIAM leadMFA coverage report, password manager enrolmentIDPMYYYY-MM-DD[status]
A.5.18 (Example)Access rights provisioning and reviewIT operations leadSigned quarterly access reviews for 6 systems, removal ticketsIDP, TKTQ2027-06-28Collected
A.5.19Security in supplier relationshipsProcurement leadSupplier register DOC-ISMS-066 with risk tierGRCAYYYY-MM-DD[status]
A.5.20Security in supplier agreementsProcurement leadSigned security clauses or agreements DOC-ISMS-068DMSEYYYY-MM-DD[status]
A.5.21ICT supply chain securityEngineering leadSoftware bill of materials, dependency review recordsREPOCYYYY-MM-DD[status]
A.5.22Supplier service monitoring and changeProcurement leadAnnual supplier reviews DOC-ISMS-067, assurance reportsGRCAYYYY-MM-DD[status]
A.5.23 (Example)Security for cloud service use (new in 2022)Cloud leadCloud policy DOC-ISMS-044, provider assurance report review, posture reportDMS, CLDA, M2027-07-30Collected
A.5.24Incident management planningIncident managerIncident response plan DOC-ISMS-020, exercise recordDMSAYYYY-MM-DD[status]
A.5.25Assessing security eventsSecurity operations leadTriage records with classification decisionsTKT, SIEMCYYYY-MM-DD[status]
A.5.26Responding to security incidentsIncident managerIncident register DOC-ISMS-021, incident ticketsTKTCYYYY-MM-DD[status]
A.5.27Learning from incidentsIncident managerPost-incident reviews DOC-ISMS-022, resulting actionsDMS, GRCCYYYY-MM-DD[status]
A.5.28Evidence collectionSecurity operations leadEvidence handling records, chain of custody formsTKTCYYYY-MM-DD[status]
A.5.29Security during disruptionContinuity leadBCP DOC-ISMS-121 with security measures, tabletop reportDMSAYYYY-MM-DD[status]
A.5.30ICT readiness for business continuity (new in 2022)IT operations leadICT readiness plan DOC-ISMS-047, DR test reportDMSAYYYY-MM-DD[status]
A.5.31Legal, regulatory and contractual requirementsLegal leadLegal register DOC-ISMS-014 with review recordGRCHYYYY-MM-DD[status]
A.5.32Intellectual property rightsLegal leadSoftware licence inventory, open source licence scanGRC, REPOHYYYY-MM-DD[status]
A.5.33Protection of recordsISMS managerRetention schedule, documented information register DOC-ISMS-028DMSAYYYY-MM-DD[status]
A.5.34 (Example)Privacy and PII protectionPrivacy leadRecords of processing as processor, DPA register, DPIA logGRCH2027-07-15Due
A.5.35Independent review of securityISMS managerIndependent review report DOC-ISMS-048 or internal audit reportDMSAYYYY-MM-DD[status]
A.5.36Compliance with security policies and standardsControl ownersCompliance checks, configuration compliance reports, exceptionsGRCQYYYY-MM-DD[status]
A.5.37Documented operating proceduresIT operations leadApproved operating procedures DOC-ISMS-049 with review datesDMSAYYYY-MM-DD[status]

6. Annex A people controls (A.6)

ControlShort label (not official title)OwnerEvidenceLoc.Freq.Last collectedStatus
A.6.1Pre-employment screeningHR leadScreening completion records per DOC-ISMS-050 (outcome only)HRCYYYY-MM-DD[status]
A.6.2Security terms in employment contractsHR leadSigned contracts or terms with security clauses (sample list)HRCYYYY-MM-DD[status]
A.6.3 (Example)Awareness, education and trainingHR leadLearning platform completion 45 of 46 staff (98%), phishing resultsLMSA, Q2027-07-25Collected
A.6.4Disciplinary processHR leadDisciplinary process DOC-ISMS-052, case log (anonymised count)HRAYYYY-MM-DD[status]
A.6.5Duties after leaving or changing roleHR leadLeaver reminders of continuing duties, signed exit formsHRCYYYY-MM-DD[status]
A.6.6Confidentiality agreementsLegal leadSigned NDAs DOC-ISMS-051, NDA review recordHR, DMSC, AYYYY-MM-DD[status]
A.6.7Remote workingIT operations leadRemote working policy DOC-ISMS-054 acknowledgements, device complianceLMS, MDMA, MYYYY-MM-DD[status]
A.6.8Reporting security eventsSecurity operations leadEvent reports received, reporting channel testTKTCYYYY-MM-DD[status]

7. Annex A physical controls (A.7)

ControlShort label (not official title)OwnerEvidenceLoc.Freq.Last collectedStatus
A.7.1Physical security perimetersFacilities leadSite security plan, perimeter inspection recordFACAYYYY-MM-DD[status]
A.7.2Physical entry controlsFacilities leadBadge access list reviews, visitor logsFACQYYYY-MM-DD[status]
A.7.3Securing offices, rooms and facilitiesFacilities leadRoom access design, lock and key registerFACAYYYY-MM-DD[status]
A.7.4 (Example)Physical security monitoring (new in 2022)Facilities leadOffice CCTV retention check, alarm test record; data centres via provider reportFAC, DMSQ2027-05-20Overdue
A.7.5Protection against physical and environmental threatsFacilities leadEnvironmental risk assessment, fire system inspectionFACAYYYY-MM-DD[status]
A.7.6Working in secure areasFacilities leadSecure area rules, access log reviewFACQYYYY-MM-DD[status]
A.7.7Clear desk and clear screenFacilities leadClear desk spot-check results DOC-ISMS-056, screen lock settingsFAC, MDMQYYYY-MM-DD[status]
A.7.8Equipment siting and protectionIT operations leadEquipment room inspection, rack inventoryFACAYYYY-MM-DD[status]
A.7.9Assets used off-premisesIT operations leadLaptop encryption and tracking reports, loss reportsMDMMYYYY-MM-DD[status]
A.7.10Storage mediaIT operations leadRemovable media control settings, media registerMDM, GRCQYYYY-MM-DD[status]
A.7.11Supporting utilitiesFacilities leadUPS and generator test records, provider reportsFACHYYYY-MM-DD[status]
A.7.12Cabling securityFacilities leadCabling inspection record, cabinet lock checkFACAYYYY-MM-DD[status]
A.7.13Equipment maintenanceIT operations leadMaintenance logs and contractsFAC, TKTCYYYY-MM-DD[status]
A.7.14Secure disposal or re-use of equipmentIT operations leadDisposal and reuse records DOC-ISMS-057, wipe certificatesGRCCYYYY-MM-DD[status]

8. Annex A technological controls (A.8)

ControlShort label (not official title)OwnerEvidenceLoc.Freq.Last collectedStatus
A.8.1 (Example)User endpoint devicesEndpoint leadMDM compliance export (encryption, OS version, screen lock) for all managed laptopsMDMM2027-08-01Collected
A.8.2Privileged access rightsIAM leadPrivileged account review, approval ticketsIDP, TKTQYYYY-MM-DD[status]
A.8.3Restricting access to informationIAM leadRole-based access configuration export, review resultsIDPQYYYY-MM-DD[status]
A.8.4Access to source codeEngineering leadRepository access list review, branch protection settingsREPOQYYYY-MM-DD[status]
A.8.5Secure authenticationIAM leadMFA and single sign-on coverage reportIDPMYYYY-MM-DD[status]
A.8.6Capacity managementIT operations leadCapacity reviews and alerts, capacity planCLD, DMSQYYYY-MM-DD[status]
A.8.7Protection against malwareEndpoint leadAnti-malware or EDR coverage and alert report (DOC-ISMS-059)MDM, SIEMMYYYY-MM-DD[status]
A.8.8Technical vulnerability managementVulnerability leadScan reports, remediation tracker DOC-ISMS-072, penetration test reportVULM, AYYYY-MM-DD[status]
A.8.9 (Example)Configuration management (new in 2022)Cloud leadBaseline DOC-ISMS-060, posture tool drift report, 2 high findings openCLDM2027-08-01Collected
A.8.10Information deletion (new in 2022)Data ownerDeletion job logs, customer data deletion confirmationsTKT, CLDCYYYY-MM-DD[status]
A.8.11Data masking (new in 2022)Engineering leadMasking rules, test data generation records (DOC-ISMS-062)REPOQYYYY-MM-DD[status]
A.8.12Data leakage prevention (new in 2022)Security operations leadDLP policy configuration, alert review recordsSIEMMYYYY-MM-DD[status]
A.8.13Information backupIT operations leadBackup job reports, restore test log DOC-ISMS-071CLD, GRCM, QYYYY-MM-DD[status]
A.8.14Redundancy of processing facilitiesIT operations leadArchitecture diagram, failover test reportDMSAYYYY-MM-DD[status]
A.8.15LoggingSecurity operations leadLog source coverage list, retention settingsSIEMQYYYY-MM-DD[status]
A.8.16Monitoring activities (new in 2022)Security operations leadAlert handling records, monthly monitoring review (DOC-ISMS-064)SIEMMYYYY-MM-DD[status]
A.8.17Clock synchronizationIT operations leadTime source configuration exportCLDAYYYY-MM-DD[status]
A.8.18Use of privileged utility programsIT operations leadRestricted utility list, usage logsSIEMQYYYY-MM-DD[status]
A.8.19Software installation on operational systemsIT operations leadAllowed software list, change tickets for installsTKT, MDMQYYYY-MM-DD[status]
A.8.20Network securityNetwork leadNetwork security standard DOC-ISMS-063, firewall rule reviewDMS, TKTHYYYY-MM-DD[status]
A.8.21Security of network servicesNetwork leadNetwork service agreements, provider security reviewDMSAYYYY-MM-DD[status]
A.8.22Network segregationNetwork leadSegmentation diagram, rule review resultsDMSHYYYY-MM-DD[status]
A.8.23Web filtering (new in 2022)Endpoint leadWeb filtering policy settings, block reportMDMQYYYY-MM-DD[status]
A.8.24Use of cryptographyPlatform leadKey and certificate register DOC-ISMS-070, rotation ticketsGRC, TKTA, MYYYY-MM-DD[status]
A.8.25Secure development life cycleEngineering leadSecure development policy DOC-ISMS-065, release checklistsDMS, REPOCYYYY-MM-DD[status]
A.8.26Application security requirementsEngineering leadSecurity requirements in design records or ticketsTKTCYYYY-MM-DD[status]
A.8.27Secure architecture and engineering principlesEngineering leadArchitecture principles, design review records, threat modelsDMSCYYYY-MM-DD[status]
A.8.28Secure coding (new in 2022)Engineering leadCode review records, static analysis results in pipelinesREPOCYYYY-MM-DD[status]
A.8.29Security testing in development and acceptanceEngineering leadPipeline security test results, acceptance test sign-offREPOCYYYY-MM-DD[status]
A.8.30 (Example)Outsourced developmentProcurement leadNot applicable: no outsourced development (SoA section 5); supplier register confirmsGRCE2027-05-12Not applicable
A.8.31Separation of development, test and productionEngineering leadEnvironment separation diagram, access lists per environmentDMS, IDPAYYYY-MM-DD[status]
A.8.32Change managementIT operations leadApproved change tickets, emergency change reviewsTKTCYYYY-MM-DD[status]
A.8.33Test informationEngineering leadTest data approvals, masking evidenceTKT, REPOCYYYY-MM-DD[status]
A.8.34Protecting systems during audit testingISMS managerApproved test plans for audits and penetration testsDMSEYYYY-MM-DD[status]

9. Summary and health of the evidence

ThemeControlsCollectedDueOverdueGapNot applicable
A.5 Organizational37[n][n][n][n][n]
A.6 People8[n][n][n][n][n]
A.7 Physical14[n][n][n][n][n]
A.8 Technological34[n][n][n][n][n]
Total93[n][n][n][n][n]

Worked summary for Quillmere Analytics Ltd (Example), eight weeks before Stage 2:

ThemeControlsCollectedDueOverdueGapNot applicable
A.5 Organizational (Example)37314110
A.6 People (Example)871000
A.7 Physical (Example)14121100
A.8 Technological (Example)34292111
Total93798321

Reading the example: 79 of the 92 applicable controls (86%) have current evidence. The 3 overdue and 2 gap items are the priority list for the next four weeks; each gets an owner and a date in the risk treatment plan or the corrective action log.

Useful indicators for the measurement programme (DOC-ISMS-080): percentage of applicable controls with current evidence, number of overdue records older than one period, and number of gaps.

10. Using the matrix for Stage 2 and surveillance audits

10.1 Before Stage 2

  1. Freeze a snapshot of the matrix about [4 to 6] weeks before the audit and record the snapshot date in Document control.
  2. Make sure every applicable control has at least one record from the period the ISMS has operated, and every clause 4 to 10 row has its record. Certification bodies usually expect one full internal audit of the ISMS and one management review before Stage 2 (CB practice, not a clause).
  3. Close or plan every Gap. A Gap on a control marked "Implemented" in the SoA is a contradiction an auditor will find.
  4. Build the Stage 2 audit evidence index (isms/stage-2-audit-evidence-index, DOC-ISMS-092) from the matrix: same rows, with direct links to the sampled records and a named person to present each area.
  5. Check access: auditors may view records on screen; agree how they see sensitive records (for example HR screening outcomes only).

10.2 During the audit

  • Keep the matrix open as the navigation aid; log each record shown and each request in an audit request log.
  • When a record cannot be found, say so and note it, rather than improvising evidence.

10.3 For surveillance and recertification

  • Surveillance audits sample part of Annex A each year, while some topics are covered at every surveillance. ISO/IEC 17021-1:2015 sets that list. As commonly summarised by accreditation bodies and auditor training material, it covers: internal audits and management review; review of action taken on nonconformities from the previous audit; handling of complaints; how effective the management system is at achieving the organization's objectives and intended results; progress of planned continual improvement; continuing operational control; changes; and use of certification marks or other references to certification. Have records for each of these ready every year, and confirm the exact list and wording in the standard and with your CB, whose audit programme decides what is sampled.
  • Plan internal audits so that over the three-year cycle every applicable control has been audited at least once, and mark the audit date per control in a working column if helpful.
  • Six weeks before each surveillance, run the readiness health check (isms/surveillance-readiness-health-check, DOC-ISMS-096) against the matrix.

11. Size tiers

AspectSmall: Quillmere Analytics Ltd (Example)Medium: Quillmere Health Systems (Example)Large: Quillmere Group (Example)
Profile46 staff, SaaS on one public cloud in two regions, part-time ISMS manager (0.5 FTE)320 staff, two offices, one colocation suite, ISMS manager plus 3-person security team2,400 staff, 6 sites in 4 countries, IT and OT, CISO with a 14-person security office
ToolOne spreadsheet tab per theme, records in the document system and cloud toolsGRC tool with owners assigned per row and remindersGRC platform with one matrix per site rolled up to group, shared rows for group-wide controls
OwnersAbout 8 people; the ISMS manager owns many organizational rowsAbout 25 control owners across IT, HR, facilities, legal and engineeringGroup control owners for shared controls plus site owners for local controls (physical, OT, local HR)
Physical rowsOffice only; data centre evidence is the cloud provider's assurance report reviewOffices plus the colocation suite (provider report and own cage controls)Each plant, service centre and the data centre with their own records
AutomationManual exports monthlyScheduled exports for identity, endpoint and vulnerability dataIntegrations pull status from identity, endpoint, SIEM and ticketing tools
ReviewISMS manager monthlyISMS manager monthly, steering committee quarterlySite coordinators monthly, group security office quarterly, integrated with ISO 9001 and ISO 22301 evidence where controls overlap

12. Records and maintenance of the matrix

RecordProvesKept byLocationRetention (Example)
Current matrixEvidence ownership and status at any timeISMS managerGRCCurrent
Audit snapshots (Stage 2, each surveillance, recertification)What was presented to the certification bodyISMS managerDMS, read-only3 years after the snapshot, or one full cycle
Change history of owners, records and frequenciesControlled changes to the evidence modelISMS managerGRC history or revision table3 years
Monthly status summariesEvidence health over timeISMS managerPerformance report DOC-ISMS-0813 years

Maintenance rules:

  • Update the matrix within [10] working days of any SoA change.
  • Owners update "last collected" when they store a new record; the ISMS manager checks monthly and chases Due and Overdue rows.
  • Align record names with the documented information register (DOC-ISMS-028) and the annual calendar (DOC-ISMS-032).
  • Review the whole matrix with internal audit once a year.

13. References

ReferenceEditionUse
ISO/IEC 27001:2022 + Amd 1:2024https://www.iso.org/standard/82875.html ; https://www.iso.org/standard/88435.htmlClauses 4 to 10, Annex A control numbering (93 controls in 4 themes)
ISO/IEC 27002:2022https://www.iso.org/standard/75652.htmlControl purpose and guidance used to choose evidence
ISO/IEC 17021-1:2015https://www.iso.org/standard/61651.htmlStage 1, Stage 2, surveillance and recertification audits
ISO/IEC 27006-1:2024https://www.iso.org/standard/82908.htmlISMS certification audit requirements for certification bodies
ISO/IEC 27007:2020https://www.iso.org/standard/77802.htmlISMS auditing guidance; under revision

Related templates: compliance/statement-of-applicability (DOC-ISMS-011), isms/stage-2-audit-evidence-index (DOC-ISMS-092), isms/isms-annual-calendar (DOC-ISMS-032), isms/isms-documented-information-register (DOC-ISMS-028), isms/isms-measurement-programme (DOC-ISMS-080), isms/surveillance-readiness-health-check (DOC-ISMS-096), isms/stage-1-readiness-pack (DOC-ISMS-091), compliance/internal-audit-program (DOC-ISMS-082), isms/isms-roles-raci (DOC-ISMS-006).

Standard and licence note

Structure aligned with ISO/IEC 27001:2022 + Amd 1:2024 clauses 4 to 10 and the Annex A numbering of 93 controls in four themes. Only clause and control numbers are used; the short labels, suggested owners, records, frequencies and examples are original wording and are not the official control titles, control text or guidance. No ISO or IEC text is reproduced, and you need the official standards to apply them. ISO and IEC standards are copyrighted and sold by ISO, IEC and national standards bodies. Check the current edition and amendments, and your certification body's rules, before use. This is a documentation format, not certification advice. Template licence: MIT.

Modèles associés