> For the complete documentation index, see [llms.txt](https://docs-conversational-ai.syntphony.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs-conversational-ai.syntphony.com/security-and-compliance/incident-management-and-response.md).

# Incident Management & Response

### Data Breach Notification <a href="#data-breach-notification" id="data-breach-notification"></a>

In the event that a data breach is detected in a virtual agent or eva environment, please contact the support and operations team using the [form](https://umane.everis.com/jiraserver/servicedesk/customer/portal/94/create/1637) below. In case you don't have access to the form, please contact the support team [here](mailto:support.eva@emeal.nttdata.com).

### Incident Response <a href="#incident-response" id="incident-response"></a>

Policies and procedures for operational and incident response management require incidents to be logged and reviewed, with appropriate action (e.g., system changes) taken if necessary.

A formal incident response plan and standard incident reporting form are documented to guide employees in the procedures to report security failures and incidents.

The incident response plan enforces a process of resolving and escalating reported events. Its provisions include consideration of the need to inform internal and external users of incidents and advising of corrective actions to be taken on their part, as well as a “postmortem” review requirement.

Please note the different levels of support we offer. To understand what is expected in each case from the support and operations team, please refer to the following links:

{% embed url="<https://docs.eva.bot/ntt-data-eva-r-cai-documentation/customer-support/support-policy>" %}

{% embed url="<https://docs.eva.bot/ntt-data-eva-r-cai-documentation/customer-support/support-procedures>" %}

{% embed url="<https://docs.eva.bot/ntt-data-eva-r-cai-documentation/customer-support/support-policy/support-levels>" %}


---

# 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-conversational-ai.syntphony.com/security-and-compliance/incident-management-and-response.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.
