saint-graves/sica-fondt
1
0
Fork 0
mirror of https://github.com/SHOGGOTH-SECTOR/sica-fondt.git synced 2026-08-01 08:30:20 +00:00
Code Issues Packages Projects Releases Wiki Activity
sica-fondt/knowledge/cyber-skills/skills/performing-cloud-incident-containment-procedures/assets/template.md
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

1.4 KiB
Raw Blame History

Cloud Incident Containment Report Template

Case Information

Field Details
Case ID
Cloud Platform(s) AWS / Azure / GCP
Incident Type
Containment Start
Containment End
IR Lead

Affected Resources

Resource Type Account/Subscription Region Status

Pre-Containment Evidence

  • Disk snapshots created
  • Log exports completed
  • Configuration state captured
  • Network flow logs preserved

Containment Actions Taken

# Time (UTC) Action Resource Result Executed By
1

Credential Actions

Identity Action Timestamp Verified
Keys disabled
Sessions revoked
Password reset

Network Isolation

Resource Previous SG/NSG Quarantine SG/NSG Verified

Verification Results

  • Compromised resource cannot reach internet
  • Compromised credentials are non-functional
  • Forensic access still available
  • No new unauthorized activity detected

Next Steps

  1. Eradication planning
  2. Root cause analysis
  3. Recovery procedures
  4. Post-incident review