AI security
LLMs, AI agents and RAG pipelines tested for prompt injection, data leakage and unsafe tool execution.
- Direct and indirect prompt injection
- System prompt and training data extraction
- RAG corpus poisoning and tenant leakage
- Unsafe agent tool calls and privilege escalation
- Model denial of service and token exhaustion
- Guardrail bypass and output handling flaws
The business problem
AI models shipped without adversarial testing expose system prompts, leak private retrieval data, bypass guardrails and trigger unauthorised tool or API actions.
Scope of assessment
Scope is agreed with you before any work starts. A typical engagement covers the areas below, adjusted to your environment, your priorities and any testing windows you need.
- Direct and indirect prompt injection
- System prompt and training data extraction
- RAG corpus poisoning and tenant leakage
- Unsafe agent tool calls and privilege escalation
- Model denial of service and token exhaustion
- Guardrail bypass and output handling flaws
Methodology
Automated coverage first, then manual work where it counts. Every finding is validated before it reaches you.
- Discovery
- Reconnaissance
- Threat modeling
- Scanning
- Manual testing
- Exploitation
- Validation
- Risk analysis
- Reporting
- Remediation support
- Retesting
Typical engagement timeline
Usually two weeks for an LLM application or agent workflow. Confirmed at scoping.
Standards and references
- OWASP Top 10 for LLM Applications
- MITRE ATLAS
- NIST AI RMF
Tools and techniques
- Adversarial prompt harnesses
- Custom red-team evaluation suites
- Proxy interception of model APIs
- Manual agent and RAG exploitation
What you receive.
- Executive summary for leadership
- Technical findings with evidence
- Severity and business risk rating
- Step by step remediation guidance
- Retest results
Benefits
- Know which weaknesses are real and exploitable
- Fix in the order that reduces the most risk
- Give leadership and auditors clear evidence
- Confirm fixes work through retesting
AI security report
Executive summary
Each finding: evidence, impact, steps to reproduce, fix.
Why us.
- Experienced security professionalsAssessments are led by practitioners who do this work every day.
- Offensive security expertiseWe think like attackers because that is our core discipline.
- Manual validationEvery finding is confirmed by a person before it reaches your report.
- Enterprise focused assessmentsScoping, communication and reporting that fit large organisations.
- Transparent reportingEvidence, reproduction steps and plain language. No padding.
- Actionable remediationSpecific fixes your developers and administrators can apply.
Questions.
How long does a penetration test take?
It depends on scope. A single application often takes one to three weeks, and larger estates take longer. We confirm the timeline during scoping, before work begins.
What does a security assessment report contain?
An executive summary, scope and methodology, each finding with severity, evidence and reproduction steps, the business risk, and specific remediation guidance.
Do you provide remediation support?
Yes. We walk your developers and administrators through each finding and stay available for questions while they fix it.
Do you provide retesting?
Yes. Once fixes are in place we retest the affected items and update the report with the verified status.
What security standards do you follow?
Our work references the OWASP Top 10, OWASP API Security Top 10, OWASP ASVS, OWASP MASVS, CWE Top 25, PTES, NIST guidance and MITRE ATT&CK, as applicable to the engagement.
