mirror of
https://github.com/SHOGGOTH-SECTOR/sica-fondt.git
synced 2026-08-01 00:23:15 +00:00
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
1.4 KiB
1.4 KiB
XSOAR Playbook Design Template
Playbook Metadata
| Field | Value |
|---|---|
| Playbook Name | |
| Version | |
| Incident Type | |
| Description | |
| Author | |
| Created Date | |
| SLA Target |
Playbook Logic Flow
Phase 1: Enrichment
- Extract indicators from alert/incident
- Enrich IPs via threat intelligence
- Enrich domains via threat intelligence
- Enrich file hashes via sandbox/TI
- Query asset database for affected hosts
- Query identity store for affected users
Phase 2: Analysis
- Determine verdict (malicious/benign/unknown)
- Calculate risk score
- Check against allowlists/blocklists
- Correlate with existing incidents
Phase 3: Response
- Manual approval gate for destructive actions
- Containment actions
- Eradication actions
- Recovery actions
Phase 4: Documentation
- Update incident fields
- Generate closing report
- Update ticketing system
- Notify stakeholders
Integrations Required
| Integration | Commands Used | Purpose |
|---|---|---|
Error Handling
| Task | Error Type | Handling |
|---|---|---|
Testing Checklist
- Test with known malicious sample
- Test with known benign sample
- Test error handling paths
- Verify manual gates function correctly
- Confirm notifications are sent
- Validate closing report content