A.8 Technological controls

A.8.7 Protection against malware

Not mandatory by default – decided in your SoA

What it means in plain language

Protect against malware with technical tools and user awareness.

Is it mandatory? Not automatically. You must consider this control in your Statement of Applicability (6.1.3 d). Include it if your risk assessment, laws, contracts or business needs require it; if you exclude it, write down a justification an auditor will accept.

Why this control matters

The Malware Protection Procedure should translate threat scenarios into operational checks, rather than staying at a policy level. Focus on how endpoint detection, email filtering, and user reporting work together when malware arrives through attachments, links, removable media, or compromised downloads. Reviewers often look for evidence that the organization can identify who watches alerts, who isolates affected systems, and how lessons are fed back into awareness and technical tuning.

Common auditor findings to check for

Potential gaps to test in your own environment, not a claim about observed audit frequency.

  • Endpoint protection is deployed, but alert triage is unclear; analysts cannot show who reviews high-severity detections, when hosts are isolated, or how escalations are recorded.
  • Email filtering exists, but attachment sandboxing and URL inspection settings are not aligned with current threats; exceptions lack business justification and expiry dates.
  • Awareness content mentions phishing generally, but staff do not receive practical guidance on reporting suspicious files, preserving messages, or handling infected devices.

How you can implement it

Tools and review intervals are examples; choose them according to risk, obligations and your operating environment.

  • Assign the security lead or IT operations manager to maintain a malware response matrix covering detection sources, containment steps, and ownership for endpoints, servers, and email gateways. Include the conditions for quarantine, forensic image capture, and approval to reconnect systems after cleansing and validation. Keep the matrix consistent with incident handling records.
  • Tune controls using a risk-based checklist: EDR policy coverage, real-time protection, signature update status, macro restrictions, attachment sandboxing, and blocked file types. Review exclusions monthly with documented business rationale from system owners, because unmanaged exclusions often create avoidable exposure paths.
  • Use role-based awareness for users, service desk, and administrators. Users should learn how malicious attachments look, how to report suspicious activity immediately, and why they must not bypass controls. Administrators need handling steps for tamper alerts, offline systems, and remediation verification before restoration.
  • Maintain practical records showing both prevention and response: malware alert tickets, containment timestamps, endpoint health dashboards, blocked attachment logs, investigation notes, and training attendance. Sample evidence could include a sanitized incident timeline, an EDR policy export, and a mail security quarantine report linked to actions taken.

What an auditor will ask to see

  • Malware Protection Procedure with named roles, escalation points, and containment workflow.
  • EDR console export showing coverage, outdated agents, and recent quarantine events.
  • Email security report listing blocked attachments, sandbox outcomes, and approved exceptions.
  • Awareness attendance and phishing-report ticket samples demonstrating user reporting behavior.

Baseline documents in the kit

These free kit documents help you document or evidence A.8.7. Each one is tailored to your organization when you build your kit.

Connect this work to your ISMS

Review the dependencies with A.8.1 — User endpoint devices and A.5.24 — Information security incident management planning and preparation. Keep the ownership and evidence consistent across these activities.

Required information and the kit’s 19-document core for the wider implementation context.

Use the SIG and CAIQ questionnaire accelerator to find supporting documents. A mapping is a starting point: verify your actual operating evidence before answering a buyer.

For help adapting this to your environment, explore ISO/IEC 27001 consulting, starting with a free one-hour consultation.

Get these documents tailored to your organization

109 ready-to-edit documents, including all 19 mandatory ones, tailored from a short scoping questionnaire and linked to your risk register and SoA.

Start free

Plain-language interpretation by an ISO/IEC 27001 lead implementer, not the official text of ISO/IEC 27001:2022.