Skip to main content
Last reviewed: March 5, 2026 Owner: Security + Engineering Review cadence: Quarterly Status: Implemented Tero detects, triages, communicates, and follows through on incidents. This page describes what you can expect at each phase.

Reviewer focus

  • How Tero responds to security-relevant incidents
  • What customers can expect for communication during material incidents
  • How resilience controls support recovery and continuity

Implementation status (March 5, 2026)

Tero monitors security and operational events, including cloud security alerts, and triages them through incident-response workflows.

Incident-response lifecycle

Customer communication baseline

  • Tero notifies affected customers when it confirms a material incident.
  • Communication includes impact scope, current status, and next steps.
  • Tero keeps sending updates until it resolves the customer-impacting risk.

Resilience controls

Hosted vs self-hosted boundary

Evidence you can request

Exceptions and governance

Any incident-handling exception requires explicit risk acceptance and time-bound remediation. Evidence requests: