Home /Modules/server-edition/SECURITY-STANDARDS.md

SECURITY-STANDARDS.md

server-edition/SECURITY-STANDARDS.md · 86 line(s) · markdown

SLeeLa Server Edition — Security and Standards Baseline

Document date: 2026-10-26 Scope: server-edition/ Status: Initial hardening baseline with mutual-TLS transport and identity-operation authorization implemented in source; compilation, integration testing, and production review remain outstanding.

Security posture

The server should be treated as a transport/admission component, not as a production-secure application gateway, until authentication, protected transport, authorization, bounded concurrency, deterministic shutdown, and service dispatch are implemented and tested.

Current hardening changes set the default listener to 127.0.0.1:19866, validate CLI port and packet-size values, reject unknown CLI options, and require an explicit --allow-remote flag before the command-line executable will attempt a non-loopback bind. The remote-bind flag alone is insufficient: remote use additionally requires TLS 1.3, mutual client-certificate verification, an allowlisted certificate identity, and explicit service/operation permissions. These source changes have not yet been build- or runtime-verified.

Required engineering controls

Network and identity

Input and resource safety

Lifecycle and concurrency

Logging and privacy

Build and release

Standards and guidance to map against

These are engineering references, not claims of certification or compliance.

Minimum release gate

A release must not be marked production-ready until all are true:

  1. Build and automated tests pass on every advertised platform.
  2. Transport tests cover truncated/oversized frames, partial I/O, timeouts, and invalid numeric fields.
  3. Concurrency tests cover connection floods, active-connection limits, races, and shutdown under load.
  4. Security tests verify authenticated transport, identity validation, per-service authorization, and replay behavior.
  5. End-to-end tests prove that authorized packets reach registered service handlers and unauthorized packets do not.
  6. Documentation matches tested behavior and clearly states any deployment-provided controls.
  7. A reviewer records the commit, test commands, results, known limitations, and release decision.