Firevault, offline secure storage, physically disconnected from the internet
Pricing

Control BlueprintCP-06

Prove Compliance Through Control

A policy says what should happen. Your evidence should show who approved access, what was allowed and what the control actually did.

Blueprint
CP-06
Primary modules
  • Validate
  • Lock
  • Archive
Supporting
  • Transfer
  • Relay
  • Execute
  • Firebreak
Where it fits
Audit-grade governance of access and evidence
CP-06 Prove Compliance Through Control, as drawnIllustration
Zone 0Operators and analystsNamed individuals raising requests and acting on them
Boundary 1
  • Validate
  • Lock
  • Relay
Window only
Reach is named, time-bound and validated against an authorised request.
Zone 1Controlled dataRecords, evidence and sensitive datasets
Boundary 2
  • Transfer
  • Execute
  • Firebreak
Scoped
Movement out is governed; the boundary is physical, not just policy.
Zone 2Evidence and auditWhere signed attestations are gathered for review
Held offlineSealed evidence vaultAttestations, audit trails and protected records sealed offline for the retention period.Offline

Out-of-band command pathManagement Ethernet, cellular SMS or an authenticated API, off the production network.

The sequenceStep through how the modules work together, as the Blueprint sets them out.

The pattern

Connect permission, action and retained evidence.

What it does

CP-06 makes access governance demonstrable. Validate checks the request, Lock applies identity and policy, and Archive preserves the records of the resulting action. The aim is an evidence trail tied to a defined control, not a general claim that the estate is compliant.

Where it fits

For regulated access and evidence handling in financial services, healthcare, public services and critical infrastructure. Use it where an auditor, investigator or customer needs to review a specific engagement and the authority behind it.

Zone by zone

How CP-06 proves compliance through control.

Follow the evidence chain from an operator’s request through controlled access to the records available for later review.

  1. Zone 0

    Operators and analysts

    Operators and analysts request access under a named role, with a business purpose that can be reviewed.

  2. Boundary 1

    Window only

    Validate the request and authority before admitting the operator to controlled information.

    • ValidateIntegrity check. Primary in CP-06
    • LockNamed access. Primary in CP-06
    • RelayTime-bound path. Supporting in CP-06
  3. Zone 1

    Controlled data

    This is the data covered by the approved engagement. Access should reflect its sensitivity and the permitted task.

  4. Boundary 2

    Scoped

    Govern exports and preserved artefacts so the evidence boundary is not an unrecorded route out of the controlled environment.

    • TransferControlled move. Supporting in CP-06
    • ExecuteTrigger, act, terminate. Supporting in CP-06
    • FirebreakPhysical sever. Supporting in CP-06
  5. Zone 2

    Evidence and audit

    Reviewers need the approval, action and exchange records together, with access appropriate to their role.

  6. Offline

    Sealed evidence vault

    Keep selected evidence separately offline, with retention and access governed by the organisation’s evidence policy.

    Offline Secure Storage®

Bill of modules

Validate, Lock and Archive lead. Transfer, Relay, Execute and Firebreak support.

The primary modules establish authority and preserve the record. Supporting modules govern the exchange and the path used for the approved action.

Module Layer In CP-06 Where it sits What it does here
Validate Protect the asset Primary Boundary 1 Checks that the access request has the authority and conditions required by the organisation’s policy.
Lock Protect the asset Primary Boundary 1 Applies the approved identity and role to the controlled information.
Archive Protect the asset Primary Across the Blueprint Preserves the approval and control records selected for audit or later investigation.
Transfer Protect the asset Supporting Boundary 2 Governs the evidence or data artefacts permitted to move between review environments.
Relay Control the path Supporting Boundary 1 Limits the review or access engagement to its authorised window.
Execute Control the path Supporting Boundary 2 Carries out the approved action that the evidence record must account for.
Firebreak Control the path Supporting Boundary 2 Provides a physical disconnect where the audited control requires the selected path to close.

If the assurance requirement includes a physical disconnect, Firebreak® is supplied by Firevault within Control. Describe the control tested, not an unsupported claim of compliance.Explore Firebreak®

All nine modules

Versus the alternatives

Audit the action, not just the intention.

Existing monitoring and manual records remain useful. The question is whether the authority, boundary action and retained evidence can be reviewed together.

Question Detect and respond Manual shutdown CP-06
Access authority Identity logs show activity under configured policy An operator keeps a separate approval record Validate ties the request to its approving authority
Role restriction Software permissions govern the account Cable state does not define a role Lock applies the permitted identity and policy
Evidence retention Depends on logging and retention arrangements Notes and timestamps need a collection process Archive preserves the designated control records
Data export Requires tooling to govern the artefacts Physical reconnection alone does not govern exports Transfer controls the approved material crossing
Physical-state evidence Monitoring is not itself a physical boundary Staff can record a cable intervention Firebreak can enforce the specified physical control
Compliance conclusion Logs require interpretation against obligations A manual record is only part of the assessment The evidence supports review; it does not confer certification

Questions

Questions from assurance and audit teams.

It provides a pattern for demonstrating governed access and retaining the records of the control action. What an organisation can prove depends on the implementation, evidence collected and review performed.

No. Compliance is assessed against the organisation’s obligations and wider controls. CP-06 supports evidence of particular access and enforcement decisions, not a blanket certification.

The request, approving authority, permitted scope, relevant control action and any governed exchange. Set retention and access requirements with the people responsible for assurance and information governance.

An alert indicates an observed condition. The evidence trail should also show the authorised response and what the control did, so a reviewer can relate the decision to the action.

Yes. Lock governs the reviewer’s identity and role, and Relay can limit the review engagement. Evidence should not become a new standing access route to the production estate.

Some requirements concern whether a particular connection was actually unavailable. Firebreak provides that enforcement where specified; the evidence must identify the boundary and the control being assessed.

All questions

Disconnect to Protect®

Make the next control review answerable.

Bring the access decision or assurance question you need to evidence. We will discuss the authority, action and records around it.