AI Cyber Defense / Cloud, Kubernetes and software supply chain
AI Cyber Defense: Separate cloud logging administration from workload control
Protect organization-level collection and restrict deletion or redirection of audit data. Alert on delivery gaps and keep an escalation path outside the affected workload account.
Environment and inputs: Cloud control planes, workload identity, Kubernetes clusters, CI/CD pipelines and immutable deployment artifacts; provider support varies.
Scenario and goal
A compromised administrator may alter event collection before performing sensitive actions.
Why it matters
For this scenario, an attacker can automate permitted API operations after gaining a workload or pipeline identity. Review who can change trust, who can assume the resulting identity and what resources it can reach. Keep source review, build provenance, deployment authorization and runtime permissions as distinct checks. A configuration object or successful deployment does not prove the intended runtime boundary is enforced.
Evidence to collect
Track audit configuration changes, destination policy, delivery health and access to the log archive from an independent account where available.
Validate with an authorized exercise
In a disposable environment, change a test logging configuration and verify independent alerting; confirm the ordinary workload identity cannot remove protected archived records.
Rollout and checks
Evaluate effective permissions and runtime behavior in a disposable account or namespace before production rollout. Retain the approved source revision, resulting artifact and independent audit trail. Plan recovery if identity, policy or admission dependencies fail. Reconcile running assets after the change because resources created outside the normal pipeline can otherwise remain outside its checks.
Scope and limits
This guide proposes a defensive test; it is not a tested production design. Check platform support and local requirements. References explain the mechanisms but do not certify the design. Behavior alone does not prove AI involvement.