Start with the product and module that provide the evidence.
ManageEngine is a product family. Endpoint inventory, patch assessment and other modules supply different information; support for one module should not be presented as support for every ManageEngine service.
The published EasyNAC matrix lists ManageEngine Patch Manager and Endpoint Central, on-premises or cloud, with API v1.3/v1.4 references. Confirm the exact product name, deployment and current connector compatibility.
Use the connector’s supported management information with the access requirements defined for your environment. Management, enrollment and health are different kinds of evidence. Confirm which supported policy conditions apply to this connector rather than treating it as an interchangeable XDR source.
Connect the integration.
- Deploy the EasyNAC appliance or VM, configure its IP and review discovered devices.
- Select Endpoint Central or Patch Manager Plus, then its cloud or on-premises deployment. Use the corresponding server credentials or OAuth configuration; for Endpoint Central, also select the edition and MSP customer where applicable.
- Confirm the managed-device recognition used by default Auto Trust, then select any additional documented health conditions required by your access policy.
- Use a managed test endpoint and an unapproved test device to verify access, restrictions and recovery.
Choose Endpoint Central or Patch Manager Plus.
EasyNAC has separate connectors for ManageEngine Endpoint Central and Patch Manager Plus. Both support on-premises and cloud deployment configurations; use the connector for the product supplying your device information.
- Endpoint Central: computer enrollment, mobile enrollment, Unknown / Healthy / Vulnerable / Highly Vulnerable system-health categories and devices that have not reported within a configured period.
- Patch Manager Plus: enrollment, highly vulnerable devices and devices that have not reported within a configured period. Its help describes highly vulnerable devices as having critical or important patches pending installation.
Endpoint Central additionally offers MSP and Enterprise edition selections. For MSP, the configuration identifies the customer being queried.
Use the source health category in access decisions.
The connector applies tags when enabled conditions match the information reported by the source. EasyNAC uses those tags in Auto Trust and role-based access decisions. Managed-device recognition and additional health requirements serve different purposes: the resulting access follows the policy in use.
A useful pilot distinguishes an enrolled device from one reported as Highly Vulnerable. Verify the source category, the tag applied by the correct connector and the intended access outcome. Keep the management connectivity needed for patching available under any restricted role.
Checks refresh on the configured query interval; they are not an instantaneous live assessment of every endpoint. After correcting a condition, confirm the source has reported the change and EasyNAC has refreshed its information before checking restored access.
Prove the access outcome.
| Pilot case | What to demonstrate |
|---|---|
| Connector and scope | Confirm Endpoint Central or Patch Manager Plus, cloud/on-premises deployment and the correct organization or MSP customer. |
| Enrollment | Match a managed computer, or a mobile device supported by the Endpoint Central enrollment condition. |
| Health category | Verify the appropriate source-reported health or Highly Vulnerable condition and its configured access outcome. |
| Patching and recovery | After remediation and source reporting, confirm the refreshed tag and restored access while preserving required management services. |
Record the source condition, EasyNAC tag, policy reason and access result in the Evaluation Kit scorecard. Agree the test and recovery procedure with your security team before changing endpoint conditions.
Keep the integration useful after deployment.
Review API compatibility before upgrades, maintain the appropriate credential scope and keep server connectivity and reporting jobs healthy. Define how missing scans, stale inventory or a changed device identity should affect access.
Expand only after the first network’s device matching, access and recovery behavior is understood. Review EasyNAC appliances, remote Enforcer Sensors and optional CVM when planning branches or regions.
Common questions.
Are Endpoint Central and Patch Manager Plus the same integration?
No. They are separate EasyNAC connectors with different documented conditions. Endpoint Central includes computer/mobile enrollment and system-health categories; Patch Manager Plus includes enrollment and highly vulnerable status.
Does EasyNAC install the missing patches?
The integration queries ManageEngine and tags the reported conditions for access decisions. Patch deployment remains with ManageEngine and your endpoint-management process.
Sources and deployment scope.
Prepared by InfoExpress, Inc., the company behind EasyNAC. The connector checks described here were verified against the EasyNAC appliance help on 14 October 2026. Product API references provide source-platform background. Confirm availability for your connector version and source-product configuration.
Test it on your network.
Agree the requirements, connect a representative endpoint and record the actual result.