AWS authentication confirms the identity of users trying to access your resources, safeguarding against potential intrusions and data breaches. But weak authentication practices—like easy-to-guess passwords and single-factor authentication (SFA)—are far too common and they leave the door wide open for threat actors. Weak authentication often leads to data theft, resource misuse, financial and reputational nightmares…the list goes on. On the contrary, strong authentication measures like Multi-Factor Authentication (MFA) significantly reduce the risk of these incidents occurring. StrongDM takes AWS authentication to the next level, going beyond MFA to include granular access controls based on roles (RBAC), attributes (ABAC), and just-in-time approvals.
StrongDM manages and audits access to infrastructure.
- Role-based, attribute-based, & just-in-time access to infrastructure
- Connect any person or service to any infrastructure, anywhere
- Logging like you've never seen
Some might say humans are the weak link in information security, but prominent data breaches show otherwise. Early in 2021, retail chain Hobby Lobby identified a security breach that impacted over 300,000 users and exposed 138GB of data – everything from names and phone numbers to the last four digits of customers’ payment cards. In 2019, a security incident resulted in 10.7 million MGM guests’ data being leaked, including names, addresses, and phone numbers. And back in 2018, 150 million MyFitnessPal users had their accounts compromised.
The common element in all these data breaches is access control. As one security expert noted from the MyFitnessPal breach, “trust but verify” isn’t enough when data is stored in the cloud and accessed from locations outside a company’s secured internal network. The infrastructure access security gap has only expanded with the rise of remote work and increased numbers of connected systems.
Organizations are turning toward Zero Trust principles to secure their infrastructure. With access and identity being two critical points to adopt Zero Trust, it’s not a surprise that 80 percent of companies have an Access Management initiative planned for the next year, according to our recent survey 2022: The Year of Access.
Legacy Access Practices Increase Risks
Unfortunately, many organizations are still using legacy access practices for their infrastructure. An overwhelming number of respondents to the study – 93 percent – have granted technical staff access to sensitive infrastructure, indicating how infrastructure has been democratized. But at what cost?
Nearly two-thirds (65 percent) use shared logins, and 42 percent rely on shared SSH keys. These practices make it hard to track who is accessing your systems. It could be a developer with a legitimate reason – or it could be a disgruntled former employee or malicious actor with plans to sell sensitive customer data on the dark web to the highest bidder.
Many companies use shared logins and shared SSH keys because they’re easy. Otherwise, they’d have to manually approve access for each person and each system. That’s not a big deal for a small company with just a few databases. But the average organization is provisioning dozens of databases and systems to many more users, everyone from in-house application developers to third-party partners. Half of the survey respondents noted that it can take hours, days, or even weeks to approve user access since these requests go through several layers of approvals.
Building a Modern Bridge for Infrastructure Access
Organizations aren’t using legacy technology anymore, and they need to let go of their legacy infrastructure access approval systems. As your company grows, you’ll add more systems, more databases, and more users. A modern approach that leverages automation and role-based access can help bridge the infrastructure access security gap, keeping sensitive data where it belongs.
For example, think of the one-off permissions you might grant a third-party partner to develop an application to monitor a segment of your supply chain. The app stalls in development, and eventually, you terminate the relationship. You’ll also want to terminate access or risk leaving a gaping hole for hackers to probe and exploit. An automated system could shut off access as soon as the project is finished.
And that’s just one of many ways that you can use automation to bridge the infrastructure access security gap and lessen the risk of a headline-making data breach – while still making sure your employees and partners have everything they need.
If you’re ready to ditch the legacy approvals for an approach that keeps your data secure, schedule your free demo of StrongDM today.
About the Author
💙 this post?
Then get all that StrongDM goodness, right in your inbox.
You May Also Like
So, you’ve decided to conduct an annual access audit. Now comes the obvious question: where do I start? Just like you wouldn’t embark on a mountain climbing excursion without a clear understanding of the terrain and gear you need, the starting point for an annual access audit requires an understanding of the process, people, and tools you’ll need to get started. Let’s go!
The great outdoors and your infrastructure have more in common than you might think. Both environments have diverse ecosystems and unique terrain, but they can also feel wild and untamed. In the spirit of adventuring and access, we wrote this blog to help you learn why you should conduct an annual access audit every year.
Secret vaults ensure that sensitive and privileged credentials are well protected, rotated, and only used–or checked out–when necessary. This makes them a critical and foundational tool for credential protection in modern infrastructures.
