DUBSAR for CISO
Role · CISO
Test an AI agent’s control boundary with the CISO
The workflow says a message was denied. Could the same account still send it through another route? Before accepting a scope, the integrator and the client’s CISO need to check where the decision actually takes effect and how they can establish that it does.
This guide proposes a test plan limited to an identified action, access rights and routes. It supports a decision to accept the tested boundary, request further checks or keep the action on hold. The method can be used without DUBSAR.
In brief
The question and the useful result.
- Question
- For which action and route, and on what evidence, can we accept a control boundary?
- Useful result
- A test plan covering explicit denial, revoked access, decision-service failure and bypass routes, with expected criteria, observations and coverage limits.
DUBSAR for CISO
Define the boundary before testing
Choose a specific operation, such as sending a message to a test recipient. Record the account, its access rights, the intended route, the applicable rule and the relevant component versions. Identify other routes available to that account.
Agree with the client on the observations available before and after the control point: the decision, an outgoing attempt and the receiving system’s response. Establish who can consult each source and what it can show. A denial displayed in an interface does not, by itself, establish that nothing was sent.
Run the checks within an authorised test scope, using test data and recipients. The expected results below are criteria to agree; they do not describe tests already completed on DUBSAR.
DUBSAR for CISO
Four situations to test
| Situation | Preconditions and requested action | Expected result to verify |
|---|---|---|
| Explicit denial | The rule denies sending to the selected recipient. Request that action through the route under review. | The denial prevents an outgoing attempt through that route; both the decision and its enforcement are observable. |
| Revoked access | Revoke the identified access, record when the revocation is expected to take effect, then request a new action. | The revoked access no longer permits the action under the stated conditions. A denial or access failure is recorded as such. |
| Decision service unavailable | Make the service unavailable within the test scope, then request a new action that requires its agreement. | The new attempt remains on hold while no applicable authorisation can be established. The service outage remains visible. |
| Bypass route | Using the account under review, examine another route authorised for testing, such as direct access to the receiving system. | The account cannot produce the effect through a route it is forbidden to use. If a bypass succeeds, the claimed boundary must be corrected or its scope explicitly narrowed. |
A conclusion limited to one route does not cover direct access or other accounts. These four situations are not a complete security test programme: add the checks required by the scope and its dependencies.
DUBSAR for CISO
Separate blocking a new attempt from the outcome of one already sent
In an illustrative example, a mission prepares a supplier message. An initial send attempt receives an acknowledgement, then the decision service becomes unavailable. The team checks that the outage holds back a new attempt.
That finding establishes neither cancellation of the first attempt nor absence of a message at the recipient. Interpret the acknowledgement according to what it confirms: a received request can still have an unknown outcome. The messaging example does not announce an available DUBSAR integration.
Keep the request, authorisation, attempt, acknowledgement and confirmed effect distinct. In the mission record, retain “new attempt on hold” separately from “previous attempt’s outcome to be checked”. Passing the blocking test does not resolve the second question.
DUBSAR for CISO
A record to complete for each test
Keep the plan in your preferred working document. It is not an automatic DUBSAR export.
| Field | Information to record |
|---|---|
| Scenario | The denial or failure condition to test, with a test reference. |
| Preconditions | Identity, access rights, rule, versions, route and observation points. |
| Requested action | The exact operation, test data and recipient. |
| Expected result | A criterion agreed before testing and the scope of the intended conclusion. |
| Observed result | Findings, date and status: not tested, criterion met, criterion not met or undetermined. |
| Evidence | Accessible references, their sources and what each item establishes. |
| Coverage limit | Routes, accounts, versions or effects that could not be checked. |
| Corrective-action owner | The person responsible for the gap, the next check and its agreed due date. |
Do not turn a missing observation into a favourable result. A silent log may simply leave the question open; record the check still needed.
DUBSAR for CISO
Make a decision about the exact scope
The integrator gives the results to the CISO and the person authorised to accept the scope under the client’s arrangements. The decision identifies the relevant actions, accounts, routes and versions.
- Accept the tested boundary when the agreed criteria are established, recording remaining limits and the conditions for review.
- Request further checks when evidence is missing or a finding remains ambiguous, naming the person responsible for resolving it.
- Keep the action on hold when the necessary conditions for authorisation or the expected control have not been established.
Acceptance of a test does not itself authorise a business action. It records what has been checked to support the client’s decision.
DUBSAR for CISO
Frequently asked questions
Does a denial in a log prove that an action was blocked?
It establishes that a denial was recorded, within that source’s scope. To conclude that the action was blocked, connect the decision to observations of the route under review and identify access paths or effects outside the coverage.
Does a decision-service outage cancel actions already sent?
It does not establish cancellation. Check the suspension of new attempts separately from the outcome of each attempt already sent. An acknowledgement without sufficient confirmation leaves the effect uncertain.
Does this plan demonstrate that DUBSAR is secure?
No. It is a method to adapt to the client’s scope. Only tests actually performed and their evidence can support a conclusion limited to the observed conditions; this guide is not a product security assessment.
DUBSAR for CISO
Where DUBSAR fits and its development status
DUBSAR is developing a foundation to connect durable mission state, authorisations, human decisions and execution evidence alongside existing tools. The aim is to make decisions and their outcomes open to review; it does not establish that a control applies to every possible access path.
Components and selected workflows have been tested. Full B2B integration and validation are still underway. Pilots are not currently open.