Compliance Management Use Cases

Services such as L2/L3 VPNs, L2/L3 services, EVPN services etc  provisioned using ATOM’s service orchestration are constantly monitored by ATOM for any out-of-band changes. ATOM ensures 100% compliance by notifying and remediating any configuration discrepancies.

ATOM detects any software non-compliance to the golden software version in any network and trigger upgrade workflows for the relevant vendor to ensure software compliance

Policies to ensure ACLs on the VTY lines are part of ATOM. It detects any non-compliance and helps you remediate it to ensure compliance to Day-0/Day-1 policies.

Policies to ensure HTTP is disabled across the network are part of ATOM. It detects any non-compliant CLIs on the device, reports it and allows you to remediate them.

If you prefer to disable CDP and LLDP globally or on interfaces bearing public IPs across the network, ATOM has policies that can detect the interfaces having public IPs across all the devices in the network, and disable CDP, and LLDP under those interfaces. ATOM will ensure compliance with this policy at all times.

Mandatory day-0 configurations such as password encryption CLIs are part of ATOM’s compliance policies. ATOM detects and remediates this to ensure CLI compliance

Do you have standard QoS policies to be maintained as per your customer requirements?  ATOM has policies that can detect any changes to QoS policies at a scheduled interval, report them and offers on-demand or scheduled remediation.

If there are unwanted users created on the devices, ATOM can compare it against a set of allowed users and remove unnecessary accounts thus avoiding a security hassle.

Day-0 configurations such as domain name and name server details are captured as policies on ATOM. ATOM can check these against a default set of values that aids in   ATOM’s support for jinja2 templates to detect discrepancies and remediate them.

If there is an internal standard to point a region to a set of NTP servers and use a particular timezone, ATOM’s clock policies is the way to maintain those standards. ATOM can check the existing configuration against a default set of values, detect discrepancies and remediate them. 

If there is a pattern or naming convention for the hostnames in your network, ATOM supports policies that can detect any deviation from the standard pattern and remediate them.

Use ATOM to define standard banner templates across multi-vendor devices. Any deviation can be reported and remediated to ensure maintenance of standards

Use ATOM to ensure all unused ports are shut down only after its movement into an  unused VLAN.

Have a network wide standard for the protocol timers for BFD, OSPF LSA, STP hello messages, forward. Max-age etc? Use ATOM to define the default values using ATOM’s jinja templates and ensure compliance to these standards through regular checks and remediation  

Use ATOM to detect and remediate router-id configurations to Loopback0 IP for OSPF and BGP to ensure effective routing infrastructure.

Use ATOM’s policies to maintain interface related configurations such as Speed, Duplex and MTU settings as per your network infrastructure requirements.