Asimily Configuration Control

Asimily’s Configuration Control keeps connected devices in an approved, known good state and detects when they drift from it. Configuration drift can come from routine maintenance, third-party service work, firmware updates that revert settings to factory defaults, human error, or an attacker, and on IoT, OT, and IoMT devices it often goes unnoticed until it is exploited. Configuration Control is a capability not found in competing connected device security platforms. Asimily captures a snapshot of each device’s secure configuration and stores it as the known good baseline. Snapshots can be taken on demand or based on defined policies, and Asimily’s experts can help teams identify the right secure configuration for the devices in their environment. Asimily then regularly compares each device’s current configuration against its baseline and highlights exactly what changed. To prevent alert storms, teams assign High, Medium, Low, or no severity to configuration categories, so only meaningful deviations generate alerts. A change to a security-relevant setting such as credentials or access control rules can raise a high-priority alert, while routine adjustments stay quiet. When a device drifts, teams can return it to its last known good state, and historical configuration data provides a record of what changed and when for investigations and audits. Configuration Control works alongside the rest of the Asimily Platform. Teams can address drift on the high-risk devices identified by ATT&CK Analysis first, check configurations against the baseline after a firmware update, and use configuration history to support NIST guidance and other frameworks that call for documented secure baselines and recovery to a known good state.