Audit, Validation, and Anomaly Detection
Selector Platform Architecture
Observability tools have historically focused on logs and metrics, but not configuration information. This is surprising given how often configuration changes lead to outages as well as their potential to create security vulnerabilities.
Enter the Selector Configuration Compliance solution. Operations teams can now audit configuration changes, correlate configuration changes to anomalies, and search for the presence or absence of specific configuration statements. Operations teams can be configuration commandos, with an elite understanding of configuration changes, settings, and consequences.
The basic workflow is as follows:
Selector users can drill down on all correlated information including diff and whole configuration
Through this workflow, anomaly detection is much richer, and correlated to likely causes whether it is a fault in the network or a configuration change. Instead of operations teams having to guess at what the likely sources of anomalies are, there is greater clarity, more efficient triage, lower mean time to detect (MTTD), and lower mean time to repair (MTTR).
With the impact of the configuration change identified, operations teams can roll back the change if needed, using an approved process.
This solution highlights the strength of the selector architecture, capable of correlating any data source or data type, including configuration changes.
Ever been in a situation where you are about to go live with a major new network segment and/or change, and wondered if every configuration was set the way it needed to be?
Now you can do a configuration search for the absence or presence of any configuration element.
Show me the devices that have this BGP statement. Show me the devices that do not have this ACL statement. All with a natural language query. A Selector customer recently used this capability before going live with a major, highly visible media event, and were very pleased they did, observing that no other solution on the market has this capability.
As with many Selector events, a timeline is constructed so that Selector users can explore a timeline, see correlations, and do drill downs as needed. With the Selector Configuration Change Timeline, operations teams can see when a change was made, what the change was, and who/what made the change. As automation becomes more prevalent, the frequency of changes is likely to increase. Buried in such changes may be configuration changes made by hackers that create significant security vulnerabilities. A configuration change trace / timeline is essential as configuration changes are among the most common sources of outage, performance degradation, and increasingly, security exposures.
While change management processes may provide a check on what planned changes occur, the outcome of a change is unpredictable and there may be unwanted changes occurring outside of the change management process that operations teams need to know about. Importantly, if there is a correlation between a configuration change and outages / performance degradation, operations teams need to know about that as rapidly as possible, and then return to the desired KPIs as soon as possible.