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.9 KiB
1.9 KiB
Workflows - Implementing Disk Encryption with BitLocker
Workflow 1: Enterprise BitLocker Deployment
[Pre-deployment assessment]
│
├── Verify TPM 2.0 across fleet
├── Confirm UEFI/Secure Boot
├── Plan recovery key escrow (AD DS or Azure AD)
│
▼
[Configure GPO/Intune policy]
│
├── Set encryption method (XTS-AES 256)
├── Configure key protectors (TPM + PIN for laptops, TPM for desktops)
├── Enable recovery key escrow
│
▼
[Pilot deployment (test group)]
│
├── Verify encryption completes without errors
├── Test recovery key retrieval
├── Verify no boot issues
│
▼
[Production rollout (phased)]
│
▼
[Monitor encryption status via Intune/SCCM reports]
│
▼
[Verify 100% coverage, address failures]
Workflow 2: BitLocker Recovery Process
[User locked out (BitLocker recovery screen)]
│
▼
[User provides Recovery Key ID to helpdesk]
│
▼
[Helpdesk retrieves recovery key]
│
├── AD DS: RSAT BitLocker Recovery Password Viewer
├── Azure AD: Azure Portal → Devices → BitLocker keys
├── Intune: Intune Portal → Devices → Recovery keys
│
▼
[User enters 48-digit recovery key]
│
▼
[Investigate why recovery was triggered]
│
├── BIOS/firmware update ──► [Expected, no action]
├── TPM failure ──► [Replace TPM or re-encrypt]
├── Boot configuration change ──► [Review change, re-seal TPM]
└── Potential tampering ──► [Security investigation]
Workflow 3: Key Rotation
[Quarterly key rotation policy]
│
▼
[Generate new recovery password]
│
▼
[Backup new key to AD/Azure AD]
│
▼
[Remove old recovery password protector]
│
▼
[Verify new key works in test recovery]