> ## Documentation Index
> Fetch the complete documentation index at: https://docs.tess.im/llms.txt
> Use this file to discover all available pages before exploring further.

# Operations and Detection

Preventive controls are not enough: we need to **see** what happens, **decide** what is abnormal, and **act**. Operations combine telemetry, security logging, vulnerability management, and review cycles.

## Capabilities

| Capability | What we do | Outcome for you |
| - | - | - |
| Observability | We track errors, latency, and application degradation signals; anomalies generate alerts for the responsible team. | Issues are detected early and handled before they become prolonged incidents. |
| Security logging | Authentication events, privileged actions, and relevant activity are available for investigation and support. | There is a factual basis to analyze unauthorized access or suspicious behavior. |
| Vulnerabilities | Components and surfaces are assessed on a defined cadence; findings are severity-ranked and tracked to remediation. | Known risks are not left open indefinitely — there is prioritization and a remediation timeline. |
| Availability | We monitor capacity and publish System Status when there is relevant operational impact. | You get visibility into outages and official communication during events. |
| Continuous improvement | Access reviews, risk assessments, and response/continuity exercises produce tracked action plans. | The security program evolves based on evidence, not only intent. |

## Related

* [Incident Response](https://docs.tess.im/Incident-Response.md)
* [Secure Development](https://docs.tess.im/SecureDevelopment.md)
* [Identity and Access](https://docs.tess.im/Identity-Access.md)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.