Why CertiField · Disconnected environments
Cloud-connected, locally-hosted, or no model at all.
For a lot of the systems that need this most, sending anything to an external inference service is not a policy discussion — it is simply not going to happen. That is a deployment mode, not an exception.
- Hosted providers
- Local OpenAI-compatible
- Fully disabled
- Offline STIG bundles
- Ref
- W-41
- Kind
- Modes
- Master switch
- one flag, everything subordinate
Three ways to run it.
Hosted
A supported hosted provider, for environments where that is appropriate. Retries are bounded, token use is capped, and every call logs its tokens and latency so the spend is visible rather than discovered later.
Local
An OpenAI-compatible model on your own hardware — Ollama or LM Studio, for instance. No prompt and no credential leaves the host. This configuration is documented and verified end to end, not offered in principle.
Disabled
Off entirely. Not degraded, not silently retrying a provider that is not there — off, with every feature that depended on it reporting honestly that AI is disabled rather than that something failed.
The distinction in that last one matters more than it sounds. A tool that keeps trying to reach an absent provider fills the log with what looks like a model fault and is actually a deployment choice, and somebody spends a day debugging a configuration that was correct all along.
- Ref
- W-42
- Kind
- Offline
- Bundle carries
- catalog + relevance profiles
An enclave should not have to choose between isolation and useful data.
DISA STIG catalog updates move into a disconnected environment as an exported bundle rather than as a call out to Cyber.mil. Those bundles carry the AI-derived relevance profiles with them, so an enclave running with AI switched off still gets applicability ranking of the same quality as a connected deployment.
That is the difference between supporting air-gapped operation and merely surviving it. The isolated deployment is not the degraded one.
- Ref
- W-43
- Kind
- Posture
- Standards
- DISA STIG · OWASP · NIST SSDF
Built to the standards the environment is held to.
CertiField is developed against DISA STIG, OWASP secure coding practice, the SANS Top 25 and the NIST Secure Software Development Framework — because a tool that holds authorization data for a high-impact system is itself part of that system's attack surface.
Authentication is default-on rather than opt-in, with a short, individually justified list of endpoints that are not, each naming what authenticates it instead. Authorization is a policy table rather than six hundred scattered checks, and a new endpoint with no entry in it fails the build.
- TOTP two-factor with recovery codes; no SMS path
- Session revocation that fails closed on locked or deleted accounts
- Fail-closed malware scanning on every upload surface
- Hash-chained audit verified nightly
- Errors sanitized so internals never reach a response
Next step