
Governance & Compliance
https://hmmnm.com/iso-27001-from-scratch-part-6-running-the-isms-after/
TL;DR: Passing the Stage 2 audit is the starting line, not the finish. An ISO 27001 certificate only stays valid if you can demonstrate a living ISMS — internal audits, management reviews, metrics that prove controls actually run, and a recertification audit every three years. This final part of the series covers how to operate the ISMS day-to-day, keep your risk register alive, and consolidate everything from Parts 1–5 into one checklist.
Authorization note: All commands below are meant to run against your own lab machines only — VMs you own or systems you have explicit written permission to audit. Never scan, probe, or pull logs from systems you don’t control.
ISO 27001 certificates are typically issued for a three-year cycle. Within that cycle:
Surveillance audits focus on continuity: Are internal audits happening? Did management review occur? Are nonconformities from last time closed? Is the Statement of Applicability (SoA) current? If you’ve let the ISMS gather dust, this is where it shows.
Your risk register is not a document you finish — it’s a database you maintain. In practice, it should change whenever:
Keep the register in something you can diff and query. A Git-tracked CSV works fine for a small ISMS:
~/isms/
├── risk-register.csv
├── soa.md
├── incidents/
├── internal-audits/
└── management-review/
$ git log --oneline risk-register.csv | head -5
a3f19c2 Q3 review: added vendor risk for new CRM
7b44e01 Post-incident update: R-014 likelihood raised to High
21ce88a Initial baseline risk assessment
The git history itself is audit evidence — it shows the register was touched throughout the year, not rewritten the night before the surveillance audit. Auditors appreciate that.
Surveillance auditors don’t want to see that you documented controls — they want evidence the controls ran. Collect metrics continuously; they feed both internal audit and management review.
Track, per quarter: incident count, severity breakdown, mean time to detect (MTTD) and mean time to respond (MTTR). Even a quiet quarter is data — “0 incidents, monitoring verified by monthly alert test” is a valid record.
Define an SLA (e.g., critical vulnerabilities patched within 14 days, high within 30) and measure against it. On your own lab machines, a quick local check demonstrates the measurement method:
# List packages with pending security updates (Debian/Ubuntu)
$ apt list --upgradable 2>/dev/null | grep -i securi | wc -l
3
# Show kernel version vs. latest available
$ uname -r
5.15.0-91-generic
$ apt-cache policy linux-image-generic | grep Candidate
Candidate: 5.15.0-105.115
Record the output in a monthly patch-compliance file. The delta between runs is your metric. If criticals sit unpatched past SLA, either fix the process or document a risk-accepted exception — both are defensible; silence is not.
ISO 27001 clause 7.2/7.3 requires competence and awareness. Track completion percentages per cycle. For a lab-scale ISMS, a simple CSV per quarter suffices:
quarter,person,training,completed,date
2025-Q3,alice,Phishing awareness,yes,2025-08-14
2025-Q3,alice,Access control refresher,yes,2025-09-02
2025-Q3,bob,Phishing awareness,no,-
The no row is important — auditors trust registers that show exceptions being chased, not 100% scores with no follow-up.
Plan-Do-Check-Act (PDCA) is the engine of continual improvement. Two Check activities are mandatory:
A lightweight internal audit you can run on a lab host — checking your own documented baseline against reality:
# Check: is SSH password authentication disabled per our baseline?
$ sudo sshd -T | grep -E 'passwordauthentication|permitrootlogin'
passwordauthentication no
permitrootlogin no
# Check: is the audit daemon running per our logging control?
$ systemctl is-active auditd
active
# Check: no world-writable files in a sensitive directory
$ find /srv/app -perm -o+w -type f | head
(no output — control conforms)
Save commands + outputs as the audit workpaper. One file per control checked. Findings feed the corrective action process (clause 10.2): root cause, correction, and a check that the fix worked.
If you process personal data, ISO 27001 and privacy law overlap heavily. Don’t run two parallel programs — map them.
| ISO 27001 activity | DPDP (India) / GDPR overlap |
|---|---|
| Risk register entries for personal data flows | Records of processing / data mapping |
| Incident response process | Breach notification duties (GDPR: 72 hours to authority; DPDP: notify Data Protection Board and affected data principals) |
| Access control and logging controls | Security of processing (GDPR Art. 32) |
| Vendor/supplier controls in the SoA | Processor agreements, data processing addenda |
| Training program | Privacy awareness modules (one session can cover both) |
Practical tip: add a contains_personal_data column to your risk register. When the answer is yes, the same entry doubles as evidence for privacy compliance. One review, one meeting, two programs updated.
What auditors actually ask for at surveillance:
A useful dry run is a quarterly self-check against the same list. Keep a single “audit binder” folder with dated evidence files; when the auditor asks, you produce it in minutes instead of reconstructing history for a week.
$ ls ~/isms/evidence/2025-Q3/
2025-09-30_access-review.csv
2025-09-28_patch-compliance.txt
2025-08-14_training-log.csv
2025-07-02_internal-audit-findings.md
2025-10-01_management-review-minutes.md
The whole series in one table — your ISMS build plan:
| # | Step | Series part | Key deliverable |
|---|---|---|---|
| 1 | Define scope, context, and interested parties | Part 1 | Scope statement, boundaries |
| 2 | Leadership commitment and policy | Part 2 | ISMS policy, roles, objectives |
| 3 | Risk assessment and treatment | Part 3 | Risk register, treatment plan |
| 4 | Statement of Applicability and Annex A controls | Part 4 | SoA, control documentation |
| 5 | Operational controls, awareness, documentation | Part 5 | Runbooks, training records, asset inventory |
| 6 | Internal audit + management review | Part 6 | Audit report, review minutes |
| 7 | Stage 1 + Stage 2 certification audit | Part 6 (context) | Certificate, initial findings |
| 8 | Continual operation: metrics, surveillance prep | Part 6 | Quarterly evidence, KPIs |
| 9 | Yearly: risk register review, internal audit cycle | Part 6 | Updated register, audit reports |
| 10 | Year 3: recertification audit; restart cycle | Part 6 | Renewed certificate |
This closes the ISO 27001 from-scratch series. You now have the full path: scope, policy, risk, SoA, operations, and the post-certificate lifecycle. The certificate is a snapshot; the ISMS is the system. Keep the system running and the audits take care of themselves.