liveBook · Manning

Recommendation

As explained in Azure Security

A security recommendation is guidance that identifies a security weakness or misconfiguration and specifies how to improve the protection of a resource.

A security recommendation identifies a misconfiguration or weakness in an Azure resource and gives concise remediation guidance. Microsoft Defender for Cloud generates recommendations using the Microsoft Cloud Security Benchmark (MCSB), aligned with NIST, CIS, and PCI DSS controls. section 6.2.2

Figure 6.3 An overview of recommendations in the Microsoft Defender for Cloud dashboard

Use the Recommendations view to review detected issues across an onboarded subscription. Prioritize work with Potential Score Increase to focus first on changes that most improve security posture. section 6.2.2

Recommendations and secure score are available without additional cost after onboarding Azure subscriptions to Defender for Cloud. Secure score aggregates security findings from 0% to 100%; following recommendations under a control raises the score, while preview recommendations do not yet count. section 6.2.3 section 6.2.4

Turn guidance into accountable remediation:

  • Open a recommendation, inspect its unhealthy resources and remediation steps, implement the fix, then check again after the stated freshness interval. section 6.7
  • Assign an owner, due date, and optional grace period to each affected resource; the grace period prevents score impact until the due date. section 6.4.1
  • Use governance rules to assign owners by resource tag and set 7-, 14-, 30-, or 90-day remediation timeframes across selected scopes. section 6.4.3
  • Automate a Logic App response by using recommendation name, severity, state, or regulatory-control conditions as workflow triggers. section 7.4.1

VM system updates campaign

A governance rule can target “System Updates Should Be Installed on Your Machines,” select an owner from a resource tag, allow 14 days for remediation, and retain a grace period until the item is overdue. section 6.4.3

How Azure Security covers it

How deep it goes
Explains viewing, prioritizing, remediating, assigning, governing, and automating recommendations, without detailing MCSB control internals.
Examples
Uses MFA, secure management ports, vulnerability remediation, VM system updates, owners, due dates, and grace periods.
What it assumes
Assumes an Azure subscription onboarded to Defender for Cloud with MCSB assigned; teaches remediation from the portal.
What you can do after
Apply it via Microsoft Defender for Cloud to prioritize, remediate, verify, assign, and automate security improvements.
How it connects
Connects recommendations to Microsoft Defender for Cloud, MCSB, secure score, CSPM, governance rules, resource tags, and Logic Apps.

Also explained in

Compare how 2 books explain recommendation →

Related concepts

This explainer was generated by Manning's knowledge graph from the text of Azure Security. The section links point to the parts of the book it draws on.