MCPInstall

iso27001-controls

Эксперт ISO 27001. Используй для ISMS, security controls и compliance implementation.

Installs
70
Last 24h
—
Trending rank
—
Security
Not audited

Install

Works with every agent the skills CLI supports.

npx skills add https://github.com/dengineproblem/agents-monorepo --skill iso27001-controls
  1. 01

    Install

    Run the command in your project. The CLI asks which agents to install for.

  2. 02

    Describe the task

    Ask your agent for something this skill covers. It loads iso27001-controls automatically when relevant.

  3. 03

    Review the result

    The agent follows the SKILL.md steps, scripts and references bundled with the skill.

SKILL.md

The instructions your agent reads when the skill is triggered.

ISO 27001 Controls Expert

Expert in implementing and auditing ISO 27001 Information Security Management System controls.

Control Categories Overview

ISO 27001:2022 Annex A Structure

CategoryControlsFocus Area
A.5 Organizational37 controlsPolicies, roles, responsibilities
A.6 People8 controlsHR security, awareness
A.7 Physical14 controlsPhysical and environmental
A.8 Technological34 controlsTechnical security measures

Risk-Based Approach

  • Controls selection based on risk assessment outcomes
  • Statement of Applicability (SoA) documents rationale
  • Controls can be implemented, not applicable, or excluded with justification
  • Continuous improvement through PDCA cycle

Control Implementation Framework

Control Assessment Template

control_assessment:
  control_id: "A.8.24"
  control_name: "Use of Cryptography"
  category: "Technological Controls"
  objective: "Ensure proper and effective use of cryptography to protect confidentiality, authenticity and integrity of information"

  current_state:
    implementation_status: "Partial"
    existing_controls:
      - "TLS 1.2 for web traffic"
      - "AES-256 for database encryption"
    gaps:
      - "No key management policy"
      - "Legacy systems using TLS 1.0"
      - "Inconsistent encryption at rest"

  risk_assessment:
    likelihood: "Medium"
    impact: "High"
    risk_level: "High"
    risk_treatment: "Mitigate"

  implementation_plan:
    actions:
      - description: "Develop cryptography policy"
        owner: "Security Manager"
        deadline: "2024-03-01"
        status: "In Progress"

      - description: "Upgrade all systems to TLS 1.3"
        owner: "IT Infrastructure"
        deadline: "2024-04-15"
        status: "Planned"

      - description: "Implement key management solution"
        owner: "Security Operations"
        deadline: "2024-05-01"
        status: "Planned"

  evidence_required:
    - "Cryptography policy document"
    - "TLS configuration audit report"
    - "Key management procedures"
    - "Encryption inventory"

  success_metrics:
    - "100% systems using TLS 1.2+"
    - "All sensitive data encrypted at rest"
    - "Key rotation performed quarterly"

Key Control Areas

A.5 Organizational Controls

A.5.1_Policies_for_Information_Security:
  requirement: "Information security policy and topic-specific policies shall be defined, approved by management, published, communicated and acknowledged"

  implementation:
    policies_required:
      - "Information Security Policy (overarching)"
      - "Acceptable Use Policy"
      - "Access Control Policy"
      - "Data Classification Policy"
      - "Incident Response Policy"
      - "Business Continuity Policy"
      - "Cryptography Policy"

    policy_structure:
      - "Purpose and scope"
      - "Roles and responsibilities"
      - "Policy statements"
      - "Compliance requirements"
      - "Review and update procedures"

    review_cycle: "Annual minimum, or upon significant changes"

  evidence:
    - "Approved policy documents"
    - "Communication records"
    - "Acknowledgment signatures/records"
    - "Review meeting minutes"

A.5.15_Access_Control:
  requirement: "Rules to control physical and logical access to information and other associated assets shall be established and implemented"

  implementation:
    principles:
      - "Need-to-know basis"
      - "Least privilege"
      - "Segregation of duties"
      - "Role-based access control"

    processes:
      access_request:
        - "Formal request submission"
        - "Manager approval"
        - "Security review for sensitive access"
        - "Provisioning within SLA"

      access_review:
        frequency: "Quarterly for privileged, annual for standard"
        scope: "All access rights"
        output: "Remediation of inappropriate access"

      access_revocation:
        triggers:
          - "Employment termination"
          - "Role change"
          - "Extended leave"
        sla: "Same day for terminations"

  evidence:
    - "Access control policy"
    - "Access request forms/tickets"
    - "Approval records"
    - "Access review reports"
    - "Revocation procedures"

A.8 Technological Controls

