Back to catalog
Static reviewDevelopment

Skill dossier

implementing-iso-27001-information-security-management

Source declaration

Guides implementation of an ISO/IEC 27001:2022 Information Security Management System (ISMS) end to end: gap analysis and scoping, risk assessment methodology, Annex A control selection, Statement of Applicability (SoA) creation, and continuous improvement. Use when scoping a new ISMS, preparing for ISO 27001 certification or audit, or selecting and documenting Annex A controls for a compliance program.

The author's original description, preserved in English. It describes intent, not verified performance.

Guides implementation of an ISO/IEC 27001:2022 Information Security Management System (ISMS) end to end: gap analysis and scoping, risk assessment methodology, Annex A control selection, Statement of Applicability (SoA) creation, and continuous improvement. Use when scoping a new ISMS, preparing for ISO 27001 certification or audit, or selecting and documenting Annex A controls for a compliance program.

developmentreferencesscripts

Research summary

Machine-generated analysis; pending human review

These observations come from deterministic source parsing, not a human security review or controlled task evaluation.

Guides implementation of an ISO/IEC 27001:2022 Information Security Management System (ISMS) end to end: gap analysis and scoping, risk assessment methodology, Annex A control selection, Statement of Applicability (SoA) creation, and continuous improvement. Use when scoping a new ISMS, preparing for ISO 27001 certification or audit, or selecting and documenting Annex A controls for a compliance program. This bilingual summary is generated deterministically from collected source text and file structure; it is pending human editorial review.

Review scope

Deterministic static analysis of collected SKILL.md and supporting text/code. Machine-assisted candidates and findings await human editorial review; no dynamic behavior or effect is assessed.

Observable capabilities

  • Workflow [Source statement; provisional, not tested. Evidence: skills/implementing-iso-27001-information-security-management/SKILL.md:L88]

Limitations & scope

  • Static analysis cannot assess runtime behavior, command success, network reachability, or model output quality.
  • No commands, scripts, network requests, model calls, or controlled skill executions were performed.
  • Category, tags, capabilities, workflows, and bilingual editorial summaries are deterministic candidates pending human review, not verified outcomes.
  • Exact token counts are unavailable until a later pipeline performs and records an official model-specific count.

Relevant for

  • Practitioners evaluating whether to inspect and install the source skill; this audience is inferred from the product context, not measured usage. [Evidence: skills/implementing-iso-27001-information-security-management/SKILL.md:L1-L32]

What ships with the skill

The file inventory comes from the collected source at the recorded commit. Paths and sizes are structural observations, not a measure of quality.

files
8
Markdown files
5
scripts
2
references
4
Size
85.6 KB
Structural complexity
Low

File inventory

PathTypeBytes
skills/implementing-iso-27001-information-security-management/assets/template.mdReference11.4 KB
skills/implementing-iso-27001-information-security-management/LICENSEOther11 KB
skills/implementing-iso-27001-information-security-management/references/api-reference.mdReference1.5 KB
skills/implementing-iso-27001-information-security-management/references/standards.mdReference7.3 KB
skills/implementing-iso-27001-information-security-management/references/workflows.mdReference6.5 KB
skills/implementing-iso-27001-information-security-management/scripts/agent.pyScript8.2 KB
skills/implementing-iso-27001-information-security-management/scripts/process.pyScript31.8 KB
skills/implementing-iso-27001-information-security-management/SKILL.mdInstruction7.9 KB

SKILL.md frontmatter

{
  "name": "implementing-iso-27001-information-security-management",
  "description": "Guides implementation of an ISO/IEC 27001:2022 Information Security Management System (ISMS) end to end: gap analysis and scoping, risk assessment methodology, Annex A control selection, Statement of Applicability (SoA) creation, and continuous improvement. Use when scoping a new ISMS, preparing for ISO 27001 certification or audit, or selecting and documenting Annex A controls for a compliance program.",
  "domain": "cybersecurity",
  "subdomain": "compliance-governance",
  "tags": [
    "compliance",
    "governance",
    "iso27001",
    "isms",
    "risk-management",
    "certification"
  ],
  "nist_csf": [
    "GV.OC-01",
    "GV.RM-01",
    "GV.PO-01",
    "ID.RA-01",
    "PR.DS-01"
  ],
  "version": "1.0",
  "author": "mahipal",
  "license": "Apache-2.0",
  "mitre_attack": [
    "T1078",
    "T1530",
    "T1685.002"
  ]
}

