Compliancemanzill.com
CIS Microsoft Azure Foundations Benchmark v1.4.0

CIS Microsoft Azure Foundations Benchmark v1.4.0/Database Services/55 of 115

4.2.3Ensure that VA setting 'Periodic recurring scans' to 'on' for each SQL server

Control family: Database Services

Control description

Enable Vulnerability Assessment (VA) Periodic recurring scans for critical SQL servers and corresponding SQL databases.

How to implement

ResponsibilityCustomerYou configure and operate this in your own cloud accounts.

A single scan goes out of date as soon as the database changes. Recurring scans run vulnerability assessment every week, so new weaknesses show up without anyone remembering to scan. The express configuration scans weekly on its own.

Before you start

The same on every cloud, before the steps in the tabs.

  • Note that vulnerability assessment now defaults to an express configuration, which needs no storage account and scans automatically; the storage, recurring scan and email settings in 4.2.2 to 4.2.5 belong to the classic configuration. Record which configuration each server uses.

Evidence

  • The vulnerability assessment configuration chosen for each SQL server

On Azure the tasks set this option in the vulnerability assessment settings of each SQL server, then check the reports reach people.

Task 1Set Periodic recurring scans

  1. Sign in to the Azure portal at portal.azure.com and open SQL servers, then the server.
  2. Select Security > Defender for Cloud, then Configure.
  3. In the classic vulnerability assessment settings, set Periodic recurring scans to On.
  4. Select Save.
  5. Check it: reopen the settings and confirm the value. On the express configuration, check Defender for Cloud email notifications (2.13 to 2.15) instead.

Task 2Check the reports reach people

  1. After the next weekly scan, ask the recipients to confirm they received the report.
  2. Open the database's Defender for Cloud page and view the vulnerability assessment findings and scan history.
  3. Track each high-risk finding to a fix or an accepted risk.

Evidence

  • The vulnerability assessment settings of each SQL server, showing Periodic recurring scans
  • A recent scan report received by the recipients

Console steps as of 5 November 2026. Not every step has been confirmed in a live console yet, and menus and labels can move between releases, so look for the nearest match if one has changed.