Credential stuffing’s popularity rose dramatically in 2018 — in fact, Akamai recorded nearly 30 billion credential stuffing attacks in 2018 — and businesses certainly haven’t seen the last of this type of cyber attack. For example, on 24 May 2019, a credential stuffing attack enabled criminals to access up to 139 million profiles on the popular graphic design platform, Canva. So businesses that take cybersecurity seriously need to protect against credential stuffing cyber attacks.
A credential stuffing attack is a type of brute force cyber attack used to gain unauthorised access to one or more user accounts. Criminals use an automated system to enter large numbers of previously breached username and password pairs into website login fields to see if any of them match existing accounts. The attacker then hijacks any accounts they’ve been able to log into.
As is almost always the case, the best way to deal with credential stuffing is to prevent it from happening in the first place.
Businesses can prevent credential stuffing attacks in two main ways: they can implement security measures for their business, and ensure they and their staff implement personal cybersecurity measures.
Every staff member should:
Once all staff members are taking adequate security precautions, the risk that their credentials will be stolen is significantly reduced. And if a set of credentials for one account is stolen, the damage will be reduced as well because it will be limited to a single account. Implementing the following proactive and reactive company cybersecurity measures will further reduce the likelihood that a business’s systems will be compromised by a credential stuffing attack.
For more information on cyber risk exposure mitigation, contact us for more information. These 12 tips were first shared during Chubb’s ‘Credential Stuffing Debunked’ webinar, by guest speaker, Jeremy du Bruyn, Practice Manager at Sense of Security Pty Ltd.
Disclaimer - This content is brought to you by Chubb Insurance Malaysia Berhad (“Chubb”) as a convenience to readers and is not intended to constitute advice or recommendations upon which a reader may rely. Chubb makes no warranty or guarantee about the accuracy, completeness, or adequacy of this content. It is the responsibility of the reader to evaluate the quality and accuracy of material herein.