In recent times, you might have noticed user accounts being compromised by the millions, and yet companies refute these claims saying that their systems are secure and have not been attacked. In these cases, the companies are right – instead of a direct attack, the hackers may have performed an attack called ‘credential stuffing’. In this type of attack, hackers get their hands on usernames and passwords of one application or service and stuff the same credentials on another login for another digital provider.

For example, if you have used the same user ID and password for creating your Facebook and Twitter accounts, a hacker who has access to your Facebook user id and password can use the same for getting into your Twitter account. This does not mean that Twitter’s systems are faulty. It simply means that your credentials have been stuffed. Credential stuffing attacks use code injection techniques to test the credentials against multiple accounts like social media, online marketplaces, and bank accounts. Once access is gained, the hacker can get access to personal information, credit card information and other personally verifiable information.

In recent times, this type of attack has gained popularity due to the fact that most users use the same user ID and password for multiple accounts. The situation right now is precarious for most online users – a recent breach of breaches has given hackers access to a whopping 2.2 billion user IDs and passwords. It is called a ‘breach of breaches’ because a few hackers hacked into millions of Dropbox and LinkedIn accounts and compiled a list of plain text credentials. However, another team of hackers hacked into this list to compile an even bigger list of stolen credentials.

If you have built enterprise applications, how sure can you be that your users have created different passwords for all your applications? There is no way for you to know for sure. However, you could put in place a password policy which prevents them from using the same password for all the applications in your network.

Akku from CloudNow Technologies allows you to set custom password policies to help you standardize the passwords set by your users. You can also leverage it to prevent the setting of the same passwords. To know more, get in touch with us now.

Ananthasayanam Nallan Chakravarthy

Ananthasayanam is Executive Vice President – Global Sales at Akku, where he leads the company’s global go-to-market strategy, driving revenue growth and building long-term client relationships across industries. His focus is on expanding Akku into new markets, while strengthening strategic alliances and cultivating high-performance teams. Prior to joining Akku, he held senior leadership roles at Denodo, Oracle, Tectura, Ramco Systems, and other organizations, gaining extensive experience in sales management, business development, and enterprise technology across global markets.

Share
Published by
Ananthasayanam Nallan Chakravarthy

Recent Posts

IRDAI Item 10: Dormant Account Controls and the Automated Deprovisioning Requirement

Introduction IRDAI ICS Annexure III Item 10 requires that user accounts inactive beyond a defined…

1 month ago

ISO 27001 A.5.18 Access Reviews: How to Implement With Structured Evidence

Introduction ISO 27001:2022 Annex A.5.18 requires that access rights be reviewed at regular intervals and…

1 month ago

SOC 2 CC5.1 Segregation of Duties: What Technical Enforcement Requires

Introduction SOC 2 Trust Services Criteria CC5.1 requires that the entity selects and develops control…

1 month ago

SEBI CSCRF and Qualified REs: What Higher-Tier Entities Must Implement

Introduction SEBI CSCRF applies to all regulated entities but differentiates requirements by entity tier. Market…

1 month ago

Dormant Account Controls Under SEBI CSCRF: The Access Hygiene Requirement

Introduction SEBI CSCRF PR.AA.S1(G1g) and PR.AA.S1(G1h) require that user accounts inactive beyond a defined threshold…

2 months ago

ISO 27001 A.8.2: Privileged Access Management Requirements and Implementation

Introduction ISO 27001:2022 Annex A.8.2 requires that the allocation and use of privileged access rights…

2 months ago