Read approved engineering data
Ask an approved client to read an approved engineering resource through a governed connection. Confirm the requesting identity, client, connection, resource policy, decision, and result are attributable.
Start with the decision you need to prove.
Use practical evaluation scenarios to assess Durin’s gateway coverage, identity attribution, policy decisions, approvals, and evidence.
Test the boundary before you make a claim.
Use these representative evaluation scenarios to test whether the access boundary fits your organization. Check each workflow against your requirements and the evidence needed for production rollout.
Try this sample scenario
Write only with review
Attempt a ticket or issue write that requires independent approval. Change the arguments, policy, schema, requesting identity, or expiry and confirm the original grant no longer authorizes the request.
Revoke and investigate
Revoke a member or connection authority, retry a governed request, inspect the denial, and export the authorized evidence. Activate provider access after its governed path is verified.
Representative evaluation scenarios, not customer stories. Samples show governed request paths and review outcomes.
Test the workflow you need to prove.
Create an account to apply these access scenarios to your team’s workflows and controls.
Create an accountProduction connections use provider setup and trust review.