mirror of
https://github.com/SHOGGOTH-SECTOR/sica-fondt.git
synced 2026-08-01 08:30:20 +00:00
24f816b6a3
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
2.2 KiB
2.2 KiB
Workflows - Vulnerability Exception Tracking
Workflow 1: Exception Request and Approval
Steps
- Asset owner identifies vulnerability that cannot be remediated within SLA
- Owner submits exception request with justification and compensating controls
- System validates request completeness and category-specific fields
- System routes request to appropriate approver based on severity and category
- Approver reviews justification and compensating controls
- Approver approves, rejects, or requests additional information
- If approved, exception is recorded with expiration date
- Vulnerability status updated in scanner/DefectDojo to "exception_approved"
- Audit log entry created with full approval chain
Workflow 2: Daily Expiration Check
Steps
- Cron job queries all active exceptions with expires_at <= today + 14 days
- For exceptions expiring within 14 days: send renewal reminder to requestor
- For exceptions expiring within 7 days: send urgency reminder with escalation
- For expired exceptions: update status to "expired", revert vulnerability to "open"
- Send expiration notification to asset owner and security team
- Regenerate SLA tracking to include re-opened findings
Workflow 3: Quarterly Exception Review
Steps
- Generate report of all active exceptions grouped by category and severity
- For each exception, verify compensating controls are still in place
- Review if vendor patch has become available for "no_fix" exceptions
- Re-assess risk rating based on current threat landscape
- Escalate exceptions with changed risk profiles for re-approval
- Update exception records with review notes and new risk ratings
- Submit quarterly report to security governance committee
Workflow 4: Compensating Control Validation
Steps
- For each active exception, extract listed compensating controls
- Validate each control is still operational:
- WAF rules: Query WAF API for rule status
- Network segmentation: Verify firewall rules
- Monitoring alerts: Confirm SIEM rules are active and triggering
- Flag exceptions where compensating controls have degraded
- Notify exception requestor and security team of control failures
- If controls cannot be restored within 48 hours, revoke exception