An audit finds that the appliance's SNMPv3 monitoring user password has been pasted into three network management station configs authored by two contractors, with slightly different values in each. What is the correct remediation thinking for this monitoring credential?

SNMPv3 credentials must match exactly on the agent and the manager; the security comes from the pairing, so the governance job is keeping one authoritative record and moving all consumers in lockstep. Correct remediation pulls the secret out of contractor prose, stores it once in the vault, rotates appliance and all managers inside a single planned change, and finishes with a verification poll per station. Rotating only the appliance is the fastest way to create an unnoticed fleet-wide monitoring outage: every consumer keeps presenting the old credential and simply stops receiving, silently. Continued shared use with periodic rotation preserves the core defect - one secret known to multiple parties and copied into unmanaged files - and SNMPv3's privacy layer protects traffic on the wire, not plaintext secrets resting in configuration archives. Adding a second user while leaving the first intact expands the audit surface instead of shrinking it: the leaked value is still valid on the original user, and now two users' scopes must be tracked. Exam caveat: SNMPv3 has separate authentication and privacy passphrases; rotate coherently and confirm both ends agree on the hash and cipher choices, or users fail in confusing half-states. Operational check: after rotation, confirm fresh successful polls and traps from each station, then search the contractor config repositories to prove the old value is gone.