Trust / NIST CSF 2.0

Security, aligned to NIST CSF 2.0.

How Level Zero's security program maps to the six NIST Cybersecurity Framework 2.0 functions - Govern, Identify, Protect, Detect, Respond, Recover.

FrameworkNIST Cybersecurity Framework 2.0 (Feb 2024) PostureCSF-aligned control design for a TRL-4 demonstrator EvidenceControl summary available on request

Approach

NIST CSF 2.0 is our anchor framework. The SOC 2 criteria and ISO/IEC 27001 controls we design for map back to the same control library. This page summarizes our control design against each of the six CSF functions; several items are roadmap targets for the demonstrator rather than independently evidenced controls. Supporting documentation is available under NDA via contact@levelzero.fr.

Govern

  • Information security policy reviewed and signed off annually by the executive of the operating company (DOMSELARDI).
  • Risk register maintained quarterly; risks tied to CSF outcomes and to specific controls.
  • Roles & responsibilities documented (RACI) for each subsystem owner.
  • Third-party risk: every subprocessor reviewed against a standard questionnaire before onboarding; annual reassessment is part of the control design.

Identify

  • Asset and dependency inventory tracked in version control; automated drift detection is a roadmap target.
  • Data inventory and data-flow documentation for the four source types (radio downlink, EO/SAR scene metadata, live track state, operator reports).
  • Threat model reviewed quarterly and on every significant architecture change.

Protect

  • Identity: SSO with hardware-bound MFA on every administrative account; least-privilege role-based access on every system.
  • Encryption: TLS in transit; encryption at rest and per-tenant key management are roadmap targets.
  • Network: schema-per-tenant isolation by default on a single self-hosted server; private endpoints and egress allow-listing are roadmap targets.
  • Software supply chain: dependencies pinned via lockfiles and built/tested in CI on every change; SBOM generation and signed build provenance are roadmap targets - see SBOM & SLSA.
  • Backups: a backup and restore policy with documented RPO/RTO is a roadmap target for the demonstrator.

Detect

  • Application audit logging on security-relevant actions; centralized retention-controlled aggregation is a roadmap target.
  • Detection rules and on-call paging are roadmap targets for the demonstrator.
  • Dependency review on update; continuous vulnerability scanning and documented patch windows are roadmap targets.

Respond

  • Incident response plan published internally; severity matrix and external comms templates ready.
  • Tabletop incident-response exercises are a roadmap target.
  • An incident-communications process (status page, email, postmortems) is a roadmap target; there are no customers today.

Recover

  • Recovery runbooks and disaster-recovery rehearsals are roadmap targets.
  • Target RPO/RTO objectives will be defined as part of the resilience roadmap.
  • Post-incident reviews feed back into the risk register and the control roadmap.
[ Ready to integrate ]