Managed
Endura operates a dedicated Team Server instance and PostgreSQL database for your organization. You manage users, integrations, Sensors, and policies without operating the underlying service.
Service Summary
| Included | Customer-managed equivalent |
|---|---|
| Dedicated Team Server instance | Container and host operations |
| Managed PostgreSQL | Database administration |
| Updates and security maintenance | Image and platform updates |
| Monitoring, backup, and recovery | Operational tooling and runbooks |
| Capacity management | Resource planning and scaling |
Configuration changes that self-hosted customers make directly are coordinated through Endura support.
Regions
Choose a region during onboarding. The selected region determines primary data residency and Sensor latency.
| Area | Regions |
|---|---|
| United States | New York, San Francisco, Atlanta |
| Europe | Amsterdam, London, Frankfurt |
| Asia Pacific | Singapore, Bangalore, Sydney |
| Canada | Toronto |
Each customer receives an isolated instance with a managed database and automatic capacity adjustment.
Onboarding
Provide Endura with:
- the preferred deployment region;
- tenant name and primary administrative contact;
- OIDC provider, client ID, client secret, and issuer URL; and
- the email domains allowed to authenticate.
The onboarding sequence is:
- Confirm service terms and region.
- Provide OIDC and domain configuration.
- Endura provisions the instance, typically within one to two business days.
- Receive the Team Server URL and validate the first login.
- Confirm the initial Administrator account.
Security and Data Residency
| Control | Managed-service behavior |
|---|---|
| Transport encryption | TLS 1.3 |
| Database encryption | AES-256 at rest |
| Isolation | Dedicated customer environment and network isolation |
| Administrative access | MFA, least privilege, access reviews, and audit logging |
| Data residency | Primary data and backups remain in the selected region |
| Edge protection | Web application firewall, DDoS protection, and traffic filtering |
MFA for Team Server users is enforced by your OIDC provider.
Shared Responsibility
| Endura | Your organization |
|---|---|
| Infrastructure and network security | Runtime Sensor deployment |
| Team Server and operating-system updates | Policy creation and assignment |
| Database maintenance, backup, and recovery | OIDC application maintenance |
| Capacity, monitoring, and incident response | User roles and access scope |
| Service availability | Violation investigation and response |
See Access Control for user roles and scope.
Updates
Endura applies application and infrastructure updates during managed maintenance windows. Patch and minor releases use rolling updates. Customers receive advance notice before major releases.
Team Server and Sensors must share a major version. Coordinate Sensor upgrades for a managed major-version change; see Runtime Sensor Compatibility.
Backup and Recovery
| Item | Commitment |
|---|---|
| Database backup | Every 6 hours |
| Backup retention | 90 days |
| Recovery time objective | 4 hours |
| Recovery point objective | 6 hours |
| Availability design | Multiple availability zones with monitored failover |
Endura tests disaster-recovery procedures and backs up configuration before changes.
Data Retention
| Data | Retention |
|---|---|
| Sensor telemetry | 2 years |
| User activity logs | 1 year |
| Audit logs | 7 years |
| Configuration changes | 5 years |
| Policies | Life of the service |
Backup retention is:
| Backup | Retention |
|---|---|
| Daily | 90 days |
| Monthly | 1 year |
| Annual | 7 years |
| Configuration snapshots | 2 years |
Export and Deletion
- Request an export of telemetry, policies, configuration, and audit data at any time. Exports use JSON and CSV and are delivered within five business days.
- Service termination requires 30 days’ notice. Data remains exportable during that period and is deleted within 90 days after termination.
- Specific erasure requests are processed within 30 days where applicable.
- A certificate of destruction is available on request.
Managed service operations support GDPR and CCPA obligations, regional data sovereignty, and data-processing agreements on request.
Monitoring and Support
Endura monitors service health, application and database performance, capacity, and network security. Planned maintenance and incidents are communicated by email and through the service status page.
Support is available at support@endurasecurity.com, Monday through Friday from 9 AM to 5 PM in the customer’s region. Responses are best effort within 24 hours; critical service and security incidents receive priority escalation.
Configuration requests such as OIDC or domain changes are handled through support and backed up before application.
Next Steps
After onboarding: