Resources / Security

Security Architecture for the operating team.

Air-gap native. No telemetry. No vendor data access. Built for classified environments.

Full technical documentation is provided to customers and evaluation partners under NDA. This page describes scope and structure. Request access through your account team.

Security Architecture

Air-gap native

Every product runs entirely on your infrastructure. No outbound telemetry, no cloud dependency, no vendor data access.

Least exposure

ENSUC operates with the minimum access required to schedule. It does not read workload contents.

Auditable by design

Every scheduling decision and administrative action is recorded in an immutable log.

Data Handling

ENSUC does not collect, transmit, or store your data outside your environment. It does not require internet access to operate. Workload metadata used for scheduling never leaves your network boundary.

Access & Audit

All access is governed by your existing identity and access management. Administrative actions are logged. The audit log is tamper-evident and exportable to your security tooling.

Deployment Isolation

ENSUC can be deployed in fully air-gapped and classified environments using offline installation procedures. No component requires a connection to any ENSUC-operated service.

Compliance

ENSUC is designed to operate within regulated and classified environments. Security architecture documentation, including data-flow diagrams and control mappings, is available to qualified organizations under NDA.

Documentation

Continue the conversation

Need the full technical context?

Request the security architecture package and documentation under NDA.

Request access