Getting Started
Set up Endura in this order. Each step links to the guide that contains the required commands and configuration.
1. Deploy Team Server
Choose a Team Server deployment. Team Server manages integrations, policies, Sensors, violations, and user access.
2. Install the Runtime Sensor
Install the Runtime Sensor on each host that runs protected workloads or CI/CD jobs. Configure its license, Team Server URL, and Sensor token, then verify that it reports online.
3. Connect a CI/CD Provider
Follow the provider guide for Bamboo, GitHub, GitLab, Jenkins, or TeamCity. Configure discovery, install the Sensor on the build infrastructure, and bracket each build with endura job start and endura job stop.
4. Create a Security Policy
Use the policy lifecycle: derive a baseline, refine it, observe violations, then enable enforcement.
5. Configure Notifications
Configure Slack notifications after violations are reaching Team Server. Scope each integration to the pipelines and deployments its channels own.
Prerequisites
Allow access to these services as required by your deployment:
| Resource | URL | Purpose |
|---|---|---|
| GitHub Container Registry | ghcr.io | Team Server and Sensor images and Helm charts |
| Endura package repository | repo.endurasecurity.com | Sensor packages and installation scripts |
| Docker Hub | docker.io | PostgreSQL images used by example deployments |
Sensors must also reach Team Server over HTTPS to receive policies and submit telemetry.
Next Steps
Start with Team Server deployment options.