Aviz Networks ONES Audit Service details audit logging and event forwarding

Aviz Networks ONES Audit Service provides a built-in, chronological record of actions across the ONES platform, capturing who did what, when, and via which interface. The feature supports troubleshooting and operational accountability for enterprise network and security teams managing frequent configuration and policy changes.

Research Overview

The blog describes ONES as a centralized network operations environment where multiple engineers perform day-to-day workflows that include switching configuration, telemetry-related tasks, integrations, and policy management. It frames auditing as a response to the question of accountability when network issues occur during ongoing work.

Within that context, the Audit Service component records platform activity from both the user interface and the API. The blog positions the audit log as a way to reconstruct activity without relying on memory or extended investigation.

Key Findings

According to the blog, ONES maintains an activity log that is chronologically organized and identifies each action in a single location. For each recorded event, the log captures operator name and role, the action and the object it affected, an exact timestamp, and whether the change came from UI or API access.

The blog also states that navigation within ONES is recorded, enabling users to see where an operator browsed before making changes. It describes a “View Related” option that exposes related navigation, modifications, status updates, and other connected activity.

Technical Breakdown

The blog states that audit logging happens automatically as mutations occur, such as user updates or rule toggles. It says logging is performed on the server side when the change occurs at the root source.

Because logging does not rely on the frontend recalling to ping a separate endpoint, the blog states it is impossible for a mutation to go unrecorded regardless of what happens on the frontend. It also describes filtering to quickly locate specific events based on attributes such as user, action type, or location within the platform, with results appearing almost instantly.

Operational Impact

For troubleshooting and investigations, the blog describes reconstructing what happened around a specific event, including the sequence of related actions. It uses the example of device deletion, stating that operators can see who deleted the device, how and when, and what was occurring around the time of the decision.

For reporting and integration, the blog says the activity log can be exported to CSV and can be forwarded in real time via a Syslog Connector to an existing Syslog server outside of ONES. It also states that audit logs are part of the product by default and start recording automatically from the moment the platform is in use.

Overall, the blog describes ONES Audit Service as an always-on, searchable audit trail that records platform changes and related user navigation, with options to export or stream audit events through Syslog. This Blog Signals brief is a fact-based summary of the vendor blog.

Blog post, originally published by Dipanjan Kamilya at aviznetworks.com.