A.8.9_Configuration_Management:
  requirement: "Configurations, including security configurations, of hardware, software, services and networks shall be established, documented, implemented, monitored and reviewed"

  implementation:
    baseline_configurations:
      servers:
        - "Hardened OS images"
        - "Disabled unnecessary services"
        - "Security patches current"
        - "Logging enabled"

      network_devices:
        - "Encrypted management protocols"
        - "Access lists configured"
        - "Logging to SIEM"
        - "Firmware current"

      endpoints:
        - "Endpoint protection installed"
        - "Disk encryption enabled"
        - "Auto-updates enabled"
        - "Local firewall active"

    change_management:
      - "Configuration change requests"
      - "Security impact assessment"
      - "Testing before deployment"
      - "Rollback procedures"

    monitoring:
      - "Configuration drift detection"
      - "Automated compliance scanning"
      - "Alert on unauthorized changes"

  tools:
    - "Ansible/Terraform for IaC"
    - "CIS Benchmarks"
    - "Qualys/Nessus for scanning"
    - "SIEM for change detection"

A.8.24_Use_of_Cryptography:
  requirement: "Rules for the effective use of cryptography, including cryptographic key management, shall be defined and implemented"

  implementation:
    encryption_standards:
      data_at_rest:
        algorithm: "AES-256"
        scope: "All sensitive data"
        key_storage: "HSM or secure vault"

      data_in_transit:
        protocol: "TLS 1.3 (minimum 1.2)"
        cipher_suites: "ECDHE with AES-GCM"
        certificate_management: "Automated renewal"

      hashing:
        passwords: "bcrypt/Argon2"
        integrity: "SHA-256 or higher"
        prohibited: "MD5, SHA-1"

    key_management:
      generation: "Cryptographically secure RNG"
      storage: "HSM for production keys"
      rotation:
        symmetric: "Annual or per policy"
        asymmetric: "Per certificate validity"
      destruction: "Secure deletion with audit trail"

  prohibited_algorithms:
    - "DES, 3DES"
    - "RC4"
    - "MD5 for security purposes"
    - "SHA-1 for signatures"
    - "TLS 1.0, 1.1"

A.8.16_Monitoring_Activities:
  requirement: "Networks, systems and applications shall be monitored for anomalous behaviour and appropriate actions taken"

  implementation:
    log_sources:
      - "Authentication systems"
      - "Firewalls and network devices"
      - "Servers and endpoints"
      - "Applications and databases"
      - "Cloud services"

    monitoring_capabilities:
      real_time:
        - "Failed authentication attempts"
        - "Privileged account usage"
        - "Malware detection"
        - "Network anomalies"

      periodic:
        - "Access reviews"
        - "Vulnerability scans"
        - "Configuration compliance"
        - "Log analysis"

    alerting:
      critical:
        response_time: "15 minutes"
        examples:
          - "Multiple failed authentications"
          - "Privileged escalation"
          - "Malware detection"
          - "Data exfiltration indicators"

      high:
        response_time: "1 hour"
        examples:
          - "Unusual access patterns"
          - "Policy violations"
          - "Configuration changes"

    retention:
      security_logs: "12 months minimum"
      audit_logs: "7 years for compliance"

Statement of Applicability (SoA)

soa_template:
  document_control:
    version: "1.0"
    date: "2024-01-15"
    owner: "Information Security Manager"
    approved_by: "CISO"
    next_review: "2025-01-15"

  controls:
    A.5.1:
      control_name: "Policies for information security"
      applicable: true
      justification: "Required for ISMS governance"
      implementation_status: "Implemented"
      implementation_description: "Suite of 12 security policies approved and communicated"
      evidence_reference: "POL-001 to POL-012"

    A.5.2:
      control_name: "Information security roles and responsibilities"
      applicable: true
      justification: "Required for clear accountability"
      implementation_status: "Implemented"
      implementation_description: "RACI matrix and job descriptions updated"
      evidence_reference: "ORG-RACI-001"

    A.7.4:
      control_name: "Physical security monitoring"
      applicable: false
      justification: "Fully cloud-based organization, no physical premises to protect"
      residual_risk_acceptance: "Accepted by CISO on 2024-01-10"

  summary:
    total_controls: 93
    applicable: 87
    not_applicable: 6
    implemented: 72
    partially_implemented: 12
    planned: 3

Audit Preparation

Internal Audit Checklist