A reading of the operating sequence

This workflow reconstructs the apparent sequence from source material. Unless controlled evaluation is explicitly recorded, it is provisional—not an observed trace.

  1. 01
    Action

    Overview

    Source-described action candidate under “Overview”; not verified execution.

  2. 02
    Decision

    When to Use

    Source-described decision candidate under “When to Use”; not verified execution.

  3. 03
    Action

    Core Concepts

    Source-described action candidate under “Core Concepts”; not verified execution.

  4. 04
    Action

    A.5.7 - Threat Intelligence

    Source-described action candidate under “New Controls in 2022 Edition”; not verified execution.

  5. 05
    Action

    A.5.23 - Information Security for Cloud Services

    Source-described action candidate under “New Controls in 2022 Edition”; not verified execution.

  6. 06
    Action

    A.5.30 - ICT Readiness for Business Continuity

    Source-described action candidate under “New Controls in 2022 Edition”; not verified execution.

Inspect all extracted workflow candidates (51 candidate steps)
  1. 07
    Action

    A.7.4 - Physical Security Monitoring

    Source-described action candidate under “New Controls in 2022 Edition”; not verified execution.

  2. 08
    Action

    A.8.9 - Configuration Management

    Source-described action candidate under “New Controls in 2022 Edition”; not verified execution.

  3. 09
    Action

    A.8.10 - Information Deletion

    Source-described action candidate under “New Controls in 2022 Edition”; not verified execution.

  4. 10
    Action

    A.8.11 - Data Masking

    Source-described action candidate under “New Controls in 2022 Edition”; not verified execution.

  5. 11
    Action

    A.8.12 - Data Leakage Prevention

    Source-described action candidate under “New Controls in 2022 Edition”; not verified execution.

  6. 12
    Action

    A.8.16 - Monitoring Activities

    Source-described action candidate under “New Controls in 2022 Edition”; not verified execution.

  7. 13
    Action

    A.8.23 - Web Filtering

    Source-described action candidate under “New Controls in 2022 Edition”; not verified execution.

  8. 14
    Action

    A.8.28 - Secure Coding

    Source-described action candidate under “New Controls in 2022 Edition”; not verified execution.

  9. 15
    Action

    Workflow

    Source-described action candidate under “Workflow”; not verified execution.

  10. 16
    Action

    Define ISMS scope boundaries (locations, business units, systems)

    Source-described action candidate under “Phase 1: Gap Analysis and Scoping (Weeks 1-4)”; not verified execution.

  11. 17
    Action

    Identify interested parties and their requirements

    Source-described action candidate under “Phase 1: Gap Analysis and Scoping (Weeks 1-4)”; not verified execution.

  12. 18
    Action

    Perform gap analysis against ISO 27001:2022 requirements

    Source-described action candidate under “Phase 1: Gap Analysis and Scoping (Weeks 1-4)”; not verified execution.

  13. 19
    Action

    Document internal and external context (PESTLE, SWOT)

    Source-described action candidate under “Phase 1: Gap Analysis and Scoping (Weeks 1-4)”; not verified execution.

  14. 20
    Action

    Obtain top management commitment and allocate budget

    Source-described action candidate under “Phase 1: Gap Analysis and Scoping (Weeks 1-4)”; not verified execution.

  15. 21
    Action

    Define risk assessment methodology (asset-based, scenario-based, or hybrid)

    Source-described action candidate under “Phase 2: Risk Assessment (Weeks 5-10)”; not verified execution.

  16. 22
    Action

    Create asset inventory covering information, people, processes, technology

    Source-described action candidate under “Phase 2: Risk Assessment (Weeks 5-10)”; not verified execution.

  17. 23
    Action

    Identify threats and vulnerabilities for each asset

    Source-described action candidate under “Phase 2: Risk Assessment (Weeks 5-10)”; not verified execution.

  18. 24
    Action

    Assess risk likelihood and impact using defined criteria

    Source-described action candidate under “Phase 2: Risk Assessment (Weeks 5-10)”; not verified execution.

  19. 25
    Action

    Calculate risk levels and determine risk treatment options (mitigate, accept, transfer, avoid)

    Source-described action candidate under “Phase 2: Risk Assessment (Weeks 5-10)”; not verified execution.

  20. 26
    Action

    Develop Risk Treatment Plan (RTP)

    Source-described action candidate under “Phase 2: Risk Assessment (Weeks 5-10)”; not verified execution.

  21. 27
    Action

    Map risk treatments to Annex A controls

    Source-described action candidate under “Phase 3: Control Selection and SoA (Weeks 11-14)”; not verified execution.

  22. 28
    Action

    Create Statement of Applicability (SoA) documenting:

    Source-described action candidate under “Phase 3: Control Selection and SoA (Weeks 11-14)”; not verified execution.

  23. 29
    Action

    Design control implementation plans with owners and timelines

    Source-described action candidate under “Phase 3: Control Selection and SoA (Weeks 11-14)”; not verified execution.

  24. 30
    Action

    Develop and approve information security policy

    Source-described action candidate under “Phase 4: Implementation (Weeks 15-30)”; not verified execution.

  25. 31
    Action

    Implement selected Annex A controls

    Source-described action candidate under “Phase 4: Implementation (Weeks 15-30)”; not verified execution.

  26. 32
    Action

    Create mandatory documented procedures:

    Source-described action candidate under “Phase 4: Implementation (Weeks 15-30)”; not verified execution.

  27. 33
    Action

    Deploy technical controls and security tooling

    Source-described action candidate under “Phase 4: Implementation (Weeks 15-30)”; not verified execution.

  28. 34
    Action

    Conduct security awareness training for all personnel

    Source-described action candidate under “Phase 4: Implementation (Weeks 15-30)”; not verified execution.

  29. 35
    Action

    Plan and execute internal audit programme covering all clauses and applicable controls

    Source-described action candidate under “Phase 5: Internal Audit and Management Review (Weeks 31-36)”; not verified execution.

  30. 36
    Action

    Document audit findings and nonconformities

    Source-described action candidate under “Phase 5: Internal Audit and Management Review (Weeks 31-36)”; not verified execution.

  31. 37
    Action

    Implement corrective actions with root cause analysis

    Source-described action candidate under “Phase 5: Internal Audit and Management Review (Weeks 31-36)”; not verified execution.

  32. 38
    Action

    Conduct management review covering:

    Source-described action candidate under “Phase 5: Internal Audit and Management Review (Weeks 31-36)”; not verified execution.

  33. 39
    Action

    Stage 1 Audit: Documentation review, readiness assessment

    Source-described action candidate under “Phase 6: Certification Audit (Weeks 37-42)”; not verified execution.

  34. 40
    Action

    Address Stage 1 findings

    Source-described action candidate under “Phase 6: Certification Audit (Weeks 37-42)”; not verified execution.

  35. 41
    Action

    Stage 2 Audit: On-site assessment of ISMS effectiveness

    Source-described action candidate under “Phase 6: Certification Audit (Weeks 37-42)”; not verified execution.

  36. 42
    Action

    Resolve any nonconformities (major NCRs require re-audit)

    Source-described action candidate under “Phase 6: Certification Audit (Weeks 37-42)”; not verified execution.

  37. 43
    Input

    Receive ISO 27001 certification (valid for 3 years)

    Source-described input candidate under “Phase 6: Certification Audit (Weeks 37-42)”; not verified execution.

  38. 44
    Action

    Annual surveillance audits (Years 1 and 2)

    Source-described action candidate under “Phase 7: Continual Improvement (Ongoing)”; not verified execution.

  39. 45
    Action

    Recertification audit (Year 3)

    Source-described action candidate under “Phase 7: Continual Improvement (Ongoing)”; not verified execution.

  40. 46
    Action

    Regular risk reassessment and control effectiveness reviews

    Source-described action candidate under “Phase 7: Continual Improvement (Ongoing)”; not verified execution.

  41. 47
    Action

    Incident-driven improvements and lessons learned integration

    Source-described action candidate under “Phase 7: Continual Improvement (Ongoing)”; not verified execution.

  42. 48
    Action

    Key Artifacts

    Source-described action candidate under “Key Artifacts”; not verified execution.

  43. 49
    Action

    Common Pitfalls

    Source-described action candidate under “Common Pitfalls”; not verified execution.

  44. 50
    Action

    Integration Points

    Source-described action candidate under “Integration Points”; not verified execution.

  45. 51
    Action

    References

    Source-described action candidate under “References”; not verified execution.

