These days, enterprises are moving to cloud faster than expected, thanks to its various benefits, which include Reduced IT Costs, Scalability, Business Continuity, Collaboration Efficiency, Flexibility of Work Practices, and access to automatic updates.
The Amazon Web Services (AWS) is a leading public cloud provider that is well-known for its wide range of features, reliability, scalability, and security. But just shifting to AWS doesn’t guarantee the fool-proof security on the cloud as a simple user misconfiguration could have a disastrous impact on your business by exposing your security credentials and customer information to malicious use.
User Misconfiguration: A Major Threat to AWS Security
RedLock Inc. has recently published a research report finding many security issues primarily caused by simple user misconfigurations on public cloud platforms, with Amazon Web Services Inc. (AWS) figuring prominently. “Shockingly, the team determined that 82 percent of databases in public cloud computing environments such as Amazon Relational Database Service and Amazon RedShift are not encrypted,” the report said. It also identified several other issues besides sensitive data being left exposed, including weak network controls, poor governance, developer-caused security risks and tough compliance complications.
“On a similar note, RedLock CSI researchers also discovered that 40% organizations using cloud storage services such as Amazon Simple Storage Service (Amazon S3) had inadvertently exposed one or more such services to the public,” the report said. “In March 2017, at least 20,000 customer records containing sensitive data were exposed at Scottrade due to such a misconfiguration.”
Kromtech Security researchers have discovered yet another unsecured Amazon S3 bucket. This time, the cloud server in question was linked to HIPAA-covered entity, Patient Home Monitoring, a vendor that provides U.S. patients with disease management services and in-home monitoring.
The misconfigured server contained the lab results and other patient files of about 150,000 patients. The files were stored in a publicly accessible bucket that was left unprotected by a password, according to researchers.
What Makes Misconfiguration Critical?
A misconfiguration could be termed as critical in following cases:
- If a misconfiguration can be leveraged in a direct data breach.
- If a misconfiguration reduces or eliminates security or compliance.
- If a misconfiguration enables trivial attacks on your AWS console.
- If a misconfiguration can be leveraged in a more complex attack.
How To Identify Critical AWS Misconfigurations?
The best way to identify critical AWS Misconfigurations is to scan for them by running a configuration audit as soon as you move to cloud and every time you make a change in the environment. We also have an internally built tool that looks up your infra on cloud and will not only help you in knowing your critical AWS Misconfigurations but also give you an opportunity to correct them before they fall into wrong hands and result in massive security and data breach.
Consult AWS Security Experts
To identify and correct your AWS misconfigurations, you can consult AWS Security Experts
To get the latest insights, research and expert articles on AWS Services, Cloud Migration, DevOps and other technologies, subscribe to our Blog Newsletter here. For AWS Case studies and success stories, visit Case Study Section