Skip to content

Commit ecbd9c3

Browse files
authored
Merge pull request #105589 from memildin/asc-melvyn-vmva
Minor tweaks for issues flagged by reviewer
2 parents 8cb8180 + 506039d commit ecbd9c3

File tree

4 files changed

+29
-13
lines changed

4 files changed

+29
-13
lines changed

.vscode/settings.json

Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -54,5 +54,8 @@
5454
"XAML",
5555
"XML",
5656
"YAML"
57+
],
58+
"cSpell.words": [
59+
"auditd"
5760
]
5861
}

articles/security-center/advanced-threat-protection-key-vault.md

Lines changed: 4 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -16,9 +16,9 @@ Advanced threat protection for Azure Key Vault provides an additional layer of s
1616

1717
When Security Center detects anomalous activity, it displays alerts. It also emails the subscription administrator with details of the suspicious activity and recommendations for how to investigate and remediate the identified threats.
1818

19-
## Enabling and disabling threat protection from Azure Security Center
19+
## Configuring threat protection from Security Center
2020

21-
By default, advanced threat protection is enabled for all of your Key Vault accounts when you subscribe to the Security Center Standard tier. For more information, see [Pricing](security-center-pricing.md).
21+
By default, advanced threat protection is enabled for all of your Key Vault accounts when you subscribe to Security Center's standard pricing tier. For more information, see [Pricing](security-center-pricing.md).
2222

2323
To enable or disable the protection for a specific subscription:
2424

@@ -39,6 +39,7 @@ To enable or disable the protection for a specific subscription:
3939

4040
In this article, you learned how to enable and disable advanced threat protection for Azure Key Vault.
4141

42-
For related material, see the following article:
42+
For related material, see the following articles:
4343

