Join our Newsletter — 33% off our NHI Course
Home› Guides› ESET PROTECT Configuration Guide: Policies, Console Access, Exclusions…
Guide Endpoint Security

ESET PROTECT Configuration Guide: Policies, Console Access, Exclusions and MDR Done Safely

PDF for newsletter subscribers · free to read online

← All guides
By NHI Mgmt Group, under the editorial direction of Lalit Choda Updated 19 November 2026 16 min read
On this page

ESET PROTECT decides what every managed endpoint is allowed to do, so the way you build its policies, permission sets and exclusions matters as much as the detection engine itself. This guide sets out a configuration baseline for the ESET PROTECT console: how policy flags and ordering produce the final state on a computer, how to scope console users with permission sets, how to protect the ESET Management Agent from removal, how to govern antivirus and EDR exclusions, and what to check before you rely on ESET MDR.

It is written for endpoint engineers, security operations leads and identity teams who run or inherit an ESET PROTECT tenant. Each recommendation is either tied to ESET's own documentation or clearly labelled as NHI Mgmt Group guidance, so you can tell the vendor's stated behaviour from our operating advice.

This is an independent guide from NHI Mgmt Group, based on ESET's public documentation as of November 2026. It is not sponsored or reviewed by ESET. Product features change, so confirm settings against ESET's current documentation.

Key takeaways

  • Every policy setting carries one of three flags: Not apply, Apply or Force. ESET states that Force settings have priority and cannot be overwritten by a later policy, even one that also uses Force.
  • Apply the Force flag consistently across related settings. ESET warns that forcing only some settings can let related settings from other policies take effect and break the final state you expected.
  • Permission sets are additive, and access to a static group includes all of its subgroups. Design the static group tree first, then the permission sets.
  • Restrict Client Tasks, Run Command, and keep Permission Sets and Mapped accounts permissions away from non-administrators, as ESET recommends.
  • Turn on Password protected setup for the ESET Management Agent, store the password in a vault, and test the policy on one computer first.
  • Antivirus detection exclusions now live under More, Exclusions, not in policies. Migrated exclusions do not keep their original assignments, so reassign them deliberately.
  • ESET MDR needs an ESET PROTECT MDR or MDR Ultimate tier and is only available in selected markets. Confirm who receives its critical notifications before you depend on it.

Why the console is a high-value target

An endpoint management console is a software deployment tool with administrative reach into every managed computer. MITRE ATT&CK describes the abuse of such tools under Software Deployment Tools (T1072), and the weakening of security products under Disable or Modify Tools (T1685). An attacker who reaches a privileged ESET PROTECT account does not need to fight the detection engine on each machine; they can try to change the policy, add an exclusion or run a command through the console instead.

That is why NHI Mgmt Group treats the console as tier zero infrastructure, alongside the identity provider. The broader case for protecting the security tool itself is set out in Securing the EDR and XDR platform itself. This guide applies that thinking to the specific controls ESET PROTECT exposes.

Three kinds of identity touch the console and need governing:

  • Human administrators who sign in to the Web Console and hold permission sets.
  • Delegated or local administrators who manage one branch of the static group tree, such as a country or a subsidiary.
  • Non-human identities such as the ESET Management Agent on each computer, plus any integration or reporting accounts your team creates. These rarely get the same review as human accounts, which is why they deserve explicit owners.

How policy flags work

ESET PROTECT builds the configuration of each computer by merging the policies that apply to it. Each individual setting inside a policy carries one flag, and ESET's documentation describes the three flags as follows:

FlagWhat ESET says it doesCan a later policy change it?
Not applyThe setting is not set by the policy.Yes, later policies can set it.
ApplyThe setting is sent to the client and changes the value regardless of what was configured locally.Yes, a later policy can overwrite it.
ForceThe setting has priority and is locked against later policies.No, not even by a later policy that also uses Force.

The practical consequence is that the first policy to force a setting wins. ESET's own example assigns an administrator policy to the All static group and a user policy to a subgroup; the All policy is applied first, so its forced settings hold, and the user policy is applied afterwards.

The most important warning on the flags page concerns partial enforcement. ESET states that to ensure an expected final state, the Force flag must be applied consistently across all related policy settings. If you force one setting in a feature but leave its companions at Apply, a later policy can still change those companions and produce a combination nobody designed.

