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
2.3 KiB
2.3 KiB
Workflows - Sliver C2 Infrastructure
Infrastructure Deployment Workflow
1. Planning Phase
├── Define engagement scope and authorized targets
├── Select cloud providers for team server and redirectors
├── Register domains for C2 channels (categorized domains preferred)
└── Obtain SSL certificates (Let's Encrypt or purchased)
2. Team Server Setup
├── Deploy VPS with hardened OS configuration
├── Install Sliver server daemon
├── Configure firewall rules (restrict to redirector IPs only)
└── Generate operator configs for team members
3. Redirector Layer
├── Deploy 2+ redirector VPS instances in different regions
├── Configure NGINX reverse proxy on each redirector
├── Implement Apache mod_rewrite rules for traffic filtering
└── Optionally add Cloudflare CDN layer
4. Listener Configuration
├── HTTPS listener (primary) with valid SSL cert
├── DNS listener (fallback) for restricted networks
├── mTLS listener (high-security sessions)
└── WireGuard listener (tunneled access)
5. Implant Generation
├── Generate OS-specific beacons (Windows, Linux, macOS)
├── Configure callback intervals and jitter
├── Test implant connectivity through redirector chain
└── Validate implant evasion against target AV/EDR
6. Operational Use
├── Deploy implant to target via initial access vector
├── Establish C2 session through redirector infrastructure
├── Execute post-exploitation tasks
└── Maintain operational security throughout engagement
Failover and Resilience Workflow
Primary C2 Path:
Target → Redirector A → Team Server (HTTPS/443)
Failover Path 1:
Target → Redirector B → Team Server (HTTPS/8443)
Failover Path 2:
Target → DNS Resolver → Team Server (DNS/53)
Emergency Path:
Target → WireGuard Tunnel → Team Server (UDP/51820)
Multi-Operator Workflow
1. Team Lead generates operator configs:
sliver-server > new-operator --name <operator> --lhost <server-ip>
2. Distribute .cfg files securely to each operator
3. Operators connect using Sliver client:
sliver-client import <operator-config.cfg>
4. All operators share access to beacons and sessions
5. Use naming conventions for implants per operator