Choose the correct Carbon Black product and connector.
Carbon Black product families should not be treated as one interchangeable API. Start the evaluation by identifying the product, cloud region or server and device population that the connector must read.
The published EasyNAC matrix lists CB Response 6.x+ and Carbon Black Endpoint Standard Cloud. These are the documented product scopes; confirm current naming, release compatibility and support before deployment.
Connect the supported endpoint-security integration and AD where your access design requires it. Default Auto Trust includes AD-joined and XDR-managed checks. Confirm the current management recognition, then validate any supported health requirements separately.
Connect the integration.
- Deploy the EasyNAC appliance or VM, configure its IP and review discovered devices.
- Select Cb Response or Cloud and supply the corresponding server/token or Cloud API credentials. Set the query interval and test the connection against a representative device.
- 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 Cb Response or Carbon Black Cloud.
The connector provides a Cb Response or Cloud version selection. Cb Response uses its server connection and token; the Cloud configuration includes API ID, API Secret Key and Org Key. Select the product you operate and verify the fields it returns.
- Enrollment and a sensor that is deregistered, uninstalled, inactive, out of date, in bypass mode or in quarantine.
- Devices that have not connected within a configured number of days.
- Protection conditions including an inactive scanner, old AV signatures, disabled signature updates, disabled on-access or on-demand scanning and disabled product updates.
These are documented connector conditions. Available values depend on the selected Carbon Black product; do not assume every condition is returned by both versions.
Separate enrollment from sensor and protection health.
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.
An enrolled endpoint can still be reported with an inactive sensor or bypass mode. Use those distinct conditions to explain why a managed device may receive restricted access. Quarantine is a reported status check; it does not establish that the connector sends quarantine commands.
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 |
|---|---|
| Product scope | Record the selected Cb Response or Cloud mode and inspect the conditions returned for the test endpoint. |
| Enrollment | Match the enrolled endpoint and confirm its managed-device access reason. |
| Sensor condition | Verify an available bypass, inactive or out-of-date sensor condition and the intended policy response. |
| Recovery | Restore the tested condition and confirm the refreshed tag and intended access. |
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.
Include the selected product’s API access, credential scope, cloud endpoint or server changes and upgrade planning in the maintenance checklist. Revalidate mappings after a migration between product families.
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.
Does enrollment alone prove the sensor is protecting the endpoint?
No. Enrollment, sensor activity, bypass mode and other documented conditions are separate. Check the values returned by the selected Carbon Black product.
Are all documented conditions available in both Carbon Black modes?
Do not assume they are. Select Cb Response or Cloud and validate the returned conditions for that product and release.
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.