isms-audit-expert — Claude Code skill: what it does, how to install
Assists with ISO 27001 audits, control assessments, and certification readiness in Claude Code. Ideal for planning surveillance cycles and logging nonconformities.
/plugin marketplace add alirezarezvani/claude-skills
/plugin install ra-qm-skills@claude-code-skillsWhat isms-audit-expert does
This skill manages internal and external audits for ISO 27001 compliance. It includes checklists for Stage 1 documentation reviews and Stage 2 operational readiness checks. It classifies findings into major nonconformities, minor nonconformities, and observations, setting strict resolution windows: 30 days for major failures and 90 days for minor issues.
The package provides scripts/isms_audit_scheduler.py to create risk-based audit schedules in Markdown or JSON format. For control assessment, it follows ISO 27002 testing methods, including inquiry, observation, inspection, and re-performance. Root cause analyses must be completed within 10 days of acknowledging a finding.
Install this skill if your team prepares for ISO 27001 certification or tracks Annex A controls. Skip it for casual projects. Without formal compliance obligations, you will not need these audit workflows.
What it helps with
- Build a risk-based annual audit schedule
- Verify documentation readiness for Stage 1 certification
- Document and classify nonconformities with root cause analysis
- Assess technical Annex A controls using ISO 27002 testing methods
Example prompts for the agent
- Review our access control evidence against ISO 27001 Stage 2 audit requirements.
- Generate a risk-based audit plan using `python scripts/isms_audit_scheduler.py --year 2025 --format markdown`.
- Draft a finding report for an unpatched vulnerability using the nonconformity template.
How to install isms-audit-expert
1Plugin marketplace
/plugin marketplace add alirezarezvani/claude-skills/plugin install ra-qm-skills@claude-code-skillsThis installs the whole ra-qm-skills plugin with all its skills
2Skills CLI (Vercel)
npx skills add alirezarezvani/claude-skills --skill isms-audit-expert -a claude-code3Manually: put the files in place
~/.claude/skills/isms-audit-expert/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/isms-audit-expert/
Manually: put the files in place
.agents/skills/isms-audit-expert/SKILL.mdFor all projects use ~/.agents/skills/
Manually: put the files in place
.cursor/skills/isms-audit-expert/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install alirezarezvani/claude-skills isms-audit-expert2Manually: put the files in place
.github/skills/isms-audit-expert/SKILL.mdPlatform CLI
gemini skills install https://github.com/alirezarezvani/claude-skills --path ra-qm-team/skills/isms-audit-expertManually: put the files in place
.devin/skills/isms-audit-expert/SKILL.mdThe legacy .windsurf/skills/ path still works
Claude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
From the same set349
The whole set →Similar
Questions about isms-audit-expert
How to install isms-audit-expert in Claude Code?
Install it by running /plugin marketplace add alirezarezvani/claude-skills or via the CLI with npx skills add alirezarezvani/claude-skills --skill isms-audit-expert -a claude-code.
What does isms-audit-expert do?
It guides ISO 27001 ISMS audits, from risk-based scheduling to Stage 1 and Stage 2 certification prep. It helps evaluate Annex A security controls and document findings.
What response times does the skill assign to audit findings?
Major nonconformities require remediation within 30 days, while minor nonconformities allow 90 days. Root cause analysis must be completed within 10 days.
Source text
SKILL.md · MIT
---
name: "isms-audit-expert"
description: 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.
metadata:
triggers:
- ISMS audit
- ISO 27001 audit
- security audit
- internal audit ISO 27001
- security control assessment
- certification audit
- surveillance audit
- audit finding
- nonconformity
---
# 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](#audit-program-management)
- [Audit Execution](#audit-execution)
- [Control Assessment](#control-assessment)
- [Finding Management](#finding-management)
- [Certification Support](#certification-support)
- [Tools](#tools)
- [References](#references)
---
## 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
1. Review previous audit findings and risk assessment results
2. Identify high-risk controls and recent security incidents
3. Determine audit scope based on ISMS boundaries
4. Assign auditors ensuring independence from audited areas
5. Create audit schedule with resource allocation
6. Obtain management approval for audit plan
7. **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
1. Review ISMS documentation (policies, SoA, risk assessment)
2. Analyze previous audit reports and open findings
3. Prepare audit plan with interview schedule
4. Notify auditees of audit scope and timing
5. Prepare checklists for controls in scope
6. **Validation:** All documentation received and reviewed before opening meeting
### Audit Conduct Steps
1. **Opening Meeting**
- Confirm audit scope and objectives
- Introduce audit team and methodology
- Agree on communication channels and logistics
2. **Evidence Collection**
- Interview control owners and operators
- Review documentation and records
- Observe processes in operation
- Inspect technical configurations
3. **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
4. **Closing Meeting**
- Present preliminary findings
- Clarify any factual inaccuracies
- Agree on finding classification
- Confirm corrective action timelines
5. **Validation:** All controls in scope assessed with documented evidence
---
## Control Assessment
### Control Testing Approach
1. Identify control objective from ISO 27002
2. Determine testing method (inquiry, observation, inspection, re-performance)
3. Define sample size based on population and risk
4. Execute test and document results
5. Evaluate control effectiveness
6. **Validation:** Evidence supports conclusion about control status
For detailed technical verification procedures by Annex A control, see [security-control-testing.md](references/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
1. Auditee acknowledges finding and severity
2. Root cause analysis completed within 10 days
3. Corrective action plan submitted with target dates
4. Actions implemented by responsible parties
5. Auditor verifies effectiveness of corrections
6. Finding closed with evidence of resolution
7. **Validation:** Root cause addressed, recurrence prevented
---
## Certification Support
### Stage 1 Audit Preparation
Ensure documentation is complete:
- [ ] ISMS scope statement
- [ ] Information security policy (management signed)
- [ ] Statement of Applicability
- [ ] Risk assessment methodology and results
- [ ] Risk treatment plan
- [ ] Internal audit results (past 12 months)
- [ ] Management review minutes
### Stage 2 Audit Preparation
Verify operational readiness:
- [ ] All Stage 1 findings addressed
- [ ] ISMS operational for minimum 3 months
- [ ] Evidence of control implementation
- [ ] Security awareness training records
- [ ] Incident response evidence (if applicable)
- [ ] Access review documentation
### 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
```bash
# 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](references/iso27001-audit-methodology.md) | Audit program structure, pre-audit phase, certification support |
| [security-control-testing.md](references/security-control-testing.md) | Technical verification procedures for ISO 27002 controls |
| [cloud-security-audit.md](references/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 |
© Alireza Rezvani · MIT · alirezarezvani/claude-skills