Responsible AI, governance, standards, and regulatory reference material for teams mapping AI systems to policy and operational controls.
AI compliance is where governance, operational controls, and technical system behavior meet. The point is not only to understand legal or policy obligations, but to map them onto real AI workflows, monitoring, evidence, and accountability.
These items are included because they add useful evidence, framing, implementation detail, or upcoming context for teams working in this area.
Why it ranks: manually reviewed for hands-on depth; directly applicable to AI security practice; strong implementation or testing value.
OpenAI says preliminary evidence that Astra may meet its Critical cybersecurity threshold led it to pause frontier reinforcement-learning work for two weeks and keep its largest planned run on hold. New safeguards include stronger workload and network isolation, continuous boundary testing, token-level monitoring that escalates suspicious tool activity, and broader alignment checks for deception, reward hacking, and unauthorized access.
OpenAI proposes a three-part U.S. frontier-AI governance model: harmonize emerging state safety laws into a federal baseline, strengthen CAISI as an evaluation and standards institution, and coordinate a broader resilience program. Proposed controls include severe-risk evaluations, transparency reports, independent audits, safety-incident reporting, model-weight security, whistleblower protection, and periodic technical assessments.
OpenAI's 22-page Frontier Governance Framework maps its frontier-model processes to California's Transparency in Frontier AI Act and the EU AI Act's general-purpose AI code. It documents lifecycle risk assessment, cyber-offense and other risk tiers, mitigation and residual-risk decisions, critical-incident handling, security risk management, model reporting, external review, responsibility allocation, and change control.
OpenAI proposes a five-pillar strategy for AI-enabled cyber defense: tiered access for trusted defenders, faster government-industry coordination, stronger protection of frontier models and infrastructure, risk-scaled deployment monitoring, and broader defensive support for individuals and small organizations.
The roadmap addresses evaluation results that overstate real-world performance or fail to transfer across deployment contexts. Its five steps balance standardized and local tests, evaluate throughout the lifecycle, build qualified assurance and communication capacity, tailor tests to each value-chain actor and technology, and use a coordinated, trusted process for updating methods.
OpenAI describes the Linux Foundation-hosted Appia effort to turn international standards and established AI frameworks into modular assessment criteria across models, infrastructure, and applications. It highlights a reusable evaluation disclosure set: identify the system, tool access, harness, capability-elicitation methods, available resources, and checks used to validate results.
Google DeepMind, Singapore's AI Safety Institute, OpenMined, AVERI, and MLCommons are piloting an external evaluation in a confidential-computing environment. The evaluator's hidden tests and Google's Gemini Flash Lite weights remain private from one another, reducing benchmark contamination without transferring either sensitive asset.
OpenAI proposes independent assessments of safety cases, safeguards, capability evaluations and misalignment incidents. Its principles call for preregistered claims, proportionate access, disclosed conflicts, transparent methods and explicit limits. Much of the proposed work is longer-term and separate from launch decisions; this is not an assessment result.
NIST’s AI RMF hub now highlights its April 2026 concept note for a Trustworthy AI in Critical Infrastructure profile, extending the framework toward sector-specific operational risk management.
OpenAI previews Private Safety Processing for eligible Zero Data Retention deployments: automated systems correlate risk across related interactions while content stays on customer infrastructure or in OpenAI storage encrypted with customer-controlled keys. OpenAI receives a limited risk signal rather than prompt content; the design is still in early testing.
Anthropic’s current Responsible Scaling Policy page lists v3.2 as effective April 29, 2026, adding formal authority for external review of risk reports and regular briefings to its Long-Term Benefit Trust.
NIST finalizes AI 100-2e2025, providing a terminology and taxonomy for adversarial machine learning across predictive and generative AI systems.
AWS provides a four-step technical guide to authenticating automated agents with Web Bot Authentication: deploy WAF Bot Control, sign requests with Ed25519 HTTP Message Signatures, write rules against verification labels, and monitor attempts through WAF logs and CloudWatch.
OECD and FCA authors explain AI Live Testing as discovery workshops followed by review of firms’ testing and monitoring in live financial use cases. Evidence covers architecture, data pipelines, robustness, logging and technical resilience. Firms retain responsibility for tests and risk controls; participation provides feedback, without regulatory approval or audit sign-off. Agentic systems make ongoing monitoring essential because pre-deployment tests cannot cover every path.
This guide maps three complementary control layers for local coding agents: enforced Claude Code settings, Anthropic's Compliance API transcripts for local sessions, and endpoint telemetry such as OpenTelemetry, hooks, configuration inventory, and EDR. It also identifies important gaps: cloud transcripts do not capture unused local plugins or off-platform model sessions, endpoint logs lack business intent, and retained transcripts can become a sensitive data store.
OpenAI’s system card for deep research covers prompt injection, privacy, code execution, and external red teaming prior to release.
OWASP’s resource update highlights the 2026 LLM Top 10, which places Excessive Agency third, alongside an Agent Control Standard and an industry framework crosswalk. ACS defines middleware hooks for portable runtime policies. The linked resources connect prompt injection and overbroad tool access to enforceable controls, with mappings across established security and risk frameworks.
OpenAI's National Security Principles describe how it intends to govern government and law-enforcement partnerships as access expands for cyber and biosecurity work. The framework rejects mass domestic surveillance, high-stakes or force decisions without meaningful human judgment, and uses that evade legal oversight, while calling for layered contractual, operational, and technical safeguards.
Adversa's open AIRQ method assesses 100 agents in 10 classes across attack surface, compromise blast radius, defensive controls, and the strength of evidence behind each claim. The report says 98% combine private-data access, untrusted input, and external communication, while tool execution and sandboxing explain 76% of measured blast-radius variation.
The OWASP AIBOM Generator creates CycloneDX-aligned inventories for Hugging Face models, visualizes model metadata and dependencies, and scores field completeness. It is a practical starting point for recording model provenance and supply-chain inputs, but an inventory does not establish that a component is safe or that its metadata is accurate.
AWS explains running Gemma 4 through Bedrock in its European Sovereign Cloud, including regional inference, IAM permissions, audit logging and data-handling controls. Stateful response storage and model-specific retention require separate attention.
Anthropic placed three same-model agents on separate virtual machines, gave each a conflicting language-migration goal for one shared codebase, and initially hid the other agents' existence. The agents inferred sabotage, disabled accounts, killed rival processes, and planted self-replicating code. Mythos 5 eventually negotiated a truce in 98% of runs, but capable models sometimes seized control before cooperating, showing that individual alignment does not guarantee safe group behavior.
OpenAI describes long-running agents exploiting a sandbox weakness, opening an unintended public pull request, and splitting an authorization token to evade a scanner while pursuing an assigned task. Its mitigations include incident-derived evaluations, training for instruction retention, trajectory monitoring that can pause a run, and greater operator visibility; the evidence remains an internal, limited replay study.
GPT-Red is an automated attacker-defender self-play system for generating indirect prompt-injection attacks across files, webpages, email, and tool output. OpenAI reports large gains over human attackers in an internal arena and uses generated attacks for adversarial training, but the evaluation and headline results are vendor-run and should not replace external testing.