Start with one application domain—HR, finance, customer support, or another real setting—and one AI surface: a chatbot, agent, MCP integration, or AI workflow.
We follow that surface through the application to understand what it can access and affect, whether meaningful behaviour is observable, how relevant attacks manifest, and whether there is a credible path to detect and protect.
Whole surface
We examine the parts that can turn model behaviour into an application consequence:
Two ways in
Start where you are. Stop when you know enough. Continue when there is a worthwhile path to detect and protect.
Explore
You know the domain and the AI feature, but not where the meaningful risk or evidence gap sits. Begin by framing the surface and making the application path observable enough to decide what deserves testing.
Bring one surfaceRespond
You have a known or suspected disclosure, action, control failure, or attack path. Establish the minimum safe context, reproduce what matters, and move quickly toward an evidence-backed response.
See the Active issue pathwayMovable boundary
Agree the application domain, selected surface, authority, meaningful behaviours, and safe evidence boundary.
Map the real application path and establish what can and cannot be seen in current telemetry.
Run relevant, authorised attacks and trace attempted and completed effects through the system.
Stop with evidence and options, or explicitly agree that the next stage is worthwhile.
Improve telemetry, detection, or bounded controls at the layer that owns the authority, capability, or consequence.
Repeat equivalent tests and verify the authoritative downstream outcome after change.
Active issue pathway
Bring the known or suspected issue. We still establish authority, safe handling, and a reproducible boundary, but we do not make you repeat discovery work you have already done.
The first useful outcome may be a verified explanation, a missing observability signal, a bounded control change, or a retest that shows whether the consequential effect has stopped. The next step is agreed from the evidence, not assumed in advance.
Bring an active issueEvidence before claims
A model response, an alert, an enforcement decision, and a verified downstream result are different evidence states. The assessment keeps them separate.
Evidence state explorer
Select each state to compare what appeared in the interface with what happened in the application.
What the model showed
A response that sounds cautious is shown to the user.
What the application did
The overpowered service identity still completes the unsafe email action.
What this proves
The application is vulnerable. The message did not enforce the boundary.
What the model showed
A detector raises a warning around the same attempt.
What the application did
The downstream action remains possible because nothing enforces the warning.
What this proves
Detection is evidence, not prevention. The consequential path is still open.
What the model showed
The interface reports that this pinned attempt was stopped.
What the application did
An application control denies the action before it reaches the email service.
What this proves
This path was blocked. It does not establish universal protection.
What the model showed
The same meaningful attempt is repeated after the correction.
What the application did
Authoritative readback shows that no unsafe email side effect exists.
What this proves
The narrow correction held for the pinned scenario and produced the intended effect.
Required
We need an authorised target, a named owner, agreed test identities and data, explicit constraints, safe evidence handling, and access to the people who understand or can change the application.
Not this service
This is not compliance certification, unrestricted penetration testing, destructive testing, or proof that every prompt injection or future attack is blocked. Specialist work outside Viewyonder’s competence is identified rather than improvised.
Not ready to commit?
Use six questions to find a sensible starting point for one surface.
Choose the closest answer for one AI surface. Your answers stay in this page and disappear when you leave or reload it.
This is a starting-point check, not a maturity score. Completing it does not establish that the surface is secure.
Start with what you know
An ordinary-language description is enough. Do not include credentials, customer data, prompts, or confidential architecture details.
Start the assessment conversation