mirror of
https://github.com/SHOGGOTH-SECTOR/sica-fondt.git
synced 2026-08-01 16:40:24 +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
41 lines
1.7 KiB
Markdown
41 lines
1.7 KiB
Markdown
# Standards and References - Alert Triage with Elastic SIEM
|
|
|
|
## Elastic Common Schema (ECS)
|
|
|
|
ECS is a standardized field naming convention for Elasticsearch data. All Elastic Security detections and triage workflows rely on ECS compliance.
|
|
|
|
### Key ECS Field Categories for Triage
|
|
|
|
| Category | Fields | Usage |
|
|
|---|---|---|
|
|
| Base | `@timestamp`, `message`, `tags` | Event timing and classification |
|
|
| Agent | `agent.name`, `agent.type` | Data source identification |
|
|
| Host | `host.name`, `host.ip`, `host.os` | Affected system context |
|
|
| User | `user.name`, `user.domain` | Identity attribution |
|
|
| Process | `process.name`, `process.pid`, `process.command_line` | Execution context |
|
|
| Network | `source.ip`, `destination.ip`, `destination.port` | Network activity |
|
|
| File | `file.name`, `file.hash.sha256`, `file.path` | File-related events |
|
|
| Threat | `threat.tactic.name`, `threat.technique.id` | MITRE ATT&CK mapping |
|
|
|
|
## MITRE ATT&CK Integration
|
|
|
|
Elastic Security maps detection rules and alerts to MITRE ATT&CK tactics and techniques, providing a common taxonomy for triage prioritization.
|
|
|
|
## NIST SP 800-61 Rev 2
|
|
|
|
Triage aligns with NIST incident handling phases:
|
|
- Detection and Analysis (triage is the core of this phase)
|
|
- Prioritization based on functional impact, information impact, and recoverability
|
|
|
|
## SOC Maturity Model
|
|
|
|
### Triage Capability Levels
|
|
|
|
| Level | Capability |
|
|
|---|---|
|
|
| Level 1 | Manual review of individual alerts |
|
|
| Level 2 | Grouped alert triage with correlation |
|
|
| Level 3 | AI-assisted triage with automated enrichment |
|
|
| Level 4 | Automated classification with human oversight |
|
|
| Level 5 | Fully autonomous triage with exception-based review |
|