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 |
Source: alirezarezvani/claude-skills → ra-qm-team/skills/isms-audit-expert/SKILL.md
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.4---567# ISMS Audit Expert89Internal and external ISMS audit management for ISO 27001 compliance verification, security control assessment, and certification support.1011## Table of Contents1213- [Audit Program Management](#audit-program-management)14- [Audit Execution](#audit-execution)15- [Control Assessment](#control-assessment)16- [Finding Management](#finding-management)17- [Certification Support](#certification-support)18- [Tools](#tools)19- [References](#references)2021---2223## Audit Program Management2425### Risk-Based Audit Schedule2627| Risk Level | Audit Frequency | Examples |28|------------|-----------------|----------|29| Critical | Quarterly | Privileged access, vulnerability management, logging |30| High | Semi-annual | Access control, incident response, encryption |31| Medium | Annual | Policies, awareness training, physical security |32| Low | Annual | Documentation, asset inventory |3334### Annual Audit Planning Workflow35361. Review previous audit findings and risk assessment results372. Identify high-risk controls and recent security incidents383. Determine audit scope based on ISMS boundaries394. Assign auditors ensuring independence from audited areas405. Create audit schedule with resource allocation416. Obtain management approval for audit plan427. **Validation:** Audit plan covers all Annex A controls within certification cycle4344### Auditor Competency Requirements4546- ISO 27001 Lead Auditor certification (preferred)47- No operational responsibility for audited processes48- Understanding of technical security controls49- Knowledge of applicable regulations (GDPR, HIPAA)5051---5253## Audit Execution5455### Pre-Audit Preparation56571. Review ISMS documentation (policies, SoA, risk assessment)582. Analyze previous audit reports and open findings593. Prepare audit plan with interview schedule604. Notify auditees of audit scope and timing615. Prepare checklists for controls in scope626. **Validation:** All documentation received and reviewed before opening meeting6364### Audit Conduct Steps65661. **Opening Meeting**67 - Confirm audit scope and objectives68 - Introduce audit team and methodology69 - Agree on communication channels and logistics70712. **Evidence Collection**72 - Interview control owners and operators73 - Review documentation and records74 - Observe processes in operation75 - Inspect technical configurations76773. **Control Verification**78 - Test control design (does it address the risk?)79 - Test control operation (is it working as intended?)80 - Sample transactions and records81 - Document all evidence collected82834. **Closing Meeting**84 - Present preliminary findings85 - Clarify any factual inaccuracies86 - Agree on finding classification87 - Confirm corrective action timelines88895. **Validation:** All controls in scope assessed with documented evidence9091---9293## Control Assessment9495### Control Testing Approach96971. Identify control objective from ISO 27002982. Determine testing method (inquiry, observation, inspection, re-performance)993. Define sample size based on population and risk1004. Execute test and document results1015. Evaluate control effectiveness1026. **Validation:** Evidence supports conclusion about control status103104For detailed technical verification procedures by Annex A control, see [security-control-testing.md](references/security-control-testing.md).105106---107108## Finding Management109110### Finding Classification111112| Severity | Definition | Response Time |113|----------|------------|---------------|114| Major Nonconformity | Control failure creating significant risk | 30 days |115| Minor Nonconformity | Isolated deviation with limited impact | 90 days |116| Observation | Improvement opportunity | Next audit cycle |117118### Finding Documentation Template119120```121Finding ID: ISMS-[YEAR]-[NUMBER]122Control Reference: A.X.X - [Control Name]123Severity: [Major/Minor/Observation]124125Evidence:126- [Specific evidence observed]127- [Records reviewed]128- [Interview statements]129130Risk Impact:131- [Potential consequences if not addressed]132133Root Cause:134- [Why the nonconformity occurred]135136Recommendation:137- [Specific corrective action steps]138```139140### Corrective Action Workflow1411421. Auditee acknowledges finding and severity1432. Root cause analysis completed within 10 days1443. Corrective action plan submitted with target dates1454. Actions implemented by responsible parties1465. Auditor verifies effectiveness of corrections1476. Finding closed with evidence of resolution1487. **Validation:** Root cause addressed, recurrence prevented149150---151152## Certification Support153154### Stage 1 Audit Preparation155156Ensure documentation is complete:157- [ ] ISMS scope statement158- [ ] Information security policy (management signed)159- [ ] Statement of Applicability160- [ ] Risk assessment methodology and results161- [ ] Risk treatment plan162- [ ] Internal audit results (past 12 months)163- [ ] Management review minutes164165### Stage 2 Audit Preparation166167Verify operational readiness:168- [ ] 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| Script | Purpose | Usage |193|--------|---------|-------|194| `isms_audit_scheduler.py` | Generate risk-based audit plans | `python scripts/isms_audit_scheduler.py --year 2025 --format markdown` |195196### Audit Planning Example197198```bash199# Generate annual audit plan200python scripts/isms_audit_scheduler.py --year 2025 --output audit_plan.json201202# With custom control risk ratings203python scripts/isms_audit_scheduler.py --controls controls.csv --format markdown204```205206---207208## References209210| File | Content |211|------|---------|212| [iso27001-audit-methodology.md](references/iso27001-audit-methodology.md) | Audit program structure, pre-audit phase, certification support |213| [security-control-testing.md](references/security-control-testing.md) | Technical verification procedures for ISO 27002 controls |214| [cloud-security-audit.md](references/cloud-security-audit.md) | Cloud provider assessment, configuration security, IAM review |215216---217218## Audit Performance Metrics219220| KPI | Target | Measurement |221|-----|--------|-------------|222| Audit plan completion | 100% | Audits completed vs. planned |223| Finding closure rate | >90% within SLA | Closed on time vs. total |224| Major nonconformities | 0 at certification | Count per certification cycle |225| Audit effectiveness | Incidents prevented | Security improvements implemented |226227---228229**Source:** [`alirezarezvani/claude-skills`](https://github.com/alirezarezvani/claude-skills) → `ra-qm-team/skills/isms-audit-expert/SKILL.md`