Potential risk surfaces

Static findings identify points to inspect before installation. They do not establish that a skill is safe, malicious, or effective.

Items warrant review

42 deterministic lexical finding(s) require review across the collected text. Findings can occur in documentation and do not prove execution or exploitability; binary-only files were not scanned.

Network accessObserved
File writesObserved
Credential useNot observed
Medium

Network access is mentioned

7 occurrences

A URL or network client appears in this source line. Review destinations, data sent, and trust boundaries; static text cannot establish actual network activity. This rule matched 7 location(s) in the collected text; 3 representative location(s) are cited. Matching text may be documentation, and the analyzer did not execute it.

Note

File modification is described or implemented

35 occurrences

This line contains a possible file-write or redirection operation. Check destination paths and overwrite behavior; the static review did not write any file. This rule matched 35 location(s) in the collected text; 3 representative location(s) are cited. Matching text may be documentation, and the analyzer did not execute it.

Where context can be spent

Discovery, activation, and resource layers have different meanings. Exact values appear only when the official token-counting method was run with a named model.

Exact token counts unavailable

All token values, including per-file inventory, are null until the pipeline performs an official exact count with an explicit model.

No token measurement was recorded with the required official method. This dossier does not substitute character counts, file sizes, or estimates.

Controlled evaluation

