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

31 lines
1.1 KiB
Markdown

# Standards for Cloud Incident Containment
## NIST SP 800-61 Rev 2 - Incident Handling Guide
- Containment strategies for cloud environments
- Evidence preservation in ephemeral infrastructure
## CSA Cloud Incident Response Framework
- Cloud Security Alliance incident response procedures
- Shared responsibility model for incident handling
- Multi-cloud containment strategies
## AWS Well-Architected Framework - Security Pillar
- Incident response automation with AWS services
- CloudTrail, GuardDuty, and Security Hub integration
- Reference: https://docs.aws.amazon.com/wellarchitected/latest/security-pillar/
## Microsoft Cloud Security Benchmark
- Azure Defender incident response procedures
- Sentinel playbook automation
- Reference: https://learn.microsoft.com/en-us/security/benchmark/azure/mcsb-incident-response
## GCP Security Best Practices
- Cloud Armor and VPC Service Controls
- Security Command Center integration
- Chronicle SIEM for cloud forensics
## MITRE ATT&CK Cloud Matrix
- Cloud-specific tactics, techniques, and procedures
- Containment mapping to ATT&CK techniques
- Reference: https://attack.mitre.org/matrices/enterprise/cloud/