Security and trust
Connecting real infrastructure to a remote platform requires a clear answer to three questions: who can reach my assets, what can they do once connected, and what evidence exists afterward. This page summarizes how WingGate answers them today; each answer links to the full article in the documentation.
These controls are implemented in the current release and covered by the shipped source and tests. See what changed in each release
The controls behind the answers
Connection model
Target machines never need an inbound listener or a public IP — the wing-connector dials out over mutual TLS and stays inside your trust boundary.
Read the article →Identity and access
Access is granted, never implied: password plus TOTP or passkey MFA sign-in, credentials isolated by class, and a fixed Organization / Project / Grant chain that no grant can widen.
Read the article →Credential protection
Asset secrets are write-only through the API, encrypted at rest with AES-256-GCM, and never appear in lists, logs, audits, or errors.
Read the article →Audit and evidence
An append-only, organization-scoped audit trail records who did what and when — and contractually excludes every secret from its entries.
Read the article →Deployment requirements
These guarantees depend on how you run the components; they are your responsibility to provide.
- WingGate terminates TLS for the web console and API, and expects HTTPS in front of it. Run it behind a reverse proxy or load balancer that provides valid certificates.
- The SSH endpoint and the connector mTLS endpoint require their own reachable addresses and certificates; plan DNS and firewall rules accordingly.
- connectors authenticate to WingGate with credentials issued at deployment or binding time; protect and rotate them like any machine credential.
- Keep WingGate's backing store and its backups inside your trust boundary — it holds asset metadata, grants, and audit history.
- The current reference deployment is a baremetal or systemd setup you operate yourself. Patch cadence, certificate renewal, and host hardening are operational responsibilities, not provided by the software.