Getting Started
This documentation guides you through setting up and configuring the Endura Security platform. Whether you’re securing a single application or an entire infrastructure, follow these steps to get up and running.
What You’ll Learn
1. Deploy Team Server
Team Server is the foundation of your Endura Security deployment. It provides centralized management, monitoring, and reporting for all security components. Choose the deployment method that fits your infrastructure—Docker, Podman, Kubernetes, or our managed service.
2. Install Runtime Sensors
Runtime Sensors are lightweight agents deployed alongside your applications. They collect security telemetry and enforce policies in real time. Installation guides are available for all major Linux distributions.
3. Secure Your Pipelines
Integrate security checks directly into your CI/CD workflows. Pipeline Security catches vulnerabilities and policy violations before code reaches production.
4. Configure Security Policies
Security Policies define the rules that govern your environment. Learn how to create, customize, and enforce policies that match your organization’s security requirements.
Prerequisites
This documentation assumes you have network access to the following resources:
| Resource | URL | Purpose |
|---|---|---|
| GitHub Container Registry | ghcr.io | Pulling Endura Security container images (Team Server) and Helm Charts (Runtime Sensor, Team Server) |
| Endura Security Repository | https://repo.endurasecurity.com | RPM and DEB package repositories for Runtime Sensor installation |
| Docker Hub | docker.io | Pulling PostgreSQL container images |
Additionally, network connectivity is required between the hosts where Runtime Sensors are installed and the host where Team Server is running. Runtime Sensors must be able to reach Team Server to report telemetry and receive policy updates.
Next Steps
Ready to begin? Start by deploying Team Server to establish your security foundation.