Deployment guide

Deploy agentless NAC. One clear step at a time.

Start with a standalone network. Configure the appliance, recognize managed devices and prove the access controls work.

Free resource. No email required.

01Connect + configure
02Discover + trust
03Enable + test

Define a useful first deployment.

Choose a representative office network and agree what authorized and unknown devices should be able to reach. Include a managed computer and an unknown test device. Identify essential services before applying restrictions.

A standalone evaluation needs an EasyNAC appliance or VM, the intended network connection and the information for your selected integrations. CVM is optional central management for multiple appliances; it is not a prerequisite for this first deployment.

1. Connect the appliance or deploy the VM.

Connect the appliance or import the EasyNAC virtual appliance, then configure its IP address. Use the installation and configuration guide for the exact setup sequence and your hypervisor quick start for VM preparation.

Keep the initial scope simple. Additional subnets and branches require appropriate appliance or sensor coverage, which you can plan after the standalone workflow is proven.

2. Review discovered devices.

Allow EasyNAC to discover and profile the devices on the protected network. Review the inventory with the team that knows the environment. Identify managed computers, printers, guest devices and anything that needs attention.

Start with visibility before enabling broader enforcement. Confirm that required devices are present and that the information used by your trust rules corresponds to the device you are testing.

3. Configure Auto Trust Policy.

Connect Active Directory and your supported XDR platform. Configure the AD joined machine and XDR managed machine checks needed for your policy so managed devices can be authorized automatically.

Define the intended access for devices that do not meet your rules. Keep guest approval, essential equipment and temporary exceptions clear. You do not need separate Windows or macOS supplicant profiles for this agentless workflow.

4. Enable protection and test the result.

Connect the unknown test device. Confirm that protected resources are blocked and that the configured captive portal is reachable where it is part of your access policy. Then verify that authorized devices retain the access needed for normal work.

Test how access is restored after approval or remediation. Review the device and event records so the team can explain why access was allowed or restricted. Use the Evaluation Kit for the ten practical tests and editable scorecard; this page explains the deployment sequence.

Expand after the first network works.

Use remotely deployed software Enforcer Sensors for suitable branch networks. For larger regional environments, set up head-office EasyNAC first, then use optional CVM management to send configuration and policy to the other EasyNAC appliances.

Plan timing around your organization’s change process and test scope. EasyNAC does not require introducing switch 802.1X authentication for this approach, and can coexist with an existing 802.1X deployment.

From reading to a real pilot

See how EasyNAC fits your network.

Use the standalone Evaluation Kit for practical tests, a deployment checklist and an editable scorecard. Bring your network questions to the EasyNAC team.

Choose which optional services EasyNAC may use. You can change your choice at any time using Cookie preferences in the footer.

Your choice is remembered for 180 days in this browser. Read our Privacy Policy.