Azure Security Benchmark ASBv3-ES-3: Ensure anti-malware software and signatures are updated

What else in your programme already covers this

This control maps to 33 controls across 25 other frameworks. If you already hold one of them, the evidence you collected for it is the starting point here rather than new work.

CMMC 2.0 · 2 controls

SI.L2-3.14.4 Update Malicious Code Protection
SI.L2-3.14.5 System & File Scanning

FedRAMP High · 2 controls

SI-2 Flaw Remediation
SI-3 Malicious Code Protection

FedRAMP Moderate · 2 controls

SI-2 Flaw Remediation
SI-3 Malicious Code Protection

NIST SP 800-161 Rev 1 · 2 controls

161R1-SI-3 Malicious Code Protection
161R1-SI-5 Security Alerts, Advisories, and Directives

NIST SP 800-53 Rev 5 LOW · 2 controls

SI-2 Flaw Remediation
SI-3 Malicious Code Protection

NIST SP 800-53 Rev 5 MODERATE · 2 controls

SI-2 Flaw Remediation
SI-3 Malicious Code Protection

NIST SP 800-53 Revision 5.1 HIGH · 2 controls

SI-2 Flaw Remediation
SI-3 Malicious Code Protection

PCI DSS 4.0 · 2 controls

5.3.5 Anti-malware cannot be disabled by users
5.3.1 The anti-malware solution(s) is kept current via automatic updates

ACSC Essential Eight · 1 control

E8-PATCHAPP-ML1 Patch Applications (ML1)

ASD Strategies to Mitigate Cyber Security Incidents · 1 control

ASD37-16 Antivirus software with signatures (Limited)

Australia Consumer Data Right - Banking (CDR) · 1 control

AUCDR-IS-5 Limit, prevent, detect and remove malware

C5 (Germany) · 1 control

C5-OPS-05 Protection Against Malware - Implementation

CIS Controls v8 · 1 control

CIS-10.2 Configure Automatic Anti-Malware Signature Updates

Cloud Security Alliance Cloud Controls Matrix (CCM) v4.0.1 · 1 control

CCM-TVM-04 Detection Updates

HIPAA Security Rule · 1 control

164.308(a)(5)(ii)(B) Protection from Malicious Software (Addressable)

NIST Cybersecurity Framework 2.0 · 1 control

NIST-CSF-PR.PS-02 Software is maintained, replaced, and removed commensurate with risk

NIST SP 800-171 Rev 3 · 1 control

03.14.02 Malicious Code Protection

NIST SP 800-172 · 1 control

3.14.6e Use Threat Indicator Information for Detection

NIST SP 800-53 Rev 5 · 1 control

NIST800-SI-3 Malicious code protection

NIST SP 800-66 Rev 2 · 1 control

164.308(a)(5)(ii)(B) Protection from Malicious Software (Addressable)

SOC 2 · 1 control

SOC2-CC6.8 Controls to prevent or detect unauthorized or malicious software

UK Cyber Essentials · 1 control

CE-MP.2 Anti-Malware Signatures Updated

Every mapping shown was judged rather than inferred from wording similarity, and the ones that failed review are published too. See the coverage reports and what was rejected.

You are reading one control. How much of Azure Security Benchmark have you already done?

Azure Security Benchmark ASBv3-ES-3 is one control. If you already hold one of the frameworks below, a reviewed crosswalk already says how much of Azure Security Benchmark your existing evidence covers. Hold NIST SP 800-53 Rev 5 and 71 of 85 Azure Security Benchmark controls already carry evidence.

If you hold NIST SP 800-53 Rev 583.5% covered · 14 gaps If you hold FedRAMP Moderate78.8% covered · 18 gaps If you hold Cloud Security Alliance Cloud Controls Matrix (CCM) v4.0.172.9% covered · 23 gaps If you hold ISO 27002:202269.4% covered · 26 gaps If you hold C5 (Germany)65.9% covered · 29 gaps If you hold ISO 27001:202261.2% covered · 33 gaps

Each report names every control your existing framework evidences, every one it does not, the reasoning behind each claim, and the claims that were argued against and rejected. 0 were rejected on the NIST SP 800-53 Rev 5 pair alone.

See the released pairs, $299 each Browse the graph free