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.3 KiB
1.3 KiB
Malware Incident Communication Tracking Template
Case Information
| Field | Details |
|---|---|
| Case ID | |
| Severity | P1/P2/P3/P4 |
| Malware Type | |
| Communication Lead |
Notification Tracker
| Stakeholder | Method | Time Sent | Acknowledged | By Whom |
|---|---|---|---|---|
| CISO | Phone | |||
| CEO | Phone | |||
| Legal | ||||
| IT Director | Slack | |||
| Board |
Update Log
| Update # | Time (UTC) | Type | Recipients | Summary |
|---|---|---|---|---|
| 1 | Initial | |||
| 2 | Status |
Regulatory Notifications
| Regulation | Required | Deadline | Sent | Confirmed |
|---|---|---|---|---|
| GDPR (DPA) | 72 hours | |||
| HIPAA (HHS) | 60 days | |||
| State Breach | Varies | |||
| SEC (8-K) | 4 bus days |
Customer Communication
- Notification drafted
- Legal review complete
- Executive approval
- Support resources ready
- Notification sent
- FAQ published
Media Handling
- Holding statement prepared
- Spokesperson designated
- Media inquiry response approved
- Social media monitoring active
Lessons Learned (Communication)
- What worked well:
- What needs improvement:
- Template updates needed: