Quinine Cybersecurity · London

Continuous AI Penetration Testing for Teams Shipping AI

Quinine Cybersecurity builds Q9 Continuous, a platform for AI security testing, re-testing and evidence. Find weaknesses in LLMs, RAG systems, agents and their supporting APIs through authorised testing with human-reviewed findings.

  • Written authorisation first
  • Human-reviewed findings
  • Evidence-backed reporting
Q9 Continuous testing an AI system's security boundaries The Quinine Cybersecurity Q sits inside the core of an AI system. Test probes travel from it along each connection to the API gateway, model, agent, RAG data store and user, mobile and workload endpoints, and each checkpoint on a trust boundary lights as it is tested. One checkpoint is flagged, its evidence is sent to the evidence log, and the checkpoint passes when it is re-tested. SEG-01 · EDGE SEG-02 · CORE SEG-03 · DATA USER MOBILE WORKLOAD ENDPOINTS EVIDENCE LOG API GATEWAY INGRESS · AUTHN MODEL AGENT RAG STORE TLS 1.3 AUTHORISED SCOPE · TESTING BOUNDARIES _ TEST · RE-TEST · EVIDENCE
Test each boundary. Re-test the fix. Keep the evidence.

01Our product

Find the risk. Re-test the fix. Keep the evidence.

Start with a one-week Diagnostic, then keep testing as your AI changes. Every finding is reviewed by a person before it is reported.

Platform overview

Starting prices depend on the agreed scope.

02How it works

From first test to continuous evidence.

Nothing is tested before scope is agreed and authorised in writing.

How it works in detail

  1. 01

    Discovery

    Understand the application and security requirements.

  2. 02

    Scope and Authorisation

    Confirm testing boundaries in writing.

  3. 03

    Diagnostic

    Test the agreed AI system.

  4. 04

    Human Review

    Review findings, evidence and severity.

  5. 05

    Continuous Testing

    Re-test fixes and significant changes.

  6. 06

    Proof

    Preserve evidence and verify approved public proof where supported.

03What we test

Security testing for the systems behind your AI.

The parts of an AI system an attacker would use. Coverage is confirmed during scoping.

Everything we test

04Evidence and proof

Evidence your security team can verify.

Every result records what was tested, when, and what was not covered.

  • Human-reviewed findings A person reviews every finding and its severity before it is reported.
  • Reproducible evidence Evidence references your engineers can follow and re-test.
  • Scope and limitations A record of what was in scope, and what testing could not cover.
  • Dated, versioned records Results tied to the date and the version of the system that was checked.
  • Signed proof verification Where supported and approved, anyone can verify a signed proof without seeing client findings.

A proof is not a certification and does not guarantee security. Automated platform checks complement, and do not replace, an independent penetration test.

Methods and reports reference OWASP Top 10 for LLM Applications, MITRE ATLAS, NIST AI RMF, ISO/IEC 42001, ISO/IEC 27001, UK GDPR and the EU AI Act. Framework alignment

Alignment means our methods and reports reference these frameworks. It is not a certification, and an assessment does not by itself make a system compliant.

05Who it is for

For teams whose AI keeps changing.

A single test goes stale as models, prompts and integrations change.

Industries

  • AI Startups and SaaS Teams

    You ship AI features every sprint. Re-testing after significant changes keeps your findings current.

  • Financial Services and Regulated Organisations

    Dated, human-reviewed evidence supports your risk and assurance work as AI systems evolve.

  • CTOs and Security Teams

    One record of scope, findings and re-tests shows what was checked and what has changed since.

06Founder

Founder-led and focused on AI security.

About Quinine Cybersecurity

Chinmay Khuspare, Founder and CEO of Quinine Cybersecurity

Chinmay Khuspare

Founder & CEO

I am an MSc Cybersecurity postgraduate from NCSC-certified Lancaster University. I built Quinine Cybersecurity because I saw the same pattern across every organisation deploying AI: the models shipped fast, the security came later, and the gap kept growing. Quinine exists to close that gap. We provide hands-on AI security testing for companies that take their AI deployments seriously.

07FAQ

Common questions.

What is Q9 Continuous?

The continuous AI penetration testing platform from Quinine Cybersecurity. It holds the agreed scope, reviewed findings and evidence, runs authorised re-tests, and lets an approved proof be checked publicly.

What happens during the Diagnostic?

A one-week AI penetration test of an agreed scope. We confirm the boundaries, test instruction, data and tool boundaries, then walk your team through findings with evidence, limitations and a route to re-test fixes.

Is testing automated or human-reviewed?

Both. Q9 Continuous runs AI-driven tests; every finding is reviewed by a person before it is reported.

When does continuous testing begin?

After the Diagnostic, once the scope is agreed in writing. It then re-tests fixes and significant changes within that authorised scope.

What does Q9 Driftmark monitor?

Supported change signals for a previously checked system, compared with the checked state, so you can see when a re-check is due. Q9 Driftmark is in early access; edition, scope and availability are confirmed before you join.

Is signed proof a certification?

No. A signed proof states what was checked, for which version and when. It is not a certification and does not guarantee security.

08Next step

Ready to test your AI system?

Start with a Q9 Continuous Diagnostic, or talk through your application and scope first. Submitting an enquiry never authorises or starts any testing.

Please do not send credentials or confidential findings through the enquiry form.