The policy editor offers section level shortcuts: an Apply flag action that sets Apply on every item in the current section, and a Not apply flag action that removes the rules set on items in that section. Rule counts are shown per section and per category in the settings tree, which is a useful quick audit of how much a policy really changes.

NHI Mgmt Group recommendations for flags

  • Reserve Force for a short list of security-critical settings: protection modules that must stay on, the Agent password, and the settings that stop users from changing the product locally.
  • When you force a setting, review its whole section and force the related settings too, following ESET's consistency warning.
  • Leave operational preferences such as scan schedules or notifications at Apply, so that regional teams can tune them in lower policies.
  • Write the intent of each forced setting in the policy description. Six months later, nobody will remember why it was locked.

Policy order, inheritance and the applied view

Because the first forced value wins and later Apply values overwrite earlier ones, order is everything. ESET documents how policies are applied through the group tree and how the order of groups and policies can be changed, and it gives a direct way to check the result: open More, Groups, select the group and the computer, then Details, Configuration, Applied policies. That view shows the final order in which policies reached a specific machine.

NHI Mgmt Group suggests a simple layered model:

  1. Baseline security policy on the All static group. Forces the non-negotiable protection and tamper settings. Owned by the central security team.
  2. Platform policies for Windows servers, Windows workstations, macOS and Linux, set mainly with Apply.
  3. Business unit or regional policies lower in the tree for local preferences, never forcing security settings.
  4. Temporary exception policies assigned to a small named group, with an expiry date in the description and a ticket reference.

Before each change, pick two or three representative computers and record their Applied policies view. After the change, compare. This catches the most common surprise: a regional policy that was assumed to be lower in the order turns out to apply first.

ESET's guidance on the Agent password policy also contains two habits worth applying to every policy: test by assigning the policy to one computer before more targets, and assign groups rather than many individual computers to avoid slowing the Web Console. ESET notes that a policy is applied after the target's next connection to ESET PROTECT, and that the Send Wake-Up Call action can speed this up.

Console access with permission sets

ESET describes permission sets as defining what a user can do or see in the Web Console. Each set has two parts: functionality permissions and a domain of application made up of static groups. Several properties shape a safe design:

  • Static group scope inherits downwards. Access to a static group also gives access to all of its subgroups. ESET presents this as a way to build separate branches for local administrators.
  • Permission sets are additive. A user's effective access is the combined result of every set assigned to them. Two harmless looking sets can add up to more than you intended.
  • Access levels. ESET's examples use Read to view objects, Use to apply or run them without editing (for example applying a policy), and Write to create, edit and delete them.
  • Home groups. Each permission set is stored in the home group of the user who created it, and new user accounts are stored in the creating user's home group, usually All when the Administrator creates them.

ESET also makes specific recommendations that belong in every baseline:

  • Consider restricting Client Tasks, Run Command, which ESET calls a very powerful task that could be abused.
  • Do not give non-administrator users permissions for Permission Sets or Mapped accounts. Either would let them change their own or others' access.
  • Remember that audit log permissions let a user view the logged actions of all users and domains, including assets the user cannot otherwise view. Grant them to auditors and the security team, not to delegated administrators by default.

A starting role model

The table below is NHI Mgmt Group guidance, not a set of predefined ESET roles. Adapt it to your static group tree.

RoleStatic group scopeTypical permissions
Security platform ownerAllWrite on policies, exclusions and permission sets; held by two to three named people
Regional administratorOwn branch onlyUse on policies, Write on local computers and tasks; no Run Command; no Permission Sets or Mapped accounts
SOC analystAllRead on computers and detections, Use on isolation tasks; no policy Write
AuditorAllRead and audit log access only
Help deskWorkstation branchesRead on computers; limited tasks agreed with security

Review assignments every quarter. Because sets are additive, the review should look at each user's combined access, not each set in isolation. Joiner, mover and leaver changes for console users should flow from your identity process, the same as for any privileged system.

Protecting the ESET Management Agent

The ESET Management Agent is the component on each computer that talks to ESET PROTECT. If a local administrator or an attacker can uninstall it, the computer silently drops out of management. ESET provides Password protected setup for this purpose.

