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/
| 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 |
1---2name: isms-audit-expert3description: Information Security Management System (ISMS) audit expert for ISO 27001 compliance verification, security control assessment, and certification support. Use when the user mentions ISO 27001, ISMS audit, Annex A controls, Statement of Applicability (SOA), gap analysis, nonconformity management, internal audit, surveillance audit, or security certification preparation. Helps review control implementation evidence, document audit findings, classify nonconformities, generate risk-based audit plans, map controls to Annex A requirements, prepare Stage 1 and Stage 2 audit documentation, and support corrective action workflows.4license: Unspecified5---6# ISMS Audit Expert78Internal and external ISMS audit management for ISO 27001 compliance verification, security control assessment, and certification support.910## Table of Contents1112- [Audit Program Management](#audit-program-management)13- [Audit Execution](#audit-execution)14- [Control Assessment](#control-assessment)15- [Finding Management](#finding-management)16- [Certification Support](#certification-support)17- [Tools](#tools)18- [References](#references)1920---2122## Audit Program Management2324### Risk-Based Audit Schedule2526| Risk Level | Audit Frequency | Examples |27|------------|-----------------|----------|28| Critical | Quarterly | Privileged access, vulnerability management, logging |29| High | Semi-annual | Access control, incident response, encryption |30| Medium | Annual | Policies, awareness training, physical security |31| Low | Annual | Documentation, asset inventory |3233### Annual Audit Planning Workflow34351. Review previous audit findings and risk assessment results362. Identify high-risk controls and recent security incidents373. Determine audit scope based on ISMS boundaries384. Assign auditors ensuring independence from audited areas395. Create audit schedule with resource allocation406. Obtain management approval for audit plan417. **Validation:** Audit plan covers all Annex A controls within certification cycle4243### Auditor Competency Requirements4445- ISO 27001 Lead Auditor certification (preferred)46- No operational responsibility for audited processes47- Understanding of technical security controls48- Knowledge of applicable regulations (GDPR, HIPAA)4950---5152## Audit Execution5354### Pre-Audit Preparation55561. Review ISMS documentation (policies, SoA, risk assessment)572. Analyze previous audit reports and open findings583. Prepare audit plan with interview schedule594. Notify auditees of audit scope and timing605. Prepare checklists for controls in scope616. **Validation:** All documentation received and reviewed before opening meeting6263### Audit Conduct Steps64651. **Opening Meeting**66 - Confirm audit scope and objectives67 - Introduce audit team and methodology68 - Agree on communication channels and logistics69702. **Evidence Collection**71 - Interview control owners and operators72 - Review documentation and records73 - Observe processes in operation74 - Inspect technical configurations75763. **Control Verification**77 - Test control design (does it address the risk?)78 - Test control operation (is it working as intended?)79 - Sample transactions and records80 - Document all evidence collected81824. **Closing Meeting**83 - Present preliminary findings84 - Clarify any factual inaccuracies85 - Agree on finding classification86 - Confirm corrective action timelines87885. **Validation:** All controls in scope assessed with documented evidence8990---9192## Control Assessment9394### Control Testing Approach95961. Identify control objective from ISO 27002972. Determine testing method (inquiry, observation, inspection, re-performance)983. Define sample size based on population and risk994. Execute test and document results1005. Evaluate control effectiveness1016. **Validation:** Evidence supports conclusion about control status102103For detailed technical verification procedures by Annex A control, see [security-control-testing.md](references/security-control-testing.md).104105---106107## Finding Management108109### Finding Classification110111| Severity | Definition | Response Time |112|----------|------------|---------------|113| Major Nonconformity | Control failure creating significant risk | 30 days |114| Minor Nonconformity | Isolated deviation with limited impact | 90 days |115| Observation | Improvement opportunity | Next audit cycle |116117### Finding Documentation Template118119```120Finding ID: ISMS-[YEAR]-[NUMBER]121Control Reference: A.X.X - [Control Name]122Severity: [Major/Minor/Observation]123124Evidence:125- [Specific evidence observed]126- [Records reviewed]127- [Interview statements]128129Risk Impact:130- [Potential consequences if not addressed]131132Root Cause:133- [Why the nonconformity occurred]134135Recommendation:136- [Specific corrective action steps]137```138139### Corrective Action Workflow1401411. Auditee acknowledges finding and severity1422. Root cause analysis completed within 10 days1433. Corrective action plan submitted with target dates1444. Actions implemented by responsible parties1455. Auditor verifies effectiveness of corrections1466. Finding closed with evidence of resolution1477. **Validation:** Root cause addressed, recurrence prevented148149---150151## Certification Support152153### Stage 1 Audit Preparation154155Ensure documentation is complete:156- [ ] 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:167- [ ] All Stage 1 findings addressed168- [ ] ISMS operational for minimum 3 months169- [ ] Evidence of control implementation170- [ ] Security awareness training records171- [ ] Incident response evidence (if applicable)172- [ ] Access review documentation173174### Surveillance Audit Cycle175176| Period | Focus |177|--------|-------|178| Year 1, Q2 | High-risk controls, Stage 2 findings follow-up |179| Year 1, Q4 | Continual improvement, control sample |180| Year 2, Q2 | Full surveillance |181| Year 2, Q4 | Re-certification preparation |182183**Validation:** No major nonconformities at surveillance audits.184185---186187## Tools188189### scripts/190191| Script | Purpose | Usage |192|--------|---------|-------|193| `isms_audit_scheduler.py` | Generate risk-based audit plans | `python scripts/isms_audit_scheduler.py --year 2025 --format markdown` |194195### Audit Planning Example196197```bash198# Generate annual audit plan199python scripts/isms_audit_scheduler.py --year 2025 --output audit_plan.json200201# With custom control risk ratings202python scripts/isms_audit_scheduler.py --controls controls.csv --format markdown203```204205---206207## References208209| File | Content |210|------|---------|211| [iso27001-audit-methodology.md](references/iso27001-audit-methodology.md) | Audit program structure, pre-audit phase, certification support |212| [security-control-testing.md](references/security-control-testing.md) | Technical verification procedures for ISO 27002 controls |213| [cloud-security-audit.md](references/cloud-security-audit.md) | Cloud provider assessment, configuration security, IAM review |214215---216217## Audit Performance Metrics218219| KPI | Target | Measurement |220|-----|--------|-------------|221| Audit plan completion | 100% | Audits completed vs. planned |222| Finding closure rate | >90% within SLA | Closed on time vs. total |223| Major nonconformities | 0 at certification | Count per certification cycle |224| Audit effectiveness | Incidents prevented | Security improvements implemented |