TAPPaaS

Security design

A high security standard is essential for TAPPaaS to compete with cloud providers. TAPPaaS addresses security across seven areas:

Secrets and password management

A trusted, self-hostable password manager is essential; the choice is Bitwarden/VaultWarden — a Rust reimplementation of the Bitwarden server, audited, and the only true open-source self-hostable option. The same vault also holds integration secrets, which simplifies setup.

The server runs behind the TAPPaaS reverse proxy, so it is reachable everywhere; secrets are stored encrypted, so even a server compromise does not expose the passwords.

VaultWarden complements the Authentik SSO provided by the identity foundation module — together they form the complete TAPPaaS identity and credential strategy:

Root and management access to VMs

Public administrative access with no public IP is delivered by the satellite admin-vpn role — see satellite.

Network segmentation

TAPPaaS segments the network into security zones so that a breach of one service or VM does not immediately reach the others. The zone model — trust tiers, the isolation invariant, and the VLAN bands — is the network module's design, with the operational definitions the single source of truth in Network Zones. VLAN tags map to zones by band — Service 2xx, IoT 4xx, DMZ 6xx (management is untagged):

TAPPaaS network switching

Inbound internet access security

External access is controlled by three components:

Supply chain security

Monitoring

Observability is delivered by the Health lens — the logging foundation module (Loki / Grafana / Promtail) with the health-manager aggregating module and VM health.

Resiliency in case of breach

Two design principles: