Initial commit - 611 cybersecurity skills across all subdomains

skills/building-c2-infrastructure-with-sliver-framework/references/standards.md

@@ -0,0 +1,32 @@
+# Standards and References - Sliver C2 Infrastructure
+
+## MITRE ATT&CK References
+
+| Technique ID | Name | Tactic |
+|-------------|------|--------|
+| T1071.001 | Application Layer Protocol: Web Protocols | Command and Control |
+| T1071.004 | Application Layer Protocol: DNS | Command and Control |
+| T1573.002 | Encrypted Channel: Asymmetric Cryptography | Command and Control |
+| T1090.002 | Proxy: External Proxy | Command and Control |
+| T1105 | Ingress Tool Transfer | Command and Control |
+| T1132.001 | Data Encoding: Standard Encoding | Command and Control |
+| T1572 | Protocol Tunneling | Command and Control |
+
+## Industry Standards
+
+- **PTES (Penetration Testing Execution Standard)** - Post-Exploitation and C2 sections
+- **OWASP Testing Guide** - Infrastructure testing methodology
+- **NIST SP 800-115** - Technical Guide to Information Security Testing and Assessment
+- **TIBER-EU** - Threat Intelligence-Based Ethical Red Teaming framework
+
+## Official Documentation
+
+- Sliver GitHub: https://github.com/BishopFox/sliver
+- Sliver Wiki: https://github.com/BishopFox/sliver/wiki
+- Sliver Armory: https://github.com/sliverarmory
+
+## Key Research
+
+- BishopFox Red Team Tools and C2 Frameworks Report (2025)
+- SpecterOps Adversary Simulation methodology
+- SANS SEC565: Red Team Operations and Adversary Emulation

skills/building-c2-infrastructure-with-sliver-framework/references/workflows.md

@@ -0,0 +1,72 @@
+# 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
+```