FV-Lock. Access governed as one coherent layer.
Lock restricts access through identity, authority, policy, permission and operational controls. Each of these matters on its own, but the protection comes from treating them as one coherent layer rather than five disconnected ones.
Control Module - VAULT
Access is a sentence with five clauses. Lock reads all of them before answering.
Identity
Who is asking, established before anything else
Authority
Under whose authority the request is being made
Policy
What the policy of the moment actually allows
Operational
Controls that reflect the state of the environment
Access controls that disagree with each other quietly grant everything.
Fragmented enforcement
When identity, policy and operational controls live in different places and tools, the disagreements between them tend to resolve in favour of access.
Permissions without authority
A user may hold a permission, but without the authority to use it in the current context, the permission alone is not enough to justify the action.
Standing privilege
Privilege that exists permanently is privilege that can be abused permanently, by anyone who reaches the account or the session.
The Scenario
Scenario: a permitted user, the wrong moment
An administrator who holds the necessary permission attempts a sensitive operation outside the approved change window. Identity and permission both check out, but the operational controls do not, because the change window is closed. Lock refuses the operation, returns the rationale and notifies the policy owner. The administrator schedules the work for the next window and the operation proceeds in its proper place.
"Lock is what stops a yes from being the answer to the wrong question."
Where Lock enforces named, scoped access.
Lock turns access from a long-lived right into a named, scoped event. Reach is granted to a person, for a purpose, for a window, and recorded.
Grounded in NIST CSF PR.AC-1 and PR.AC-4, ISO 27001 A.5.15, A.8.2 and IEC 62443-3-3 SR 1.1, SR 2.1.
FV-Lock
Control layer
Privileged operator sessions
Administrative reach into protected zones is granted per session, per person, with explicit scope.
Vendor maintenance accounts
Vendor identities are locked to a named engagement. No shared, evergreen credentials.
Crown-jewel data access
Sensitive datasets are reachable only by named requestors through an approved Lock event.
Emergency break-glass
Emergency access is a Lock event with quorum approval, full audit and a hard expiry.
Relies on · prerequisites
- Reliable identity for the named actor
- Scope that is narrower than the access path can technically allow
- Recorded purpose for each grant, not just the grant
Pairs with · companion modules
Relay
Execute
Unlink
ValidateFeatured In
Key Capabilities
Identity as the first clause
Who is asking is established before any other clause is evaluated.
Authority as the second
The authority under which the request is made is treated as a first-class input.
Policy as the third
The policy of the moment, including its exceptions and constraints, is part of the evaluation.
Permission as the fourth
Permissions are necessary but not sufficient, and are evaluated against the other clauses rather than alone.
Operational state as the fifth
Operational controls reflect the current state of the environment, so an answer that suits one moment is not assumed to suit another.
Evidential record
Outcomes and rationales are recorded through Archive on physically separate storage.
Demo to Live
Adoption Guide
Map the access surface
Identify the access decisions that matter, the identities involved and the policies that apply.
Define the five clauses
For each decision, agree the identity, authority, policy, permission and operational expectations.
Pilot a coherent decision
Move one workflow onto Lock end-to-end, with the rationale returned to the requester.
Operate and review
Extend Lock across further workflows and review patterns through Archive on a regular cadence.
Map the access surface
Identify the access decisions that matter, the identities involved and the policies that apply.
Define the five clauses
For each decision, agree the identity, authority, policy, permission and operational expectations.
Pilot a coherent decision
Move one workflow onto Lock end-to-end, with the rationale returned to the requester.
Operate and review
Extend Lock across further workflows and review patterns through Archive on a regular cadence.
Questions