OpenAI's Codex Security demo introduces a repository-review workflow; the official plugin quickstart provides the operational detail needed to assess its output. A standard local scan is described as leaving source files unchanged while producing findings, coverage information and remediation guidance. Teams should confirm the repository, branch and revision before starting, supply relevant security context, and record both host and plugin versions so failures can be investigated consistently. The documentation distinguishes the local desktop or CLI plugin from the separate cloud workflow for connected GitHub repositories. Most importantly, completion is not a clean bill of health. Reviewers must inspect which areas were covered or deferred and read each finding's source evidence, attacker prerequisites, validation method and remaining uncertainty. Validation can consist of source analysis without a running reproducer. Keeping the report, manifest, findings and coverage artifacts together preserves those qualifications when results move into engineering triage.
Codex Security: verify scan scope, evidence and coverage before acting
Related research
More curated notes connected through AI Red Teaming and Model Evaluation.
Pacing model development in an era of cyber-critical capabilities
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.
OWASP Top 10 for Agentic Applications for 2026
OWASP's community guide organizes agentic-system risk into ten categories, including goal hijacking, tool misuse, identity and privilege abuse, memory poisoning, insecure inter-agent communication, cascading failures, and rogue-agent behavior. It provides a shared taxonomy and mitigation starting point rather than a certification checklist or evidence that a deployed system is secure.
A blueprint for democratic governance of frontier AI
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.