> For the complete documentation index, see [llms.txt](https://docs.elastiflow.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.elastiflow.com/data_platforms/elastic/ml/netsec/netsec_activity/rare_conversation.md).

# Rare Conversation

Identifying rare network conversations — interactions between network entities that deviate from usual communication patterns — is essential for maintaining robust network security and operational integrity. In the complex landscape of network interactions, rare conversations can be indicative of various anomalies, ranging from misconfigurations and system malfunctions to cybersecurity threats like data breaches, advanced persistent threats (APTs), or insider attacks. These atypical conversations may involve unusual pairs of source and destination addresses, uncommon protocols, or unexpected data flows. Prompt detection of such rare conversations is key in preempting potential issues, allowing network administrators to investigate and address the root causes before they escalate into more significant problems.

ElastiFlow provides a collection of anomaly detection jobs designed to identify rare network conversations encompassing a range of analytics and monitoring strategies focused on discerning and evaluating atypical network interactions.

## Attributes

| Attribute    | Information |
| ------------ | ----------- |
| **Analysis** | temporal    |

## Downloads

| Schema    | Perspective  | Link                                                                                                                                                                                     |
| --------- | ------------ | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **CODEX** | **inbound**  | [elastiflow\_codex\_netsec\_rare\_conversation\_in](https://github.com/elastiflow/elastiflow_for_elasticsearch/raw/master/ml/codex/netsec_activity/netsec_rare_conversation_in.json)     |
| **CODEX** | **outbound** | [elastiflow\_codex\_netsec\_rare\_conversation\_out](https://github.com/elastiflow/elastiflow_for_elasticsearch/raw/master/ml/codex/netsec_activity/netsec_rare_conversation_out.json)   |
| **CODEX** | **private**  | [elastiflow\_codex\_netsec\_rare\_conversation\_priv](https://github.com/elastiflow/elastiflow_for_elasticsearch/raw/master/ml/codex/netsec_activity/netsec_rare_conversation_priv.json) |
| **ECS**   | **inbound**  | [elastiflow\_ecs\_netsec\_rare\_conversation\_in](https://github.com/elastiflow/elastiflow_for_elasticsearch/raw/master/ml/ecs/netsec_activity/netsec_rare_conversation_in.json)         |
| **ECS**   | **outbound** | [elastiflow\_ecs\_netsec\_rare\_conversation\_out](https://github.com/elastiflow/elastiflow_for_elasticsearch/raw/master/ml/ecs/netsec_activity/netsec_rare_conversation_out.json)       |
| **ECS**   | **private**  | [elastiflow\_ecs\_netsec\_rare\_conversation\_priv](https://github.com/elastiflow/elastiflow_for_elasticsearch/raw/master/ml/ecs/netsec_activity/netsec_rare_conversation_priv.json)     |

By implementing this collection of anomaly detection jobs, organizations can effectively monitor their network for rare conversations, gaining the ability to swiftly identify and investigate unusual network activities. This proactive approach to network monitoring is crucial in today's digital environment, where the rapid identification and resolution of anomalies can prevent security breaches, ensure network stability, and maintain optimal operational performance.


---

# 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.elastiflow.com/data_platforms/elastic/ml/netsec/netsec_activity/rare_conversation.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.