Notifications
Clear all
Topic starter
01/08/2026 8:57 pm
TL;DR: As frontier models gain access to offensive AppSec tools, the traditional vulnerability-finding workflow becomes increasingly automatable, but reliability, reproducibility, safety guards, and auditability remain non-negotiable, according to PortSwigger. The decisive control is now the governance layer around the agentic core, because capability gains without deterministic enforcement amplify both attacker reach and operator risk.
NHIMG editorial — based on content published by PortSwigger: The beast needs a cage, what's next for AppSec post-Mythos
By the numbers:
- 17 minutes, redentials are exposed publicly, attackers attempt access within an average of 17 minutes, and as quickly as 9 minutes in some cases.
Questions worth separating out
Q: How should security teams govern AI-enabled workflows that can act on their own?
A: Treat them as identity-governed execution paths, not just software features.
Q: Why do agentic AI systems increase initial access and privilege abuse risk?
A: Because they can chain valid access into multiple tool calls without needing a human to approve each step.
Q: What do teams get wrong when they rely on human-in-the-loop controls for AI?
A: Teams often treat human-in-the-loop as a compliance checkbox, but the real test is whether the organisation understood the risk and placed controls around irreversible actions.
Practitioner guidance
- Build a deterministic action layer Separate model reasoning from privileged execution, and require every sensitive action to pass through explicit policy enforcement, approval rules, and immutable logging.
- Scope tool access like privileged access Treat scanners, exploit chains, and data connectors as privileged resources, then assign only the minimum target, dataset, and command scope required for the task.
- Define human approval points for high-risk steps Place approval gates before target selection, exploit execution, data export, and any action that could affect a live system or expose sensitive information.
What's in the full article
PortSwigger's full post covers the operational detail this post intentionally leaves for the source:
- How its next-generation Burp AI is structured around an agentic core with policy enforcement and audit logging
- The specific ways the toolset uses deterministic components to make autonomous testing more reliable
- The private beta feedback loop that is shaping the public release before the Black Hat research presentation
👉 Read PortSwigger's analysis of AI agentic security and the future of AppSec →
AI agentic security tools: are your governance controls keeping up?
Explore further
01/08/2026 9:04 pm
Capability without governance is the real security failure mode. Frontier models will keep improving, but model capability is not the limiting factor anymore. The limitation is whether security teams can force action-taking systems through a deterministic cage of policy, approval, and logging. In practice, this is the same governance problem that appears in NHI and privileged automation programmes, where access must be governed as a controlled runtime event, not assumed safe because the actor is software.
A question worth separating out:
Q: How do I know if an agentic security workflow is actually safe?
A: Look for reproducibility, deterministic policy checks, and complete audit trails. A safe workflow should produce the same governed outcome when rerun under the same conditions, and every action should be attributable to a policy decision rather than model improvisation. If that evidence is missing, the workflow is not ready.
👉 Read our full editorial: AI agentic security tools need stronger governance, not just more power
