Not available today
Restricted-network software testing: scope and prerequisites
Define the runtime, evidence and approval requirements for verification in a restricted network. A fully air-gapped installation is not available today.
Platform and security teams evaluating software verification for restricted networks, on-premises systems or environments without public internet access.
What Zof does
Your environment and policies
In private deployments, evidence storage and any approved egress follow your configured environment and policies. Assess code and review existing test results inside the environment you approve.
A deployment needs its own acceptance test
Zof’s platform positioning is an independent verification and control layer between AI and production. Secure enclave deployment is not available today. Any private deployment must establish where planning, execution, evidence and approvals operate before you rely on it.
From a change to a review decision
- 01
Define the boundary
List permitted connections, application access, identity services, model use and evidence destinations. Distinguish a restricted segment with approved transfers from an environment with no external connection.
- 02
Prepare dependencies
Inventory runtimes, packages, browser binaries where needed, OS libraries and updates. Agree how approved artifacts enter the environment, how integrity is checked and how credentials are provisioned.
- 03
Test the full lifecycle
Validate installation and a representative verification run with external access blocked. Check restart, failure handling, evidence review, export policy and upgrades. Record remaining network dependencies before accepting a design.
What evidence you get
Verification results
Results should carry explicit execution status, so missing and incomplete evidence remain non-passing. Static checks do not establish that application behavior was tested.
Deployment acceptance evidence
Require an approved dependency inventory, network observations, installation records and representative run results. Agree local storage, retention, access and export controls. These are evaluation requirements, not artifacts supplied automatically.
Prerequisites and limits
- Offline execution is different from offline installation. An offline installation needs a separately prepared and tested dependency set.
- Git is required for revision analysis. Browser tests need their own binaries, OS dependencies and a reachable application.
- Executing configured tests runs trusted commands and is not a sandbox. The test command and application can have their own network dependencies.
- A fully air-gapped Zof installation, a transfer gateway and model isolation are not available today.
Technical sources
In practice
Establish feasibility for a restricted environment
A secure enclave requirement needs a precise description of permitted execution and communication. This page is a scoping guide for that discussion. A production-ready isolated deployment is not established merely by naming the requirement; availability must be confirmed with Zof for the proposed engagement.
01
Document permitted connections
Identify the target applications, artifact sources, identity services and any external dependencies the work needs. State which connections are prohibited and how approved software or updates may enter the environment.
02
Define the operating boundary
Specify who administers infrastructure, approves credentials and handles test data. Describe how execution records can be reviewed, how long they must be retained and which information may be exported.
03
Validate a representative workflow
Agree on a limited proof of concept and acceptance criteria. Verify setup, execution and access to results within the proposed restrictions. Record unsupported requirements before making a production commitment.
Illustrative scenario · not a customer result
Testing without unrestricted internet access
A team wants to verify an internal application. Its checks may need packages, browser binaries or an external service. Inventory those dependencies and determine which are already available or can be approved. If a required dependency cannot be provided, the evaluation must expose that limitation.
Questions to resolve before you begin
Is this a ready-to-install isolated product?
Do not assume that. Confirm the deployment capability and support scope directly with Zof. Treat the environment requirements as evaluation inputs until a workable configuration is demonstrated and agreed.
What makes a useful acceptance criterion?
Specify an observable outcome: a named check runs against the permitted target, results can be reviewed by the authorized person and prohibited network paths are not required for that workflow.
Next step
Scope a secure deployment review
Bring your network policy, target application, approved runtimes, artifact-transfer process and evidence-retention requirements. Agree what must be demonstrated inside your boundary.