Skip to main content

Network Config Policy

Overview​

NCCM (network configuration and compliance management) Policies allow you to define proactive rules that monitor configuration changes or enforce network actions on your managed network devices. These policies help in detecting unauthorized config changes, enforcing security standards, and triggering automated responses like email/SMS alerts or remediation scripts.

Once you configure your NCCM devices(newlink), you can create a policy to track changes, compare versions, or trigger alerts/actions based on set conditions.

Go to Menu and select Settings . After that, go to Policy Settings . Then, select Network Config Policy.

Create NCCM Policy​

Click on Create Policy to launch the configuration page.

Fill in the fields as described below:

FieldDescription
Policy NameProvide a name that clearly defines the purpose of the policy.
TagAdd tags to categorize and filter policies more efficiently.
Evaluate OnChoose between Config Conflict or Failed Action.

If Evaluate On is set to Config Conflict, you'll be able to choose from available comparison types in the Conflict Detection For dropdown (e.g., BAseline-Running Conflict, Startup-Running Conflict, Running Conflict, Startup Conflict). If set to Failed Action, you will configure the type of Action monitored on the NCCM device.

Set Conditions​

FieldDescription
Conflict Detection For / Action TypeDepending on your selection in Evaluate On, you will either select change types or NCCM actions like Backup, Upload, Execute Script, etc.
Source FilterChoose source filter from the drop-down list. You can filter by Network Config Device, Group or Tag.
SourcePopulated based on your Source Filter.
SeverityChoose alert severity: Critical, Major, or Warning.

Set Alert Message​

FieldDescription
SubjectModify the subject-line for the alert message.
MessageModify the alert message from here.
info

For a list of default supported Macros to modify the default set message, Please visit: Alert Macros

Notification​

Configure how alerts from this policy are sent to your team.

FieldDescription
NotifyThere are multiple ways you can populate this field:
  • Username of registered user in MotadataObserveOps (formerly known as AIOps) (The alert notification will be sent over email and SMS to the mapped email address and phone number respectively).
  • Any email address (In case the recipient whom you wish to notify is not a registered user, you can enter an email address).
  • Mention Teams Handle, if you have integrated Microsoft Teams with Motadata ObserveOps you can simple mention the Teams Handle provided at the time of the configuring the integration. It will send a notification to the teams channel when the policy is breached.
  • Use @ to mention a registered username, email address, or Microsoft Teams handle.
  • Use # to select a user profile for alert notification.
  • Use ! to select a Syslog Forwarder or SNMP Trap Forwarder integration profile and forward the alert to the configured external destination.
    • Play SoundActivate this toggle to enable sound notifications when an alert is triggered.

    Take Action​

    Motadata ObserveOps allows you to execute scripts or commands automatically as a response to policy violations. You can select actions from the drop-down menu.

    Declare Incident​

    FieldDescription
    Select Integration Profile to TriggerChoose an Integration profile to be executed from the dropdown when the chosen alert severity is triggered.
    Create Integration ProfileSelect this button to start creating a new Integration profile that you might want to assign to the policy you are creating.

    Once all fields are configured, click Create Policy to apply the policy.