[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7BRNP2V3TY39DV3846MN7XP":3,"skill-same:01M7BRNP2V3TY39DV3846MN7XP":71},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":24,"commitSha":25,"skillDirectory":26,"forksCount":27,"repositoryHtmlUrl":28,"repositoryHomepageUrl":6,"ownerHtmlUrl":29,"ownerBlogUrl":30,"ownerDescription":31,"updatedAt":32,"install":33,"resources":46},"01M7BRNP2V3TY39DV3846MN7XP","information-security-manager-iso27001",null,"ISO 27001 ISMS implementation and cybersecurity governance for HealthTech and MedTech companies. Use when designing an ISMS, running security risk assessments, implementing controls, pursuing ISO 27001 certification, preparing security audits, responding to security incidents, or verifying compliance. Covers ISO 27001, ISO 27002, healthcare security, and medical device cybersecurity.","devlify-marketplace\u002Fdevlify-skills","devlify-marketplace","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F196752365?v=4","01M7BPJC94F4G2AG0T3N220BQ3","Sadiq Abdullahi","01M7BPJC9QENFCHFM5NEFAJR1Y",1,"MIT","https:\u002F\u002Fgithub.com\u002Fdevlify-marketplace\u002Fdevlify-skills\u002Fblob\u002Fmain\u002Fra-qm-team\u002Fskills\u002Finformation-security-manager-iso27001\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: \"information-security-manager-iso27001\"\ndescription: ISO 27001 ISMS implementation and cybersecurity governance for HealthTech and MedTech companies. Use when designing an ISMS, running security risk assessments, implementing controls, pursuing ISO 27001 certification, preparing security audits, responding to security incidents, or verifying compliance. Covers ISO 27001, ISO 27002, healthcare security, and medical device cybersecurity.\n---\n\n# Information Security Manager - ISO 27001\n\nImplement and manage Information Security Management Systems (ISMS) aligned with ISO 27001:2022 and healthcare regulatory requirements.\n\n---\n\n## Table of Contents\n\n- [Trigger Phrases](#trigger-phrases)\n- [Quick Start](#quick-start)\n- [Tools](#tools)\n- [Workflows](#workflows)\n- [Reference Guides](#reference-guides)\n- [Validation Checkpoints](#validation-checkpoints)\n\n---\n\n## Trigger Phrases\n\nUse this skill when you hear:\n- \"implement ISO 27001\"\n- \"ISMS implementation\"\n- \"security risk assessment\"\n- \"information security policy\"\n- \"ISO 27001 certification\"\n- \"security controls implementation\"\n- \"incident response plan\"\n- \"healthcare data security\"\n- \"medical device cybersecurity\"\n- \"security compliance audit\"\n\n---\n\n## Quick Start\n\n### Run Security Risk Assessment\n\n```bash\npython scripts\u002Frisk_assessment.py --scope \"patient-data-system\" --output risk_register.json\n```\n\n### Check Compliance Status\n\n```bash\npython scripts\u002Fcompliance_checker.py --standard iso27001 --controls-file controls.csv\n```\n\n### Generate Gap Analysis Report\n\n```bash\npython scripts\u002Fcompliance_checker.py --standard iso27001 --gap-analysis --output gaps.md\n```\n\n---\n\n## Tools\n\n### risk_assessment.py\n\nAutomated security risk assessment following ISO 27001 Clause 6.1.2 methodology.\n\n**Usage:**\n\n```bash\n# Full risk assessment\npython scripts\u002Frisk_assessment.py --scope \"cloud-infrastructure\" --output risks.json\n\n# Healthcare-specific assessment\npython scripts\u002Frisk_assessment.py --scope \"ehr-system\" --template healthcare --output risks.json\n\n# Quick asset-based assessment\npython scripts\u002Frisk_assessment.py --assets assets.csv --output risks.json\n```\n\n**Parameters:**\n\n| Parameter | Required | Description |\n|-----------|----------|-------------|\n| `--scope` | Yes | System or area to assess |\n| `--template` | No | Assessment template: `general`, `healthcare`, `cloud` |\n| `--assets` | No | CSV file with asset inventory |\n| `--output` | No | Output file (default: stdout) |\n| `--format` | No | Output format: `json`, `csv`, `markdown` |\n\n**Output:**\n- Asset inventory with classification\n- Threat and vulnerability mapping\n- Risk scores (likelihood × impact)\n- Treatment recommendations\n- Residual risk calculations\n\n### compliance_checker.py\n\nVerify ISO 27001\u002F27002 control implementation status.\n\n**Usage:**\n\n```bash\n# Check all ISO 27001 controls\npython scripts\u002Fcompliance_checker.py --standard iso27001\n\n# Gap analysis with recommendations\npython scripts\u002Fcompliance_checker.py --standard iso27001 --gap-analysis\n\n# Check specific control domains\npython scripts\u002Fcompliance_checker.py --standard iso27001 --domains \"access-control,cryptography\"\n\n# Export compliance report\npython scripts\u002Fcompliance_checker.py --standard iso27001 --output compliance_report.md\n```\n\n**Parameters:**\n\n| Parameter | Required | Description |\n|-----------|----------|-------------|\n| `--standard` | Yes | Standard to check: `iso27001`, `iso27002`, `hipaa` |\n| `--controls-file` | No | CSV with current control status |\n| `--gap-analysis` | No | Include remediation recommendations |\n| `--domains` | No | Specific control domains to check |\n| `--output` | No | Output file path |\n\n**Output:**\n- Control implementation status\n- Compliance percentage by domain\n- Gap analysis with priorities\n- Remediation recommendations\n\n---\n\n## Workflows\n\n### Workflow 1: ISMS Implementation\n\n**Step 1: Define Scope and Context**\n\nDocument organizational context and ISMS boundaries:\n- Identify interested parties and requirements\n- Define ISMS scope and boundaries\n- Document internal\u002Fexternal issues\n\n**Validation:** Scope statement reviewed and approved by management.\n\n**Step 2: Conduct Risk Assessment**\n\n```bash\npython scripts\u002Frisk_assessment.py --scope \"full-organization\" --template general --output initial_risks.json\n```\n\n- Identify information assets\n- Assess threats and vulnerabilities\n- Calculate risk levels\n- Determine risk treatment options\n\n**Validation:** Risk register contains all critical assets with assigned owners.\n\n**Step 3: Select and Implement Controls**\n\nMap risks to ISO 27002 controls:\n\n```bash\npython scripts\u002Fcompliance_checker.py --standard iso27002 --gap-analysis --output control_gaps.md\n```\n\nControl categories:\n- Organizational (policies, roles, responsibilities)\n- People (screening, awareness, training)\n- Physical (perimeters, equipment, media)\n- Technological (access, crypto, network, application)\n\n**Validation:** Statement of Applicability (SoA) documents all controls with justification.\n\n**Step 4: Establish Monitoring**\n\nDefine security metrics:\n- Incident count and severity trends\n- Control effectiveness scores\n- Training completion rates\n- Audit findings closure rate\n\n**Validation:** Dashboard shows real-time compliance status.\n\n### Workflow 2: Security Risk Assessment\n\n**Step 1: Asset Identification**\n\nCreate asset inventory:\n\n| Asset Type | Examples | Classification |\n|------------|----------|----------------|\n| Information | Patient records, source code | Confidential |\n| Software | EHR system, APIs | Critical |\n| Hardware | Servers, medical devices | High |\n| Services | Cloud hosting, backup | High |\n| People | Admin accounts, developers | Varies |\n\n**Validation:** All assets have assigned owners and classifications.\n\n**Step 2: Threat Analysis**\n\nIdentify threats per asset category:\n\n| Asset | Threats | Likelihood |\n|-------|---------|------------|\n| Patient data | Unauthorized access, breach | High |\n| Medical devices | Malware, tampering | Medium |\n| Cloud services | Misconfiguration, outage | Medium |\n| Credentials | Phishing, brute force | High |\n\n**Validation:** Threat model covers top-10 industry threats.\n\n**Step 3: Vulnerability Assessment**\n\n```bash\npython scripts\u002Frisk_assessment.py --scope \"network-infrastructure\" --output vuln_risks.json\n```\n\nDocument vulnerabilities:\n- Technical (unpatched systems, weak configs)\n- Process (missing procedures, gaps)\n- People (lack of training, insider risk)\n\n**Validation:** Vulnerability scan results mapped to risk register.\n\n**Step 4: Risk Evaluation and Treatment**\n\nCalculate risk: `Risk = Likelihood × Impact`\n\n| Risk Level | Score | Treatment |\n|------------|-------|-----------|\n| Critical | 20-25 | Immediate action required |\n| High | 15-19 | Treatment plan within 30 days |\n| Medium | 10-14 | Treatment plan within 90 days |\n| Low | 5-9 | Accept or monitor |\n| Minimal | 1-4 | Accept |\n\n**Validation:** All high\u002Fcritical risks have approved treatment plans.\n\n### Workflow 3: Incident Response\n\n**Step 1: Detection and Reporting**\n\nIncident categories:\n- Security breach (unauthorized access)\n- Malware infection\n- Data leakage\n- System compromise\n- Policy violation\n\n**Validation:** Incident logged within 15 minutes of detection.\n\n**Step 2: Triage and Classification**\n\n| Severity | Criteria | Response Time |\n|----------|----------|---------------|\n| Critical | Data breach, system down | Immediate |\n| High | Active threat, significant risk | 1 hour |\n| Medium | Contained threat, limited impact | 4 hours |\n| Low | Minor violation, no impact | 24 hours |\n\n**Validation:** Severity assigned and escalation triggered if needed.\n\n**Step 3: Containment and Eradication**\n\nImmediate actions:\n1. Isolate affected systems\n2. Preserve evidence\n3. Block threat vectors\n4. Remove malicious artifacts\n\n**Validation:** Containment confirmed, no ongoing compromise.\n\n**Step 4: Recovery and Lessons Learned**\n\nPost-incident activities:\n1. Restore systems from clean backups\n2. Verify integrity before reconnection\n3. Document timeline and actions\n4. Conduct post-incident review\n5. Update controls and procedures\n\n**Validation:** Post-incident report completed within 5 business days.\n\n---\n\n## Reference Guides\n\n### When to Use Each Reference\n\n**references\u002Fiso27001-controls.md**\n- Control selection for SoA\n- Implementation guidance\n- Evidence requirements\n- Audit preparation\n\n**references\u002Frisk-assessment-guide.md**\n- Risk methodology selection\n- Asset classification criteria\n- Threat modeling approaches\n- Risk calculation methods\n\n**references\u002Fincident-response.md**\n- Response procedures\n- Escalation matrices\n- Communication templates\n- Recovery checklists\n\n---\n\n## Validation Checkpoints\n\n### ISMS Implementation Validation\n\n| Phase | Checkpoint | Evidence Required |\n|-------|------------|-------------------|\n| Scope | Scope approved | Signed scope document |\n| Risk | Register complete | Risk register with owners |\n| Controls | SoA approved | Statement of Applicability |\n| Operation | Metrics active | Dashboard screenshots |\n| Audit | Internal audit done | Audit report |\n\n### Certification Readiness\n\nBefore Stage 1 audit:\n- [ ] ISMS scope documented and approved\n- [ ] Information security policy published\n- [ ] Risk assessment completed\n- [ ] Statement of Applicability finalized\n- [ ] Internal audit conducted\n- [ ] Management review completed\n- [ ] Nonconformities addressed\n\nBefore Stage 2 audit:\n- [ ] Controls implemented and operational\n- [ ] Evidence of effectiveness available\n- [ ] Staff trained and aware\n- [ ] Incidents logged and managed\n- [ ] Metrics collected for 3+ months\n\n### Compliance Verification\n\nRun periodic checks:\n\n```bash\n# Monthly compliance check\npython scripts\u002Fcompliance_checker.py --standard iso27001 --output monthly_$(date +%Y%m).md\n\n# Quarterly gap analysis\npython scripts\u002Fcompliance_checker.py --standard iso27001 --gap-analysis --output quarterly_gaps.md\n```\n\n---\n\n## Worked Example: Healthcare Risk Assessment\n\n**Scenario:** Assess security risks for a patient data management system.\n\n### Step 1: Define Assets\n\n```bash\npython scripts\u002Frisk_assessment.py --scope \"patient-data-system\" --template healthcare\n```\n\n**Asset inventory output:**\n\n| Asset ID | Asset | Type | Owner | Classification |\n|----------|-------|------|-------|----------------|\n| A001 | Patient database | Information | DBA Team | Confidential |\n| A002 | EHR application | Software | App Team | Critical |\n| A003 | Database server | Hardware | Infra Team | High |\n| A004 | Admin credentials | Access | Security | Critical |\n\n### Step 2: Identify Risks\n\n**Risk register output:**\n\n| Risk ID | Asset | Threat | Vulnerability | L | I | Score |\n|---------|-------|--------|---------------|---|---|-------|\n| R001 | A001 | Data breach | Weak encryption | 3 | 5 | 15 |\n| R002 | A002 | SQL injection | Input validation | 4 | 4 | 16 |\n| R003 | A004 | Credential theft | No MFA | 4 | 5 | 20 |\n\n### Step 3: Determine Treatment\n\n| Risk | Treatment | Control | Timeline |\n|------|-----------|---------|----------|\n| R001 | Mitigate | Implement AES-256 encryption | 30 days |\n| R002 | Mitigate | Add input validation, WAF | 14 days |\n| R003 | Mitigate | Enforce MFA for all admins | 7 days |\n\n### Step 4: Verify Implementation\n\n```bash\npython scripts\u002Fcompliance_checker.py --controls-file implemented_controls.csv\n```\n\n**Verification output:**\n\n```\nControl Implementation Status\n=============================\nCryptography (A.8.24): IMPLEMENTED\n  - AES-256 at rest: YES\n  - TLS 1.3 in transit: YES\n\nAccess Control (A.8.5): IMPLEMENTED\n  - MFA enabled: YES\n  - Admin accounts: 100% coverage\n\nApplication Security (A.8.26): PARTIAL\n  - Input validation: YES\n  - WAF deployed: PENDING\n\nOverall Compliance: 87%\n```\n","# Information Security Manager - ISO 27001\n\nImplement and manage Information Security Management Systems (ISMS) aligned with ISO 27001:2022 and healthcare regulatory requirements.\n\n---\n\n## Table of Contents\n\n- [Trigger Phrases](#trigger-phrases)\n- [Quick Start](#quick-start)\n- [Tools](#tools)\n- [Workflows](#workflows)\n- [Reference Guides](#reference-guides)\n- [Validation Checkpoints](#validation-checkpoints)\n\n---\n\n## Trigger Phrases\n\nUse this skill when you hear:\n- \"implement ISO 27001\"\n- \"ISMS implementation\"\n- \"security risk assessment\"\n- \"information security policy\"\n- \"ISO 27001 certification\"\n- \"security controls implementation\"\n- \"incident response plan\"\n- \"healthcare data security\"\n- \"medical device cybersecurity\"\n- \"security compliance audit\"\n\n---\n\n## Quick Start\n\n### Run Security Risk Assessment\n\n```bash\npython scripts\u002Frisk_assessment.py --scope \"patient-data-system\" --output risk_register.json\n```\n\n### Check Compliance Status\n\n```bash\npython scripts\u002Fcompliance_checker.py --standard iso27001 --controls-file controls.csv\n```\n\n### Generate Gap Analysis Report\n\n```bash\npython scripts\u002Fcompliance_checker.py --standard iso27001 --gap-analysis --output gaps.md\n```\n\n---\n\n## Tools\n\n### risk_assessment.py\n\nAutomated security risk assessment following ISO 27001 Clause 6.1.2 methodology.\n\n**Usage:**\n\n```bash\n# Full risk assessment\npython scripts\u002Frisk_assessment.py --scope \"cloud-infrastructure\" --output risks.json\n\n# Healthcare-specific assessment\npython scripts\u002Frisk_assessment.py --scope \"ehr-system\" --template healthcare --output risks.json\n\n# Quick asset-based assessment\npython scripts\u002Frisk_assessment.py --assets assets.csv --output risks.json\n```\n\n**Parameters:**\n\n| Parameter | Required | Description |\n|-----------|----------|-------------|\n| `--scope` | Yes | System or area to assess |\n| `--template` | No | Assessment template: `general`, `healthcare`, `cloud` |\n| `--assets` | No | CSV file with asset inventory |\n| `--output` | No | Output file (default: stdout) |\n| `--format` | No | Output format: `json`, `csv`, `markdown` |\n\n**Output:**\n- Asset inventory with classification\n- Threat and vulnerability mapping\n- Risk scores (likelihood × impact)\n- Treatment recommendations\n- Residual risk calculations\n\n### compliance_checker.py\n\nVerify ISO 27001\u002F27002 control implementation status.\n\n**Usage:**\n\n```bash\n# Check all ISO 27001 controls\npython scripts\u002Fcompliance_checker.py --standard iso27001\n\n# Gap analysis with recommendations\npython scripts\u002Fcompliance_checker.py --standard iso27001 --gap-analysis\n\n# Check specific control domains\npython scripts\u002Fcompliance_checker.py --standard iso27001 --domains \"access-control,cryptography\"\n\n# Export compliance report\npython scripts\u002Fcompliance_checker.py --standard iso27001 --output compliance_report.md\n```\n\n**Parameters:**\n\n| Parameter | Required | Description |\n|-----------|----------|-------------|\n| `--standard` | Yes | Standard to check: `iso27001`, `iso27002`, `hipaa` |\n| `--controls-file` | No | CSV with current control status |\n| `--gap-analysis` | No | Include remediation recommendations |\n| `--domains` | No | Specific control domains to check |\n| `--output` | No | Output file path |\n\n**Output:**\n- Control implementation status\n- Compliance percentage by domain\n- Gap analysis with priorities\n- Remediation recommendations\n\n---\n\n## Workflows\n\n### Workflow 1: ISMS Implementation\n\n**Step 1: Define Scope and Context**\n\nDocument organizational context and ISMS boundaries:\n- Identify interested parties and requirements\n- Define ISMS scope and boundaries\n- Document internal\u002Fexternal issues\n\n**Validation:** Scope statement reviewed and approved by management.\n\n**Step 2: Conduct Risk Assessment**\n\n```bash\npython scripts\u002Frisk_assessment.py --scope \"full-organization\" --template general --output initial_risks.json\n```\n\n- Identify information assets\n- Assess threats and vulnerabilities\n- Calculate risk levels\n- Determine risk treatment options\n\n**Validation:** Risk register contains all critical assets with assigned owners.\n\n**Step 3: Select and Implement Controls**\n\nMap risks to ISO 27002 controls:\n\n```bash\npython scripts\u002Fcompliance_checker.py --standard iso27002 --gap-analysis --output control_gaps.md\n```\n\nControl categories:\n- Organizational (policies, roles, responsibilities)\n- People (screening, awareness, training)\n- Physical (perimeters, equipment, media)\n- Technological (access, crypto, network, application)\n\n**Validation:** Statement of Applicability (SoA) documents all controls with justification.\n\n**Step 4: Establish Monitoring**\n\nDefine security metrics:\n- Incident count and severity trends\n- Control effectiveness scores\n- Training completion rates\n- Audit findings closure rate\n\n**Validation:** Dashboard shows real-time compliance status.\n\n### Workflow 2: Security Risk Assessment\n\n**Step 1: Asset Identification**\n\nCreate asset inventory:\n\n| Asset Type | Examples | Classification |\n|------------|----------|----------------|\n| Information | Patient records, source code | Confidential |\n| Software | EHR system, APIs | Critical |\n| Hardware | Servers, medical devices | High |\n| Services | Cloud hosting, backup | High |\n| People | Admin accounts, developers | Varies |\n\n**Validation:** All assets have assigned owners and classifications.\n\n**Step 2: Threat Analysis**\n\nIdentify threats per asset category:\n\n| Asset | Threats | Likelihood |\n|-------|---------|------------|\n| Patient data | Unauthorized access, breach | High |\n| Medical devices | Malware, tampering | Medium |\n| Cloud services | Misconfiguration, outage | Medium |\n| Credentials | Phishing, brute force | High |\n\n**Validation:** Threat model covers top-10 industry threats.\n\n**Step 3: Vulnerability Assessment**\n\n```bash\npython scripts\u002Frisk_assessment.py --scope \"network-infrastructure\" --output vuln_risks.json\n```\n\nDocument vulnerabilities:\n- Technical (unpatched systems, weak configs)\n- Process (missing procedures, gaps)\n- People (lack of training, insider risk)\n\n**Validation:** Vulnerability scan results mapped to risk register.\n\n**Step 4: Risk Evaluation and Treatment**\n\nCalculate risk: `Risk = Likelihood × Impact`\n\n| Risk Level | Score | Treatment |\n|------------|-------|-----------|\n| Critical | 20-25 | Immediate action required |\n| High | 15-19 | Treatment plan within 30 days |\n| Medium | 10-14 | Treatment plan within 90 days |\n| Low | 5-9 | Accept or monitor |\n| Minimal | 1-4 | Accept |\n\n**Validation:** All high\u002Fcritical risks have approved treatment plans.\n\n### Workflow 3: Incident Response\n\n**Step 1: Detection and Reporting**\n\nIncident categories:\n- Security breach (unauthorized access)\n- Malware infection\n- Data leakage\n- System compromise\n- Policy violation\n\n**Validation:** Incident logged within 15 minutes of detection.\n\n**Step 2: Triage and Classification**\n\n| Severity | Criteria | Response Time |\n|----------|----------|---------------|\n| Critical | Data breach, system down | Immediate |\n| High | Active threat, significant risk | 1 hour |\n| Medium | Contained threat, limited impact | 4 hours |\n| Low | Minor violation, no impact | 24 hours |\n\n**Validation:** Severity assigned and escalation triggered if needed.\n\n**Step 3: Containment and Eradication**\n\nImmediate actions:\n1. Isolate affected systems\n2. Preserve evidence\n3. Block threat vectors\n4. Remove malicious artifacts\n\n**Validation:** Containment confirmed, no ongoing compromise.\n\n**Step 4: Recovery and Lessons Learned**\n\nPost-incident activities:\n1. Restore systems from clean backups\n2. Verify integrity before reconnection\n3. Document timeline and actions\n4. Conduct post-incident review\n5. Update controls and procedures\n\n**Validation:** Post-incident report completed within 5 business days.\n\n---\n\n## Reference Guides\n\n### When to Use Each Reference\n\n**references\u002Fiso27001-controls.md**\n- Control selection for SoA\n- Implementation guidance\n- Evidence requirements\n- Audit preparation\n\n**references\u002Frisk-assessment-guide.md**\n- Risk methodology selection\n- Asset classification criteria\n- Threat modeling approaches\n- Risk calculation methods\n\n**references\u002Fincident-response.md**\n- Response procedures\n- Escalation matrices\n- Communication templates\n- Recovery checklists\n\n---\n\n## Validation Checkpoints\n\n### ISMS Implementation Validation\n\n| Phase | Checkpoint | Evidence Required |\n|-------|------------|-------------------|\n| Scope | Scope approved | Signed scope document |\n| Risk | Register complete | Risk register with owners |\n| Controls | SoA approved | Statement of Applicability |\n| Operation | Metrics active | Dashboard screenshots |\n| Audit | Internal audit done | Audit report |\n\n### Certification Readiness\n\nBefore Stage 1 audit:\n- [ ] ISMS scope documented and approved\n- [ ] Information security policy published\n- [ ] Risk assessment completed\n- [ ] Statement of Applicability finalized\n- [ ] Internal audit conducted\n- [ ] Management review completed\n- [ ] Nonconformities addressed\n\nBefore Stage 2 audit:\n- [ ] Controls implemented and operational\n- [ ] Evidence of effectiveness available\n- [ ] Staff trained and aware\n- [ ] Incidents logged and managed\n- [ ] Metrics collected for 3+ months\n\n### Compliance Verification\n\nRun periodic checks:\n\n```bash\n# Monthly compliance check\npython scripts\u002Fcompliance_checker.py --standard iso27001 --output monthly_$(date +%Y%m).md\n\n# Quarterly gap analysis\npython scripts\u002Fcompliance_checker.py --standard iso27001 --gap-analysis --output quarterly_gaps.md\n```\n\n---\n\n## Worked Example: Healthcare Risk Assessment\n\n**Scenario:** Assess security risks for a patient data management system.\n\n### Step 1: Define Assets\n\n```bash\npython scripts\u002Frisk_assessment.py --scope \"patient-data-system\" --template healthcare\n```\n\n**Asset inventory output:**\n\n| Asset ID | Asset | Type | Owner | Classification |\n|----------|-------|------|-------|----------------|\n| A001 | Patient database | Information | DBA Team | Confidential |\n| A002 | EHR application | Software | App Team | Critical |\n| A003 | Database server | Hardware | Infra Team | High |\n| A004 | Admin credentials | Access | Security | Critical |\n\n### Step 2: Identify Risks\n\n**Risk register output:**\n\n| Risk ID | Asset | Threat | Vulnerability | L | I | Score |\n|---------|-------|--------|---------------|---|---|-------|\n| R001 | A001 | Data breach | Weak encryption | 3 | 5 | 15 |\n| R002 | A002 | SQL injection | Input validation | 4 | 4 | 16 |\n| R003 | A004 | Credential theft | No MFA | 4 | 5 | 20 |\n\n### Step 3: Determine Treatment\n\n| Risk | Treatment | Control | Timeline |\n|------|-----------|---------|----------|\n| R001 | Mitigate | Implement AES-256 encryption | 30 days |\n| R002 | Mitigate | Add input validation, WAF | 14 days |\n| R003 | Mitigate | Enforce MFA for all admins | 7 days |\n\n### Step 4: Verify Implementation\n\n```bash\npython scripts\u002Fcompliance_checker.py --controls-file implemented_controls.csv\n```\n\n**Verification output:**\n\n```\nControl Implementation Status\n=============================\nCryptography (A.8.24): IMPLEMENTED\n  - AES-256 at rest: YES\n  - TLS 1.3 in transit: YES\n\nAccess Control (A.8.5): IMPLEMENTED\n  - MFA enabled: YES\n  - Admin accounts: 100% coverage\n\nApplication Security (A.8.26): PARTIAL\n  - Input validation: YES\n  - WAF deployed: PENDING\n\nOverall Compliance: 87%\n```\n",{"name":5,"description":7},"main","7e219d4f922f94392cb65883ba910846c3c2e71b","ra-qm-team\u002Fskills\u002Finformation-security-manager-iso27001",0,"https:\u002F\u002Fgithub.com\u002Fdevlify-marketplace\u002Fdevlify-skills","https:\u002F\u002Fgithub.com\u002Fdevlify-marketplace","devlify.com.ng","Software Developer & full-stack dev building secure web and mobile applications, AI\u002FML solutions, and scalable digital products. Founder of Devlify ","2026-08-30 00:40:50",{"source":8,"skillName":5,"commands":34,"prompt":44,"zipAvailable":45},[35,38,41],{"tool":36,"command":37},"npx","npx skills add devlify-marketplace\u002Fdevlify-skills --skill information-security-manager-iso27001",{"tool":39,"command":40},"bunx","bunx skills add devlify-marketplace\u002Fdevlify-skills --skill information-security-manager-iso27001",{"tool":42,"command":43},"pnpm","pnpm dlx skills add devlify-marketplace\u002Fdevlify-skills --skill information-security-manager-iso27001","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fdevlify-marketplace\u002Fdevlify-skills\u002Fblob\u002Fmain\u002Fra-qm-team\u002Fskills\u002Finformation-security-manager-iso27001\u002FSKILL.md",true,[47,53,57,61,67],{"path":48,"resourceType":49,"resourceTypeDesc":50,"sizeBytes":51,"sourceHtmlUrl":52},"references\u002Fincident-response.md","REFERENCE","参考文档",11273,"https:\u002F\u002Fgithub.com\u002Fdevlify-marketplace\u002Fdevlify-skills\u002Fblob\u002Fmain\u002Fra-qm-team\u002Fskills\u002Finformation-security-manager-iso27001\u002Freferences\u002Fincident-response.md",{"path":54,"resourceType":49,"resourceTypeDesc":50,"sizeBytes":55,"sourceHtmlUrl":56},"references\u002Fiso27001-controls.md",9667,"https:\u002F\u002Fgithub.com\u002Fdevlify-marketplace\u002Fdevlify-skills\u002Fblob\u002Fmain\u002Fra-qm-team\u002Fskills\u002Finformation-security-manager-iso27001\u002Freferences\u002Fiso27001-controls.md",{"path":58,"resourceType":49,"resourceTypeDesc":50,"sizeBytes":59,"sourceHtmlUrl":60},"references\u002Frisk-assessment-guide.md",8440,"https:\u002F\u002Fgithub.com\u002Fdevlify-marketplace\u002Fdevlify-skills\u002Fblob\u002Fmain\u002Fra-qm-team\u002Fskills\u002Finformation-security-manager-iso27001\u002Freferences\u002Frisk-assessment-guide.md",{"path":62,"resourceType":63,"resourceTypeDesc":64,"sizeBytes":65,"sourceHtmlUrl":66},"scripts\u002Fcompliance_checker.py","SCRIPT","脚本",16201,"https:\u002F\u002Fgithub.com\u002Fdevlify-marketplace\u002Fdevlify-skills\u002Fblob\u002Fmain\u002Fra-qm-team\u002Fskills\u002Finformation-security-manager-iso27001\u002Fscripts\u002Fcompliance_checker.py",{"path":68,"resourceType":63,"resourceTypeDesc":64,"sizeBytes":69,"sourceHtmlUrl":70},"scripts\u002Frisk_assessment.py",17356,"https:\u002F\u002Fgithub.com\u002Fdevlify-marketplace\u002Fdevlify-skills\u002Fblob\u002Fmain\u002Fra-qm-team\u002Fskills\u002Finformation-security-manager-iso27001\u002Fscripts\u002Frisk_assessment.py",[72,79,86,93,100,107],{"skillNo":73,"name":74,"nameZh":6,"description":75,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":76,"categories":77,"keywords":78,"publishedAt":19},"01M7BRV5Q3BJT22HG25WJFTKZN","syllabus","Generates a curated supplementary reading list from any course syllabus using Consensus academic search. Grill-me intake (syllabus input format + course audience + year range) plus a grouping forcing-options checkpoint before any search runs — so the reading list matches the course's level and recency need. Parses the syllabus to extract topics and learning outcomes, searches Consensus for recent peer-reviewed papers per topic, and produces a professionally formatted .docx with clickable Consensus links, plain-language summaries calibrated to audience level, and Bloom-higher-order discussion questions tied to course learning goals. Use when the user uploads a syllabus, course outline, or curriculum document and wants supplementary readings (e.g., 'create a reading list from this syllabus', 'find recent papers for my course') — even casual mentions with a syllabus attached should trigger this skill.","https:\u002F\u002Fgithub.com\u002Fdevlify-marketplace\u002Fdevlify-skills\u002Fblob\u002Fmain\u002Fresearch\u002Fsyllabus\u002Fskills\u002Fsyllabus\u002FSKILL.md",[],[],{"skillNo":80,"name":81,"nameZh":6,"description":82,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":83,"categories":84,"keywords":85,"publishedAt":19},"01M7BRTW6RRTHXT6SBE41AY5GD","research","Default entry point for any research request — a hybrid router that classifies the question deterministically and either delegates to a specialist research skill (pulse for trends\u002Fsentiment, grants for NIH funding, litreview for academic literature, syllabus for course reading, patent for prior-art + IP landscape, dossier for entity research, deepread for evidence-first reading of supplied documents) or runs its own plan-decompose-multi-source-search-synthesize-cite fallback workflow when no specialist matches. Always surfaces the routing decision so users can override. Use when the user makes any research request that doesn't obviously match a more-specific specialist skill (e.g., \"research [topic]\", \"look into [topic]\", \"what do we know about [topic]\", \"investigate [topic]\", \"find me information on [topic]\", \"do some research on [topic]\", \"I need to understand [topic]\"). Output is a markdown briefing (default) or .docx document (on request) with full citations and an audit log.","https:\u002F\u002Fgithub.com\u002Fdevlify-marketplace\u002Fdevlify-skills\u002Fblob\u002Fmain\u002Fresearch\u002Fresearch\u002Fskills\u002Fresearch\u002FSKILL.md",[],[],{"skillNo":87,"name":88,"nameZh":6,"description":89,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":90,"categories":91,"keywords":92,"publishedAt":19},"01M7BRTMK3PGPNH76R2HY57AKC","pulse","Multi-source recency research skill that takes the pulse of any topic across Reddit, Hacker News, the open web, and optionally X\u002FTwitter within a configurable recent window (default 30 days). Forcing intake clarifies topic specificity, angle (trend\u002Fsentiment\u002Fproblems\u002Fopportunities\u002Fcomparison), time window, and platform scope before searching. Returns a synthesized briefing with citations, engagement metrics, and cross-platform pattern analysis. Use when the user requests multi-source recency intelligence on a topic (e.g., 'pulse on [topic]', 'what's happening with [topic]', 'what are people saying about [topic]', 'current conversation about [topic]', 'take the pulse of [topic]', 'trending: [topic]', 'find me info on [topic]'), and for competitor research, trend discovery, tool comparisons, and audience sentiment analysis.","https:\u002F\u002Fgithub.com\u002Fdevlify-marketplace\u002Fdevlify-skills\u002Fblob\u002Fmain\u002Fresearch\u002Fpulse\u002Fskills\u002Fpulse\u002FSKILL.md",[],[],{"skillNo":94,"name":95,"nameZh":6,"description":96,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":97,"categories":98,"keywords":99,"publishedAt":19},"01M7BRTAR0YJWNZ2AP3QTH39BW","patent","Patent prior-art and landscape intelligence skill — not generic patent help. Commits to one of five sub-use-cases via forcing intake (novelty search \u002F freedom-to-operate \u002F competitive landscape \u002F acquisition diligence \u002F litigation prior-art) before any search runs. Searches Google Patents, Espacenet, USPTO, and optionally Lens.org for citation-graph signals. Output is an editable Word document (.docx) with verdict, ranked closest art (claim-text extracted), CPC-class-aware landscape, family-resolved hits, geographic coverage, FTO flags where applicable, strategy recommendations, and full audit log. Use when the user asks for patent searching or analysis (e.g., 'prior art search for [invention]', 'freedom to operate analysis for [product]'). Produces search signal, not legal advice — always recommends consulting a patent attorney before filing or licensing decisions. Trademark, copyright, and trade-secret questions are out of scope.","https:\u002F\u002Fgithub.com\u002Fdevlify-marketplace\u002Fdevlify-skills\u002Fblob\u002Fmain\u002Fresearch\u002Fpatent\u002Fskills\u002Fpatent\u002FSKILL.md",[],[],{"skillNo":101,"name":102,"nameZh":6,"description":103,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":104,"categories":105,"keywords":106,"publishedAt":19},"01M7BRT3J0V5A9V3VJ96G97AGW","notebooklm","Browser automation skill for controlling Google's NotebookLM. Use when the user wants anything done in NotebookLM (e.g., 'open NotebookLM', 'check my [name] notebook', 'ask my notebook about X', 'add [source] to NotebookLM', 'generate a Video Overview from my notebook', 'use NotebookLM Studio'). Handles reading and querying notebooks, adding sources (URLs, text, files, YouTube links, synthesized content), generating Studio outputs (Audio\u002FVideo Overviews, Mind Maps, Reports incl. Briefing Doc\u002FStudy Guide\u002FFAQ, Flashcards, Quiz, slide decks, infographics — discover the exact set from the live Studio panel; the UI evolves fast), and creating new notebooks. Requires browser automation environment — fails gracefully when unavailable.","https:\u002F\u002Fgithub.com\u002Fdevlify-marketplace\u002Fdevlify-skills\u002Fblob\u002Fmain\u002Fresearch\u002Fnotebooklm\u002Fskills\u002Fnotebooklm\u002FSKILL.md",[],[],{"skillNo":108,"name":109,"nameZh":6,"description":110,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":111,"categories":112,"keywords":113,"publishedAt":19},"01M7BRSS7P0CJP7X9ERDFYN6GC","litreview","Academic literature orientation skill that searches papers via free keyless APIs (PubMed E-utilities + OpenAlex) by default — with the Consensus MCP as an optional enhancement lane when connected — builds a strategic search plan using PICO (default) or SPIDER \u002F Decomposition \u002F hybrid as fallbacks, and synthesizes findings into a formatted Word (.docx) research guide. Grill-me intake (research question specificity + framework hint + tentative depth) before the recon search; a second forcing checkpoint after Phase 2 confirms framework + sub-areas + depth before searches consume budget. Configurable depth (5\u002F10\u002F20 queries) controls coverage vs. speed. Output is a 'launching pad' — an orientation guide that lets a researcher dive in confidently, not a finished review. Use when the user starts literature-oriented research (e.g., 'litreview on [topic]', 'literature review on [topic]', 'I'm starting a literature review on X', 'I'm writing a paper on X', 'help me research X', 'I'm doing research on X', 'can you help me research X'). Do NOT use for single one-off paper searches wanting a quick list — that's a plain PubMed\u002FOpenAlex (or Consensus) query.","https:\u002F\u002Fgithub.com\u002Fdevlify-marketplace\u002Fdevlify-skills\u002Fblob\u002Fmain\u002Fresearch\u002Flitreview\u002Fskills\u002Flitreview\u002FSKILL.md",[],[]]