Consolidating ESET Inspect into ESET PROTECT (OpenXDR)
UPDATED August 24, 2026:
Summary
This page explains how ESET Inspect cloud workflows move into ESET PROTECT, who is affected, what actions are required, and when the standalone ESET Inspect console will be terminated.
We are consolidating the Endpoint Detection and Response (EDR) and Extended Detection and Response (XDR) capabilities of ESET Inspect directly into ESET PROTECT, so that endpoint protection, detection and response are managed in a single console. The standalone ESET Inspect console will undergo termination and will reach End of Life.
|
The EDR/XDR capabilities will not reach End of Life. They will remain available in ESET PROTECT. |
Who is affected?
•This change affects cloud customers who currently use the ESET Inspect console and partners who manage those customer environments.
•This change does not affect ESET Inspect On-Prem customers or customers who use ESET PROTECT without ESET Inspect.
What is not affected
•ESET Inspect On-Prem—a separate application, not affected by anything described here.
•Your subscription—no new subscription or activation step. EDR/XDR capabilities are enabled in ESET PROTECT based on the subscription you already hold.
Required actions
1.Keep ESET Inspect Connector up to date. Version 3.2, planned for October 2026, is required to use EDR/XDR without the ESET Inspect console. ESET began to enable automatic ESET Inspect Connector updates gradually on July 31, 2026. After the version 3.2 release, ESET Inspect Connector installations that have automatic updates enabled will receive the update without action from you.
Use ESET PROTECT to check the ESET Inspect Connector version on your devices. If a device has an older version and does not update automatically, update the ESET Inspect Connector manually. If updates do not apply, make sure that your network does not block ESET update servers. For more information, refer to Repository required for deployment.
2.Start working in ESET PROTECT. Several capabilities are already there and the rest arrive with ESET PROTECT 7.3.
3.If you use an API through ESET Connect or the ESET Inspect alerts Syslog export, plan for a migration when replacement capabilities become available. See the section below.
No further action is required. ESET automatically migrates your rules, exclusions, and blocked hashes, with no configuration work on your side.
What changes in daily work
The following changes apply:
ESET Inspect |
ESET PROTECT |
What happens |
|---|---|---|
Detections |
Indicators |
Review Indicators in Advanced Search. |
Detection investigations |
Incidents |
Perform investigations in Incidents. |
Rules |
EDR Rules |
Name and location change. |
Exclusions |
EDR Exclusions |
Name and location change. |
ESET AI Advisor |
ESET LiveAI |
Name change. |
Blocked hashes |
Blocked executables |
Name change. |
Some capabilities will be removed from the ESET Inspect console when their replacements become available in ESET PROTECT On-Prem. In most cases, removal will occur before ESET terminates your ESET Inspect console.
After the planned release of ESET PROTECT 7.3, ESET will gradually migrate rules, exclusions, and blocked hashes. Customers will not be migrated at the same time. After migration, you can use these capabilities in ESET PROTECT while your ESET Inspect console remains available.
Unchanged features
The following features keep the current name and function:
•Terminal
Timeline
Dates marked as planned are targets and can change.
When |
What happens |
|---|---|
From 31 July, 2026 |
Automatic updates of the ESET Inspect Connector begin gradually. Customers with restricted environments must update the ESET Inspect Connector manually. |
September–October 2026 (planned) |
ESET PROTECT 7.3 adds the remaining EDR/XDR capabilities. ESET Inspect Connector 3.2 is released. ESET automatically migrates rules, exclusions, and blocked hashes. New and newly eligible EDR/XDR customers start directly in ESET PROTECT. ESET no longer deploys new standalone ESET Inspect consoles. |
October 2026–March 2027 (planned) |
ESET terminates the ESET Inspect console for customers who have not logged in during the previous 90 days and do not use an API through ESET Connect or Syslog export. |
January 2027–June 2027 (planned) |
ESET terminates the ESET Inspect console for customers who have logged in during the previous 90 days but do not use an API through ESET Connect or Syslog export. Customers must update ESET Inspect Connector installations to version 3.2 or later before ESET Inspect console termination. |
July 2027–December 2027 (planned) |
ESET terminates the ESET Inspect console for customers who use an API through ESET Connect or Syslog export after the replacement capabilities become available and the six-month migration period ends. If you use both integrations, your console remains available until the migration period for both replacements ends. |
Before your ESET Inspect console is terminated
The termination process depends on your scheduled termination date.
Termination from late 2026 through early 2027
You will receive information through external announcements on ESET websites. You will not receive an in-application notification or a transition period. Access to the ESET Inspect console will end on your scheduled termination date.
Termination later in 2027
You will receive notifications in the ESET Inspect console:
•60 days before termination: You receive the termination date and information about where to find the capabilities in ESET PROTECT.
•30 days before termination: The console becomes read-only. You can view historical data, but you must make configuration changes in ESET PROTECT.
•On the termination date: The console is terminated. Links, bookmarks, and login attempts redirect you to ESET PROTECT.
ESET Inspect capabilities remain available in ESET PROTECT. ESET Inspect will no longer operate as a separate console.
What ESET migrates to ESET PROTECT
Data that ESET migrates
ESET automatically migrates the following data to ESET PROTECT:
•Rules
•Exclusions
•Blocked hashes
ESET converts existing Mark as Safe—Executable entries to EDR exclusions. Existing suppression logic continues to operate. Incidents are already stored in ESET PROTECT and remain available after the ESET Inspect console is terminated.
Historical data
Advanced Search Indicators use a data model that differs from the ESET Inspect Detection data model. Therefore, ESET does not convert existing Detection records to Indicators.
ESET PROTECT collects Indicators in parallel with ESET Inspect Detections. Indicator history will be available in ESET PROTECT when your ESET Inspect console is terminated. Indicator collection requires ESET Inspect Connector 3.0 or later.
When ESET terminates the ESET Inspect console, you will lose access to ESET Inspect Detection records. Indicators and Incidents in ESET PROTECT will provide the primary investigation and response workflows.
Features that are not carried over
The following ESET Inspect features will not be available in ESET PROTECT:
•Rerun Rule
•Executables list
•Scripts list
•Mark Detection as Resolved
•Creation of Mark as Safe—Executable entries
After ESET terminates the ESET Inspect console, ESET will reassess these features based on customer demand.
If a listed feature is important to your operations, use Submit Feedback in ESET PROTECT. You can also contact your ESET representative or partner.
If you use API through ESET Connect or Syslog export for ESET Inspect alerts
