Blog
Agent provenance is ambitious, so let’s get the hard parts right
Agent provenance is a useful stress test for whether your agent security stack can actually deliver accountability. It requires more than discovery or observability. You need an immutable chain of events, blended human-agent identity, runtime policy enforcement, and enough context to determine whether an agent’s actions stayed within the originator’s intent.
No results found.
4 mins
Developers must restrict agent access, mandate human code reviews, and sanitize inputs to mitigate unauthorized repo takeovers.
4 mins
If you are running agents in evaluation, production, or anywhere in between, do not only ask whether the model will stay inside its sandbox. Ask whether your identity and authorization controls can stop the model after it finds a way out.
4 mins
P0 now supports connectors for Salesforce, Cloudflare, Grafana Cloud and Datadog, extending Zero Standing Privilege controls for users and agents beyond cloud infrastructure into broader workforce application coverage.
3 mins
Logging can tell you something happened. But none of that alone determines whether the action should be allowed, given the full chain of authority behind it.
7 min
Tool-level filtering alone is not access control.
6 mins
"Just in Time (JIT) access" is a simple concept but can be architected in multiple ways with significant ...
5 mins
Salesforce Agentforce and Snowflake Cortex have quietly become two of the largest agentic deployment platforms in the enterprise.
4 mins
The Composio breach was not only about agentic AI, leaked credentials or sandbox execution. It was about trusted internal systems with enough standing privilege to become an attack path.
5 mins
The future of agentic security will not be determined by model quality alone. It will be determined by how well organizations govern human authority, delegation and operational identity before autonomous systems begin operating at AI scale.
6 mins
Vibe coding changes the relationship between a developer and the code they ship. It does not change the fact that code carries identity and access decisions, and that those decisions have consequences.
5 mins
The PocketOS incident is being told as a story about a coding agent that went off the rails, but that is not the true extent of the tale. It is a story about a long-lived API token with no scoping, no expiry, no approval gate, and no separation between production and backup, sitting where any sufficiently curious actor could find it.
4 mins
Snowflake Cortex is a powerful addition to the modern data platform, and the use cases are real. But every Cortex Agent deployment is also an identity governance event. The agent does not audit itself. It queries what it can query, surfaces what it can surface, and connects to what it is given access to.
No results found.