EMS Gateway Compliance Dossier

Status: DRAFT / WORKING DOCUMENTATION

This repository contains the cybersecurity and product-compliance evidence for the EMS Gateway. It is intended to be maintained together with the product source code and release process.

Current product baseline

Important distinction

Backend registration by e-mail + Raspberry Pi serial number is device inventory / ownership binding, not a cryptographic device identity on its own. The security identity should be based on unique device credentials (for example NATS NKey/JWT and VPN keys/certificates), while the serial number is used as an inventory attribute.

Evidence model

Every security requirement should have four things:

  1. Requirement
  2. Implementation
  3. Verification/test
  4. Evidence

A control is not considered complete only because it is described in documentation.

Status vocabulary

First milestone

Complete these documents first:

Release evidence

Create one evidence directory per released firmware/image version:

evidence/
└── 0.1.0/
    ├── manifest.json
    ├── sbom.cdx.json
    ├── vulnerabilities.json
    ├── packages.txt
    ├── sha256sums.txt
    ├── network-surface.txt
    └── test-report.md

Do not put secrets, NATS seeds, VPN private keys or customer data in this repository.

← Wszystkie dokumenty