audit_checklist:
  documentation_review:
    - "ISMS scope and boundaries defined"
    - "Information security policy approved"
    - "Risk assessment methodology documented"
    - "Risk treatment plan current"
    - "Statement of Applicability complete"
    - "Policies and procedures accessible"

  control_testing:
    access_control:
      - "Review user access provisioning process"
      - "Sample access requests for approval evidence"
      - "Verify access review completion"
      - "Test termination access revocation"

    change_management:
      - "Review change management procedure"
      - "Sample changes for approval evidence"
      - "Verify testing before production"
      - "Check rollback capability"

    incident_management:
      - "Review incident response procedure"
      - "Sample incidents for handling evidence"
      - "Verify root cause analysis"
      - "Check lessons learned implementation"

  interviews:
    - "Management commitment to ISMS"
    - "Staff awareness of security policies"
    - "IT understanding of technical controls"
    - "HR knowledge of people controls"

audit_evidence_requirements:
  for_each_control:
    - "Policy/procedure documentation"
    - "Implementation evidence"
    - "Operating effectiveness evidence"
    - "Exception handling records"

Common Non-Conformities

common_findings:
  major_non_conformities:
    - finding: "No risk assessment performed"
      clause: "6.1.2"
      typical_cause: "Lack of methodology or resources"
      remediation: "Conduct formal risk assessment"

    - finding: "Missing Statement of Applicability"
      clause: "6.1.3 d)"
      typical_cause: "Incomplete documentation"
      remediation: "Create comprehensive SoA"

    - finding: "No management review conducted"
      clause: "9.3"
      typical_cause: "Lack of ISMS awareness"
      remediation: "Schedule and conduct management review"

  minor_non_conformities:
    - finding: "Access reviews not performed quarterly"
      control: "A.5.18"
      typical_cause: "Process not established"
      remediation: "Implement automated review process"

    - finding: "Incident response plan not tested"
      control: "A.5.24"
      typical_cause: "Resource constraints"
      remediation: "Schedule tabletop exercise"

  observations:
    - finding: "Security awareness training could be more frequent"
      control: "A.6.3"
      recommendation: "Increase from annual to quarterly"

    - finding: "Vulnerability scan results not trending"
      control: "A.8.8"
      recommendation: "Implement dashboard for metrics"

Continuous Improvement

pdca_cycle:
  plan:
    activities:
      - "Conduct risk assessment"
      - "Define security objectives"
      - "Create implementation plan"
      - "Allocate resources"
    outputs:
      - "Risk treatment plan"
      - "Security objectives"
      - "Implementation roadmap"

  do:
    activities:
      - "Implement controls"
      - "Conduct training"
      - "Deploy security tools"
      - "Document procedures"
    outputs:
      - "Implemented controls"
      - "Training records"
      - "Operational procedures"

  check:
    activities:
      - "Internal audits"
      - "Management reviews"
      - "Monitor KPIs"
      - "Incident analysis"
    outputs:
      - "Audit reports"
      - "Performance metrics"
      - "Improvement opportunities"

  act:
    activities:
      - "Corrective actions"
      - "Preventive actions"
      - "Process improvements"
      - "Control updates"
    outputs:
      - "Updated controls"
      - "Improved processes"
      - "Enhanced ISMS"

kpis:
  effectiveness:
    - "Number of security incidents"
    - "Mean time to detect/respond"
    - "Vulnerability remediation time"
    - "Audit findings closure rate"

  compliance:
    - "Policy acknowledgment rate"
    - "Training completion rate"
    - "Access review completion"
    - "Patch compliance percentage"

  maturity:
    - "Control implementation percentage"
    - "Process automation level"
    - "Risk treatment progress"

Лучшие практики

  1. Risk-based approach — приоритизируйте контроли по уровню риска
  2. Document everything — evidence критичен для аудита
  3. Continuous monitoring — не только для сертификации
  4. Management commitment — без поддержки руководства ISMS не работает
  5. Regular reviews — ежегодный минимум для всех политик
  6. Lessons learned — учитесь на инцидентах и аудитах

FAQ

What does the iso27001-controls skill do?

Эксперт ISO 27001. Используй для ISMS, security controls и compliance implementation.

How do I install iso27001-controls?

Run npx skills add https://github.com/dengineproblem/agents-monorepo --skill iso27001-controls in your project. The skills CLI detects the agents you use and copies the skill into the right folder. For Claude Code you can also place the skill folder at ~/.claude/skills/iso27001-controls/ (personal) or .claude/skills/iso27001-controls/ (project).

Which AI agents can use iso27001-controls?

Any agent that supports the open Agent Skills format (a folder with a SKILL.md file), including Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Windsurf, Cline, OpenCode and more.

Is iso27001-controls safe to install?

No partner security audit is available yet. Skills can run commands and scripts, so read the SKILL.md and any bundled files before installing.

Who maintains iso27001-controls?

It is published by dengineproblem in dengineproblem/agents-monorepo. It has 70 recorded installs.

