Topic
Policy as Code is the practice of expressing governance, security, and compliance rules in machine-readable form for automated enforcement.
Devops.com argues that when an agent opens 40 pull requests before lunch, plan review still blocks merges and writes audit events but stops checking anything. Its remedy automates policy checks and caps the damage, so people review intent.
Reality
JFrog is deprecating Xray's Block Download between April and November 2026 and moving enforcement into Curation, a product licensed per seat. Teams who use Xray as their gate have eight months to fund a replacement.
Reality
GitHub's workflow execution protections went generally available on September 17, and the evaluate mode that shows what a rule would block before enforcement is documented as an Enterprise Cloud capability.
Reality
A dev.to walkthrough puts the spend limit in an Azure Policy deny rule bound to one resource group, with a two-SKU allow list and a custom RBAC role whose only actions are read and restart. The gate declines the request at deployment time.
Reality
Arcjet's new product evaluates an agent's next action inside application code, returning an allow or deny before the tool call runs, with policies written in Rego and managed centrally by the security team.
Reality
In HackerOne 121461 a researcher created the missing bucket in their own AWS account and served files on a2.bime.io. The state that allowed it is a name sitting in the DNS zone with no matching bucket in the account.
Reality
A dev.to checklist of ten software delivery gates for AI agents insists every check be automated, fast, blocking and observable. The gate its author calls no replacement for human review cannot meet that bar.
Reality
In HackerOne report #3022516 the trail was multi-region, the metric filter for unauthorised API calls existed and the alarm published to an SNS topic, while threat_detection.enabled read false. Turning it on costs one CLI call.
Reality
The New Stack's three-pillar recipe for cloud resource ownership pairs a CloudQuery inventory query with an env0 admission policy and a creation-time audit record. Two of them look for the owner in different places.
Reality
PolicyAware 0.4.4 evaluates identity, tenant, region, arguments and risk tier before an agent's action changes state. Enforcement sits inline on every turn, and the project's own guidance is that adopters measure what that costs.
Reality
GitHub put Copilot approvals into public preview on 1 September 2026. The toggles that decide whether an approval counts live in Copilot settings across three scopes, not in the rulesets a policy-as-code audit reads.
Reality
AWS EBS volumes are zonal, so a StatefulSet pod can only run in the zone that holds its disk. An admission policy reads that zone and places eligible stateless pods beside it, for a claimed saving above 10%.
Reality
A dev.to write-up prints the ClusterRole that gives an operator four write verbs on mutating webhook configurations, then the two manifest lines that make the resulting persistence read as a healthy cluster.
Reality
Ed25519 tells you which key signed which bytes. A slice log from the Ranex project shows how a policy path read from the working tree let the gated side pick the rules, and what pinning the trust root to the evaluated commit cost.
Reality
EU Cyber Resilience Act enforcement starts in September with personal liability for security leaders written in, according to JFrog, so the lag between an auditor's request and the proof now has a named owner.
Reality
HashiCorp's pitch is that agents should propose changes while Terraform governs them, with per-run OIDC credentials and project-scoped identities doing the work that change-by-change human review cannot do at machine speed.
Reality
AWS has extended Policy in Amazon Bedrock AgentCore to rate limits, prerequisites, ordering and cumulative effects, checked at the gateway rather than requested in a prompt.
Reality
A CNCF blog post argues Kyverno gets filed as an admission gate and then run at a quarter of its capacity. The teams getting returns are platform teams, not security teams.
Reality
Blocking newly published packages from being indexed treats ingestion speed as the attack surface. The cooldown window is a policy call platform teams have to own, not a switch they flip.
Reality