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.6 KiB

Standards Reference - Kubernetes Penetration Testing

MITRE ATT&CK for Containers

Relevant Techniques

ID Technique Phase
T1609 Container Administration Command Execution
T1610 Deploy Container Execution
T1611 Escape to Host Privilege Escalation
T1613 Container and Resource Discovery Discovery
T1612 Build Image on Host Defense Evasion
T1552.007 Container API Credential Access

CIS Kubernetes Benchmark v1.8

Master Node Checks

  • 1.1: Control Plane Configuration Files
  • 1.2: API Server (anonymous auth, RBAC, audit logging)
  • 1.3: Controller Manager
  • 1.4: Scheduler

Worker Node Checks

  • 4.1: Worker Node Configuration Files
  • 4.2: Kubelet (anonymous auth, authorization mode)

Policies

  • 5.1: RBAC and Service Accounts
  • 5.2: Pod Security Standards
  • 5.3: Network Policies
  • 5.4: Secrets Management

NSA/CISA Kubernetes Hardening Guide

Key Areas

  • Scan containers and pods for vulnerabilities
  • Run containers as non-root users
  • Use network policies to restrict traffic
  • Encrypt secrets at rest
  • Audit logging for all API calls
  • Scan for misconfigurations regularly

OWASP Kubernetes Top 10

  1. K01: Insecure Workload Configurations
  2. K02: Supply Chain Vulnerabilities
  3. K03: Overly Permissive RBAC
  4. K04: Lack of Centralized Policy Enforcement
  5. K05: Inadequate Logging and Monitoring
  6. K06: Broken Authentication
  7. K07: Missing Network Segmentation
  8. K08: Secrets Management Failures
  9. K09: Misconfigured Cluster Components
  10. K10: Outdated and Vulnerable Kubernetes Components