Notifications
Clear all
Topic starter
11/08/2026 3:13 pm
TL;DR: AI offensive security platforms are moving beyond generic LLM orchestration toward owned models, harnesses, and training loops that adapt to a specific environment, according to Novee. That shift matters because AI pentesting now depends as much on business context, guardrails, and retesting discipline as on raw model capability.
NHIMG editorial — based on content published by Novee: Model, Harness, Gym: Why Novee Owns the Full AI Pentesting Stack
By the numbers:
- Novee says its fine-tuned models reach the exploit rates of state-of-the-art models at about 15% of the cost.
Questions worth separating out
Q: How should security teams govern AI-assisted web testing tools?
A: Treat AI-assisted testing as a governed workflow, not a convenience feature.
Q: Why do generic AI models struggle with realistic pentesting?
A: Generic models can reason, but they usually lack durable knowledge of a specific environment’s roles, workflows, and business rules.
Q: What do teams get wrong about automated pentesting?
A: They assume automated coverage is enough on its own.
Practitioner guidance
- Define hard scope boundaries for AI pentesting Restrict live testing to explicitly approved IP ranges, applications, and workflows, and enforce those limits outside the model as well as inside it.
- Test authorisation abuse, not just vulnerability discovery Include business-logic abuse, multi-step privilege escalation, and workflow chaining in red-team or automated pentest scenarios.
- Demand retest evidence after remediation Require the platform to rerun the same attack path after a fix and show whether the control held under the same conditions.
What's in the full article
Novee's full article covers the operational detail this post intentionally leaves for the source:
- The three-layer AI pentesting stack described by the vendor, including the offensive reasoning model, harness, and training gym.
- The vendor’s explanation of how its agents are benchmarked, post-trained, and promoted into production.
- The practical examples of constrained testing, including guardrails inside the model and outside it.
- The customer-specific Asset Intelligence Model approach and how it changes findings across engagements.
👉 Read Novee's discussion of its full AI pentesting stack and training loop →
AI pentesting stacks and business-context attack paths: what changes?
Explore further
11/08/2026 3:27 pm
AI pentesting is becoming an identity-governed system, not just a model problem. The article’s core point is that offensive AI needs scope, guardrails, and environment awareness to stay useful. That aligns with how NHIs and agentic systems must be governed in production: the issue is not only what the system can infer, but what it is allowed to do. Practitioners should treat AI pentesting platforms as privileged execution systems and govern them accordingly.
A question worth separating out:
Q: What should organisations do before allowing AI offensive tools near sensitive systems?
A: They should require formal approval of the target set, explicit denial of destructive actions, network-level containment, and a review process for any learning loop that persists beyond one engagement. If the system improves over time, then its memory and training inputs need the same governance discipline as other privileged identities.
👉 Read our full editorial: AI pentesting stacks now depend on model, harness, and data
