Skip to content
System hardening
ASD ISMISM-1034

ASD ISM 1034 Deploy HIPS or EDR on critical and high-value servers

What it says

A HIPS or EDR solution is implemented on critical servers and high-value servers.

Quoted as published. Everything else on this page is written by Control Stack.

In plain English

Run a HIPS or EDR solution on every critical server, such as domain controllers, and every high-value server, such as DNS, database, email, file and web servers.

A host-based intrusion prevention system (HIPS) or an endpoint detection and response (EDR) solution must be implemented on critical servers and high-value servers. Either product type is enough, but both server groups are covered. Critical servers run essential network or security services, such as domain controllers and certificate servers. High-value servers run important network services or hold data stores, such as DNS, database, email, file and web servers. This control does not cover other servers. ISM-1341 sets the same requirement for workstations.

Why it matters

Variants of known malicious code slip past signature-based detection, and on a domain controller or database server a missed intrusion can expose accounts across the network or whole data stores. A HIPS or EDR solution adds behaviour-based detection, helping identify and block what signatures miss.

How to implement

  1. Identify your critical servers and high-value servers.

    Go through every server, including cloud-hosted ones, by what it does rather than what it is called. Compare the result with the logical network diagrams, which must show both groups (ISM-0516), and the networked IT equipment register (ISM-0336).

  2. Agree a trial and a change window with those who run each server.

    Try the agent on a matching non-production server first, because domain controllers and database servers can be sensitive to added load. Check the vendor's supported versions and documented exclusions, and keep exclusions to those.

  3. Deploy the agent and turn on protection.

    Build it into the server's standard operating environment (ISM-1406) and push it to existing servers with your configuration tool. Set a HIPS to block rather than only monitor, and set up EDR response actions. Send events to the central facility, since ISM-1987 requires timely analysis of security product logs.

  4. Handle servers that cannot take an agent.

    For a vendor appliance, ask for a supported agent or a built-in HIPS or EDR function. For a server a provider runs, get the provider's assurance report or written confirmation. If neither works, record a risk for the authorising officer: it remains a known shortfall until closed.

Keep it running

Recheck the server list whenever a server is built, moved or changes role, because a new database or file share can make an ordinary server high-value. Chase agents that stop reporting, and retest after operating system upgrades or product changes.

Evidence and audit

  1. Check 1 of 3What an auditor asks for

    Ask for

    The list of critical servers and high-value servers, with the logical network diagrams (ISM-0516), the networked IT equipment register (ISM-0336) and a discovery scan or cloud inventory to compare it with.

    Look at

    Whether any server running domain, certificate, federation, directory synchronisation, DNS, database, email, file or web services, or another critical network or security service, important network service or data store, is missing from the list.

    Good evidence

    Every server doing any of those jobs is on the list, including cloud-hosted ones, and none has been left off because it is hard to protect.

  2. Check 2 of 3What an auditor asks for

    Ask for

    The HIPS or EDR console's agent list, compared with that checked server list.

    Look at

    Whether each listed server has an agent that is running and in contact with the console or, for an appliance or provider-run server, a built-in function or provider confirmation.

    Good evidence

    Every critical server and high-value server has a running HIPS or EDR agent in contact with its console or, for an appliance or provider-run server, a built-in function or provider confirmation showing the solution is running. A recorded exception with neither is a shortfall and does not pass.

  3. Check 3 of 3What an auditor asks for

    Ask for

    The live policy on a sample of those servers from both groups, and a harmless behaviour test on one server from each group under change control, such as the vendor's test tool.

    Look at

    Whether the product really is a HIPS or EDR, the blocking or response settings, the exclusions, and what the test triggers.

    Good evidence

    The product is a HIPS or EDR, a HIPS policy blocks rather than only monitors or an EDR detection reaches a console where someone can respond, exclusions do not cover whole drives, and the test activity, which matches no known malicious code signature, is detected or blocked and shows on the console.

Mappings

Closest match in ISO/IEC 27001: A.8.7, Protection against malware, which this control partially meets.

ISO 27001

ISO/IEC 27001: 2 mappings

  • A.8.7Protection against malwarePartially meets
  • A.8.16Monitoring activitiesSupports

Mappings show how controls relate across frameworks. They do not imply full equivalence or certification.