You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/sentinel/entities-reference.md
+8-8Lines changed: 8 additions & 8 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -12,11 +12,11 @@ ms.custom: ignite-fall-2021
12
12
13
13
## Entity types and identifiers
14
14
15
-
The following table shows the **entity types** currently available for mapping in Microsoft Sentinel, and the **attributes** available as **identifiers** for each entity type - which appear in the **Identifiers** drop-down list in the [entity mapping](map-data-fields-to-entities.md) section of the [analytics rule wizard](detect-threats-custom.md).
15
+
The following table shows the **entity types** currently available for mapping in Microsoft Sentinel, and the **attributes** available as **identifiers** for each entity type. These attributes appear in the **Identifiers** drop-down list in the [entity mapping](map-data-fields-to-entities.md) section of the [analytics rule wizard](detect-threats-custom.md).
16
16
17
-
Each one of the identifiers in the **required identifiers** column is minimally necessary to identify its entity. However, a required identifier might not, by itself, be sufficient to provide *unique* identification. The more identifiers used, the greater the likelihood of unique identification. You can use up to three identifiers for a single entity mapping.
17
+
Each one of the identifiers in the **required identifiers** column is necessary to identify its entity. However, a required identifier might not, by itself, be sufficient to provide *unique* identification. The more identifiers used, the greater the likelihood of unique identification. You can use up to three identifiers for a single entity mapping.
18
18
19
-
For best results - for guaranteed unique identification - you should use identifiers from the **strongest identifiers** column whenever possible. The use of multiple strong identifiers enables correlation between strong identifiers from varying data sources and schemas. This in turn allows Microsoft Sentinel to provide more comprehensive insights for a given entity.
19
+
For best results—for guaranteed unique identification—you should use identifiers from the **strongest identifiers** column whenever possible. The use of multiple strong identifiers enables correlation between strong identifiers from varying data sources and schemas. This correlation in turn allows Microsoft Sentinel to provide more comprehensive insights for a given entity.
@@ -43,7 +43,7 @@ For best results - for guaranteed unique identification - you should use identif
43
43
44
44
## Entity type schemas
45
45
46
-
The following is a more in-depth look at the full schemas of each entity type. You'll notice that many of these schemas include links to other entity types - for example, the User account schema includes a link to the Host entity type, as one attribute of a user account is the host it's defined on. These externally linked entities can't be used as identifiers for entity mapping, but they are very useful in giving a complete picture of entities on entity pages and the investigation graph.
46
+
The following section contains a more in-depth look at the full schemas of each entity type. You'll notice that many of these schemas include links to other entity types—for example, the User account schema includes a link to the Host entity type, since one attribute of a user account is the host it's defined on. These externally linked entities can't be used as identifiers for the purpose of entity mapping, but they are very useful in giving a complete picture of entities on entity pages and the investigation graph.
47
47
48
48
> [!NOTE]
49
49
> A question mark following the value in the **Type** column indicates the field is nullable.
@@ -149,8 +149,8 @@ Strong identifiers of an IP entity:
149
149
| Type | String | ‘malware’ |
150
150
| Name | String | The malware name by the vendor, such as `Win32/Toga!rfn`. |
151
151
| Category | String | The malware category by the vendor, e.g. Trojan. |
152
-
| Files | List\<Entity> | List of linked file entities on which the malware was found. Can contain the File entities inline or as reference.<br>See the File entity for additional details on structure. |
153
-
| Processes | List\<Entity> | List of linked process entities on which the malware was found. This would often be used when the alert triggered on fileless activity.<br>See the [Process](#process) entity for additional details on structure. |
152
+
| Files | List\<Entity> | List of linked file entities on which the malware was found. Can contain the File entities inline or as reference.<br>See the [File](#file) entity for more details on structure. |
153
+
| Processes | List\<Entity> | List of linked process entities on which the malware was found. This would often be used when the alert triggered on fileless activity.<br>See the [Process](#process) entity for more details on structure. |
154
154
155
155
Strong identifiers of a malware entity:
156
156
@@ -180,8 +180,8 @@ Strong identifiers of a file entity:
180
180
| CommandLine | String | The command line used to create the process. |
181
181
| ElevationToken | Enum? | The elevation token associated with the process.<br>Possible values:<li>TokenElevationTypeDefault<li>TokenElevationTypeFull<li>TokenElevationTypeLimited |
182
182
| CreationTimeUtc | DateTime? | The time when the process started to run. |
183
-
| ImageFile | Entity (File) | Can contain the File entity inline or as reference.<br>See the File entity for additional details on structure. |
184
-
| Account | Entity | The account running the processes.<br>Can contain the [Account](#user-account) entity inline or as reference.<br>See the [Account](#user-account) entity for additional details on structure. |
183
+
| ImageFile | Entity (File) | Can contain the File entity inline or as reference.<br>See the [File](#file) entity for more details on structure. |
184
+
| Account | Entity | The account running the processes.<br>Can contain the Account entity inline or as reference.<br>See the [Account](#user-account) entity for more details on structure. |
185
185
| ParentProcess | Entity (Process) | The parent process entity. <br>Can contain partial data, i.e. only the PID. |
186
186
| Host | Entity | The host on which the process was running. |
187
187
| LogonSession | Entity (HostLogonSession) | The session in which the process was running. |
0 commit comments