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/security/fundamentals/operational-best-practices.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -106,15 +106,15 @@ Here are some best practices for preventing, detecting, and responding to threat
106
106
**Detail**: Investigate the features and capabilities of [Azure Sentinel](/azure/sentinel/overview) and compare them with the capabilities of what you’re currently using on-premises. Consider adopting Azure Sentinel if it meets your organization’s SIEM requirements.
107
107
108
108
**Best practice**: Find the most serious security vulnerabilities so you can prioritize investigation.
109
-
**Detail**: Review your [Azure secure score](../../security-center/security-center-secure-score.md) to see the recommendations resulting from the Azure policies and initiatives built into Azure Security Center. These recommendations help address top risks like security updates, endpoint protection, encryption, security configurations, missing WAF, internet-connected VMs, and many more.
109
+
**Detail**: Review your [Azure secure score](../../security-center/secure-score-security-controls.md) to see the recommendations resulting from the Azure policies and initiatives built into Azure Security Center. These recommendations help address top risks like security updates, endpoint protection, encryption, security configurations, missing WAF, internet-connected VMs, and many more.
110
110
111
111
The secure score, which is based on Center for Internet Security (CIS) controls, lets you benchmark your organization’s Azure security against external sources. External validation helps validate and enrich your team’s security strategy.
112
112
113
113
**Best practice**: Monitor the security posture of machines, networks, storage and data services, and applications to discover and prioritize potential security issues.
114
114
**Detail**: Follow the [security recommendations](../../security-center/security-center-recommendations.md) in Security Center starting, with the highest priority items.
115
115
116
116
**Best practice**: Integrate Security Center alerts into your security information and event management (SIEM) solution.
117
-
**Detail**: Most organizations with a SIEM use it as a central clearinghouse for security alerts that require an analyst response. Processed events produced by Security Center are published to the Azure Activity Log, one of the logs available through Azure Monitor. Azure Monitor offers a consolidated pipeline for routing any of your monitoring data into a SIEM tool. See [Integrate security solutions in Security Center](../../security-center/continuous-export.md#configuring-siem-integration-via-azure-event-hubs) for instructions. If you’re using Azure Sentinel, see [Connect Azure Security Center](../../sentinel/connect-azure-security-center.md).
117
+
**Detail**: Most organizations with a SIEM use it as a central clearinghouse for security alerts that require an analyst response. Processed events produced by Security Center are published to the Azure Activity Log, one of the logs available through Azure Monitor. Azure Monitor offers a consolidated pipeline for routing any of your monitoring data into a SIEM tool. See [Export security alerts and recommendations](../../security-center/continuous-export.md#configuring-siem-integration-via-azure-event-hubs) for instructions.. If you’re using Azure Sentinel, see [Connect Azure Security Center](../../sentinel/connect-azure-security-center.md).
118
118
119
119
**Best practice**: Integrate Azure logs with your SIEM.
120
120
**Detail**: Use [Azure Monitor to gather and export data](/azure/azure-monitor/overview#integrate-and-export-data). This practice is critical for enabling security incident investigation, and online log retention is limited. If you’re using Azure Sentinel, see [Connect data sources](../../sentinel/connect-data-sources.md).
0 commit comments