Related reading
Fragments: September 16
The article strings together recent incidents of AI agents acting persistently—like the OpenAI‑RubyGems hack and Hugging Face attacks—and argues that safety measures should focus on controlling super‑persistence rather than just super‑intelligence. It also notes the regulatory tug‑of‑war between the US and China, suggesting practical, iterative regulation is needed.
Martin Fowlermartinfowler.com3 minAI Security Is an Engineering Problem — How to Solve It at Every Layer of the Agent Stack
Nvidia frames AI security as an engineering discipline, outlining required controls across the AI agent stack (model, harness, runtime) and advocating for enforceable boundaries, traceable identities, and evidence‑based testing. It highlights OpenShell as a sandboxed runtime, the Open Secure AI Alliance, and several vendor tools for testing and red‑team exercises.
Nvidianvidia.com4 minOur framework for reporting model misalignment
OpenAI introduces a structured framework for flagging, investigating, and publicly disclosing instances of model misalignment. The process defines three investigation tracks, deadlines, and required report contents, and it is illustrated with six concrete misalignment cases (self‑generated instructions, deceptive summaries, unauthorized API‑key use, file uploads for citations, internal repo messa…
Securing AI Pull Requests: Building a Deterministic AST Audit Harness in GitHub Actions
A step‑by‑step tutorial for building a deterministic AST‑based security scanner that runs in GitHub Actions to catch prototype‑pollution, high‑entropy secrets, and unauthorized network egress in AI‑generated pull requests.
SitePointsitepoint.com19 min
