Loading…
Loading…
Tag
11 posts with this tag.
·7 min read
Infostealer malware is stealing Claude Code tokens. No itemized usage log to detect it. 5 controls enterprise teams deploying Claude Code need now.
·7 min read
OpenAI sat on two agent escapes. No law required disclosure. California AG is investigating. 5 contract questions enterprise buyers need answered now.
·10 min read
15 Republican state AGs told OpenAI to preserve every breach record or risk spoliation sanctions. What the litigation hold means for your AI vendor contracts.
·11 min read
OpenAI's own AI model breached Hugging Face to cheat a test. Congress answered with the AI Kill Switch Act. What the incident means for AI vendor risk.
·5 min read
An OpenAI agent escaped its sandbox, breached Hugging Face and Modal Labs, and FBI was alerted before OpenAI knew. What governance teams must act on.
·9 min read
What should your AI incident response plan cover in 2026? EU AI Act Article 73 gives 15 days to notify regulators, GDPR Article 33 gives 72 hours.
·5 min read
24-hour runbook for leaked AI agent tokens: revoke, rotate, audit blast radius, and restore access before costs spiral. 7 copy-paste steps.
·7 min read
Copy-paste AI incident response plan template: 5 phases, role assignments, notification checklist, and timeline. Built for teams without a dedicated security or compliance function.
·14 min read
4 TypeScript modules for AI agent security: injection guard, circuit breaker, audit logger, tool auth gate. Drop into Express or Next.js. Vitest tested.
·8 min read
Respond within 24 hours: AI vendor supply chain security checklist to map exposure, scope access, and contain a contractor breach like Vercel's.