> For the complete documentation index, see [llms.txt](https://msdocs.aohwv.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://msdocs.aohwv.com/get-expert-help/redlegg-managed-soc.md).

# RedLegg Managed SOC

RedLegg operates a **24x7x365 Security Operations Center**. Once your Microsoft logs are flowing, our analysts watch them around the clock and act when something's wrong.

### What we do

1. **Monitor continuously.** Detection rules run day and night against your Microsoft and other data.
2. **Triage alerts.** Analysts review each alert, rule out false positives and set severity.
3. **Investigate.** For real threats, we trace what happened across identity, email, files, devices and cloud.
4. **Escalate and respond.** You're notified *\[within X minutes for critical alerts]* with clear findings and next steps.
5. **Tune.** We keep adjusting detections to reduce noise and keep up with new attacks.
6. **Report.** *\[Reporting cadence: monthly reports, quarterly reviews, etc.]*

### Your part

* **Connect every source** in the Quick Start.
* **Keep licenses current.** Downgrades can quietly remove data we rely on.
* **Tell us about changes**, such as new tenants, subscriptions or acquisitions.
* **Keep escalation contacts current** so we can reach you at any hour.

## Related

* [Quick Start](/quick-start/getting-started.md) — Send your Microsoft logs to the SOC
* [Get Expert Help](/get-expert-help/overview.md) — All services


---

# 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://msdocs.aohwv.com/get-expert-help/redlegg-managed-soc.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.