To configure it, ESET's documentation says to create a new policy, select ESET Management Agent from the drop-down list, expand Setup and click Set next to Password protected setup, then enter the password. ESET states that when Password protected setup is used, the Agent cannot be uninstalled or repaired unless a password is provided, and that the password is also needed to upgrade the Agent with changes.

ESET advises recording the password in a safe place. NHI Mgmt Group adds:

  • Treat the Agent password as a shared secret for a non-human identity. Store it in your enterprise vault with a named owner, not in a spreadsheet or a ticket.
  • Limit who can read it to the platform owners and the team that runs upgrades, and log each retrieval.
  • Rotate it on a schedule and after any staff departure from the platform team, using the same policy, and confirm the new value has applied with the Applied policies view.
  • Force this setting in the baseline policy so no lower policy can clear it.
  • Plan your upgrade and repair runbooks around the password, so that teams are not tempted to remove the protection to get a deployment done.

Review the tamper and settings protection options in your security product policy against ESET's current documentation as well, and alert on any computer that stops reporting. A device that falls silent is a signal to investigate, not just a hygiene issue. The EDR Tampering and BYOVD Response Playbook covers the response side.

Governing exclusions

Exclusions are the most direct way to weaken endpoint protection, whether by mistake or on purpose. ESET PROTECT now manages them in a dedicated Exclusions area with two types.

AV exclusions

AV exclusions cover antivirus detections and firewall IDS rules. ESET states that in ESET PROTECT you cannot create antivirus detection exclusions through a policy. Existing policy exclusions are exported from the policy (Detection engine, Detection exclusions) and imported under More, Exclusions, AV Exclusions.

Two details from ESET's documentation matter during migration. Imported exclusions go to the home group by default, and the original exclusion assignments are not preserved. Targets are then set with Change Assignments. ESET also notes that exclusions are not applied to incompatible ESET security products and are ignored on them.

EDR exclusions

EDR exclusions cover indicators created when EDR rules trigger. They are created under Exclusions, EDR Exclusions, New Exclusion, with Basics, Definition, Rules, Targets and Summary sections, or from an indicator in an incident using Create Rule Exclusion. Definition criteria can be scoped to the current process, the parent process or any ancestor process, and include process name, path, command line, signer, signature type, SHA-1, SHA-256 and user. ESET notes that signature type is required when a signer is specified. EDR exclusions can be enabled, disabled, duplicated, and exported or imported as XML. ESET's page states that EDR features are rolling out gradually through October 2026 and depend on your environment, so confirm what your tenant shows.

Access to an exclusion follows its static group, set through Access Group, Move.

NHI Mgmt Group recommendations for exclusions

  • Prefer the narrowest criteria: a hash or a signer with signature type, plus a path, scoped to the current process, rather than a broad path or any ancestor process.
  • Never assign an exclusion to All unless the business case covers every computer.
  • Record an owner, a reason, a ticket and a review date for every exclusion. Export the list as XML each month so you have a dated record to diff.
  • When migrating from policy exclusions, reassign each one on purpose instead of leaving everything in the home group.
  • Restrict Write on exclusions to the security platform owners. A regional administrator who can add exclusions can switch off protection for their branch.

A wider method for tuning and exclusion hygiene across any EDR is in the EDR Tuning and Exclusions Management Guide.

ESET MDR: what to set up before relying on it

ESET describes ESET MDR as a managed service providing around the clock threat monitoring, detection and incident response, combining AI with human analysts. It groups alarms and detections into incidents and gives an overview of incidents, indicators and telemetry events. ESET states that if an attack pattern is confirmed, the service stops its escalation and blocks further access to the environment.

Prerequisites and limits from ESET's documentation:

  • You need the ESET PROTECT MDR or ESET PROTECT MDR Ultimate tier.
  • ESET MDR is only available in selected service-enabled markets.
  • After you activate the subscription, one report server task is scheduled automatically, using the email address assigned to the administrator. Critical notifications and weekly or monthly reports go to the login email address.
  • Scheduling MDR reports needs the ESET MDR reports Write permission and Server Tasks and Triggers, Generate Report, Use and Write.
  • The weekly report is generated every Monday and the monthly report on the first day of each month, only while the MDR tier is active. Depending on tier, you can generate the ESET MDR or the ESET MDR Ultimate report.
  • Reports can be sent as a link to ESET PROTECT instead of a PDF attachment. If you do not choose Send report as a link, the quarterly MDR Threat Report is also attached to the monthly report.

