Skip to content

Commit d52f709

Browse files
committed
edits
1 parent 6cc32d5 commit d52f709

File tree

2 files changed

+2
-2
lines changed

2 files changed

+2
-2
lines changed

articles/sentinel/soc-optimization/soc-optimization-access.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -105,7 +105,7 @@ SOC optimization recommendations are calculated every 24 hours. Each optimizatio
105105

106106
Filter the optimizations based on optimization type, or search for a specific optimization title using the search box on the side. Optimization types include:
107107

108-
- **Coverage** : Includes recommendations to help you close coverage gaps against specific threats and tighten your ingestion rates against data that doesn't provide security value. Includes:
108+
- **Coverage** : Includes recommendations to help you close coverage gaps against specific threats and tighten your ingestion rates against data that doesn't provide security value. Coverage recommendations include:
109109
- **Threat-based recommendations** for adding security controls to help close coverage gaps for various types of attacks.
110110
- **AI MITRE ATT&CK recommendations** for adding tagging recommendations to help close coverage gaps for various types of attacks, based on the MITRE ATT&CK framework.
111111
- **Risk-based recommendations** for adding security controls to help close coverage gaps for various types of business risks.

articles/sentinel/soc-optimization/soc-optimization-reference.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -25,7 +25,7 @@ Microsoft Sentinel SOC optimizations include the following types of recommendati
2525

2626
- **Data value recommendations** suggest ways to improve your data use, such as a better data plan for your organization.
2727

28-
- **Coverage based recommendations** suggest adding controls to prevent coverage gaps that can lead to vulnerability to attacks or scenarios that can lead to financial loss.
28+
- **Coverage based recommendations** suggest adding controls to prevent coverage gaps that can lead to vulnerability to attacks or scenarios that can lead to financial loss. Coverage recommendations include:
2929
- **Threat-based recommendations** suggest adding security controls that help you detect coverage gaps to prevent attacks and vulnerabilities.
3030
- **AI MITRE ATT&CK tagging recommendations (Preview)** uses artificial intelligence to suggest tagging security detections with MITRE ATT&CK tactics and techniques.
3131
- **Risk-based recommendations (Preview)** suggest adding controls to detect coverage gaps that correlate with use cases that could lead to business risks and financial loss, including Operational, Financial, Reputational, Compliance, and Legal business risks.

0 commit comments

Comments
 (0)