Skip to main content
All CollectionsLockwell App
How to Handle Account Breaches
How to Handle Account Breaches

Intro to Breach Monitoring & Guide on How to Respond to Breached Accounts

Lockwell Support avatar
Written by Lockwell Support
Updated over a year ago

Understanding Data Breaches: The Role of Threat Intelligence

Data breaches are an unfortunate reality in today's online world. Even if you follow every security best-practice in the book, hackers can still potentially break into the servers of a website you use and steal your credentials (along with everyone else's).

With continuous dark web and domain scanning along with real-time notifications, Lockwell ensures you're the first to know if your company's data is at risk.

How Lockwell's Breach Monitoring Works

Lockwell monitors the dark web (a shady section of the internet where cyber criminals often exchange hacked credentials & other data) as well as other online channels for hacked account data related to your organization.

If a hacked account related to your organization is found, Lockwell:

  1. Identifies the team member the account belongs to.

  2. Immediately alerts the team member and creates a critical security issue for them to update their password.

  3. All org admins can monitor the status of active breaches in the admin dashboard.

    1. Active breach security issues are also surfaced in the admin digest email.

Responding to Account Breaches

Lockwell automatically monitors for breached accounts from the moment you signup and works with your team to update their password(s) if any breaches are found. To check whether your team has any active account breaches, simply open the Admin Dashboard & browse to the Breaches page.

In this example, the SurveyMonkey service that our team uses has been hacked. We can click the affected service to see:

  • The date of the breach

  • The site that was breached

  • All security issues Lockwell created to help your team members update their SurveyMonkey account passwords

Lockwell creates a security issue for each compromised account related to the service in your team. In this case, it looks like there's only one:

After opening the related security issue, we see that our team member Jordan is the owner of the breached SurveyMonkey account. We're also able to view all the security issue's important details, including a timeline of every action Lockwell & the team member have taken to resolve the issue.

From this point, you have control. Check the timeline to see how long the breach security issue has been open for. If the team member hasn't updated their compromised password yet, Lockwell recommends reaching out to them directly and asking them to do so.

With Lockwell, you don't have to worry about whether or not your account data has been compromised - we're always on the lookout for you.

Did this answer your question?