Mark breaches as resolved

Find out how and when to mark breaches as resolved for users in SMBreach Pro.


In this article, you'll learn:

  • How to mark breaches as resolved
  • When and why you should mark breaches as resolved

You can only mark user breaches as resolved and track resolutions if you have SMBreach Pro. Read more about SMBReach Pro here.


How can I mark breaches as resolved?

There are multiple ways to mark breaches as resolved in SMBreach Pro.


How do I mark a breach as resolved for all users?

You can mark entire breaches as resolved for all affected users by clicking the Mark Resolved button in the main Breaches view for that breach. You'll be asked to confirm the number of individual breach-user combinations you wish to resolve.

How do I mark all breaches as resolved for an individual user?

You can mark all breaches that a user has been affected by as resolved for that individual user by clicking the Mark Resolved button in the main Users view for that user. You'll be asked to confirm the number of individual breach-user combinations you wish to resolve.


How do I mark a single breach as resolved for an individual user?

You can mark an individual breach as resolved for a single user by navigating to:

  • Breaches -> Click the desired breach -> Click Mark Resolved on a user
  • Users -> Click the desired user -> Click Mark Resolved on a breach

When and why should I mark a breach as resolved?

When employee credentials such as passwords become exposed it is important to take immediate action to mitigate the potential impacts of the breach. This usually involves contacting the affected users and asking them to make sure that they have changed any password that was exposed in a breach.


By marking a breach as resolved in SMBreach Pro, you can keep track of which breaches you have contacted users about and verified that they have taken action to reduce further impact of the breach.

Did this answer your question? Thanks for the feedback There was a problem submitting your feedback. Please try again later.