A scheduled window, written rules of engagement, and a confidential report. Destructive production tests are off by default.
Testing is an authorized attempt to demonstrate how an attacker could abuse a named system. It is scheduled, scoped and bounded by written rules of engagement. You have a named stop contact while work is running.
We recommend a test when a client, insurer or internal policy asks for one, or when an audit has already shown that a deeper, human-led attempt is warranted. If an audit or a public scan will answer the question, we say so instead of selling a larger test.
The same authorization rules apply for clients internationally. Adjacent networks, third-party clouds and customer devices are out of scope unless named.
Authenticated and unauthenticated testing of the applications, hosts and services you list, within the accounts and roles you provide.
Prompt injection, agent misuse and data leakage against only the models and tools you authorize. See AI assurance for the broader review.
After you apply fixes, we retest the agreed items and update the record. Retesting is scoped; it is not assumed in the first fee unless written in.
What you receive
Penetration testing in more detail →
Describe the system, vendor or AI deployment under consideration. We respond with the proposed scope, timeline and fee.