mirror of
https://github.com/SHOGGOTH-SECTOR/sica-fondt.git
synced 2026-08-01 16:40:24 +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.0 KiB
1.0 KiB
Workflow - Implementing Pod Security Admission
Phase 1: Assessment
- List all namespaces and their current security posture
- Run dry-run against restricted profile for each namespace
- Document violations and required exemptions
Phase 2: Apply Audit Mode
for ns in production staging; do
kubectl label namespace $ns \
pod-security.kubernetes.io/audit=restricted \
pod-security.kubernetes.io/warn=restricted
done
Phase 3: Fix Violations
- Update Deployments/StatefulSets with compliant security contexts
- Add seccomp profiles
- Switch containers to non-root
- Drop ALL capabilities
Phase 4: Enable Enforcement
kubectl label namespace production \
pod-security.kubernetes.io/enforce=restricted \
pod-security.kubernetes.io/enforce-version=v1.28
Phase 5: Set Cluster Defaults
- Create AdmissionConfiguration with baseline defaults
- Apply to kube-apiserver
- Exempt system namespaces
Phase 6: Monitor
- Watch for FailedCreate events
- Review audit logs weekly
- Update exemptions as needed