Claude 24f816b6a3
Consolidate 22 sibling repos into layered organism structure
Place useful parts of the surrounding repos into sica-fondt by layer, per the
body model (Ada = membrane; brain/endocrine/capabilities/knowledge non-Ada):

- brain/        LLM reasoning + providers (dapr, hermes, MoMoA)
- capabilities/ REPRAG sidecars: hermes tools/skills, dapr tools, parallel
                dispatch, A51 channels, and the OSINT cluster
- knowledge/    LORAG corpus: 754 cyber-skills, agency personas, secure-coding,
                MITRE ATT&CK data
- reference/    defensive threat-reference (C3, shhbruh doc) + AdaYaml parser

License handling: AGPL sources (worldosint, advanced_evolution, mercury,
Reticulum) and GPL DeTTECT are SPEC-only clean-room/port descriptions — no
copyleft code copied. MIT/Apache/data parts copied as working trees.

Safety: shhbruh escape/persistence material and C3 covert-C2 kept as reference
only, not wired into the running organism. See CONSOLIDATION.md.

https://claude.ai/code/session_01UehUqEXXJJCsHoA4voCU5c
2026-06-10 06:53:01 +00:00

56 lines
1.7 KiB
Markdown

# Vulnerability Exception Request Template
## Exception Request Form
### Vulnerability Information
- **CVE ID**: CVE-YYYY-NNNNN
- **Finding ID**: [Scanner reference number]
- **Affected Asset(s)**: [hostname/IP]
- **Severity**: [Critical/High/Medium/Low]
- **CVSS Score**: [0.0 - 10.0]
- **Discovery Date**: [YYYY-MM-DD]
- **Original SLA Deadline**: [YYYY-MM-DD]
### Exception Details
- **Category**: [ ] Remediation Delay [ ] No Fix Available [ ] Business Critical [ ] False Positive [ ] Compensating Control
- **Requested Expiration Date**: [YYYY-MM-DD]
- **Justification**: [Detailed explanation of why remediation cannot be completed within SLA]
### Compensating Controls
1. **Detection Control**: [How will exploitation attempts be detected?]
2. **Prevention Control**: [What barriers reduce exploitation likelihood?]
3. **Response Procedure**: [What IR procedures are in place for this vulnerability?]
4. **Monitoring**: [What ongoing monitoring ensures controls remain effective?]
### Risk Assessment
- **Residual Risk Rating**: [High/Medium/Low]
- **Business Impact if Exploited**: [Description]
- **Likelihood of Exploitation**: [High/Medium/Low]
### Requestor
- **Name**: [Full name]
- **Email**: [email@company.com]
- **Department**: [Team/Department]
- **Date**: [YYYY-MM-DD]
---
## Approval Section (For Approver Use)
### Decision
- [ ] **Approved** - Exception granted with conditions below
- [ ] **Rejected** - See rejection reason below
- [ ] **More Information Required** - See notes below
### Conditions (if approved)
- [List any additional conditions]
### Reviewer Notes
- [Notes from security review]
### Approver
- **Name**: [Full name]
- **Title**: [Job title]
- **Date**: [YYYY-MM-DD]
- **Signature**: [Digital signature or email confirmation reference]