Preventing a data breach through leaked accounts

News of yet another large database leak made the client ask a direct question: could its corporate accounts be among the leaked ones, and could someone get in with them?

1. Every personal and corporate e-mail address was scanned against the available leaked databases through an API. The scan revealed a number of compromised accounts and their passwords, and some personal accounts used passwords similar to corporate ones.
2. All compromised accounts were locked.
3. An activity audit of the compromised accounts ruled out any third-party access to corporate accounts or harmful activity.

1. All users changed their passwords according to the security standards.
2. A stronger password policy was enforced, with a forced reset on any sign of compromise.
3. Two-factor authentication (2FA) was enabled for all accounts.
4. Some corporate resources were restricted to access from inside the corporate network.
5. Leaked-account scanning became part of the company security protocol.

Managed IT services →
Compliance audit →