ISO 27701:2019
PIMS-specific guidance related to ISO/IEC 27002, ISO 27701:2019

ISO 27701:2019 6.9.2: Protection from malware

Controls against malware apply as the base guidance requires, read as protecting the personal data that a compromise would expose.

Maintained by Gerard Blokdyk

What else in your programme already covers this

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

PCI DSS 4.0 · 7 controls

  • 5.3.5 5.3.5 Users cannot disable or alter anti-malware
  • 5.4.1 5.4.1 Mechanisms detect and protect against phishing
  • 5.2.1 5.2.1 Anti-malware deployed on all system components
  • 5.2.2 5.2.2 Anti-malware detects and handles all known malware
  • 5.3.1 5.3.1 Anti-malware kept current through automatic updates
  • 5.3.2 5.3.2 Periodic and real-time scans or continuous behavioural analysis
  • 5.3.3 5.3.3 Anti-malware covers removable electronic media

CIS Controls v8 · 5 controls

  • CIS-10.1 Deploy and Maintain Anti-Malware Software
  • CIS-10.2 Configure Automatic Anti-Malware Signature Updates
  • CIS-10.7 Use Behavior-Based Anti-Malware Software
  • CIS-13.5 Manage Access Control for Remote Assets
  • CIS-9.7 Deploy and Maintain Email Server Anti-Malware Protections
  • ASBv3-ES-3 Ensure anti-malware software and signatures are updated
  • ES-1 Use Endpoint Detection and Response (EDR)
  • ES-2 Use modern anti-malware software
  • NIST-CSF-DE.CM-09 Computing hardware and software, runtime environments, and their data are monitored to find potentially adverse events
  • NIST-CSF-PR.DS-10 The confidentiality, integrity, and availability of data-in-use are protected
  • NIST-CSF-PR.PS-05 Installation and execution of unauthorized software are prevented
  • AWWA-4.1 Malware Protection
  • AWWA-G430-8 Malware Protection

CMMC 2.0 · 2 controls

NIST SP 800-53 Rev 5 · 2 controls

SOC 2 · 2 controls

  • SOC2-CC6.6 CC6.6 Protection against threats from outside the system boundary
  • SOC2-CC6.8 CC6.8 Preventing and detecting unauthorised or malicious software

API 1164 · 1 control

  • API1164-10 Malware Protection
  • AUCDR-IS-5 Limit, prevent, detect and remove malware

C5 (Germany) · 1 control

  • C5-OPS-05 Protection Against Malware - Implementation

FedRAMP High · 1 control

  • SI-3 Malicious Code Protection

FedRAMP Moderate · 1 control

  • SI-3 Malicious Code Protection

HIPAA Security Rule · 1 control

ISO 27001:2022 · 1 control

  • 8.7 Protection against malware

ISO 27002:2022 · 1 control

  • 8.7 Protection against malware

ISO 27017:2015 · 1 control

  • 12.2 Protection from malware

ISO 27018:2019 · 1 control

  • 12.2 Protection from malware

ISO/IEC 27010:2015 · 1 control

  • 27010-12.2 Protection from malware

ISO/IEC 27019:2024 · 1 control

  • ISO27019-12.2.1 Malware Protection in OT

ISO/IEC 27043:2015 · 1 control

  • ISO27043-22 Protection from malware

ISO/SAE 21434 · 1 control

  • ISO21434-22 Protection from malware

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.

Other controls in PIMS-specific guidance related to ISO/IEC 27002, ISO 27701:2019

You are reading one control. How much of ISO 27701:2019 have you already done?

ISO 27701:2019 6.9.2 is one control. If you already hold one of the frameworks below, a reviewed crosswalk already says how much of ISO 27701:2019 your existing evidence covers. Hold SOC 2 and 58 of 108 ISO 27701:2019 controls already carry evidence.

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. 289 were rejected on the SOC 2 pair alone.

Query this from an agent

The graph holds this control, the 46 it maps to, and the evidence behind each claim, over MCP and REST.