Q9 Continuous capability

AI application security controls testing

Q9 Continuous tests the controls around your AI application: who and what can reach the model, where data flows, where the trust boundaries sit, how secrets are handled, which third-party models and services it depends on, and whether misuse would be visible to you.

Capability
05 / AI application security controls
Coverage
Confirmed during scoping
Tested in
Q9 Continuous, with human review
Mapped to
MITRE ATLAS, NIST AI Risk Management Framework, ISO 42001

01What it does

What it does

AI application security controls testing checks the access, data-flow, secrets and monitoring controls around an AI system. It is tested as part of Q9 Continuous, within the authorised scope, alongside the model, retrieval and API testing for the same application.

Design documentation and walkthroughs with your engineers help target the tests. Every finding is reviewed by a person before it reaches you, and coverage is confirmed during scoping.

AI application controls test surfaceUsers and internal services reach an AI application inside your trust boundary. The application holds model access credentials, reads from internal data and calls an external model provider across the boundary. Test points sit on model access, data flows, the trust boundary and the third-party dependency.YOUR TRUST BOUNDARYUsersCHANNELSServicesINTERNALAI applicationORCHESTRATIONDataCONTEXTSecretsMODEL KEYSModel providerTHIRD PARTYT1T2T3T4
Controls testing traces each path into and out of the model, including the ones that leave your organisation.

02Risk register

Risks we evaluate

What Q9 Continuous tests for within your agreed scope. Coverage is confirmed during scoping; not every item applies to every deployment.

  • 05.01Model accessWho and what can call each model, with which credentials, and with what level of privilege.
  • 05.02Data flowsWhere personal, confidential or regulated data enters prompts, context, logs and outputs.
  • 05.03Trust boundariesWhere untrusted content meets instructions, and where the design relies on the model to enforce access.
  • 05.04Third-party model dependenciesReliance on external model providers and AI services, and what data is shared with them.
  • 05.05Secrets in the AI pathHow keys and credentials used by models, tools and integrations are stored and scoped.
  • 05.06Monitoring and loggingWhether misuse or unexpected behaviour of AI components would be visible to you.

03Who needs it

Who needs it

  • Teams launching AI features who need to know the controls around them hold up under attack.
  • Organisations combining several models, providers or AI services in one system.
  • Security and risk teams that need evidence about the controls around an AI system already in use.

04Approach

How Q9 Continuous tests it

Every test follows the same path, agreed in writing before any testing starts.

Our full approach

  1. Discovery

    We map your AI architecture, understand your threat model, and define what’s in scope based on your risk appetite and compliance obligations.

  2. Agreed scope & written authorisation

    Scope, environments, accounts and testing windows are agreed in writing. Nothing is tested without written authorisation from the people responsible for the system.

  3. Testing

    Q9 Continuous runs AI-driven tests against the authorised system, tailored to your deployment.

  4. Human-reviewed findings

    Every finding is reviewed by a person before it reaches you, with severity, context and stated limitations.

  5. Reporting & remediation

    Severity ratings, reproduction steps and remediation guidance your engineering team can act on, plus an executive summary for board-level reporting.

  6. Re-testing where agreed

    Where agreed, fixes are re-tested within the authorised scope through Continuous AI Pen Testing.

Testing runs on Q9 Continuous: fixes and significant changes can be re-tested within the authorised scope, and Q9 Driftmark (early access) can show when a checked system changes. Automated checks complement, and do not replace, independent penetration testing.

05Deliverables

What you receive

  • A findings report with severity ratings, reproduction steps and remediation guidance
  • A record of the access paths, data flows and trust boundaries tested
  • An executive summary for board-level reporting
  • A clear statement of what was in scope, and of any testing limitations

Each test is a point-in-time check of an agreed scope. It is not a certification and does not guarantee that every risk has been found.

What We Test

Everything Q9 Continuous tests