NHI Mgmt Group recommendations for MDR

  • Check that the administrator login email used for critical notifications is a monitored shared mailbox or routes into your incident process. A notification sent to one person on leave is a gap.
  • Agree in writing which containment actions the service may take on which groups, and test the escalation path with a tabletop exercise.
  • Prefer Send report as a link, so incident detail stays inside the console under its access controls rather than in mail attachments.
  • Keep the SOC's own monitoring of console changes, because a managed service watching endpoints does not replace your review of who changed policies and exclusions.

For the general trade-offs between running detection in-house and buying a managed service, see EDR vs MDR.

Monitoring console changes

ESET PROTECT provides an audit log, audit log notifications and an audit log report. NHI Mgmt Group recommends using them to watch the changes that most often precede an endpoint compromise or follow an insider mistake:

  • Any change to a policy assigned to All or to server groups.
  • Any new or edited AV or EDR exclusion.
  • Any new console user, new permission set or change in permission set assignment.
  • Use of Run Command and other high-impact client tasks.
  • Changes to the Agent password protection policy.

Forward these events to your SIEM where possible, and review them weekly with the platform owner. The goal is that no exclusion or forced setting change goes unnoticed for more than a working day.

Common failure patterns

  • Partial Force. One setting in a feature is forced while related ones stay at Apply, so a lower policy produces a mixed state. ESET warns about exactly this.
  • Assumed order. Teams assume a regional policy applies after the baseline, but the Applied policies view shows otherwise.
  • Additive access creep. Users collect several permission sets over time and end up with combined rights nobody approved.
  • Run Command for everyone. A powerful client task is available to regional or help desk users.
  • Unprotected Agent. Password protected setup is not set, or the password sits in a document with no owner and has never been rotated.
  • Migrated exclusions left in the home group. Because original assignments are not preserved, exclusions end up broader or narrower than intended.
  • Broad EDR exclusions. Path-only criteria scoped to any ancestor process, created in a hurry during an incident and never reviewed.
  • MDR alerts to one inbox. Critical notifications go to a single administrator address that nobody else watches.

Practitioner checklist

  • Map your static group tree and confirm which policies sit on All.
  • List every forced setting in the baseline and confirm related settings in the same section are forced consistently.
  • Record the Applied policies view for representative computers before and after each policy change.
  • Test new policies on one computer first, then assign by group, not by individual computer.
  • Review every console user's combined permission sets each quarter.
  • Restrict Client Tasks, Run Command to named platform owners.
  • Remove Permission Sets and Mapped accounts permissions from non-administrators.
  • Limit audit log permissions to auditors and the security team.
  • Set and force Password protected setup for the ESET Management Agent; vault the password with an owner and rotation date.
  • Export AV and EDR exclusions monthly; check owner, reason and review date for each.
  • Reassign every migrated AV exclusion deliberately.
  • Confirm your MDR tier, market availability and the mailbox receiving critical notifications.
  • Alert on policy, exclusion, permission and Run Command changes from the audit log.

Standards and references

Related NHI Mgmt Group resources: NIST CSF 2.0 Protect Function Guide · EDR Guide · Endpoint Hardening Checklist · Securing the EDR and XDR platform itself

PDF for subscribers

Take this guide with you

Every section, table and checklist in one PDF, with links to the sources and related guides. Subscribe to our weekly NHI & AI Identity Journal and we’ll email you a download link.

Free weekly newsletter

Subscribe to the NHI & AI Identity Journal

The latest on NHI and Agentic AI security – articles, research, breaches, news and events every week.

Bonus 33% off our NHI Course when you subscribe.

PDF Downloads for Newsletter Subscribers

Get the guide

Enter your details and we’ll email you a download link.

The full guide is free to read online. The PDF is a thank you for subscribing.

Fill in all fields marked * and tick both boxes to continue.