> For the complete documentation index, see [llms.txt](https://docs.threatdefence.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.threatdefence.com/getting-started/guided-onboarding/security-operations.md). # Security Operations Once technical onboarding is complete and data sources are integrated, the next step is operational onboarding. This stage ensures that ThreatDefence and your internal teams are aligned on workflows, escalation paths, SLAs, and responsibilities. The goal is to establish a seamless hybrid SOC model from day one. Objectives: * Align detection, escalation, and response processes between ThreatDefence and your internal teams. * Validate operational readiness through simulations and testing. * Formalize governance, reporting, and service cadence. *** ## Key Activities ### 1. Security Operations * Confirm notificaiton and escalation emails / contacts. * Review the Security Operations and Incident Management Lifecycle. * Start 24/7 Security Operations. ### 2. SLA and Operations Manual Alignment * Confirm processes documented in the ThreatDefence Operations Manual. * Document escalation contact orders. * Provide training to customer escalation contacts on how to engage with ThreatDefence SOC. * Review containment procedures. ### 4. Governance Setup * Schedule regular reports. * Establish monthly operational reviews to discuss incidents, SLA adherence, and tuning opportunities. *** ## Outcome This phase ensures the SOC service is not just technically connected, but operationally ready. Both ThreatDefence and your internal teams will have clear roles, responsibilities, and communication channels, enabling faster response and improved collaboration during incidents. --- # 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.threatdefence.com/getting-started/guided-onboarding/security-operations.md?ask=&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.