Is an external source of truth required to define rules?

No. Rules are written in Avalon and evaluated against data collected from the devices.

Is the report usable outside the network team?

Yes. It gives the compliance rate per device and per rule, exports as PDF or spreadsheet and carries your logo, which makes it a document that can be shared with the security officer. A device the rule does not concern shows as out of scope rather than counted compliant, which avoids the flattering rate nobody can defend in an audit.

Does auditing disturb the network?

No, collection reads the state of the devices. Only remediation actions change a configuration, and they are explicitly triggered.

Network compliance checking

A configuration that is compliant on delivery day does not stay that way. Interventions accumulate, urgencies leave traces, and the gap between the target and the field grows without anyone measuring it. Compliance checking means continuously verifying that the network still looks like what was decided.

Request a trial

Rules written once, evaluated continuously

A rule describes a requirement about the real state of devices, for example that loop detection is enabled on every access port, or that access control is in place on the relevant ports. The audit runs on a schedule and produces a report readable by engineers and management alike.

Rules defined by the team, with no imposed method
Scheduled audits across all or part of the estate
Two distinct rates: fully compliant devices, and compliant rows or ports
A device with nothing to evaluate is out of scope, not compliant by default
A trend over time that flags scope changes and rule definition changes
Report exported as PDF or spreadsheet, carrying your logo

The necessary counterpart of security projects

Deploying access control, DHCP snooping or dynamic ARP inspection is only worth it if it holds over time. Compliance checking turns a one-off project into a verifiable state, and provides the evidence expected during an audit or a regulatory compliance programme.

From detection to remediation

Detecting drift is a first step. Avalon then lets the target configuration be reapplied to the affected devices only, with a dry run first, so a whole estate is not touched to fix a handful of cases.

Frequently asked questions

Is an external source of truth required to define rules?: No. Rules are written in Avalon and evaluated against data collected from the devices.
Is the report usable outside the network team?: Yes. It gives the compliance rate per device and per rule, exports as PDF or spreadsheet and carries your logo, which makes it a document that can be shared with the security officer. A device the rule does not concern shows as out of scope rather than counted compliant, which avoids the flattering rate nobody can defend in an audit.
Does auditing disturb the network?: No, collection reads the state of the devices. Only remediation actions change a configuration, and they are explicitly triggered.

Offers

Avalon is available under a transparent yearly subscription, based on the number of managed IP devices alone.

Yearly subscription, no hidden fees
One license per device (switch stacks count as a single license)
Decreasing cost per device as your network scales
Guaranteed price stability, with no unexpected increases year over year
Every feature included, no add-on modules

Designed with network engineers

Benefit from a platform shaped through real-world deployments and continuous collaboration with network teams.

Real customers!

University Hospital of Limoges — Olivier H. Network Administrator

Airbus Atlantic — Mathieu S. Network & Security Architect

Measure the gap between your target and your real network

Thirty days, up to 500 devices, on your infrastructure, with no meeting to sit through. The first audit will tell you where you actually stand.