Start with a defined configuration policy
Use this workflow when a policy check reports a violation, a review identifies an exception or engineers need to understand configuration changes over a time window. Name the policy owner and target devices so the finding has an operational scope.
This use case depends on configured SolarWinds Network Configuration Manager access and relevant NCM data. NetPrompt helps retrieve and analyze those records; it does not establish legal or regulatory compliance merely by producing a report.
Connect the finding with configuration evidence
Collect the policy result, applicable configuration and available change history. Confirm device identity and observation time before comparing records. A configuration archive may describe an earlier state rather than the currently running device.
| Input | Review question |
|---|---|
| Policy result | Which rule failed and what evidence triggered it? |
| Configuration record | Which device and timestamp does this represent? |
| Difference and history | What changed within the relevant period? |
| Approved exception | Is the deviation documented and still applicable? |
| Service context | What is exposed if the setting is changed? |
Illustrative example: an approved exception or an unintended change
A recurring review reports that a device differs from a required configuration policy. NetPrompt retrieves the relevant result and history for the reviewer. The reviewer checks whether the difference corresponds to a valid exception or an unapproved change.
The action plan records the evidence, owner and next decision. A historical difference alone does not prove malicious activity or current service impact. This example is a review scenario, not a customer compliance claim.
Separate analysis from configuration execution
Begin with retrieval and analysis. NetPrompt’s NCM capabilities also include operations such as backup, script execution and restoring an archived configuration, but these need a separately reviewed scope and the applicable execution controls.
A restore can reintroduce obsolete settings or affect dependent services. Confirm the archive, recovery access and validation plan before approving any action. Version comparison is evidence for a decision, not automatic permission to roll back.
Evaluate the workflow with known policy outcomes
Choose one genuine violation, one valid exception and one stale archive. Ask the workflow to retain the distinction and identify the evidence that needs review. Measure how much manual effort remains to turn the result into an actionable record.
The desired output names the policy, target, evidence date, exception status and accountable owner. After an approved correction, rerun the applicable policy and service checks and record the observed outcome.
Common questions
- Is configuration compliance the same as configuration drift?
- No. Drift describes a difference from a baseline. Compliance review evaluates a defined policy and any approved exception; a difference may be intentional or irrelevant to that policy.
- Does this work without SolarWinds NCM?
- This page describes the documented NCM integration. Other systems need their own validated connector operations and evidence coverage.
- Does an AI-generated report prove compliance?
- No. The relevant policy owner must review the evidence, scope and exceptions. Regulatory assurance is a separate assessment.
Continue exploring
Further technical reading
External references explain general practices; they are not endorsements of NetPrompt AI.