> For the complete documentation index, see [llms.txt](https://docs.cybaops.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.cybaops.com/modules/detect-and-respond-mdr/self-hosted-soc/phase-3-conclusion-and-validation.md).

# Phase 3: Conclusion and Validation

Before moving to resolution, you must be able to clearly articulate the outcome. Phase 3 is the checkpoint that ensures the investigation is complete.

#### <mark style="color:$primary;">You Must Be Able To Answer:</mark>

| Question                       | Expected Answer                                                     |
| ------------------------------ | ------------------------------------------------------------------- |
| What happened?                 | A clear, factual account of the incident                            |
| How it happened?               | The attack path, root cause, or mechanism                           |
| What actions are required?     | Immediate response actions: containment, remediation, notifications |
| What preventative steps apply? | Recommendations to prevent recurrence                               |

#### <mark style="color:$primary;">Customer Interaction During Conclusion</mark>

If you need input from a stakeholder before you can conclude, add a Comment. The platform transitions the case to Pending. When the customer responds, the case returns to Processing automatically.

{% hint style="info" %}

#### Status Clarification

Pending means waiting for an external party, not that the investigation is paused. Continue documenting any internal activity while waiting.
{% endhint %}


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.cybaops.com/modules/detect-and-respond-mdr/self-hosted-soc/phase-3-conclusion-and-validation.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.