4444
- [Threat protection in Azure Security Center](threat-protection.md)--This article describes the sources of security alerts in Azure Security Center.
45+
- [Key Vault security alerts](alerts-reference.md#alerts-azurekv)--The Key Vault section of the reference table for all Azure Security Center alerts

articles/security-center/alerts-reference.md

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -414,6 +414,7 @@ Security Center's supported kill chain intents are based on the [MITRE ATT&CK™
414414
## Next steps
415415
To learn more about alerts, see the following:
416416

417+
* [Threat protection in Azure Security Center](threat-protection.md)
417418
* [Security alerts in Azure Security Center](security-center-alerts-overview.md)
418419
* [Manage and respond to security alerts in Azure Security Center](security-center-managing-and-responding-alerts.md)
419420
* [Export security alerts and recommendations (Preview)](continuous-export.md)

articles/security-center/threat-protection.md

Lines changed: 21 additions & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -18,14 +18,16 @@ This page briefly describes the sources of the security alerts displayed by Azur
1818

1919
When Security Center detects a threat in any of the areas of your environment listed below, it generates an alert. These alerts describe details of the affected resources, suggested remediation steps, and in some cases an option to trigger a logic app in response.
2020

21-
Whether an alert is generated by Security Center, or received by Security Center from a different security product, you can export it to Azure Sentinel (or another SIEM) or other external location using the instructions in [Exporting alerts and recommendations](continuous-export.md).
21+
Whether an alert is generated by Security Center, or received by Security Center from a different security product, you can export it. To export your alerts to Azure Sentinel (or a third-party SIEM) or any other external locations, follow the instructions in [Exporting alerts and recommendations](continuous-export.md).
22+
23+
2224

2325

2426
## Threat protection for Windows machines <a name="windows-machines"></a>
2527

2628
Azure Security Center integrates with Azure services to monitor and protect your Windows-based machines. Security Center presents the alerts and remediation suggestions from all of these services in an easy-to-use format.
2729

28-
* **Microsoft Defender ATP** <a name="windows-atp"></a> - Security Center extends its cloud workload protection platforms by integrating with Microsoft Defender Advanced Threat Protection (ATP). This provides comprehensive endpoint detection and response (EDR) capabilities.
30+
* **Microsoft Defender ATP** <a name="windows-atp"></a> - Security Center extends its cloud workload protection platforms by integrating with Microsoft Defender Advanced Threat Protection (ATP). Together, they provide comprehensive endpoint detection and response (EDR) capabilities.
2931

3032
> [!IMPORTANT]
3133
> The Microsoft Defender ATP sensor is automatically enabled on Windows servers that use Security Center.
@@ -62,11 +64,11 @@ Security Center collects audit records from Linux machines by using **auditd**,
6264

6365
* **Linux auditd alerts and Microsoft Monitoring Agent (MMA) integration** <a name="linux-auditd"></a> - The auditd system consists of a kernel-level subsystem, which is responsible for monitoring system calls. It filters them by a specified rule set, and writes messages for them to a socket. Security Center integrates functionalities from the auditd package within the Microsoft Monitoring Agent (MMA). This integration enables collection of auditd events in all supported Linux distributions, without any prerequisites.
6466

65-
auditd records are collected, enriched, and aggregated into events by using the Linux MMA agent. Security Center continuously adds new analytics that use Linux signals to detect malicious behaviors on cloud and on-premises Linux machines. Similar to Windows capabilities, these analytics span across suspicious processes, dubious sign-in attempts, kernel module loading, and other activities. These activities can indicate a machine is either under attack or has been breached.
67+
auditd records are collected, enriched, and aggregated into events by using the Linux MMA agent. Security Center continuously adds new analytics that use Linux signals to detect malicious behaviors on cloud and on-premises Linux machines. Similar to Windows capabilities, these analytics span across suspicious processes, dubious sign in attempts, kernel module loading, and other activities. These activities can indicate a machine is either under attack or has been breached.
6668

6769
For a list of the Linux alerts, see the [Reference table of alerts](alerts-reference.md#alerts-linux).
6870

69-
> [!NOTE]
71+
> [!TIP]
7072
> You can simulate Linux alerts by downloading [Azure Security Center Playbook: Linux Detections](https://gallery.technet.microsoft.com/Azure-Security-Center-0ac8a5ef).
7173
7274

@@ -105,7 +107,7 @@ Security Center provides threat protection at different levels:
105107

106108
For a deeper insight into the security of your containerized environment, the agent monitors container-specific analytics. It will trigger alerts for events such as privileged container creation, suspicious access to API servers, and Secure Shell (SSH) servers running inside a Docker container.
107109

108-
>[!NOTE]
110+
>[!IMPORTANT]
109111
> If you choose not to install the agents on your hosts, you will only receive a subset of the threat detection benefits and alerts. You'll still receive alerts related to network analysis and communications with malicious servers.
110112
111113
For a list of the host level alerts, see the [Reference table of alerts](alerts-reference.md#alerts-containerhost).
@@ -135,7 +137,7 @@ Some network configurations may restrict Security Center from generating alerts
135137

136138
- Your virtual machine's network egress traffic isn't blocked by an external IDS solution.
137139

138-
- Your virtual machine has been assigned the same IP address for the entire hour during which the suspicious communication occurred. This also applies to VMs created as part of a managed service (e.g. AKS, Databricks).
140+
- Your virtual machine has been assigned the same IP address for the entire hour during which the suspicious communication occurred. This also applies to VMs created as part of a managed service (for example, AKS, Databricks).
139141

140142
For a list of the Azure network layer alerts, see the [Reference table of alerts](alerts-reference.md#alerts-azurenetlayer).
141143

@@ -171,7 +173,7 @@ For a list of the Azure Key Vault alerts, see the [Reference table of alerts](al
171173

172174
Advanced Threat Protection for Azure SQL Database detects anomalous activities indicating unusual and potentially harmful attempts to access or exploit databases.
173175

174-
You'll see alerts when there are suspicious database activities, potential vulnerabilities, or SQL injection attacks, as well as anomalous database access and query patterns.
176+
You'll see alerts when there are suspicious database activities, potential vulnerabilities, or SQL injection attacks, and anomalous database access and query patterns.
175177

176178
Advanced Threat Protection for Azure SQL Database and SQL is part of the [Advanced Data Security (ADS)](https://docs.microsoft.com/azure/sql-database/sql-database-advanced-data-security) unified package for advanced SQL security capabilities, covering Azure SQL Databases, Azure SQL Database managed instances, Azure SQL Data Warehouse databases, and SQL servers on Azure Virtual Machines.
177179

@@ -257,10 +259,19 @@ If you have a license for Azure WAF, your WAF alerts are streamed to Security Ce
257259

258260
### Threat protection for Azure DDoS Protection <a name="azure-ddos"></a>
259261

260-
Distributed denial of service (DDoS) attacks are known to be easy to execute. They have become a great security concern, particularly if you are moving your applications to the cloud.
262+
Distributed denial of service (DDoS) attacks are known to be easy to execute. They've become a great security concern, particularly if you're moving your applications to the cloud.
261263

262264
A DDoS attack attempts to exhaust an application’s resources, making the application unavailable to legitimate users. DDoS attacks can target any endpoint that can be reached through the internet.
263265

264-
To defend against DDoS attacks, purchase a license for Azure DDoS Protection and ensure you are following application design best practices. DDoS Protection provides different service tiers. For more information, see [Azure DDoS Protection overview](https://docs.microsoft.com/azure/virtual-network/ddos-protection-overview).
266+
To defend against DDoS attacks, purchase a license for Azure DDoS Protection and ensure you're following application design best practices. DDoS Protection provides different service tiers. For more information, see [Azure DDoS Protection overview](https://docs.microsoft.com/azure/virtual-network/ddos-protection-overview).
267+
268+
For a list of the Azure DDoS Protection alerts, see the [Reference table of alerts](alerts-reference.md#alerts-azureddos).
269+
270+
271+
## Next steps
272+
To learn more about the security alerts from these threat protection features, see the following articles:
265273

266-
For a list of the Azure DDoS Protection alerts, see the [Reference table of alerts](alerts-reference.md#alerts-azureddos).
274+
* [Reference table for all Azure Security Center alerts](alerts-reference.md)
275+
* [Security alerts in Azure Security Center](security-center-alerts-overview.md)
276+
* [Manage and respond to security alerts in Azure Security Center](security-center-managing-and-responding-alerts.md)
277+
* [Export security alerts and recommendations (Preview)](continuous-export.md)

0 commit comments

Comments
 (0)