Skip to content

Commit 9fac694

Browse files
author
Jill Grant
authored
Merge pull request #261912 from ElazarK/wi194631-alerts-repeat
combined articles
2 parents aad9407 + 424f149 commit 9fac694

18 files changed

+103
-172
lines changed

.openpublishing.redirection.defender-for-cloud.json

Lines changed: 8 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -588,7 +588,7 @@
588588
{
589589
"source_path_from_root": "/articles/security-center/managing-and-responding-alerts.md",
590590
"redirect_url": "/azure/defender-for-cloud/managing-and-responding-alerts",
591-
"redirect_document_id": true
591+
"redirect_document_id": false
592592
},
593593
{
594594
"source_path_from_root": "/articles/security-center/os-coverage.md",
@@ -702,8 +702,8 @@
702702
},
703703
{
704704
"source_path_from_root": "/articles/security-center/tutorial-security-incident.md",
705-
"redirect_url": "/azure/defender-for-cloud/tutorial-security-incident",
706-
"redirect_document_id": true
705+
"redirect_url": "/azure/defender-for-cloud/managing-and-responding-alerts",
706+
"redirect_document_id": false
707707
},
708708
{
709709
"source_path_from_root": "/articles/security-center/tutorial-security-policy.md",
@@ -904,6 +904,11 @@
904904
"source_path_from_root": "/articles/defender-for-cloud/attack-path-reference.md",
905905
"redirect_url": "/azure/defender-for-cloud/how-to-manage-attack-path",
906906
"redirect_document_id": true
907+
},
908+
{
909+
"source_path_from_root": "/articles/defender-for-cloud/tutorial-security-incident.md",
910+
"redirect_url": "/azure/defender-for-cloud/managing-and-responding-alerts",
911+
"redirect_document_id": true
907912
}
908913
]
909914
}

articles/defender-for-cloud/TOC.yml

Lines changed: 1 addition & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -109,9 +109,6 @@
109109
- name: Protect VMs
110110
displayName: manage, access, harden
111111
href: tutorial-protect-resources.md
112-
- name: Investigate and respond to security alerts
113-
displayName: triage, security, alerts, investigate,
114-
href: tutorial-security-incident.md
115112
- name: Investigate the health of your resources
116113
displayName: health, resources, outstanding, security, issues,
117114
href: investigate-resource-health.md
@@ -394,7 +391,7 @@
394391
href: powershell-onboarding.md
395392
- name: Alerts, incidents, and threat reports
396393
items:
397-
- name: Respond to security alerts
394+
- name: Manage and respond to security alerts
398395
displayName: security alerts, alerts
399396
href: managing-and-responding-alerts.md
400397
- name: Create and manage alerts suppression rules

articles/defender-for-cloud/alerts-overview.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -115,5 +115,5 @@ In this article, you learned about the different types of alerts available in De
115115

