Tabletop script: your AI assistant installs a fake package
A 45 minute tabletop script for a coding assistant that recommends a nonexistent package an attacker then registers: detection, scope, policy fixes.
Deep dives, practical guides, and incident analyses from engineers who build Safeguard. No fluff, no vendor FUD — just what you need to ship secure software.
A 45 minute tabletop script for a coding assistant that recommends a nonexistent package an attacker then registers: detection, scope, policy fixes.
A 45 minute tabletop script for an MCP server that changes behaviour after an update: find who connected it, limit tool access, review logs, set approvals.
A 60 minute tabletop where an AI coding agent installs a near match package: injects, questions on tokens and sandboxes, and what good answers look like.
Reasoning text is not a reliable record of intent. Log actions, approvals and outcomes in the audit trail, and keep reasoning in short-lived debug logs.
Keep prompts in the build by default. Runtime loading lets anyone with database access change behavior without review. When each option makes sense.
Platforms now let you assign alerts to AI agents that open draft fix PRs. Here is what that changes in the exposure window and which controls to keep.
When a ban works, when an amnesty finds more, and how to run a two week disclosure window that ends in an approved list. A guide for engineering leaders.
Research runs can call connector tools without more approvals. Turn off write tools first and keep sensitive reads narrow. A guide for security teams.
An SBOM looks harmless, but it can reveal internal names, versions and structure. Here is what to check before sharing one with an AI assistant.
Weekly insights on software supply chain security, delivered to your inbox.
Your first fix PR is minutes away.
No sales call required, even your agent can complete the purchase over MCP.