thanhnvandClaude Opus 4.8
664bd1f00c
Physically move the pure-code subtrees out of .specify into the package, leaving compat symlinks at the old .specify/<dir> paths so every existing reference (internal CASAN_HARNESS_ROOT + external CI/docker/mjs) keeps resolving. Runtime state stays put. Moved (git mv): scripts/ tests/ security/ templates/ config/ governance/ memory/ .specify/<dir> -> packages/casan-harness/<dir> (+ .specify/<dir> symlink) Stays in .specify (state/governance/domain, handled later): logs/ agentops/ level5/ init-options.json traceability-map.json Python `.resolve()` self-location followed the compat symlink into packages and lost the app root; generate-casan-demo-context.py, generate-agentops-dashboard.py and dashboard-server.py now walk UP for the `.specify` state marker instead of a fixed parent depth (fixes "missing trace files" in run-casan4). Full gate: PASS=64 FAIL=0 SKIP=3 (CASAN_CI_STEP_TIMEOUT_SEC=1200 — track-a ~450s runs close to the 600s default and can tip over under load; this is timing variance, not a regression — it passed cleanly with headroom). Runtime log/audit artifacts kept unstaged. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
98 lines
2.0 KiB
YAML
98 lines
2.0 KiB
YAML
version: 1.0
|
|
description: AI Risk Registry (Governance + Security Mapping)
|
|
|
|
risks:
|
|
|
|
- id: RISK-001
|
|
name: Prompt Injection
|
|
category: security
|
|
severity: high
|
|
likelihood: high
|
|
impact: high
|
|
detection:
|
|
source: prompt-filter
|
|
mitigation:
|
|
- block malicious pattern
|
|
- validate input
|
|
owner: security_team
|
|
|
|
- id: RISK-002
|
|
name: Data Leakage
|
|
category: data
|
|
severity: high
|
|
likelihood: medium
|
|
impact: high
|
|
detection:
|
|
source: output-policy
|
|
mitigation:
|
|
- output filtering
|
|
- redact sensitive data
|
|
owner: ai_team
|
|
|
|
- id: RISK-003
|
|
name: PII Exposure
|
|
category: privacy
|
|
severity: high
|
|
likelihood: medium
|
|
impact: high
|
|
detection:
|
|
source: pii-rules
|
|
mitigation:
|
|
- mask PII
|
|
- block if critical
|
|
owner: compliance_team
|
|
|
|
- id: RISK-004
|
|
name: Hallucination Output
|
|
category: quality
|
|
severity: medium
|
|
likelihood: high
|
|
impact: medium
|
|
detection:
|
|
source: evaluation-harness
|
|
mitigation:
|
|
- flag uncertain output
|
|
- human review
|
|
owner: ai_team
|
|
|
|
- id: RISK-005
|
|
name: Unauthorized Tool Usage
|
|
category: security
|
|
severity: high
|
|
likelihood: low
|
|
impact: high
|
|
detection:
|
|
source: tool-harness
|
|
mitigation:
|
|
- whitelist tools
|
|
- enforce permission
|
|
owner: platform_team
|
|
|
|
risk_levels:
|
|
|
|
high:
|
|
action: require_approval
|
|
|
|
medium:
|
|
action: log_and_monitor
|
|
|
|
low:
|
|
action: allow
|
|
|
|
reporting:
|
|
|
|
enabled: true
|
|
frequency: daily
|
|
output: ".specify/governance/risk-report.md"
|
|
|
|
review:
|
|
|
|
cycle: weekly
|
|
owner: architect
|
|
|
|
auto_update:
|
|
enabled: true
|
|
trigger: new_action_type_detected
|
|
script: .specify/scripts/powershell/update-risk-registry.ps1
|
|
default_risk_for_unknown_action: high
|
|
note: "Unknown actions default to high-risk (fail-secure). Run update-risk-registry.ps1 to register." |