No controlled evaluation

This skill has only the evidence identified above. No task success, token efficiency, latency, or quality advantage is claimed.

Not tested

Use with the source in view

Install command
Inspect the pinned source at https://github.com/mukul975/Anthropic-Cybersecurity-Skills/blob/54a798831d2266a3ca61ce68a7acb80b81160d57/skills/implementing-iso-27001-information-security-management/SKILL.md and follow the source repository's installation instructions. No installation was performed or verified by this static analyzer. Source license: Apache-2.0.

Prerequisites

  • Static analysis cannot assess runtime behavior, command success, network reachability, or model output quality.
  • No commands, scripts, network requests, model calls, or controlled skill executions were performed.
  • Category, tags, capabilities, workflows, and bilingual editorial summaries are deterministic candidates pending human review, not verified outcomes.
  • Exact token counts are unavailable until a later pipeline performs and records an official model-specific count.

Example prompts

Not provided

A decision, with its limits attached

Strengths

  • The snapshot contains 8 collected file(s), 5 Markdown file(s), and 2 script file(s), enabling source-level inspection. [Evidence: skills/implementing-iso-27001-information-security-management/SKILL.md:L1]

Considerations

  • No functional, security, or model-quality result has been established. Human review must inspect source context and all cited findings before installation or publication.
Research conclusion

Provisional deterministic static inventory only; pending human editorial review and, separately, controlled evaluation. No install recommendation, security assurance, or effectiveness claim is made.

Traceable by construction

The dossier is a time-bound reading of a public artifact, not an endorsement. Use the source link to inspect the exact upstream material.

mukul975Anthropic-Cybersecurity-Skillsskills/implementing-iso-27001-information-security-management
Source type
Community
Commit
54a798831d2266a3ca61ce68a7acb80b81160d57
Collected
20 Nov 2026
Last checked
20 Nov 2026
Upstream license
Apache-2.0
Repository stars
36,446
Content basis

Deterministic lexical parsing, YAML frontmatter validation, file inventory, source-described workflow extraction, and heuristic provisional classification of the supplied files only. Generated by machine; no LLM, execution, dynamic testing, or human editorial approval.