platform-security-playbook

Designs and audits security and governance controls for platforms running AI coding agents.

Updated Jul 16, 2026
One-click install
npx skills add https://github.com/Cloud-Byte-Consulting/plugins --skill platform-security-playbook-cloud-byte-consulting
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: platform-security-playbook
Source: https://github.com/Cloud-Byte-Consulting/plugins/tree/main/platform-assessment/skills/platform-security-playbook
Command: npx skills add https://github.com/Cloud-Byte-Consulting/plugins --skill platform-security-playbook-cloud-byte-consulting

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Organizations adopting AI coding agents lack deterministic governance: agents act with inherited human privileges, vendor-level controls change silently, and compliance teams cannot audit agent actions. This Skill produces a concrete control design covering provisioning, policy, audit, proxy, and boundary enforcement for platforms where humans and agents ship code side by side. ## Core Features & Use Cases - Control architecture design: Audits existing platforms against five control responsibilities and five privilege-separation patterns, mapped to a four-level autonomy ladder (L1 human-in-the-loop through L4 autonomous agents). - Regulatory mapping: Verifies agent workflows against SOX, GDPR, FedRAMP, ITAR, IL4-IL6, NIS2, and DORA, including a sovereignty overlay with provider validation questions and exit-by-design GitOps patterns. - Vulnerability management rollout: Implements shift-down security with hardened signed base images, policy-as-code enforcement (OPA, Kyverno, Conftest), and a seven-step roadmap with owners and cadences. - Use Case: A platform team at a regulated enterprise asks whether agents can safely ship code under SOX; the Skill scores their autonomy level, maps mandatory controls, and delivers a phased governance roadmap with metrics. ## Quick Start Use the platform-security-playbook to audit our platform against the five control responsibilities and produce a governance roadmap for our compliance regimes.

Frequently Asked Questions about platform-security-playbook

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I set up governance for AI coding agents?

Start with observability before enforcement: audit current AI usage, deploy model-traffic visibility, and generate SBOMs for high-traffic services. Then provision governed workspaces from infrastructure-as-code templates and implement the five control responsibilities: provisioning, policy, audit, proxy, and boundary.

What security controls do AI agents need at different autonomy levels?

Controls scale with a four-level ladder. L1 needs identity, audit logging, and secret scanning; L2 adds PR-only writes and policy-as-code gates; L3 adds approval checkpoints and per-agent firewalling; L4 adds process-level boundaries and a tested kill-switch runbook.

Can AI coding agents comply with SOX, GDPR, or FedRAMP?

Yes, when the platform enforces regime-specific controls: SOX requires full audit attribution and segregation of duties, GDPR requires workspace-level geographic enforcement, and FedRAMP requires authorized services with continuous-monitoring evidence. ITAR and IL4-IL6 typically require self-hosted or air-gapped models.

What is shift-down security versus shift-left?

Shift-left asks developers to run scanners and triage findings earlier, which relocates toil. Shift-down makes the platform responsible: hardened signed base images, policy-as-code enforcement, and pre-approved templates remove vulnerability classes centrally so developers only see findings requiring action.

Why should agent controls not live in vendor tools or IDEs?

Vendor and IDE-level settings can change silently with updates and cannot be audited by compliance teams. Enforcement must live at the infrastructure layer the organization owns, where network access, permissions, and audit logging apply consistently across any model or agent framework.

When should agents not be given repository write access?

Agents should never inherit human privilege levels; defaults are least privilege, no internet egress, and read-only or PR-only access. Direct merges to protected branches and destructive actions must be impossible through identity boundaries, not merely discouraged in prompts.