ACL Requirements for Auvik Integration

To ensure seamless monitoring, configuration management, and traffic analysis with Auvik, it's critical to configure your network's firewalls and ACLs to permit required communication between the Auvik collector, managed devices, and Auvik's cloud services. This guide outlines the essential TCP and UDP ports that must be open for proper collector operation, including flow export (NetFlow, sFlow, IPFIX), Syslog ingestion, and other discovery protocols. Following these recommendations will help maintain visibility, support device discovery, and enable accurate traffic analytics within your Auvik environment.

Note: Auvik does not apply or manage ACLs on your devices. You must configure your network device ACLs or firewalls to allow the Auvik collector to communicate with managed devices.

Best Practices

• Create ACLs/firewall rules that explicitly allow required traffic from the Auvik Collector to managed devices.
• Deny all other inbound management traffic to enforce least privilege.
• Ensure ACLs do not block LLDP, CDP, FDP, or EDP if you want full topology mapping.
• Use custom ports where applicable in Auvik:
  • Go to Admin → Discovery → Discovery Settings → Service Settings
  • Or use Inventory → All Services → Add Service → Port Check for TCP services.
     

How Auvik Traffic Flow Works

Collector-Based Architecture

Device → Auvik Collector → [Firewall/ACLs] → Auvik Cloud

Endpoint Agent Architecture

Server/Workstation → Auvik Endpoint Agent → [Firewall/ACLs] → Auvik Cloud

SaaS Agent Architecture

Workstation → Auvik SaaS Agent → [Firewall/ACLs] → Auvik Cloud

Required Protocols and Ports for Auvik

Configurable Ports in Auvik

To adjust SNMP, SSH, Telnet, HTTP/HTTPS, or WMI/WinRM ports, you can go to Admin → Discovery → Discovery Settings → Service Settings

Optionally use Inventory → All Services → Add Service → Port Check

 

Further Help

For help configuring non-standard HTTP/HTTPS ports for remote connections, click here.