Product Launch Legal Review
anthropics/claude-for-legal
Runs a category-by-category legal review of a product launch from a PRD or tracker ticket, calibrated to your team's framework, and writes a review memo in house format.
Systematic risk identification, analysis, evaluation, and treatment aligned with ISO 27005, NIST RMF, and Hack23 ISMS risk register
$ npx skills add Hack23/cia --skill risk-assessment-methodology -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install Hack23/cia risk-assessment-methodology --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/Hack23/cia.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.github/skills/risk-assessment-methodology .claude/skills/risk-assessment-methodology && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "risk-assessment-methodology" agent skill from https://github.com/Hack23/cia/tree/master/.github/skills/risk-assessment-methodology into .claude/skills/risk-assessment-methodology/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "risk-assessment-methodology", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/Hack23/cia/tree/master/.github/skills/risk-assessment-methodologyType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add Hack23/cia --skill risk-assessment-methodology -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install Hack23/cia risk-assessment-methodology --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Hack23/cia.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.github/skills/risk-assessment-methodology .agents/skills/risk-assessment-methodology && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "risk-assessment-methodology" agent skill from https://github.com/Hack23/cia/tree/master/.github/skills/risk-assessment-methodology into .agents/skills/risk-assessment-methodology/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "risk-assessment-methodology", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add Hack23/cia --skill risk-assessment-methodology -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install Hack23/cia risk-assessment-methodology --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Hack23/cia.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.github/skills/risk-assessment-methodology .cursor/skills/risk-assessment-methodology && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "risk-assessment-methodology" agent skill from https://github.com/Hack23/cia/tree/master/.github/skills/risk-assessment-methodology into .cursor/skills/risk-assessment-methodology/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "risk-assessment-methodology", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/Hack23/cia.git --path .github/skills/risk-assessment-methodology--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add Hack23/cia --skill risk-assessment-methodology -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install Hack23/cia risk-assessment-methodology --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Hack23/cia.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.github/skills/risk-assessment-methodology .gemini/skills/risk-assessment-methodology && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "risk-assessment-methodology" agent skill from https://github.com/Hack23/cia/tree/master/.github/skills/risk-assessment-methodology into .gemini/skills/risk-assessment-methodology/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "risk-assessment-methodology", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install Hack23/cia risk-assessment-methodologyInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add Hack23/cia --skill risk-assessment-methodology -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/Hack23/cia.git skills-src && mkdir -p .github/skills && cp -r skills-src/.github/skills/risk-assessment-methodology .github/skills/risk-assessment-methodology && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "risk-assessment-methodology" agent skill from https://github.com/Hack23/cia/tree/master/.github/skills/risk-assessment-methodology into .github/skills/risk-assessment-methodology/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "risk-assessment-methodology", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add Hack23/cia --skill risk-assessment-methodology -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install Hack23/cia risk-assessment-methodology --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Hack23/cia.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.github/skills/risk-assessment-methodology .opencode/skills/risk-assessment-methodology && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "risk-assessment-methodology" agent skill from https://github.com/Hack23/cia/tree/master/.github/skills/risk-assessment-methodology into .opencode/skills/risk-assessment-methodology/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "risk-assessment-methodology", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
risk-assessment-methodologySystematic risk identification, analysis, evaluation, and treatment aligned with ISO 27005, NIST RMF, and Hack23 ISMS risk register
Risk Assessment Methodology is an agent skill from Hack23/cia. Systematic risk identification, analysis, evaluation, and treatment aligned with ISO 27005, NIST RMF, and Hack23 ISMS risk register
Its SKILL.md is about 5.2k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Legal & Compliance, covering Legal risk assessment. The repository describes itself as: Citizen Intelligence Agency. Open-source intelligence platform analyzing Swedish political activities using AI and data visualization. Tracks politicians, government… The licence is Apache-2.0.
Read from SKILL.md and the folder at commit bbed538. It shows what the files ask for, not the result of running them.
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
No scripts in the folder and no shell commands in SKILL.md (its code samples are python, mermaid, yaml and markdown).
From the folder's file list and the shell code blocks in SKILL.md.
Links to these hosts (documentation or services it may open):
img.shields.iogithub.comFrom URLs in SKILL.md, links to its own repository left out.
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Risk Assessment Methodology loads about 5.2k tokens when it runs. Until then it costs about 40 tokens; SKILL.md has 920 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
The full file from Hack23/cia at commit bbed538, republished under its Apache-2.0 licence (© Hack23). 920 words, ~5,202 tokens.
.claude/skills/risk-assessment-methodology/SKILL.md (or your agent's skills folder).This skill provides quantitative risk assessment methodology aligned with Hack23 AB's enterprise risk management framework. It enables security professionals and business leaders to systematically identify, analyze, evaluate, and treat risks using defensible statistical methods that demonstrate cybersecurity consulting expertise through measurable, data-driven risk quantification.
Apply this skill when:
Do NOT use for:
flowchart TD
START["🎯 Risk Assessment<br/>Initiation"] --> IDENTIFY["📋 Risk Identification<br/>Assets • Threats • Vulnerabilities"]
IDENTIFY --> ANALYZE["🔍 Risk Analysis"]
ANALYZE --> LIKELIHOOD["📊 Likelihood Assessment<br/>Historical + Industry + Expert"]
ANALYZE --> IMPACT["💰 Impact Assessment<br/>Financial • Operational • Reputational"]
LIKELIHOOD --> CALC["🔢 Risk Score Calculation<br/>Probability × Impact × 100"]
IMPACT --> CALC
CALC --> CATEGORY{Risk Level?}
CATEGORY -->|400-600| CRITICAL["🔴 Critical Risk<br/>Immediate action required"]
CATEGORY -->|200-399| HIGH["🟠 High Risk<br/>Priority mitigation needed"]
CATEGORY -->|100-199| MEDIUM["🟡 Medium Risk<br/>Planned controls required"]
CATEGORY -->|50-99| LOW["🟢 Low Risk<br/>Monitor and accept"]
CATEGORY -->|1-49| MINIMAL["⚪ Minimal Risk<br/>Accept risk"]
CRITICAL --> TREAT{Treatment<br/>Decision}
HIGH --> TREAT
MEDIUM --> TREAT
LOW --> ACCEPT["✅ Accept Risk<br/>Document in Risk Register"]
MINIMAL --> ACCEPT
TREAT -->|Reduce| MITIGATE["🛡️ Implement Controls<br/>Reduce likelihood or impact"]
TREAT -->|Transfer| TRANSFER["🤝 Insurance/Outsource<br/>Share financial burden"]
TREAT -->|Avoid| AVOID["🚫 Eliminate Activity<br/>Remove risk source"]
TREAT -->|Accept| ACCEPT_HIGH["📋 Document Acceptance<br/>CEO approval required"]
MITIGATE --> RESIDUAL["📉 Residual Risk<br/>Reassessment"]
TRANSFER --> RESIDUAL
AVOID --> RESIDUAL
ACCEPT_HIGH --> RESIDUAL
ACCEPT --> REGISTER["📊 Risk Register<br/>Tracking & Monitoring"]
RESIDUAL --> REGISTER
REGISTER --> REVIEW["🔄 Periodic Review<br/>Quarterly/Annual"]
REVIEW --> START
style START fill:#1565C0,stroke:#0D47A1,stroke-width:3px,color:#fff
style CRITICAL fill:#D32F2F,stroke:#B71C1C,stroke-width:3px,color:#fff
style HIGH fill:#FF9800,stroke:#F57C00,stroke-width:2px
style MEDIUM fill:#FFC107,stroke:#FFA000,stroke-width:2px
style LOW fill:#4CAF50,stroke:#2E7D32,stroke-width:2px,color:#fff
style MINIMAL fill:#9E9E9E,stroke:#616161,stroke-width:1px
style REGISTER fill:#9C27B0,stroke:#7B1FA2,stroke-width:2px,color:#fffEvaluate probability using descriptive categories with quantitative ranges:
| Likelihood | Badge | Probability | Annual Frequency | ARO | Definition | Examples |
|---|---|---|---|---|---|---|
| Almost Certain | Image: Almost Certain | 80-99% | 292-361 events/year | 0.8-0.99 | Expected to occur in most circumstances | Daily operational issues, routine maintenance |
| Likely | Image: Likely | 60-79% | 219-291 events/year | 0.6-0.79 | Will probably occur | Weekly service disruptions, staff availability issues |
| Possible | Image: Possible | 40-59% | 146-218 events/year | 0.4-0.59 | Might occur at some time | Monthly supplier issues, seasonal variations |
| Unlikely | Image: Unlikely | 20-39% | 73-145 events/year | 0.2-0.39 | Could occur but not expected | Quarterly security incidents, annual contract changes |
| Rare | Image: Rare | 5-19% | 18-72 events/year | 0.05-0.19 | May occur only in exceptional circumstances | Multi-year events, rare external factors |
| Exceptional | Image: Exceptional | <5% | <18 events/year | <0.05 | Rare, once-in-decade event | Black swan events, extreme scenarios |
Quantitative Data (Preferred):
# Historical frequency analysis
def calculate_aro(events_last_3_years, trend_factor=1.0):
"""Calculate Annual Rate of Occurrence from historical data"""
base_aro = sum(events_last_3_years) / 3
adjusted_aro = base_aro * trend_factor
return min(adjusted_aro, 0.99) # Cap at 99%
# Example: 8 incidents in 3 years, increasing trend
aro = calculate_aro([2, 3, 3], trend_factor=1.2) # = 0.32 (Unlikely)Qualitative Assessment (When Data Limited):
Evaluate business impact across multiple dimensions:
| Impact | Badge | Financial | Operational | Reputational | Regulatory |
|---|---|---|---|---|---|
| Catastrophic | Image: Catastrophic | >€50K | Complete shutdown | International media | Criminal charges |
| Critical | Image: Critical | €10K-50K | Major disruption | National media | Significant fines |
| High | Image: High | €1K-10K | Significant degradation | Industry attention | Moderate penalties |
| Moderate | Image: Moderate | €500-1K | Partial service impact | Regional visibility | Minor warnings |
| Low | Image: Low | €100-500 | Minor inconvenience | Limited local impact | Verbal guidance |
| Minimal | Image: Minimal | <€100 | No significant impact | No external visibility | No implications |
Formula: Risk Score = Likelihood (midpoint %) × Impact Score (1-6) × 100
Example 1: Data Breach Risk
Example 2: DDoS Attack Risk
Example 3: Ransomware Risk
| Risk Level | Score Range | Badge | Management Response | Review Frequency |
|---|---|---|---|---|
| Critical | 400-600 | Image: Critical | CEO immediate action, daily monitoring | Daily |
| High | 200-399 | Image: High | Weekly executive review | Weekly |
| Medium | 100-199 | Image: Medium | Monthly assessment | Monthly |
| Low | 50-99 | Image: Low | Quarterly monitoring | Quarterly |
| Minimal | 1-49 | Image: Minimal | Acceptance, periodic review | Annual |
Formula: SLE = Asset Value × Exposure Factor
Asset Value Categories:
| Category | Value Range | Examples |
|---|---|---|
| Mission Critical | €100K-500K | Core infrastructure, customer data |
| High Value | €50K-100K | Business applications, intellectual property |
| Standard | €10K-50K | Supporting systems, processes |
| Low Value | €1K-10K | Documentation, utilities |
Exposure Factor Guidelines:
| Exposure | Factor | Description |
|---|---|---|
| Complete Loss | 0.8-1.0 | Total destruction (ransomware, theft) |
| Major Loss | 0.5-0.8 | Significant damage (data corruption) |
| Moderate Loss | 0.2-0.5 | Partial damage (service disruption) |
| Minor Loss | 0.1-0.2 | Limited impact (performance degradation) |
Formula: ALE = SLE × ARO
Example Calculation:
# Ransomware attack on CIA Platform
asset_value = 200000 # €200K (Mission Critical)
exposure_factor = 0.9 # 90% loss (Complete Loss)
aro = 0.7 # 70% (Likely based on industry data)
sle = asset_value * exposure_factor # €180K
ale = sle * aro # €126K annuallyFormula: VaR = Impact (€) × Probability × Confidence Factor × Time Horizon
VaR Risk Categories:
| Category | VaR Range (€) | Management Action |
|---|---|---|
| Critical | >€200K | Board escalation, immediate mitigation |
| High | €50K-200K | Executive committee, quarterly review |
| Medium | €10K-50K | Risk committee, semi-annual review |
| Low | €1K-10K | Management monitoring, annual review |
| Minimal | <€1K | Acceptance, periodic review |
graph TB
RISK["📊 Risk Identified<br/>with Score"] --> EVAL{Risk Level?}
EVAL -->|Critical/High<br/>400-600, 200-399| HIGH_TREAT["🎯 Treatment Required"]
EVAL -->|Medium<br/>100-199| MED_TREAT["⚖️ Treatment Evaluation"]
EVAL -->|Low/Minimal<br/>1-99| LOW_TREAT["✅ Consider Acceptance"]
HIGH_TREAT --> OPTIONS1[Treatment Options]
MED_TREAT --> OPTIONS2[Treatment Options]
LOW_TREAT --> ACCEPT_DIRECT[Accept Risk<br/>Document in Risk Register]
OPTIONS1 --> MITIGATE1["🛡️ Mitigate<br/>Implement controls"]
OPTIONS1 --> TRANSFER1["🤝 Transfer<br/>Insurance/Outsource"]
OPTIONS1 --> AVOID1["🚫 Avoid<br/>Eliminate activity"]
OPTIONS2 --> MITIGATE2["🛡️ Mitigate<br/>Cost-benefit analysis"]
OPTIONS2 --> ACCEPT2["📋 Accept<br/>Document rationale"]
MITIGATE1 --> COST_BENEFIT{Control Cost<br/>vs ALE?}
TRANSFER1 --> COST_BENEFIT
MITIGATE2 --> COST_BENEFIT
COST_BENEFIT -->|Control < ALE| IMPLEMENT["✅ Implement Control"]
COST_BENEFIT -->|Control > ALE| ACCEPT_COST["📋 Accept Risk<br/>Document decision"]
AVOID1 --> BUSINESS{Business<br/>Impact?}
BUSINESS -->|Acceptable| ELIMINATE["🚫 Eliminate Risk"]
BUSINESS -->|Unacceptable| FIND_ALT["🔄 Find Alternative"]
IMPLEMENT --> RESIDUAL["📉 Residual Risk<br/>Assessment"]
ACCEPT2 --> REGISTER["📊 Risk Register"]
ACCEPT_COST --> REGISTER
ACCEPT_DIRECT --> REGISTER
ELIMINATE --> REGISTER
RESIDUAL --> REEVAL{Still<br/>High/Critical?}
REEVAL -->|Yes| ADDITIONAL[Additional Controls<br/>Required]
REEVAL -->|No| REGISTER
ADDITIONAL --> COST_BENEFIT
style RISK fill:#1565C0,stroke:#0D47A1,stroke-width:3px,color:#fff
style HIGH_TREAT fill:#D32F2F,stroke:#B71C1C,stroke-width:3px,color:#fff
style MED_TREAT fill:#FF9800,stroke:#F57C00,stroke-width:2px
style IMPLEMENT fill:#4CAF50,stroke:#2E7D32,stroke-width:2px,color:#fff
style REGISTER fill:#9C27B0,stroke:#7B1FA2,stroke-width:2px,color:#fffControl Value = ALE (Before) - ALE (After) - Control Cost
def control_roi(ale_before, ale_after, control_cost_annual):
"""Calculate return on investment for security control"""
annual_benefit = ale_before - ale_after
net_benefit = annual_benefit - control_cost_annual
roi_percentage = (net_benefit / control_cost_annual) * 100
return {
'annual_benefit': annual_benefit,
'net_benefit': net_benefit,
'roi_percentage': roi_percentage,
'recommendation': 'Implement' if net_benefit > 0 else 'Reject'
}
# Example: MFA implementation
result = control_roi(
ale_before=126000, # €126K ransomware risk
ale_after=12600, # 90% reduction
control_cost_annual=5000 # €5K/year for MFA
)
# Result: €108.4K net benefit, 2068% ROI → Implement# Risk Assessment: [Risk Name]
**Risk ID:** RSK-2025-XXX
**Assessment Date:** 2025-01-XX
**Assessor:** [Name/Role]
**Status:** Open/Mitigated/Accepted/Closed
## Risk Description
Brief description of the risk scenario.
## Asset Information
- **Primary Asset:** [Asset name]
- **Asset Value:** €X
- **Classification:** [Confidentiality/Integrity/Availability levels]
## Threat & Vulnerability
- **Threat Actor:** [Who/what causes the risk]
- **Threat Motivation:** [Why would they exploit this]
- **Vulnerability:** [What weakness enables exploitation]
- **Attack Vector:** [How the attack occurs]
## Likelihood Assessment
- **Category:** [Exceptional/Rare/Unlikely/Possible/Likely/Almost Certain]
- **Probability:** X%
- **ARO:** X.XX
- **Evidence:** [Historical data, industry benchmarks, expert judgment]
## Impact Assessment
- **Financial:** €X (Category: [Minimal/Low/Moderate/High/Critical/Catastrophic])
- **Operational:** [Description]
- **Reputational:** [Description]
- **Regulatory:** [Description]
- **Impact Score:** X (1-6)
## Risk Calculation
- **Risk Score:** [Probability × Impact × 100] = XXX
- **Risk Level:** 🔴/🟠/🟡/🟢/⚪ [Critical/High/Medium/Low/Minimal]
## Financial Analysis
- **Asset Value:** €X
- **Exposure Factor:** X.X
- **SLE:** €X
- **ALE:** €X
## Current Controls
- [Existing control 1]
- [Existing control 2]
## Recommended Treatment
- **Strategy:** Mitigate/Transfer/Avoid/Accept
- **Proposed Controls:** [List controls]
- **Control Cost:** €X annually
- **Residual Risk Score:** XXX → [Risk Level]
- **Cost-Benefit:** Net benefit €X, ROI X%
- **Recommendation:** Implement/Reject
## Approval
- **Risk Owner:** [Name/Role]
- **Approval Date:** 2025-XX-XX
- **Review Date:** 2025-XX-XX| Risk ID | Description | Likelihood | Impact | Score | Level | Treatment | Owner |
|---|---|---|---|---|---|---|---|
| RSK-001 | Data breach | Unlikely (30%) | Critical (5) | 150 | 🟡 Medium | MFA implementation | CTO |
| RSK-002 | DDoS attack | Possible (50%) | High (4) | 200 | 🟠 High | CDN + WAF | CTO |
| RSK-003 | Ransomware | Likely (70%) | Catastrophic (6) | 420 | 🔴 Critical | Backup + EDR | CEO |
Align risk assessments with Classification Framework:
Confidentiality Impact:
Integrity Impact:
Availability Impact:
Risk Assessment:
risk_id: "RSK-2025-001"
risk_name: "Ransomware attack on CIA Platform"
asset: "CIA Platform (Production)"
asset_value: 200000 # €200K
likelihood:
category: "Likely"
probability: 0.70
aro: 0.70
evidence: "Industry data (DBIR 2024), phishing susceptibility"
impact:
financial: 180000 # €180K recovery costs
operational: "72-hour downtime"
reputational: "National media coverage"
regulatory: "GDPR breach notification required"
category: "Catastrophic"
score: 6
risk_score: 420 # 0.70 × 6 × 100
risk_level: "Critical"
financial_analysis:
sle: 180000 # €200K × 0.9
ale: 126000 # €180K × 0.70
current_controls:
- "Firewall"
- "Antivirus"
- "User awareness training"
proposed_treatment:
strategy: "Mitigate"
controls:
- "Multi-factor authentication (MFA)"
- "Endpoint detection and response (EDR)"
- "Immutable backups (3-2-1 rule)"
- "Email security gateway"
control_cost_annual: 15000 # €15K
residual_likelihood: 0.07 # 90% reduction
residual_risk_score: 42 # 0.07 × 6 × 100
residual_risk_level: "Minimal"
cost_benefit:
ale_reduction: 113400 # €126K - €12.6K
net_benefit: 98400 # €113.4K - €15K
roi: 656 # 656% ROI
recommendation: "IMPLEMENT IMMEDIATELY"
approval:
risk_owner: "CEO"
approval_date: "2025-01-25"
next_review: "2025-04-25"Risk Assessment:
risk_id: "RSK-2025-015"
risk_name: "No authentication system risk"
asset: "Black Trigram Gaming Platform"
asset_value: 10000 # €10K
likelihood:
category: "Rare"
probability: 0.12
aro: 0.12
evidence: "No user accounts, public content only"
impact:
financial: 500 # €500 reputation recovery
operational: "Minimal—frontend only"
reputational: "Limited local impact"
regulatory: "None—no personal data"
category: "Low"
score: 2
risk_score: 24 # 0.12 × 2 × 100
risk_level: "Minimal"
financial_analysis:
sle: 5000 # €10K × 0.5 (moderate exposure)
ale: 600 # €5K × 0.12
treatment:
strategy: "Accept"
rationale: "Low confidentiality classification. All content is public educational material. No user-specific operations."
controls_considered:
- "Authentication system: €8K/year"
- "Cost-benefit: Negative ROI (€7.4K loss)"
residual_risk: "Same as inherent risk"
risk_acceptance:
documented_in: "Risk_Register.md"
approved_by: "CEO"
review_frequency: "Annual"
trigger_conditions:
- "Introduction of user accounts"
- "Processing of personal data"
- "User-generated content features"| Risk Assessment Component | ISO 27005 | NIST RMF | CIS Controls v8 |
|---|---|---|---|
| Risk identification | Clause 8.2 | Categorize | 4.1 Asset Management |
| Likelihood assessment | Annex C | Assess | 4.1 Risk Assessment |
| Impact assessment | Annex C | Assess | 4.2 Risk Analysis |
| Risk calculation | Clause 8.3 | Assess | 4.2 Risk Analysis |
| Risk treatment | Clause 8.4 | Select + Implement | 4.3 Risk Response |
| Risk acceptance | Clause 8.4.4 | Authorize | 4.4 Risk Approval |
| Monitoring & review | Clause 9 | Monitor | 4.5 Risk Monitoring |
Core Hack23 ISMS Policies:
All Hack23 ISMS Policies: https://github.com/Hack23/ISMS-PUBLIC
© Hack23, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Just SKILL.md in .github/skills/risk-assessment-methodology of Hack23/cia.
Open the folder on GitHubat commit bbed538
Risk Assessment Methodology next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Risk Assessment Methodology this skillHack23/cia | 239 | — | ~5.2k | Automated safety check: Pass | Apache-2.0 | |
| Product Launch Legal Reviewanthropics/claude-for-legal | 9.6k | 2 repos | ~5k | Automated safety check: Pass | Apache-2.0 | |
| Legal Risk Visualizationzh-xx/legal-assistant-skills | 173 | — | ~2.4k | Automated safety check: Pass | Apache-2.0 | |
| Contract Renewal Trackeranthropics/claude-for-legal | 9.6k | 2 repos | ~3.1k | Automated safety check: Pass | Apache-2.0 | |
| Deep Risk Analysiszubair-trabzada/ai-legal-claude | 1.8k | — | ~1.9k | Automated safety check: Pass | None | |
| Canghe Tianyanchafreestylefly/canghe-skills | 461 | — | ~2.4k | Automated safety check: Pass | None |
anthropics/claude-for-legal
Runs a category-by-category legal review of a product launch from a PRD or tracker ticket, calibrated to your team's framework, and writes a review memo in house format.
zh-xx/legal-assistant-skills
法律风险结构化分析与可视化。基于法律分析文本,执行五步风险抽取模型, 生成四层可视化输出(雷达图数据、风险矩阵、影响路径图、决策树)。
anthropics/claude-for-legal
Shows which contracts renew soon and when notice must be sent by, working from a maintained renewal register, and warns about missed cancellation windows.
zubair-trabzada/ai-legal-claude
Clause-by-clause contract risk analysis with severity scoring, financial exposure estimates, and prioritized remediation guidance
freestylefly/canghe-skills
Generates Tianyancha-style company and industry insight dashboards from researched enterprise data.
anthropics/claude-for-legal
Maintains a register of AI systems under the EU AI Act, recording each system's role and risk tier separately, because both can differ from one system to the next.
Hack23/cia
WCAG 2.1 AA compliance, ARIA attributes, keyboard navigation, screen reader optimization for accessible political data platforms
Hack23/cia
Advanced chart types, D3.js/Vaadin Charts patterns, political data visualization, time series analysis
Hack23/cia
AI governance, EU AI Act compliance, OWASP LLM security, responsible AI practices for GitHub Copilot agents
Hack23/cia
External API integration patterns, retry logic, circuit breakers, caching, rate limiting for government data APIs
Hack23/cia
AWS CloudWatch metrics, alarms, dashboards, log insights, and application monitoring for the CIA platform
Hack23/cia
AWS security best practices, VPC security, IAM, KMS, CloudTrail, GuardDuty for CIA platform deployment
Categories
Systematic risk identification, analysis, evaluation, and treatment aligned with ISO 27005, NIST RMF, and Hack23 ISMS risk register. Risk Assessment Methodology is an agent skill from Hack23/cia.
Risk Assessment Methodology fits situations like: tasks that involve Legal risk assessment.
Run `npx skills add Hack23/cia --skill risk-assessment-methodology -a claude-code`. Or copy the skill folder (.github/skills/risk-assessment-methodology in Hack23/cia) into .claude/skills/risk-assessment-methodology in your project. Claude Code loads it when a task matches its description.
Run `npx skills add Hack23/cia --skill risk-assessment-methodology -a codex`. Or copy the skill folder (.github/skills/risk-assessment-methodology in Hack23/cia) into .agents/skills/risk-assessment-methodology in your project. Codex loads it when a task matches its description.
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add Hack23/cia --skill risk-assessment-methodology -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/risk-assessment-methodology, .gemini/skills/risk-assessment-methodology, .github/skills/risk-assessment-methodology and .opencode/skills/risk-assessment-methodology in your project.
SKILL.md names no scripts, command-line tools or credentials: Risk Assessment Methodology is instructions for the agent only. Our summary lists: Python 3.
SKILL.md names 2 domains. As links in the text: img.shields.io and github.com. This is read from the text; nothing was executed.
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
Risk Assessment Methodology is published under the Apache-2.0 licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.
About 5.2k tokens (SKILL.md is roughly 21k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
Skills that share tags, products or a category with Risk Assessment Methodology: Product Launch Legal Review (anthropics/claude-for-legal, 9.6k stars), Legal Risk Visualization (zh-xx/legal-assistant-skills, 173 stars), Contract Renewal Tracker (anthropics/claude-for-legal, 9.6k stars) and Deep Risk Analysis (zubair-trabzada/ai-legal-claude, 1.8k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Hack23 (a GitHub organization) maintains it in Hack23/cia, which has 239 GitHub stars. The repository holds 78 skills in this directory. The repository was last updated on October 7, 2026.
Source: Hack23/cia on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.