More from dengineproblem/agents-monorepo

View all →

social-media-marketing

dengineproblem/agents-monorepo

Эксперт по SMM. Используй для стратегий в Instagram, Facebook, TikTok, LinkedIn, контент-планов и community management.

Marketing & SEO1.2K installs

frontend-design

dengineproblem/agents-monorepo

Эксперт по frontend дизайну. Используй для создания UI/UX, типографики, цветовых схем, анимаций и distinctive visual aesthetics.

Frontend & Design288 installs

video-marketing

dengineproblem/agents-monorepo

Open the skill to read its SKILL.md instructions.

Marketing & SEO259 installs

k6-load-test

dengineproblem/agents-monorepo

Эксперт k6 нагрузочного тестирования. Используй для performance testing, load scenarios и stress tests.

Testing & QA181 installs

b2b-saas-marketing

dengineproblem/agents-monorepo

Эксперт по B2B SaaS маркетингу. Используй для стратегий генерации спроса, growth-маркетинга, PLG, расчёта CAC/LTV, оптимизации воронки и маркетинговых операций.

Marketing & SEO141 installs

seo-expert

dengineproblem/agents-monorepo

Open the skill to read its SKILL.md instructions.

Marketing & SEO129 installs

Popular security skills

View category →

azure-compliance

microsoft/azure-skills

Run Azure compliance and security audits with azqr plus Key Vault expiration checks. Covers best-practice assessment, resource review, policy/compliance validation, and security posture checks. WHEN: compliance scan, security audit, BEFORE running azqr (compliance cli tool), Azure best practices, Key Vault expiration check, expired certificates, expiring secrets, orphaned resources, compliance assessment.

OfficialSecurity567K installs

minimal-run-and-audit

lllllllama/rigorpilot-skills

Rigor Run skill for README-first deep learning repo reproduction. Use when the task is specifically to capture or normalize evidence from the selected smoke test or documented inference or evaluation command and write standardized reprooutputs/ files, including patch notes when repository files changed. Do not use for training execution, initial repo intake, generic environment setup, paper lookup, target selection, hidden scientific-meaning changes, or end-to-end orchestration by itself.

Security477.4K installs

seo-audit

coreyhaines31/marketingskills

When the user wants to audit, review, or diagnose SEO issues on their site. Also use when the user mentions "SEO audit," "technical SEO," "why am I not ranking," "SEO issues," "on-page SEO," "meta tags review," "SEO health check," "my traffic dropped," "lost rankings," "not showing up in Google," "site isn't ranking," "Google update hit me," "page speed," "core web vitals," "crawl errors," "indexing issues," "stuck on page 2," "striking distance keywords," "title tag rewrite," "low CTR," "local SEO," "Google Business Profile," or "map pack." Use this even if the user just says something vague like "my SEO is bad" or "help with SEO" — start with an audit. For building pages at scale to target keywords, see programmatic-seo. For adding structured data, see schema. For AI search optimization, see ai-seo.

Security238.7K installs

firebase-security-rules-auditor

firebase/agent-skills

Audits Firebase (Firestore, Cloud Storage) security rules for vulnerabilities, privilege escalation, role bypasses, create vs update inconsistencies, resource exhaustion, type safety, size limits, and hasOnly ownership checks. Use when auditing/reviewing rules, running red-team rule assessments, or scoring against auditor checklists. Don't use for Firebase CLI (login, deploy), Auth, Crashlytics, Remote Config, or database queries.

OfficialSecurity139.1K installs

audit

pbakaus/impeccable

Run technical quality checks across accessibility, performance, theming, responsive design, and anti-patterns. Generates a scored report with P0-P3 severity ratings and actionable plan. Use when the user wants an accessibility check, performance audit, or technical quality review.

Security81.9K installs

competitors

coreyhaines31/marketingskills

When the user wants to create competitor comparison or alternative pages for SEO and buyer-facing use. Also use when the user mentions 'alternative page,' 'vs page,' 'competitor comparison,' 'comparison page,' '[Product] vs [Product],' '[Product] alternative,' 'competitive landing pages,' 'how do we compare to X,' 'competitor teardown,' 'audit our competitor pages,' 'are our comparison pages out of date,' or 'competitive asset audit.' Use this for any content that positions your product against competitors. Covers four formats: singular alternative, plural alternatives, you vs competitor, and competitor vs competitor. For auditing existing claims (not researching competitors from scratch, which is competitor-profiling; not technical SEO on these pages, which is seo-audit), use the asset audit here. For internal battle cards and sales-specific competitor docs, see sales-enablement.

Security79.3K installs