Signature Updates
Signature updates in Netify Agent v5 enable automatic synchronization of application, protocol, and intelligence classification definitions. These signatures are the core dataset that drives accurate Deep Packet Inspection (DPI) and application identification across your network.
Netify offers both community and commercial signature lists. The community list provides a base foundation, while the commercial list delivers extensive coverage of modern applications and emerging threats. This guide explains how to access and configure signature updates, the different methods available, and how to verify which signature set is active in your deployment.
Access and License to Use
Anyone is permitted to use the Community application signature list.
Integrator API
The Integrator API is restricted to Netify clients who have been issued a Netify API Vendor key. Documentation to pull application signature updates from the Netify API can be found here.
Pushing a new application signatures file to an endpoint requires a 'HUP' message to be sent to the agent to begin using it by running:
sudo systemctl reload netifydDetermining which Signature List is in Use
If you are unsure of which application signature list your Netify agent is using, run:
$ netifyd -s
Netify Agent/5.0.56-HEAD-2616-4bc869c2 (debian; linux-gnu; x86_64; conntrack; netlink; dns-cache; tpv3; tcmalloc; regex)
✓ agent is running: PID 18154
• agent timestamp: Thu Oct 24 12:23:33 2024
...
• apps: 199, domains: 3374, networks: 783, soft-dissectors: 26, transforms: 0Look for a line listing the apps, domains, networks and other counters. If this output indicates fewer than 200 applications (e.g., apps: 199), this is an indication that you are using the community application list.