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
32 lines
1.2 KiB
Markdown
32 lines
1.2 KiB
Markdown
# Workflow - Detecting Privilege Escalation in Kubernetes Pods
|
|
|
|
## Phase 1: Assess Current State
|
|
```bash
|
|
# Find privileged pods
|
|
kubectl get pods -A -o json | jq '[.items[] | select(.spec.containers[].securityContext.privileged==true) | {name:.metadata.name, ns:.metadata.namespace}]'
|
|
|
|
# Find pods running as root
|
|
kubectl get pods -A -o json | jq '[.items[] | select(.spec.securityContext.runAsUser==0 or .spec.containers[].securityContext.runAsUser==0) | {name:.metadata.name, ns:.metadata.namespace}]'
|
|
|
|
# Find hostPath mounts
|
|
kubectl get pods -A -o json | jq '[.items[] | select(.spec.volumes[]?.hostPath!=null) | {name:.metadata.name, ns:.metadata.namespace}]'
|
|
```
|
|
|
|
## Phase 2: Deploy Prevention
|
|
1. Apply Pod Security Admission labels to namespaces
|
|
2. Deploy OPA Gatekeeper constraints
|
|
3. Test with non-compliant pods (should be rejected)
|
|
|
|
## Phase 3: Deploy Detection
|
|
1. Install Falco with privilege escalation rules
|
|
2. Enable Kubernetes audit logging
|
|
3. Configure alerts to SIEM
|
|
|
|
## Phase 4: Respond to Alerts
|
|
1. Identify compromised pod
|
|
2. Check container security context
|
|
3. Review process list and capabilities
|
|
4. Isolate with network policy
|
|
5. Capture forensic data
|
|
6. Delete compromised pod
|