ISMS Audit Expert
Internal and external ISMS audit management for ISO 27001 compliance verification, security control assessment, and certification support.
Table of Contents
Audit Program Management
Risk-Based Audit Schedule
| Risk Level |
Audit Frequency |
Examples |
| Critical |
Quarterly |
Privileged access, vulnerability management, logging |
| High |
Semi-annual |
Access control, incident response, encryption |
| Medium |
Annual |
Policies, awareness training, physical security |
| Low |
Annual |
Documentation, asset inventory |
Annual Audit Planning Workflow
- Review previous audit findings and risk assessment results
- Identify high-risk controls and recent security incidents
- Determine audit scope based on ISMS boundaries
- Assign auditors ensuring independence from audited areas
- Create audit schedule with resource allocation
- Obtain management approval for audit plan
- Validation: Audit plan covers all Annex A controls within certification cycle
Auditor Competency Requirements
- ISO 27001 Lead Auditor certification (preferred)
- No operational responsibility for audited processes
- Understanding of technical security controls
- Knowledge of applicable regulations (GDPR, HIPAA)
Audit Execution
Pre-Audit Preparation
- Review ISMS documentation (policies, SoA, risk assessment)
- Analyze previous audit reports and open findings
- Prepare audit plan with interview schedule
- Notify auditees of audit scope and timing
- Prepare checklists for controls in scope
- Validation: All documentation received and reviewed before opening meeting
Audit Conduct Steps
Opening Meeting
- Confirm audit scope and objectives
- Introduce audit team and methodology
- Agree on communication channels and logistics
Evidence Collection
- Interview control owners and operators
- Review documentation and records
- Observe processes in operation
- Inspect technical configurations
Control Verification
- Test control design (does it address the risk?)
- Test control operation (is it working as intended?)
- Sample transactions and records
- Document all evidence collected
Closing Meeting
- Present preliminary findings
- Clarify any factual inaccuracies
- Agree on finding classification
- Confirm corrective action timelines
Validation: All controls in scope assessed with documented evidence
Control Assessment
Control Testing Approach
- Identify control objective from ISO 27002
- Determine testing method (inquiry, observation, inspection, re-performance)
- Define sample size based on population and risk
- Execute test and document results
- Evaluate control effectiveness
- Validation: Evidence supports conclusion about control status
For detailed technical verification procedures by Annex A control, see security-control-testing.md.
Finding Management
Finding Classification
| Severity |
Definition |
Response Time |
| Major Nonconformity |
Control failure creating significant risk |
30 days |
| Minor Nonconformity |
Isolated deviation with limited impact |
90 days |
| Observation |
Improvement opportunity |
Next audit cycle |
Finding Documentation Template
Finding ID: ISMS-[YEAR]-[NUMBER]
Control Reference: A.X.X - [Control Name]
Severity: [Major/Minor/Observation]
Evidence:
- [Specific evidence observed]
- [Records reviewed]
- [Interview statements]
Risk Impact:
- [Potential consequences if not addressed]
Root Cause:
- [Why the nonconformity occurred]
Recommendation:
- [Specific corrective action steps]
Corrective Action Workflow
- Auditee acknowledges finding and severity
- Root cause analysis completed within 10 days
- Corrective action plan submitted with target dates
- Actions implemented by responsible parties
- Auditor verifies effectiveness of corrections
- Finding closed with evidence of resolution
- Validation: Root cause addressed, recurrence prevented
Certification Support
Stage 1 Audit Preparation
Ensure documentation is complete:
Stage 2 Audit Preparation
Verify operational readiness:
Surveillance Audit Cycle
| Period |
Focus |
| Year 1, Q2 |
High-risk controls, Stage 2 findings follow-up |
| Year 1, Q4 |
Continual improvement, control sample |
| Year 2, Q2 |
Full surveillance |
| Year 2, Q4 |
Re-certification preparation |
Validation: No major nonconformities at surveillance audits.
Tools
scripts/
Note: Bundled scripts ship as Markdown reference (.md) — copy the code out of the .md file to run it.
| Script |
Purpose |
Usage |
isms_audit_scheduler.py |
Generate risk-based audit plans |
python scripts/isms_audit_scheduler.py --year 2025 --format markdown |
Audit Planning Example
# Generate annual audit plan
python scripts/isms_audit_scheduler.py --year 2025 --output audit_plan.json
# With custom control risk ratings
python scripts/isms_audit_scheduler.py --controls controls.csv --format markdown
References
| File |
Content |
| iso27001-audit-methodology.md |
Audit program structure, pre-audit phase, certification support |
| security-control-testing.md |
Technical verification procedures for ISO 27002 controls |
| cloud-security-audit.md |
Cloud provider assessment, configuration security, IAM review |
Audit Performance Metrics
| KPI |
Target |
Measurement |
| Audit plan completion |
100% |
Audits completed vs. planned |
| Finding closure rate |
>90% within SLA |
Closed on time vs. total |
| Major nonconformities |
0 at certification |
Count per certification cycle |
| Audit effectiveness |
Incidents prevented |
Security improvements implemented |
Creator: Ra Qm Team
License: MIT
Source Repo: neekware/dojo-skills
Source Bucket: ra-qm-team
Original Path: ra-qm-team/isms-audit-expert
1---2name: isms-audit-expert-23description: ISMS Audit Expert4---5# ISMS Audit Expert67Internal and external ISMS audit management for ISO 27001 compliance verification, security control assessment, and certification support.89## Table of Contents1011- [Audit Program Management](#audit-program-management)12- [Audit Execution](#audit-execution)13- [Control Assessment](#control-assessment)14- [Finding Management](#finding-management)15- [Certification Support](#certification-support)16- [Tools](#tools)17- [References](#references)1819---2021## Audit Program Management2223### Risk-Based Audit Schedule2425| Risk Level | Audit Frequency | Examples |26| ---------- | --------------- | ---------------------------------------------------- |27| Critical | Quarterly | Privileged access, vulnerability management, logging |28| High | Semi-annual | Access control, incident response, encryption |29| Medium | Annual | Policies, awareness training, physical security |30| Low | Annual | Documentation, asset inventory |3132### Annual Audit Planning Workflow33341. Review previous audit findings and risk assessment results352. Identify high-risk controls and recent security incidents363. Determine audit scope based on ISMS boundaries374. Assign auditors ensuring independence from audited areas385. Create audit schedule with resource allocation396. Obtain management approval for audit plan407. **Validation:** Audit plan covers all Annex A controls within certification cycle4142### Auditor Competency Requirements4344- ISO 27001 Lead Auditor certification (preferred)45- No operational responsibility for audited processes46- Understanding of technical security controls47- Knowledge of applicable regulations (GDPR, HIPAA)4849---5051## Audit Execution5253### Pre-Audit Preparation54551. Review ISMS documentation (policies, SoA, risk assessment)562. Analyze previous audit reports and open findings573. Prepare audit plan with interview schedule584. Notify auditees of audit scope and timing595. Prepare checklists for controls in scope606. **Validation:** All documentation received and reviewed before opening meeting6162### Audit Conduct Steps63641. **Opening Meeting**65 - Confirm audit scope and objectives66 - Introduce audit team and methodology67 - Agree on communication channels and logistics68692. **Evidence Collection**70 - Interview control owners and operators71 - Review documentation and records72 - Observe processes in operation73 - Inspect technical configurations74753. **Control Verification**76 - Test control design (does it address the risk?)77 - Test control operation (is it working as intended?)78 - Sample transactions and records79 - Document all evidence collected80814. **Closing Meeting**82 - Present preliminary findings83 - Clarify any factual inaccuracies84 - Agree on finding classification85 - Confirm corrective action timelines86875. **Validation:** All controls in scope assessed with documented evidence8889---9091## Control Assessment9293### Control Testing Approach94951. Identify control objective from ISO 27002962. Determine testing method (inquiry, observation, inspection, re-performance)973. Define sample size based on population and risk984. Execute test and document results995. Evaluate control effectiveness1006. **Validation:** Evidence supports conclusion about control status101102For detailed technical verification procedures by Annex A control, see [security-control-testing.md](references/security-control-testing.md).103104---105106## Finding Management107108### Finding Classification109110| Severity | Definition | Response Time |111| ------------------- | ----------------------------------------- | ---------------- |112| Major Nonconformity | Control failure creating significant risk | 30 days |113| Minor Nonconformity | Isolated deviation with limited impact | 90 days |114| Observation | Improvement opportunity | Next audit cycle |115116### Finding Documentation Template117118```119Finding ID: ISMS-[YEAR]-[NUMBER]120Control Reference: A.X.X - [Control Name]121Severity: [Major/Minor/Observation]122123Evidence:124- [Specific evidence observed]125- [Records reviewed]126- [Interview statements]127128Risk Impact:129- [Potential consequences if not addressed]130131Root Cause:132- [Why the nonconformity occurred]133134Recommendation:135- [Specific corrective action steps]136```137138### Corrective Action Workflow1391401. Auditee acknowledges finding and severity1412. Root cause analysis completed within 10 days1423. Corrective action plan submitted with target dates1434. Actions implemented by responsible parties1445. Auditor verifies effectiveness of corrections1456. Finding closed with evidence of resolution1467. **Validation:** Root cause addressed, recurrence prevented147148---149150## Certification Support151152### Stage 1 Audit Preparation153154Ensure documentation is complete:155156- [ ] ISMS scope statement157- [ ] Information security policy (management signed)158- [ ] Statement of Applicability159- [ ] Risk assessment methodology and results160- [ ] Risk treatment plan161- [ ] Internal audit results (past 12 months)162- [ ] Management review minutes163164### Stage 2 Audit Preparation165166Verify operational readiness:167168- [ ] All Stage 1 findings addressed169- [ ] ISMS operational for minimum 3 months170- [ ] Evidence of control implementation171- [ ] Security awareness training records172- [ ] Incident response evidence (if applicable)173- [ ] Access review documentation174175### Surveillance Audit Cycle176177| Period | Focus |178| ---------- | ---------------------------------------------- |179| Year 1, Q2 | High-risk controls, Stage 2 findings follow-up |180| Year 1, Q4 | Continual improvement, control sample |181| Year 2, Q2 | Full surveillance |182| Year 2, Q4 | Re-certification preparation |183184**Validation:** No major nonconformities at surveillance audits.185186---187188## Tools189190### scripts/191192> **Note:** Bundled scripts ship as Markdown reference (`.md`) — copy the code out of the `.md` file to run it.193194| Script | Purpose | Usage |195| ------------------------- | ------------------------------- | ---------------------------------------------------------------------- |196| `isms_audit_scheduler.py` | Generate risk-based audit plans | `python scripts/isms_audit_scheduler.py --year 2025 --format markdown` |197198### Audit Planning Example199200```bash201# Generate annual audit plan202python scripts/isms_audit_scheduler.py --year 2025 --output audit_plan.json203204# With custom control risk ratings205python scripts/isms_audit_scheduler.py --controls controls.csv --format markdown206```207208---209210## References211212| File | Content |213| ------------------------------------------------------------------------- | --------------------------------------------------------------- |214| [iso27001-audit-methodology.md](references/iso27001-audit-methodology.md) | Audit program structure, pre-audit phase, certification support |215| [security-control-testing.md](references/security-control-testing.md) | Technical verification procedures for ISO 27002 controls |216| [cloud-security-audit.md](references/cloud-security-audit.md) | Cloud provider assessment, configuration security, IAM review |217218---219220## Audit Performance Metrics221222| KPI | Target | Measurement |223| --------------------- | ------------------- | --------------------------------- |224| Audit plan completion | 100% | Audits completed vs. planned |225| Finding closure rate | >90% within SLA | Closed on time vs. total |226| Major nonconformities | 0 at certification | Count per certification cycle |227| Audit effectiveness | Incidents prevented | Security improvements implemented |228229> **Creator:** Ra Qm Team230> **License:** MIT231> **Source Repo:** `neekware/dojo-skills`232> **Source Bucket:** `ra-qm-team`233> **Original Path:** `ra-qm-team/isms-audit-expert`