saint-graves/sica-fondt
1
0
Fork 0
mirror of https://github.com/SHOGGOTH-SECTOR/sica-fondt.git synced 2026-08-01 08:30:20 +00:00
Code Issues Packages Projects Releases Wiki Activity
sica-fondt/knowledge/cyber-skills/skills/implementing-pod-security-admission-controller/references/standards.md
Claude 24f816b6a3
Consolidate 22 sibling repos into layered organism structure 
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
2026-06-10 06:53:01 +00:00

1.1 KiB
Raw Blame History

Standards - Pod Security Admission Controller

Kubernetes Pod Security Standards

Profile Controls Enforced
Baseline No privileged, no hostPID/IPC/Network, no hostPorts, restricted volumes, no procMount, restricted seccomp, restricted capabilities
Restricted All Baseline + non-root, drop ALL caps, seccomp required, restricted volume types, no privilege escalation

CIS Kubernetes Benchmark v1.8

  • 5.2.1: Ensure privileged containers are not used
  • 5.2.2-5.2.4: Ensure host namespace sharing is disabled
  • 5.2.5: Ensure privilege escalation is not allowed
  • 5.2.6: Ensure root containers are not admitted
  • 5.2.7: Ensure seccomp profile is set
  • 5.7.3: Apply security context to pods

NIST SP 800-190

  • Section 4.3: Container runtime security
  • Section 5.4: Admission control enforcement

NSA/CISA Kubernetes Hardening Guide v1.2

  • Section 1: Pod Security - Use Pod Security Standards

Compliance Mappings

  • PCI DSS v4.0 Req 2.2: Configuration standards
  • SOC 2 CC6.1: Logical access controls
  • HIPAA 164.312(a)(1): Access controls