What should you log from a cloud coding agent session?
A cloud agent session should leave a trail: who started it, which commands ran, which hosts were blocked, and what changed. Fields worth keeping.
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 cloud agent session should leave a trail: who started it, which commands ran, which hosts were blocked, and what changed. Fields worth keeping.
Log versions and identifiers, not raw secrets: template version, model version, dataset hashes and retrieved document IDs. A short list for fast triage.
Two practical ways to poison web scale training data, per a 2023 paper: change content after indexing, or edit just before a snapshot. Defenses explained.
AI coding agents add dependencies fast. Treat each one like a human change: check it in the pull request, apply policy, and record who approved it.
A security connector should start with read scopes and ask for more only when needed. What least privilege looks like and what to do when it asks too much.
PyTorch says secure use is your job: loading untrusted models is like running untrusted code. Here is what the policy calls a bug and what you should do.
Before connecting a vendor's AI agent, list its identity, scopes, tokens, and actions. Ask for least privilege, short lived access, and logs you can read.
Keras safe_mode blocks unsafe lambda deserialization when loading .keras models. Here is what it does, what turning it off risks and a safe way to proceed.
An MCP guardrail is a checkpoint between an AI agent and its tool servers that applies your rules to each call. Here is how it works and what it cannot do.
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.