Skip to content

Commit 2967a0f

Browse files
To see Sentinel Alerts and Incidents onboard to Defender Portal (#9875)
* To see Sentinel Alerts and Incidents onboard to Defender Portal * Apply suggestion from @FaithOmbongi * Update security-api-overview.md --------- Co-authored-by: Faith Moraa Ombongi <ombongi.moraa.fe@gmail.com>
1 parent 03caea2 commit 2967a0f

2 files changed

Lines changed: 7 additions & 1 deletion

File tree

api-reference/beta/resources/security-api-overview.md

Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -105,6 +105,9 @@ The beta version of the security API offers two types of alerts that aggregate o
105105
- [Alerts and incidents](#alerts-and-incidents) - the latest generation of alerts in the Microsoft Graph security API. They're represented by the [alert](security-alert.md) resource and its collection, [incident](security-incident.md) resource, defined in the `microsoft.graph.security` namespace.
106106
- [Legacy alerts](#legacy-alerts) - the first generation of alerts in the Microsoft Graph security API. They're represented by the [alert](alert.md) resource defined in the `microsoft.graph` namespace.
107107

108+
> [!IMPORTANT]
109+
> To see Sentinel alerts and incidents you must onboard Sentinel to the Defender Portal. For more information see [Connect Microsoft Sentinel to the Microsoft Defender portal](/unified-secops/microsoft-sentinel-onboard).
110+
108111
### Alerts and incidents
109112

110113
These [alert](security-alert.md) resources first pull alert data from security provider services, that are either part of or integrated with [Microsoft 365 Defender](/microsoft-365/security/defender/microsoft-365-defender?view=o365-worldwide&preserve-view=true). Then they consume the data to return rich, valuable clues about a completed or ongoing attack, the impacted assets, and associated [evidence](security-alertevidence.md). In addition, they automatically correlate other alerts with the same attack techniques or the same attacker into an [incident](security-incident.md) to provide a broader context of an attack. They recommend response and remediation actions, offering consistent actionability across all the different providers. The rich content makes it easier for analysts to investigate and respond to threats collectively.

api-reference/v1.0/resources/security-api-overview.md

Lines changed: 4 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -69,7 +69,10 @@ Alerts are detailed warnings about suspicious activities in a customer's tenant
6969

7070
The security API offers two types of alerts that aggregate other alerts from security providers and make analyzing attacks and determining responses easier:
7171
- [Alerts and incidents](#alerts-and-incidents) - these are the latest generation of alerts in the Microsoft Graph security API. They're represented by the [alert](security-alert.md) resource and its collection, [incident](security-incident.md) resource, defined in the `microsoft.graph.security` namespace.
72-
- [Legacy alerts](#legacy-alerts) - these are the first generation of alerts in the Microsoft Graph security API. They're represented by the [alert](alert.md) resource defined in the `microsoft.graph` namespace.
72+
- [Legacy alerts](#legacy-alerts) - these are the first generation of alerts in the Microsoft Graph security AI. They're represented by the [alert](alert.md) resource defined in the `microsoft.graph` namespace.
73+
74+
> [!IMPORTANT]
75+
> To see Sentinel alerts and incidents you must onboard Sentinel to the Defender Portal. For more information see [Connect Microsoft Sentinel to the Microsoft Defender portal](/unified-secops/microsoft-sentinel-onboard).
7376
7477
### Alerts and incidents
7578

0 commit comments

Comments
 (0)