116116
- [Security alerts in Azure Activity log](https://go.microsoft.com/fwlink/?linkid=2114113) - In addition to being available in the Azure portal or programmatically, Security alerts and incidents are audited as events in Azure Activity Log
117117
- [Reference table of Defender for Cloud alerts](alerts-reference.md)
118-
- [Respond to security alerts](managing-and-responding-alerts.md#respond-to-security-alerts)
118+
- [Respond to security alerts](managing-and-responding-alerts.md#respond-to-a-security-alert)
119119
- Learn how to [manage security incidents in Defender for Cloud](incidents.md).

articles/defender-for-cloud/alerts-schemas.md

Lines changed: 12 additions & 12 deletions
Original file line numberDiff line numberDiff line change
@@ -9,26 +9,26 @@ ms.date: 11/09/2021
99

1010
# Security alerts schemas
1111

12-
If your subscription has Defender for Cloud [Defender plans](defender-for-cloud-introduction.md#protect-cloud-workloads) enabled, you'll receive security alerts when Defender for Cloud detects threats to their resources.
12+
If your subscription has Defender for Cloud [Defender plans](defender-for-cloud-introduction.md#protect-cloud-workloads) enabled, you receive security alerts when Defender for Cloud detects threats to their resources.
1313

14-
You can view these security alerts in Microsoft Defender for Cloud's pages - [overview dashboard](overview-page.md), [alerts](tutorial-security-incident.md), [resource health pages](investigate-resource-health.md), or [workload protections dashboard](workload-protections-dashboard.md) - and through external tools such as:
14+
You can view these security alerts in Microsoft Defender for Cloud's pages - [overview dashboard](overview-page.md), [alerts](managing-and-responding-alerts.md), [resource health pages](investigate-resource-health.md), or [workload protections dashboard](workload-protections-dashboard.md) - and through external tools such as:
1515

1616
- [Microsoft Sentinel](../sentinel/index.yml) - Microsoft's cloud-native SIEM. The Sentinel Connector gets alerts from Microsoft Defender for Cloud and sends them to the [Log Analytics workspace](../azure-monitor/logs/quick-create-workspace.md) for Microsoft Sentinel.
17-
- Third-party SIEMs - Send data to [Azure Event Hubs](../event-hubs/index.yml). Then integrate your Event Hub data with a third-party SIEM. Learn more in [Stream alerts to a SIEM, SOAR, or IT Service Management solution](export-to-siem.md).
17+
- Third-party SIEMs - Send data to [Azure Event Hubs](../event-hubs/index.yml). Then integrate your Event Hubs data with a third-party SIEM. Learn more in [Stream alerts to a SIEM, SOAR, or IT Service Management solution](export-to-siem.md).
1818
- [The REST API](/rest/api/defenderforcloud/) - If you're using the REST API to access alerts, see the [online Alerts API documentation](/rest/api/defenderforcloud/alerts).
1919

20-
If you're using any programmatic methods to consume the alerts, you'll need the correct schema to find the fields that are relevant to you. Also, if you're exporting to an Event Hub or trying to trigger Workflow Automation with generic HTTP connectors, use the schemas to properly parse the JSON objects.
20+
If you're using any programmatic methods to consume the alerts, you need the correct schema to find the fields that are relevant to you. Also, if you're exporting to an Event Hubs or trying to trigger Workflow Automation with generic HTTP connectors, use the schemas to properly parse the JSON objects.
2121

2222
>[!IMPORTANT]
23-
> The schema is slightly different for each of these scenarios, so make sure you select the relevant tab below.
23+
> The schema is slightly different for each of these scenarios, so make sure you select the relevant tab.
2424
2525
## The schemas
2626

2727
### [Microsoft Sentinel](#tab/schema-sentinel)
2828

2929
The Sentinel Connector gets alerts from Microsoft Defender for Cloud and sends them to the Log Analytics Workspace for Microsoft Sentinel.
3030

31-
To create a Microsoft Sentinel case or incident using Defender for Cloud alerts, you'll need the schema for those alerts shown below.
31+
To create a Microsoft Sentinel case or incident using Defender for Cloud alerts, you need the schema for those alerts shown.
3232

3333
Learn more in the [Microsoft Sentinel documentation](../sentinel/index.yml).
3434

@@ -117,16 +117,16 @@ You can view the security alerts events in Activity Log by searching for the Act
117117
|**id**|The fully qualified alert ID|
118118
|**level**|Constant, "Informational"|
119119
|**operationId**|See correlationId|
120-
|**operationName**|The value field is constant - "Microsoft.Security/locations/alerts/activate/action", and the localized value will be "Activate Alert" (can potentially be localized par the user locale)|
121-
|**resourceGroupName**|Will include the resource group name|
120+
|**operationName**|The value field is constant - `Microsoft.Security/locations/alerts/activate/action`, and the localized value is `Activate Alert` (can potentially be localized par the user locale)|
121+
|**resourceGroupName**| Includes the resource group name|
122122
|**resourceProviderName**|The value and localizedValue subfields are constant - "Microsoft.Security"|
123123
|**resourceType**|The value and localizedValue subfields are constant - "Microsoft.Security/locations/alerts"|
124124
|**resourceId**|The fully qualified Azure resource ID|
125125
|**status**|The value and localizedValue subfields are constant - "Active"|
126126
|**subStatus**|The value and localizedValue subfields are empty|
127127
|**submissionTimestamp**|The UTC timestamp of event submission to Activity Log|
128128
|**subscriptionId**|The subscription ID of the compromised resource|
129-
|**properties**|A JSON bag of additional properties pertaining to the alert. These can change from one alert to the other, however, the following fields will appear in all alerts:<br>- severity: The severity of the attack<br>- compromisedEntity: The name of the compromised resource<br>- remediationSteps: Array of remediation steps to be taken<br>- intent: The kill-chain intent of the alert. Possible intents are documented in the [Intentions table](alerts-reference.md#intentions)|
129+
|**properties**|A JSON bag of other properties pertaining to the alert. Properties can change from one alert to the other, however, the following fields appear in all alerts:<br>- severity: The severity of the attack<br>- compromisedEntity: The name of the compromised resource<br>- remediationSteps: Array of remediation steps to be taken<br>- intent: The kill-chain intent of the alert. Possible intents are documented in the [Intentions table](alerts-reference.md#intentions)|
130130
|**relatedEvents**|Constant - empty array|
131131

132132

@@ -138,8 +138,8 @@ For the alerts schema when using workflow automation, see the [connectors docume
138138

139139
Defender for Cloud's continuous export feature passes alert data to:
140140

141-
- Azure Event Hub using the same schema as [the alerts API](/rest/api/defenderforcloud/alerts).
142-
- Log Analytics workspaces according to the [SecurityAlert schema](/azure/azure-monitor/reference/tables/SecurityAlert) in the Azure Monitor data reference documentation.
141+
- Azure Event Hubs using the same schema as [the alerts API](/rest/api/defenderforcloud/alerts).
142+
- Log Analytics workspaces according to the [SecurityAlert schema](/azure/azure-monitor/reference/tables/SecurityAlert) in the Azure Monitor data documentation.
143143

144144
### [MS Graph API](#tab/schema-graphapi)
145145

@@ -151,7 +151,7 @@ The schema and a JSON representation for security alerts sent to MS Graph, are a
151151

152152
## Next steps
153153

154-
This article described the schemas that Microsoft Defender for Cloud's threat protection tools use when sending security alert information.
154+
This article described the schemas that Microsoft Defenders for Cloud's threat protection tools use when sending security alert information.
155155

156156
For more information on the ways to access security alerts from outside Defender for Cloud, see:
157157

articles/defender-for-cloud/defender-for-apis-introduction.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -24,7 +24,7 @@ Defender for APIs currently provides security for APIs published in Azure API Ma
2424
- **Threat detection**: Ingest API traffic and monitor it with runtime anomaly detection, using machine-learning and rule-based analytics, to detect API security threats, including the [OWASP API Top 10](https://owasp.org/www-project-api-security/) critical threats.
2525
- **Defender CSPM integration**: Integrate with Cloud Security Graph in [Defender Cloud Security Posture Management (CSPM)](concept-cloud-security-posture-management.md) for API visibility and risk assessment across your organization.
2626
- **Azure API Management integration**: With the Defender for APIs plan enabled, you can receive API security recommendations and alerts in the Azure API Management portal.
27-
- **SIEM integration**: Integrate with security information and event management (SIEM) systems, making it easier for security teams to investigate with existing threat response workflows. [Learn more](tutorial-security-incident.md).
27+
- **SIEM integration**: Integrate with security information and event management (SIEM) systems, making it easier for security teams to investigate with existing threat response workflows. [Learn more](managing-and-responding-alerts.md).
2828

2929
## Reviewing API security findings
3030

articles/defender-for-cloud/defender-for-databases-usage.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -43,7 +43,7 @@ When Microsoft Defender for Cloud is enabled on your database, it detects anomal
4343
> [!TIP]
4444
> A live tile on [Microsoft Defender for Cloud's overview dashboard](overview-page.md) tracks the status of active threats to all your resources including databases. Select the security alerts tile to go to the Defender for Cloud security alerts page and get an overview of active threats detected on your databases.
4545
>
46-
> For detailed steps and the recommended method to respond to security alerts, see [Respond to a security alert](tutorial-security-incident.md#respond-to-a-security-alert).
46+
> For detailed steps and the recommended method to respond to security alerts, see [Respond to a security alert](managing-and-responding-alerts.md#respond-to-a-security-alert).
4747
4848
### Respond to email notifications of security alerts
4949

@@ -62,7 +62,7 @@ Defender for Cloud sends email notifications when it detects anomalous database
6262
:::image type="content" source="media/defender-for-databases-usage/specific-alert-details.png" alt-text="Details of a specific alert." lightbox="media/defender-for-databases-usage/specific-alert-details.png":::
6363

6464
> [!TIP]
65-
> For a detailed tutorial on how to handle your alerts, see [Tutorial: Triage, investigate, and respond to security alerts](tutorial-security-incident.md).
65+
> For a detailed tutorial on how to handle your alerts, see [Manage and respond to alerts](tutorial-security-incident.md).
6666
6767
## Next steps
6868

articles/defender-for-cloud/investigate-resource-health.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -72,13 +72,13 @@ The resource health page lists the recommendations for which your resource is "u
7272
7373
- To investigate a security alert:
7474
1. From the right pane, select an alert.
75-
1. Follow the instructions in [Respond to security alerts](managing-and-responding-alerts.md#respond-to-security-alerts).
75+
1. Follow the instructions in [Respond to security alerts](managing-and-responding-alerts.md#respond-to-a-security-alert).
7676

7777
## Next steps
7878

7979
In this tutorial, you learned about using Defender for Cloud’s resource health page.
8080

8181
To learn more, see these related pages:
8282

83-
- [Respond to security alerts](managing-and-responding-alerts.md#respond-to-security-alerts)
83+
- [Respond to security alerts](managing-and-responding-alerts.md#respond-to-a-security-alert)
8484
- [Review your security recommendations](review-security-recommendations.md)

0 commit comments

Comments
 (0)