> 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.md). # Onboarding A comprehensive SIEM/SOC onboarding directly translates to tangible business benefits by mitigating cyber risk. Ensuring broad data source coverage, from endpoints to cloud platforms, eliminates visibility gaps where threats can hide, directly reducing the likelihood of a successful breach. This proactive visibility enables faster threat detection and response, minimising potential operational downtime, financial loss and reputational damage. The initial Discovery Meeting aligns stakeholders on service scope, priorities and technical requirements. The Technical Onboarding phase follows, deploying agents and configuring all necessary log sources and integrations. This ensures validated data ingestion and functional alert pipelines. Subsequently, the Operational Onboarding stage commences with the SOC assuming 24/7 monitoring responsibilities. It includes joint simulation exercises to validate incident response workflows. Customers are then introduced to dashboards, scorecards and regular governance reviews. The phase involves tuning detection rules and transitioning to steady-state operations backed by SLAs. By the end of the process, customers are fully operational with secure telemetry and clear escalation paths. This establishes a firm foundation for ongoing improvements to the security posture. --- # 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.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.