Integration
ESET PROTECT in IDA: protection status on the device, not in a second console
ESET PROTECT knows which machine is protected. IDA fetches that through ESET Connect and attaches it to the device in the inventory - visible where the ticket is worked, and not only after something has happened.
BetaThis integration is built and usable, but has not yet run against a production third-party system - it was written against the vendor’s public interface documentation. Expect some follow-up work on first connection. We would rather say so up front than let you find out.
What IDA reads from ESET PROTECT
- Managed devices per company and device group
- Protection and agent status per device
- Operating system and last contact
What IDA does with it
- The protection status sits on the device in the inventory - no second portal for the question is that machine protected
- Devices still listed in two consoles after a migration stand out: that is the clean-up list that ends duplicate licence cost
- The status carries its age: if a device has not reported for 14 days the indicator turns grey rather than green - an old reading is not an all-clear
Who it is for
IT service providers whose customers run ESET - even when other customers are on a different vendor at the same time.
Setup: Store ESET Connect credentials and choose the region (EU, DE, US, CA, JP). The region is part of the address, not just a setting - the wrong host will not find the account.
Every integration in IDA has its own switch. Turn it off and it disappears completely - including the columns, filters and reports that belong to it. You only see what you actually use.
Vendor website: ESET PROTECT. ESET PROTECT is a trademark of its respective owner; IDA connects to the system technically, which implies no partnership.
Related
- Bitdefender GravityZone - Security & backup
- OCS Inventory - Inventory & deployment
- Device offboarding - Processes
Questions about the ESET PROTECT integration
Do ESET and Bitdefender GravityZone exclude each other?
No, both can be connected at the same time. A service provider looks after customers on different products; an exclusion would force a decision for the entire estate. Even on a single device a double entry is not a data error but the normal state during a migration.
Can IDA deploy software or trigger tasks through ESET?
No. IDA reads the estate and shows it alongside customer, device and ticket. Deployment and policies stay in the ESET console.
Do security incidents come into IDA?
Deliberately not. An incident belongs with whoever works it, and the security console is the right place for that. IDA brings the estate and the protection status to where tickets, contracts and billing live.
Everything in one interface - for you too
30 days free, no payment details. Every integration is included at no extra cost.