> For the complete documentation index, see [llms.txt](https://docs.taloflow.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.taloflow.ai/security/security-operations.md).

# Security Operations

Operational security practices for detection, response, and recovery.

### Scope

Security operations covers the day-to-day practices that keep the platform safe and available.

This page is the umbrella for:

* [Malware Protection](/security/security-operations/malware-protection.md)
* [Incident Response](/security/security-operations/incident-response.md)
* [Disaster Recovery](/security/security-operations/disaster-recovery.md)
* [Availability & Continuity](/security/security-operations/availability-and-continuity.md)
* [Physical Security](/security/security-operations/physical-security.md)

### Key areas

#### Monitoring and auditability

Taloflow logs authentication and API activity for traceability. Retention and backup schedules are documented in [Logs, Audit Logs, and Backups](/security/platform-controls/logs-audit-logs-and-backups.md).

#### Malware and supply-chain controls

We use layered controls across repositories, developer environments, and CI/CD. Details are in [Malware Protection](/security/security-operations/malware-protection.md).

#### Incident response

We follow a defined incident response process for detection, containment, recovery, and communication. See [Incident Response](/security/security-operations/incident-response.md).

#### Disaster recovery and business continuity

We maintain backup and restore procedures and test recovery paths. See [Disaster Recovery](/security/security-operations/disaster-recovery.md) and [Availability & Continuity](/security/security-operations/availability-and-continuity.md).

#### Physical security

Physical security is handled by our infrastructure providers and their data center partners. See [Physical Security](/security/security-operations/physical-security.md).

### Security contact

Send security questionnaires and document requests through the [Support Hub](broken://spaces/-MQkUmzRViVxDERN9vKk/pages/7w2btLpaU63hhnW4Dd7q).


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.taloflow.ai/security/security-operations.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.