A lot of work has gone into this next release and we are excited for you to try it out.
Changelog
- New Subsystem: Unmanned Aerial Vehicle (UAV)
- New Feature: Organization and Tenant Quotas
- New Feature: Tenant Data Retention Time Configuration and New Database Management System
- New Feature: Filters and Table Sorting for All 802.11 (WiFi) Pages
- New Feature: Latitude/Longitude Coordinate Locations of Taps
- New Feature: Cursor on Target (CoT) Output
- Improvement: New Colors and Fonts Across the Web Interface
- Improvement: Multi-Factor Authentication Settings and Flow
- Improvement: New Tab Navigation for Complex Pages
- Improvement: New Fuzzing Suite to Stress-Test Parsers (by Adriano Maia – Thank You!)
- Improvement: Database Migrations Now Run on Demand
- Many Small Bug Fixes and Improvements Across the Entire System
New Subsystem: Unmanned Aerial Vehicle (UAV)
This release introduces an entirely new Nzyme subsystem dedicated to drone detection. Drones are increasingly used in physical intrusions—especially during reconnaissance—and this subsystem lays the foundation for defending against such threats.
How Does Nzyme Detect Drones?
In its initial version, the UAV subsystem identifies drones by decoding their Remote ID emissions—a global standard that allows drones to broadcast identifying information. Many modern drones support this feature due to international regulations.
Subsystem Features
- No extra hardware needed. Leverages your existing WiFi sensors.
- Live drone tracking. See drone positions and flight paths on a map within the Nzyme web interface.
- Drone classifications. Mark drones as Neutral, Friendly, or Hostile based on serial numbers. These can be pre-configured before detection.
- Alerting system. Get notified when drones are detected.
- Nzyme Connect integrates with your system to provide intelligence on hundreds of known drone models and categories (e.g., Photo/Video, Agricultural, Industrial, Inspection, Public Safety).
- Integration with TAK/ATAK. Drone locations and metadata can be forwarded via the new Cursor on Target output.
- Fully optional. The subsystem can be disabled entirely if not needed.
Here’s a quick overview of Remote ID requirements around the world:
North America
The FAA requires all drones that must be registered and were manufactured after December 2022 to include Standard Remote ID. Older drones may still fly with an approved add-on module.
South America
As of now, no country in the region mandates Remote ID. Brazil’s ANAC RBAC‑E94 covers drone registration and operational limits but not identification.
Europe
EU Regulation 2019/945 mandates Direct Remote ID for any drone bearing a C1 (<900g or impact energy <80J), C2, or C3 class label and placed on the market after January 1, 2024. Older drones must use an add-on module when operating in the Specific category.
Asia
Japan: Since June 20, 2022, all drones weighing over 100g must broadcast Remote ID (built-in or external) to be legally registered.
What About Drones Without Remote ID?
Future Nzyme versions will integrate Software Defined Radio (SDR) and other techniques to detect drones that do not emit Remote ID signals. The subsystem is designed to easily accommodate these future enhancements.
For now, consider how Remote ID-equipped drones fit into your threat model. Many Nzyme users have reported valuable insights from detecting such drones—even when no action is required. For instance, a drone might be spotted near your facility but is actually conducting a legitimate inspection on neighboring property. With Nzyme, you can confirm this directly from the web interface.
As drone deliveries and recreational use expand, especially in uncontrolled airspace, this kind of situational awareness becomes increasingly critical.
New Feature: Organization and Tenant Quotas
You can now enforce usage limits for organizations and tenants. By default, all usage is unrestricted, but users with the required permissions can optionally apply quotas to the following resources:
- Number of taps
- Number of users
- Number of tenants
- Number of integrations
New Feature: Tenant Data Retention Time Configuration and New Database Management System
Previously, data retention settings in Nzyme were configured globally across the entire cluster. With this update, you can now define data retention periods on a per-tenant basis, giving you more flexibility to tailor retention policies for each tenant’s needs.
These settings can be managed by super administrators or organization administrators for all tenants within their organization.
When upgrading to this version, your existing global data retention settings will automatically be applied to all tenants by default.
New Feature: Latitude/Longitude Coordinate Locations of Taps
Taps can now be placed not only on floor plans but also on a world map using longitude and latitude coordinates. This allows you to understand the tap’s location within a broader geographical context and lays the groundwork for future use with upcoming Nzyme outdoor sensors.
Note: Until these outdoor sensors become available, no trilateration or location-based calculations are performed using the map coordinates.
New Feature: Cursor on Target Output
Cursor on Target is a widely adopted protocol for sharing real-time information with command and control or situational awareness systems used by military, public safety organizations, and private companies. Nzyme now supports forwarding data using both plaintext and TLS-encrypted Cursor on Target messages.
Currently, the transmitted data includes tap locations and UAV positions. Support for additional detected threats and their locations will be added in future versions.
This feature is configured on a per-tenant basis and is governed by the new tenant quota system.
New Feature: Filters and Table Sorting for All 802.11 (WiFi) Pages
Data on the 802.11 (WiFi) BSSID and client pages can now be sorted and filtered.
Improvement: New Colors and Fonts Across the Web Interface
We’ve refreshed the colors and fonts across the entire web interface to align with the new Nzyme brand identity. The result is a cleaner, more modern look that enhances usability.
Stay tuned—a brand-new website is also launching in the coming weeks!
Improvement: Multi-Factor Authentication Settings and Flow
Multi-factor authentication (MFA) can now be disabled for all user types. While this is generally not recommended for security reasons, it may be useful in specific scenarios where MFA presents operational challenges.
Additionally, the MFA setup process has been improved to require users to confirm a valid OTP token before proceeding. This helps prevent misconfigurations and reduces the risk of users locking themselves out due to incorrect setup.
Improvement: New Tab Navigation for Complex Pages
As Nzyme continues to grow, some areas of the web interface became too crowded. To improve usability, we’ve introduced a new tabbed navigation system on selected pages. This allows for a cleaner layout and a more focused experience for specific use cases.
Improvement: New Fuzzing Suite to Stress-Test Parsers
One of the core responsibilities of a Nzyme tap is to process massive volumes of byte arrays arriving at very high speed. The protocols we parse—such as 802.11, Ethernet, and various IP-based protocols—are often complex and require precise buffer cursor navigation. This is a high-risk area for subtle bugs and edge cases.
While our use of Rust (we write Rust btw) provides strong memory safety and guards against common vulnerabilities like buffer overflows and use-after-free bugs, it doesn’t eliminate all risks. Parser logic can still crash if it encounters unexpected or malformed input.
To harden this critical part of the system, Adriano Maia integrated a fuzzing suite
using cargo-fuzz. This tool generates random, semi-valid inputs to stress-test our parsers and uncover crashes or
panics. His initial runs have already revealed several bugs in our protocol parsers—which he also already fixed.
This is a big step forward in ensuring long-term stability and robustness. We’re planning to integrate the fuzzer into our continuous integration pipeline to catch future issues early.
Huge thanks to Adriano for the initiative—we’re excited to see where this leads!
Improvement: Database Migrations Now Run on Demand
Previously, Nzyme automatically applied all database migrations on startup. This approach sometimes caused issues—such as nodes failing to start if another node was holding a database lock during migration—and increased the risk of deadlocks that required manual intervention.
With this update, database migrations have been moved to a separate command, improving reliability and control during upgrades.
Full instructions for running the new migration command are available in the documentation and upgrade notes.
Download & Upgrading
All packages are available for download on the downloads page. Upgrading is easy. Please follow the release notes on the downloads page.
New installations should follow the installation documentation.
How can I help?
You are some of the first users to try out nzyme v2.0.0, and we are looking for any kind of feedback:
- What didn’t work, what bugs did you experience?
- What was confusing or seemingly unnecessarily complex?
- What is missing?
- What do you think should be changed?
Again, this is an early release and no feelings will be hurt.
You can file issues on GitHub, join the nzyme Discord or post in the discussion forums to provide your feedback or ask questions.
