BLACKOPS SOFTWARE
BLACKOPS / TOOL

Trust boundary worksheet

Connect an actor, a protected asset and a trust decision to an abuse scenario, a control and a verification owner.

Purpose, output & limits Boundary model + verification register
USE WHEN

When reviewing an architecture or authority change.

TAKE AWAY

Boundary model + verification register

DOES NOT

No automatically inferred threats or verified controls.

Processed in this page’s memory. No tool-input uploads, target requests or persistent input storage. Clear or reload to discard this draft. Downloads are saved only when you request them. Keep secrets and confidential records out.

01 / BUILD THE REVIEW
Review the draft ↓

A scenario before a claim.

Describe the system, then record specific scenarios. Connect each one to a control, a bounded verification step and an accountable owner.

01System & authority

Describe roles and data categories, not secrets or customer records.

02Flows & boundaries

State where authority changes and which controls still require evidence.

03Verification register

These are your scenarios, not generated findings. Record enough detail for another engineer to repeat the check safely.

No scenarios yet. Add the first boundary you need to verify.

Up to 12 scenarios per worksheet. This tool does not check or certify any disposition.

Understand the result.

All technical guides
AI security 10 min read

Retrieved text should not acquire authority.

Design AI-enabled workflows so documents, tool output and other untrusted content cannot decide their own access or actions.

Read article
System resilience 10 min read

Designing for system resilience

Key principles for building systems that withstand real-world pressure.

Read article
Defensive infrastructure 10 min read

The role of infrastructure in defence

Why infrastructure decisions determine your security posture.

Read article