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
Evidence Collection Methods
| Method |
Use Case |
Example |
| Inquiry |
Process understanding |
Interview Security Manager about incident response |
| Observation |
Operational verification |
Watch visitor sign-in process |
| Inspection |
Documentation review |
Check access approval records |
| Re-performance |
Control testing |
Attempt login with weak password |
Control Assessment
ISO 27002 Control Categories
Organizational Controls (A.5):
- Information security policies
- Roles and responsibilities
- Segregation of duties
- Contact with authorities
- Threat intelligence
- Information security in projects
People Controls (A.6):
- Screening and background checks
- Employment terms and conditions
- Security awareness and training
- Disciplinary process
- Remote working security
Physical Controls (A.7):
- Physical security perimeters
- Physical entry controls
- Securing offices and facilities
- Physical security monitoring
- Equipment protection
Technological Controls (A.8):
- User endpoint devices
- Privileged access rights
- Access restriction
- Secure authentication
- Malware protection
- Vulnerability management
- Backup and recovery
- Logging and monitoring
- Network security
- Cryptography
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
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 |
Compliance Framework Integration
| Framework |
ISMS Audit Relevance |
| GDPR |
A.5.34 Privacy, A.8.10 Information deletion |
| HIPAA |
Access controls, audit logging, encryption |
| PCI DSS |
Network security, access control, monitoring |
| SOC 2 |
Trust Services Criteria mapped to ISO 27002 |
1---2name: isms-audit-expert3description: Information Security Management System auditing for ISO 27001 compliance, security control assessment, and certification support4---56# 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### Evidence Collection Methods9192| Method | Use Case | Example |93|--------|----------|---------|94| Inquiry | Process understanding | Interview Security Manager about incident response |95| Observation | Operational verification | Watch visitor sign-in process |96| Inspection | Documentation review | Check access approval records |97| Re-performance | Control testing | Attempt login with weak password |9899---100101## Control Assessment102103### ISO 27002 Control Categories104105**Organizational Controls (A.5):**106- Information security policies107- Roles and responsibilities108- Segregation of duties109- Contact with authorities110- Threat intelligence111- Information security in projects112113**People Controls (A.6):**114- Screening and background checks115- Employment terms and conditions116- Security awareness and training117- Disciplinary process118- Remote working security119120**Physical Controls (A.7):**121- Physical security perimeters122- Physical entry controls123- Securing offices and facilities124- Physical security monitoring125- Equipment protection126127**Technological Controls (A.8):**128- User endpoint devices129- Privileged access rights130- Access restriction131- Secure authentication132- Malware protection133- Vulnerability management134- Backup and recovery135- Logging and monitoring136- Network security137- Cryptography138139### Control Testing Approach1401411. Identify control objective from ISO 270021422. Determine testing method (inquiry, observation, inspection, re-performance)1433. Define sample size based on population and risk1444. Execute test and document results1455. Evaluate control effectiveness1466. **Validation:** Evidence supports conclusion about control status147148---149150## Finding Management151152### Finding Classification153154| Severity | Definition | Response Time |155|----------|------------|---------------|156| Major Nonconformity | Control failure creating significant risk | 30 days |157| Minor Nonconformity | Isolated deviation with limited impact | 90 days |158| Observation | Improvement opportunity | Next audit cycle |159160### Finding Documentation Template161162```163Finding ID: ISMS-[YEAR]-[NUMBER]164Control Reference: A.X.X - [Control Name]165Severity: [Major/Minor/Observation]166167Evidence:168- [Specific evidence observed]169- [Records reviewed]170- [Interview statements]171172Risk Impact:173- [Potential consequences if not addressed]174175Root Cause:176- [Why the nonconformity occurred]177178Recommendation:179- [Specific corrective action steps]180```181182### Corrective Action Workflow1831841. Auditee acknowledges finding and severity1852. Root cause analysis completed within 10 days1863. Corrective action plan submitted with target dates1874. Actions implemented by responsible parties1885. Auditor verifies effectiveness of corrections1896. Finding closed with evidence of resolution1907. **Validation:** Root cause addressed, recurrence prevented191192---193194## Certification Support195196### Stage 1 Audit Preparation197198Ensure documentation is complete:199- [ ] ISMS scope statement200- [ ] Information security policy (management signed)201- [ ] Statement of Applicability202- [ ] Risk assessment methodology and results203- [ ] Risk treatment plan204- [ ] Internal audit results (past 12 months)205- [ ] Management review minutes206207### Stage 2 Audit Preparation208209Verify operational readiness:210- [ ] All Stage 1 findings addressed211- [ ] ISMS operational for minimum 3 months212- [ ] Evidence of control implementation213- [ ] Security awareness training records214- [ ] Incident response evidence (if applicable)215- [ ] Access review documentation216217### Surveillance Audit Cycle218219| Period | Focus |220|--------|-------|221| Year 1, Q2 | High-risk controls, Stage 2 findings follow-up |222| Year 1, Q4 | Continual improvement, control sample |223| Year 2, Q2 | Full surveillance |224| Year 2, Q4 | Re-certification preparation |225226**Validation:** No major nonconformities at surveillance audits.227228---229230## Tools231232### scripts/233234| Script | Purpose | Usage |235|--------|---------|-------|236| `isms_audit_scheduler.py` | Generate risk-based audit plans | `python scripts/isms_audit_scheduler.py --year 2025 --format markdown` |237238### Audit Planning Example239240```bash241# Generate annual audit plan242python scripts/isms_audit_scheduler.py --year 2025 --output audit_plan.json243244# With custom control risk ratings245python scripts/isms_audit_scheduler.py --controls controls.csv --format markdown246```247248---249250## References251252| File | Content |253|------|---------|254| [iso27001-audit-methodology.md](references/iso27001-audit-methodology.md) | Audit program structure, pre-audit phase, certification support |255| [security-control-testing.md](references/security-control-testing.md) | Technical verification procedures for ISO 27002 controls |256| [cloud-security-audit.md](references/cloud-security-audit.md) | Cloud provider assessment, configuration security, IAM review |257258---259260## Audit Performance Metrics261262| KPI | Target | Measurement |263|-----|--------|-------------|264| Audit plan completion | 100% | Audits completed vs. planned |265| Finding closure rate | >90% within SLA | Closed on time vs. total |266| Major nonconformities | 0 at certification | Count per certification cycle |267| Audit effectiveness | Incidents prevented | Security improvements implemented |268269---270271## Compliance Framework Integration272273| Framework | ISMS Audit Relevance |274|-----------|---------------------|275| GDPR | A.5.34 Privacy, A.8.10 Information deletion |276| HIPAA | Access controls, audit logging, encryption |277| PCI DSS | Network security, access control, monitoring |278| SOC 2 | Trust Services Criteria mapped to ISO 27002 |