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
66 lines
1.4 KiB
Markdown
66 lines
1.4 KiB
Markdown
# Workflows - Recovering from Ransomware Attack
|
|
|
|
## Workflow 1: Recovery Decision and Planning
|
|
|
|
```
|
|
Containment Complete + Forensics Initiated
|
|
|
|
|
v
|
|
[Assess backup availability]
|
|
|-- Immutable copies intact? --> Primary recovery path
|
|
|-- Air-gapped copies available? --> Secondary recovery path
|
|
|-- No clean backups? --> Consider decryption key (paid or NoMoreRansom)
|
|
|
|
|
v
|
|
[Determine recovery scope]
|
|
|-- Full rebuild vs. selective restore
|
|
|-- Identify minimum viable recovery set
|
|
|
|
|
v
|
|
[Map system dependencies]
|
|
|-- AD/DNS -> Database -> Application -> Web
|
|
|
|
|
v
|
|
[Estimate recovery timeline per tier]
|
|
|
|
|
v
|
|
[Brief executive team on recovery plan and timeline]
|
|
|
|
|
v
|
|
[Begin recovery]
|
|
```
|
|
|
|
## Workflow 2: System Recovery Execution
|
|
|
|
```
|
|
[Establish clean recovery VLAN]
|
|
|
|
|
v
|
|
[Phase 1: Identity Recovery]
|
|
|-- Restore DCs from verified backup
|
|
|-- Reset krbtgt (2x)
|
|
|-- Reset all admin passwords
|
|
|-- Validate AD health (dcdiag)
|
|
|
|
|
v
|
|
[Phase 2: Critical Systems]
|
|
|-- Restore databases
|
|
|-- Verify data consistency
|
|
|-- Restore core applications
|
|
|-- Test application functionality
|
|
|
|
|
v
|
|
[Phase 3: Important Systems]
|
|
|-- Restore in groups of 5-10
|
|
|-- Validate each before proceeding
|
|
|
|
|
v
|
|
[Phase 4: Remaining Systems]
|
|
|
|
|
v
|
|
[Each system: Scan for persistence -> Patch -> Deploy EDR -> Connect]
|
|
|
|
|
v
|
|
[Post-recovery monitoring (7-14 days elevated alert)]
|
|
```
|