AI threat modeling
Map agents, tools, data flows and trust boundaries; identify abuse cases specific to your architecture.
Practice
Governance and assurance for LLM applications and agentic systems, from threat model to production controls.
Agentic AI changes the attack surface. Prompt injection, poisoned context passed between agents, over-privileged tool access and runaway planner loops are not hypothetical; they show up in the first serious review of almost every system we look at.
Our practice brings a security-engineering discipline to AI deployments: inventory what each agent can do and whom it trusts, model how that can be abused, test it, and put controls and monitoring in place before go-live. The work draws on our own published research into agentic supply-chain risk, memory-transit attacks and automated red-teaming.
We work with product teams who want to ship, not to be told no. The output is a prioritized set of fixes and a control framework your auditors will recognize.
Offerings
Map agents, tools, data flows and trust boundaries; identify abuse cases specific to your architecture.
An agentic bill of materials: what each agent can call, read and write, and the trust it inherits.
Structured adversarial testing for prompt injection, context poisoning, privilege escalation and loop exhaustion.
Policies, controls and review gates aligned to NIST AI RMF, ISO/IEC 42001 and OWASP LLM Top 10.
A pre-production gate: guardrails, monitoring, kill switches and incident playbooks.
Training for engineering and security teams on building and reviewing agentic systems.
How an engagement runs
Inventory the systems, agents, tools and data in play; agree the assessment boundary.
Threat modeling workshops, then hands-on testing against the agreed scope.
Findings ranked by exploitability and impact, each with a concrete remediation.
Implement controls with your team; define what gets logged and who gets paged.
Platforms
Questions
No. Most assessments are for organizations adopting vendor AI features, Copilots and agent platforms that touch sensitive data.
A focused assessment of one system runs three to five weeks. Program-level governance work is scoped separately.
Yes. Reports are written to be shared with auditors, enterprise customers and insurers.
A practice lead replies within one business day. No sales deck, no discovery questionnaire.