How It Works
With Smallstep, your PKI can become a unified foundation for encryption and authentication for all your devices, people and workloads: from web apps and databases to Kubernetes clusters to GitHub Actions, SSH, VPN and Wi-Fi.
We don’t do this by trying to become your identity provider, user or asset database, MDM provider, or network gateway. Instead, we leverage roots of trust that are already around you, integrate with your existing resources, and provide a platform for managing encryption everywhere in your network.
All devices registering with your Smallstep team are first added to your device trust zone (or device PKI). To register, devices can leverage existing roots of trust: a Trusted Platform Module (TPM) in Linux, an Instance Identity document or attestation token from any cloud provider, or an attestation certificate.
We rely on hardware roots of trust wherever possible, so that only your devices can register with Smallstep. The Smallstep API and IaC integrations make it easy to sync your device inventory to Smallstep. The device trust zone is a privileged trust zone. It offers an authentication factor, and it becomes a foundation for creating other trust zones.
The people and workload trust zones are dedicated to infrastructure access. Smallstep can issue certificates to people and applications by leveraging a device certificate (from the device trust zone), a Single Sign-on (SSO) token, or another authentication method. Keep managing your own directory, and Smallstep will ensure all the right attributes end up on your account certificates for the applications you need to access.
Smallstep monitors all the certificates it issues, seamlessly renewing them as needed and updating the affected services.
Smallstep builds on a foundation of trust zones for devices, workloads, and people to issue client certificates for specific applications. Account certificates are short-lived, are issued on-demand, are instantly revocable, and can combine device and user identities.
The Smallstep agent is a binary package that runs locally as a background service on devices with workloads to be managed. The agent is the backbone of the entire process and provides services such as:
- Automated certificate renewal and management for devices and workloads. The agent renews the certificate every 24 hours and will reload the service to activate the new certificate.
- Telemetry monitoring to aid troubleshooting. The agent relays essential information about its host machine, including architecture, OS, and agent version, enabling visibility on the Smallstep UI. It also relays information about certificate permissions and configuration correctness, validating certificate validity and proper workload setup. Users can easily spot and address configuration issues, such as certificate storage errors, incorrect permissions, server key access problems, or agent interruptions due to device settings.
- Remote configuration: The agent actively monitors configuration changes made either through the UI or API and promptly synchronizes them with the managed devices and workloads. For instance, when a new workload is added to a device, the agent on that device immediately fetches the updated configuration and initiates certificate issuance for the new workload. Similarly, if any changes are made to the workload, such as altering the key type, the agent will reissue certificates to align with the modified settings.
This demo shows the process of registering a Linux device into the device trust zone, and deploying TLS server authentication for a Redis server.
For walk through guides for other workloads, see Getting Started.
- Linux devices or cloud VMs running any of the following:
- Enterprise Linux (RHEL, CentOS Stream, Rocky Linux, Alma Linux, etc)
- Ubuntu (Current Stable and LTS releases)
- Debian (Current Releases)
- Fedora (Current Releases)
- Apple devices running iOS 16 or newer (with Jamf, Intune, or ACME device attestation)
- macOS Sonoma (with Intune, Jamf, or ACME device attestation)
- macOS Ventura, with any MDM that supports SCEP
- Windows devices, with any MDM that supports SCEP (eg. Intune, Workspace One)
- Enterprise WPA2/WPA3 Wi-Fi (eg. EAP-TLS, EAP-TTLS)
- Apache httpd
- Apache Tomcat
- SSH hosts
- GitHub Actions
- Any custom app that uses TLS
Don’t see your workload type listed? Ask us.