> For the complete documentation index, see [llms.txt](https://digitalgarden.batamladen.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://digitalgarden.batamladen.com/notes/certificates/cdsa/module-2-security-monitoring-and-siem-fundamentals/siem-visualization-5-8.md).

# SIEM visualization (5-8)

To create a new visualization we go on the drop menu and select "Dashboard" Click "Create Visualization"

A window opens with 4 important notices.

<figure><img src="https://2490252025-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FUwIKQPujWqWSVFxQaX98%2Fuploads%2FaMWcMZKV2NB1a4IBPNkH%2Fimage.png?alt=media&amp;token=a275a755-a749-4152-86c7-5e306f2bc74a" alt=""><figcaption></figcaption></figure>

1. A filter option that allows us to filter the data before creating a graph. For example:
2. This field indicates the data set (index) that we are going to use. It is common for data from various infrastructure sources to be separated into different indices, such as network, Windows, Linux, etc. In this particular example, we will specify `windows*` in the "Index pattern".
3. This search bar provides us with the ability to double-check the existence of a specific field within our data set, serving as another way to ensure that we are looking at the correct data.
4. Lastly, this drop-down menu enables us to select the type of visualization we want to create.

***

### Fields

**event.code: 4625** - Failed logon attempt on a Windows system.&#x20;

**event.code: 4624** - An account was successfully logged on event.code: 4732: A member was added to a security-enabled local group

**event.code: 4733 -** A member was removed from a security-enabled local group

**event.action.keyword** – Specifies the type of action that occurred in the event, such as "logon" or "file modification

**group.name** - Used to specify a certain group name

**winlog.event\_data.SubStatus: 0xC0000072** - the failure is due to a logon with disabled user.

**winlog.logon.type** - Displays the logon type (RemoteInteractive, Wired, etc...)

**winlog.event\_data.MemberSid.keyword** – Represents the Security Identifier (SID) of the user or group involved in the event

**user.name.keyword** - account name&#x20;

**host.name.keyword** - device name&#x20;

**winlog.logon.type.keyword** - logon type (remote etc...)&#x20;

**related.ip.keyword** - the IP of the computer initiating the succsessful RDP logon attempt


---

# 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://digitalgarden.batamladen.com/notes/certificates/cdsa/module-2-security-monitoring-and-siem-fundamentals/siem-visualization-5-8.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.
