NERVE is live across local, private and approved-cloud deployments. Book an evaluation
Audience
Teams evaluating NERVE where outbound network access is restricted or prohibited.
Source families
Files and archives, Documents and office content, Device and forensic packages
The workflow
01
Input
Signed local components, approved material to import, and a locally deployed CORTEX instance to query from.
02
Acquisition and preservation
Material is imported from local media. Originals are retained locally, hashed locally, and never leave the boundary.
03
Transformation
Local services decode, parse, normalise and index. The same canonical families and the same envelope apply as in a connected deployment.
04
Discovery and retrieval
Queries run from the locally deployed CORTEX through the same service contracts, so the behaviour you evaluate locally is the behaviour you get elsewhere.
05
Governance
Offline mode blocks external connector and provider operations before transport is attempted, rather than relying on a failed connection to enforce the rule.
When it goes wrong
Failure variant
A connector configured for an external provider is invoked. The operation is blocked at the policy boundary and reported, with no outbound attempt made.
What this does not claim
Offline mode is a product control. It is not by itself an air gap: network isolation is a property of your environment and must be established and verified independently.
Evaluation measures
Local operation across the full chain
Restart behaviour with no external dependency
Fresh restore from local backup
Independently established network isolation
Source-to-search time on local hardware