> For the complete documentation index, see [llms.txt](https://docs.realmjoin.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.realmjoin.com/automation/runbooks/runbook-references/org/security/add-defender-indicator.md).

# Add Defender Indicator

Add an allow or block indicator to Defender for Endpoint

### Description

Creates a custom indicator in Microsoft Defender for Endpoint that allows, warns about, audits or blocks a file hash, certificate thumbprint, IP address, domain or URL on all onboarded devices. An alert can be raised whenever the indicator matches.

### Location

Organization → Security → Add Defender Indicator

**Full Runbook name**

rjgit-org\_security\_add-defender-indicator

### Details

| Property         | Value                               |
| ---------------- | ----------------------------------- |
| Version          | 1.0.2                               |
| Required modules | RealmJoin.RunbookHelper (>= 0.8.10) |
| Schedulable      | no                                  |

### Permissions

#### Application permissions

* **Type**: WindowsDefenderATP
  * Ti.ReadWrite.All
    * *Creates the threat indicator (hash, IP, domain or URL) via POST /indicators in Defender for Endpoint*

### Parameters

#### IndicatorValue

The hash, thumbprint, IP address, domain name or URL the indicator applies to. Must match the indicator type.

| Property            | Value           |
| ------------------- | --------------- |
| Required            | true            |
| Default Value       |                 |
| Type                | String          |
| Portal display name | Indicator value |

#### IndicatorType

File hash (SHA-256, SHA-1 or MD5), certificate thumbprint, IP address, domain name or URL. The value must be of this type.

| Property            | Value          |
| ------------------- | -------------- |
| Required            | true           |
| Default Value       | FileSha256     |
| Type                | String         |
| Portal display name | Indicator type |

**Portal options**

| Portal option          | Value                 |
| ---------------------- | --------------------- |
| File hash (SHA-256)    | FileSha256            |
| File hash (SHA-1)      | FileSha1              |
| File hash (MD5)        | FileMd5               |
| Certificate thumbprint | CertificateThumbprint |
| IP address             | IpAddress             |
| Domain name            | DomainName            |
| URL                    | Url                   |

#### Title

Short name shown for the indicator in the Defender portal.

| Property            | Value  |
| ------------------- | ------ |
| Required            | true   |
| Default Value       |        |
| Type                | String |
| Portal display name | Title  |

#### Description

Why the indicator exists. Shown in the Defender portal and in alerts.

| Property            | Value       |
| ------------------- | ----------- |
| Required            | true        |
| Default Value       |             |
| Type                | String      |
| Portal display name | Description |

#### Action

What Defender does on a match: Allow, Warn, Audit, Block, Block and remediate, or Alert and block.

| Property            | Value   |
| ------------------- | ------- |
| Required            | true    |
| Default Value       | Allowed |
| Type                | String  |
| Portal display name | Action  |

**Portal options**

| Portal option       | Value             |
| ------------------- | ----------------- |
| Alert               | Alert             |
| Warn                | Warn              |
| Block               | Block             |
| Audit               | Audit             |
| Block and remediate | BlockAndRemediate |
| Alert and block     | AlertAndBlock     |
| Allow               | Allowed           |

#### Severity

Severity of the alerts raised for this indicator.

| Property            | Value         |
| ------------------- | ------------- |
| Required            | true          |
| Default Value       | Informational |
| Type                | String        |
| Portal display name | Severity      |

**Portal options**

| Portal option | Value         |
| ------------- | ------------- |
| Informational | Informational |
| Low           | Low           |
| Medium        | Medium        |
| High          | High          |

#### GenerateAlert

Raises an alert in the Defender portal each time the indicator matches.

| Property            | Value                    |
| ------------------- | ------------------------ |
| Required            | false                    |
| Default Value       | False                    |
| Type                | Boolean                  |
| Portal display name | Raise an alert on match? |

[Back to Runbook Reference overview](/automation/runbooks/runbook-references.md)


---

# 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.realmjoin.com/automation/runbooks/runbook-references/org/security/add-defender-indicator.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.
