Information Security Manager Iso27001

alirezarezvani/claude-skills/ra-qm-team/skills/information-security-manager-iso27001

作者 alirezarezvani19392f7a0826無授權條款27K 個星標收錄於 2026年10月8日更新於 2026年10月8日儲存庫5 週前更新

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.

AI 產生的概覽

指導 HealthTech 與 MedTech 企業的 ISO 27001 ISMS 導入、安全風險評估、控制項合規檢查與事件應變。

功能
提供建置 ISO 27001:2022 資訊安全管理系統的結構化工作流程,涵蓋範圍界定、風險評估、控制項選擇、監控與驗證準備。內含兩個 Python 指令碼:一個執行風險評估,產出資產清冊、威脅對應與風險評分;另一個檢查 ISO 27001/27002/HIPAA 控制項實作情形並輸出落差分析報告。參考指南涵蓋 ISO 27001 控制項、風險評估方法與事件應變程序。
適用情境
適用於設計或運作 ISMS、執行安全風險評估、實作或稽核 ISO 27001 控制項、準備驗證稽核,以及處理安全事件應變。主要針對醫療照護與醫療器材情境,例如病患資料系統與 EHR 平台。
執行需求
需要 Python 執行環境以執行隨附的 scripts/risk_assessment.py 與 scripts/compliance_checker.py。可選擇提供資產清冊與控制項狀態的 CSV 輸入檔案。未說明需要網路存取或憑證。

Information Security Manager - ISO 27001

Implement and manage Information Security Management Systems (ISMS) aligned with ISO 27001:2022 and healthcare regulatory requirements.


Table of Contents


Trigger Phrases

Use this skill when you hear:

  • "implement ISO 27001"
  • "ISMS implementation"
  • "security risk assessment"
  • "information security policy"
  • "ISO 27001 certification"
  • "security controls implementation"
  • "incident response plan"
  • "healthcare data security"
  • "medical device cybersecurity"
  • "security compliance audit"

Quick Start

Run Security Risk Assessment

bash
python scripts/risk_assessment.py --scope "patient-data-system" --output risk_register.json

Check Compliance Status

bash
python scripts/compliance_checker.py --standard iso27001 --controls-file controls.csv

Generate Gap Analysis Report

bash
python scripts/compliance_checker.py --standard iso27001 --gap-analysis --output gaps.md

Tools

risk_assessment.py

Automated security risk assessment following ISO 27001 Clause 6.1.2 methodology.

Usage:

bash
# Full risk assessmentpython scripts/risk_assessment.py --scope "cloud-infrastructure" --output risks.json
# Healthcare-specific assessmentpython scripts/risk_assessment.py --scope "ehr-system" --template healthcare --output risks.json
# Quick asset-based assessmentpython scripts/risk_assessment.py --assets assets.csv --output risks.json

Parameters:

ParameterRequiredDescription
--scopeYesSystem or area to assess
--templateNoAssessment template: general, healthcare, cloud
--assetsNoCSV file with asset inventory
--outputNoOutput file (default: stdout)
--formatNoOutput format: json, csv, markdown

Output:

  • Asset inventory with classification
  • Threat and vulnerability mapping
  • Risk scores (likelihood × impact)
  • Treatment recommendations
  • Residual risk calculations

compliance_checker.py

Verify ISO 27001/27002 control implementation status.

Usage:

bash
# Check all ISO 27001 controlspython scripts/compliance_checker.py --standard iso27001
# Gap analysis with recommendationspython scripts/compliance_checker.py --standard iso27001 --gap-analysis
# Check specific control domainspython scripts/compliance_checker.py --standard iso27001 --domains "access-control,cryptography"
# Export compliance reportpython scripts/compliance_checker.py --standard iso27001 --output compliance_report.md

Parameters:

ParameterRequiredDescription
--standardYesStandard to check: iso27001, iso27002, hipaa
--controls-fileNoCSV with current control status
--gap-analysisNoInclude remediation recommendations
--domainsNoSpecific control domains to check
--outputNoOutput file path

Output:

  • Control implementation status
  • Compliance percentage by domain
  • Gap analysis with priorities
  • Remediation recommendations

Workflows

Workflow 1: ISMS Implementation

Step 1: Define Scope and Context

Document organizational context and ISMS boundaries:

  • Identify interested parties and requirements
  • Define ISMS scope and boundaries
  • Document internal/external issues

Validation: Scope statement reviewed and approved by management.

Step 2: Conduct Risk Assessment

bash
python scripts/risk_assessment.py --scope "full-organization" --template general --output initial_risks.json
  • Identify information assets
  • Assess threats and vulnerabilities
  • Calculate risk levels
  • Determine risk treatment options

Validation: Risk register contains all critical assets with assigned owners.

Step 3: Select and Implement Controls

Map risks to ISO 27002 controls:

bash
python scripts/compliance_checker.py --standard iso27002 --gap-analysis --output control_gaps.md

Control categories:

  • Organizational (policies, roles, responsibilities)
  • People (screening, awareness, training)
  • Physical (perimeters, equipment, media)
  • Technological (access, crypto, network, application)

Validation: Statement of Applicability (SoA) documents all controls with justification.

Step 4: Establish Monitoring

Define security metrics:

  • Incident count and severity trends
  • Control effectiveness scores
  • Training completion rates
  • Audit findings closure rate

Validation: Dashboard shows real-time compliance status.

Workflow 2: Security Risk Assessment

Step 1: Asset Identification

Create asset inventory:

Asset TypeExamplesClassification
InformationPatient records, source codeConfidential
SoftwareEHR system, APIsCritical
HardwareServers, medical devicesHigh
ServicesCloud hosting, backupHigh
PeopleAdmin accounts, developersVaries

Validation: All assets have assigned owners and classifications.

Step 2: Threat Analysis

Identify threats per asset category:

AssetThreatsLikelihood
Patient dataUnauthorized access, breachHigh
Medical devicesMalware, tamperingMedium
Cloud servicesMisconfiguration, outageMedium
CredentialsPhishing, brute forceHigh

Validation: Threat model covers top-10 industry threats.

Step 3: Vulnerability Assessment

bash
python scripts/risk_assessment.py --scope "network-infrastructure" --output vuln_risks.json

Document vulnerabilities:

  • Technical (unpatched systems, weak configs)
  • Process (missing procedures, gaps)
  • People (lack of training, insider risk)

Validation: Vulnerability scan results mapped to risk register.

Step 4: Risk Evaluation and Treatment

Calculate risk: Risk = Likelihood × Impact

Risk LevelScoreTreatment
Critical20-25Immediate action required
High15-19Treatment plan within 30 days
Medium10-14Treatment plan within 90 days
Low5-9Accept or monitor
Minimal1-4Accept

Validation: All high/critical risks have approved treatment plans.

Workflow 3: Incident Response

Step 1: Detection and Reporting

Incident categories:

  • Security breach (unauthorized access)
  • Malware infection
  • Data leakage
  • System compromise
  • Policy violation

Validation: Incident logged within 15 minutes of detection.

Step 2: Triage and Classification

SeverityCriteriaResponse Time
CriticalData breach, system downImmediate
HighActive threat, significant risk1 hour
MediumContained threat, limited impact4 hours
LowMinor violation, no impact24 hours

Validation: Severity assigned and escalation triggered if needed.

Step 3: Containment and Eradication

Immediate actions:

  1. Isolate affected systems
  2. Preserve evidence
  3. Block threat vectors
  4. Remove malicious artifacts

Validation: Containment confirmed, no ongoing compromise.

Step 4: Recovery and Lessons Learned

Post-incident activities:

  1. Restore systems from clean backups
  2. Verify integrity before reconnection
  3. Document timeline and actions
  4. Conduct post-incident review
  5. Update controls and procedures

Validation: Post-incident report completed within 5 business days.


Reference Guides

When to Use Each Reference

references/iso27001-controls.md

  • Control selection for SoA
  • Implementation guidance
  • Evidence requirements
  • Audit preparation

references/risk-assessment-guide.md

  • Risk methodology selection
  • Asset classification criteria
  • Threat modeling approaches
  • Risk calculation methods

references/incident-response.md

  • Response procedures
  • Escalation matrices
  • Communication templates
  • Recovery checklists

Validation Checkpoints

ISMS Implementation Validation

PhaseCheckpointEvidence Required
ScopeScope approvedSigned scope document
RiskRegister completeRisk register with owners
ControlsSoA approvedStatement of Applicability
OperationMetrics activeDashboard screenshots
AuditInternal audit doneAudit report

Certification Readiness

Before Stage 1 audit:

  • ISMS scope documented and approved
  • Information security policy published
  • Risk assessment completed
  • Statement of Applicability finalized
  • Internal audit conducted
  • Management review completed
  • Nonconformities addressed

Before Stage 2 audit:

  • Controls implemented and operational
  • Evidence of effectiveness available
  • Staff trained and aware
  • Incidents logged and managed
  • Metrics collected for 3+ months

Compliance Verification

Run periodic checks:

bash
# Monthly compliance checkpython scripts/compliance_checker.py --standard iso27001 --output monthly_$(date +%Y%m).md
# Quarterly gap analysispython scripts/compliance_checker.py --standard iso27001 --gap-analysis --output quarterly_gaps.md

Worked Example: Healthcare Risk Assessment

Scenario: Assess security risks for a patient data management system.

Step 1: Define Assets

bash
python scripts/risk_assessment.py --scope "patient-data-system" --template healthcare

Asset inventory output:

Asset IDAssetTypeOwnerClassification
A001Patient databaseInformationDBA TeamConfidential
A002EHR applicationSoftwareApp TeamCritical
A003Database serverHardwareInfra TeamHigh
A004Admin credentialsAccessSecurityCritical

Step 2: Identify Risks

Risk register output:

Risk IDAssetThreatVulnerabilityLIScore
R001A001Data breachWeak encryption3515
R002A002SQL injectionInput validation4416
R003A004Credential theftNo MFA4520

Step 3: Determine Treatment

RiskTreatmentControlTimeline
R001MitigateImplement AES-256 encryption30 days
R002MitigateAdd input validation, WAF14 days
R003MitigateEnforce MFA for all admins7 days

Step 4: Verify Implementation

bash
python scripts/compliance_checker.py --controls-file implemented_controls.csv

Verification output:

Control Implementation Status=============================Cryptography (A.8.24): IMPLEMENTED  - AES-256 at rest: YES  - TLS 1.3 in transit: YES
Access Control (A.8.5): IMPLEMENTED  - MFA enabled: YES  - Admin accounts: 100% coverage
Application Security (A.8.26): PARTIAL  - Input validation: YES  - WAF deployed: PENDING
Overall Compliance: 87%

來源與署名

來源:alirezarezvani/claude-skills位於ra-qm-team/skills/information-security-manager-iso27001提交19392f7

授權條款: 無授權條款

內容歸原作者所有。SourceWeft 從公開儲存庫中收錄這些內容。

檢舉或申請下架