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/external-attack-surface-management/data-connections.md
+9-9Lines changed: 9 additions & 9 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -27,14 +27,14 @@ The data connector sends Defender EASM asset data to two different platforms: Mi
27
27
28
28
29
29
**Data content options**
30
-
Defender EASM data connections offers users the ability to integrate two different kinds of attack surface data into the tool of their choice. Users can elect to migrate asset data, attack surface insights or both data types. Asset data provides granular details about your entire inventory, whereas attack surface insights provide immediately actionable insights based on Defender EASM dashboards.
30
+
<br>Defender EASM data connections offers users the ability to integrate two different kinds of attack surface data into the tool of their choice. Users can elect to migrate asset data, attack surface insights or both data types. Asset data provides granular details about your entire inventory, whereas attack surface insights provide immediately actionable insights based on Defender EASM dashboards.
31
31
32
32
To accurately present the infrastructure that matters most to your organization, please note that both content options will only include assets in the “Approved Inventory” state.
33
33
34
34
35
35
36
36
**Asset data**
37
-
The Asset Data option will send data about all your inventory assets to the tool of your choice. This option is best for use cases where the granular underlying metadata is key to the operationalization of your Defender EASM integration (e.g. Sentinel, customized reporting in Data Explorer). Users can export high-level context on every asset in inventory as well as granular details specific to the particular asset type. This option does not provide any pre-determined insights about the assets; instead, it offers an expansive amount of data so users can surface the customized insights they care about most.
37
+
<br>The Asset Data option will send data about all your inventory assets to the tool of your choice. This option is best for use cases where the granular underlying metadata is key to the operationalization of your Defender EASM integration (e.g. Sentinel, customized reporting in Data Explorer). Users can export high-level context on every asset in inventory as well as granular details specific to the particular asset type. This option does not provide any pre-determined insights about the assets; instead, it offers an expansive amount of data so users can surface the customized insights they care about most.
38
38
39
39
40
40
**Attack surface insights**
@@ -45,13 +45,13 @@ Attack Surface Insights provide an actionable set of results based on the key in
45
45
46
46
47
47
**Accessing data connections**
48
-
Users can access Data Connections from the **Manage** section of the left-hand navigation pane within their Defender EASM resource blade. This page displays the data connectors for both Log Analytics and Azure Data Explorer, listing any current connections and providing the option to add, edit or remove connections.
48
+
<br>Users can access Data Connections from the **Manage** section of the left-hand navigation pane within their Defender EASM resource blade. This page displays the data connectors for both Log Analytics and Azure Data Explorer, listing any current connections and providing the option to add, edit or remove connections.
49
49
50
50

51
51
52
52
53
53
**Connection prerequisites**
54
-
To successfully create a data connection, users must first ensure that they have completed the required steps to grant Defender EASM permission to the tool of their choice. This process enables the application to ingest our exported data and provides the authentication credentials needed to configure the connection.
54
+
<br>To successfully create a data connection, users must first ensure that they have completed the required steps to grant Defender EASM permission to the tool of their choice. This process enables the application to ingest our exported data and provides the authentication credentials needed to configure the connection.
55
55
56
56
**Configuring Log Analytics permissions via UI**
57
57
@@ -89,7 +89,7 @@ To successfully create a data connection, users must first ensure that they have
89
89
90
90
91
91
**Add a data connection**
92
-
Users can connect their Defender EASM data to either Log Analytics or Azure Data Explorer. To do so, simply select **“Add connection”** for the appropriate tool from the Data Connections page.
92
+
<br>Users can connect their Defender EASM data to either Log Analytics or Azure Data Explorer. To do so, simply select **“Add connection”** for the appropriate tool from the Data Connections page.
93
93
A configuration pane will open on the right-hand side of the Data Connections screen. The following four fields are required:
94
94
95
95
-**Name**: enter a name for this data connection.
@@ -104,7 +104,7 @@ A configuration pane will open on the right-hand side of the Data Connections sc
104
104
Once all four fields are configured, select **Add** to create the data connection. At this point, the Data Connections page will display a banner that indicates the resource has been successfully created and data will begin populating within 30 minutes. Once connections are created, they will be listed under the applicable tool on the main Data Connections page.
105
105
106
106
**Edit or delete a data connection**
107
-
Users can edit or delete a data connection. For example, you may notice that a connection is listed as “Disconnected” and would therefore need to re-enter the configuration details to fix the issue.
107
+
<br>Users can edit or delete a data connection. For example, you may notice that a connection is listed as “Disconnected” and would therefore need to re-enter the configuration details to fix the issue.
108
108
To edit or delete a data connection:
109
109
110
110
1. Select the appropriate connection from the list on the main Data Connections page.
@@ -116,9 +116,9 @@ To edit or delete a data connection:
116
116
• **Updated**: the date and time that the data connection was last updated.
117
117

118
118
119
-
1. From this page, users can elect to reconnect, edit or delete their data connection.
120
-
• **Reconnect**: this option attempts to validate the data connection without any changes to the configuration. This option is best for those who have validated the authentication credentials used for the data connection.
121
-
• **Edit**: this option allows users to change the configuration for the data connection.
119
+
1. From this page, users can elect to reconnect, edit or delete their data connection.<br>
120
+
• **Reconnect**: this option attempts to validate the data connection without any changes to the configuration. This option is best for those who have validated the authentication credentials used for the data connection.<br>
121
+
• **Edit**: this option allows users to change the configuration for the data connection.<br>
122
122
• **Delete**: this option deletes the data connection.
0 commit comments