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
1.6 KiB
1.6 KiB
Workflows - Alert Triage with Elastic SIEM
5-Step Rapid Triage Framework
1. Alert Reception (30 seconds)
- Review alert title, severity, risk score
- Check MITRE ATT&CK mapping
|
v
2. Context Assessment (2 minutes)
- Examine affected host and user
- Check asset criticality
- Review process tree for endpoint alerts
|
v
3. Intelligence Enrichment (2 minutes)
- Check threat intelligence feeds
- Query for related alerts (same source/user)
- Search for known IOCs
|
v
4. Classification (1 minute)
- True Positive / False Positive / Needs Investigation
- Assign confidence level
|
v
5. Action (2 minutes)
- Document findings in alert notes
- Escalate or close with rationale
- Create tuning task if false positive
Alert Grouping Strategy
Smart Grouping Criteria
- Time window: Group alerts within 15-minute windows
- Entity: Group by affected host or user
- Kill chain stage: Group by MITRE ATT&CK tactic
- Source: Group by originating IP or detection rule
Group Triage Process
- Sort alert groups by highest severity member
- Triage group as single unit when correlated
- Escalate entire group if attack chain detected
- Close group if false positive pattern identified
Shift-Based Triage Queue Management
| Queue Priority | Alert Criteria | Analyst Tier |
|---|---|---|
| Immediate | Critical severity, critical assets | Tier 2+ |
| High | High severity or multiple related alerts | Tier 1/2 |
| Standard | Medium severity, standard assets | Tier 1 |
| Low | Low/info severity, non-critical | Tier 1 (batch review) |