What are the biggest AWS Security Vulnerabilities? | Security Engineer Interview Questions

As the biggest provider of cloud services in the world by far, Amazon Web Services (#AWS) is a juggernaut powering the massive and complex applications deployed by entertainment giants, governments, and social networks. Given the sheer volume of user data they handle on a daily basis, it's only logical to assume they're the target of numerous security attacks and threats.
In this episode of Security Engineer Interview Questions, Abhay Bhargav answers the question: "What are the biggest AWS security vulnerabilities?"
Despite having very robust security across its services, most of the security issues that plague AWS-hosted apps tend to stem from the users' end, ie., the people deploying their apps on AWS. Security misconfigurations, access control and privilege issues, and more comprise the majority of security vulnerabilities found on AWS.
Here are some of the most common AWS vulnerabilities out there:
Misconfigured Access Control - #S3 Buckets
Subdomain Takeovers - S3/ #Cloudfront
Vulnerabilities with apps deployed on compute infrastructure
Host and Network hardening flaws
Privilege escalation of credentials from compute services
Watch the video to see a full breakdown of all of these, and ace that job interview!
Content of this video
0:00- Intro
01:08- What is the biggest AWS security vulnerability?
02:56- S3 bucket vulnerabilities
03:40- Subdomain takeovers
04:44- privilege right escalation vulnerability
05:20- Server side request attack forgery demo
14:18- Start access S3
17:21- Like and subscribe
---------
AppSecEngineer is a powerful training platform that delivers amazing hands-on training on AppSec, AWS Security, Cloud Security, Kubernetes, Container Security and Advanced Application Security.
#AppSecEngineer​ is ideal for jobseekers, knowledge seekers and companies that want to get their workforce equipped to handle real-world security issues with their newly minted and highly educated AppSec Engineers
Learn more about AWS Security at appsecengineer.com/aws-cloud-...
Twitter: / appsecengineer​
Linkedin: / appsecengineer
#AWSsecurity #AWSvunerabilities

[@hariprasad0511]

It is a good explanation. Thanks for doing this

[@AppSecEngineer]

Glad it was helpful!

[@realnetworkadetunji3459]

Good job, thanks a lot

[@AppSecEngineer]

Glad it helped !🙂

[@MK-rn2hm]

Thank-you. My issue is I have to assess AWS itself from a data security perspective and this is a big help. Any more content you have put out related to this ask?

[@AppSecEngineer]

Glad it was helpful! Any specific queries you have?

[@MK-rn2hm]

@@AppSecEngineer Are there any other un publicized vulnerabilities in AWS?

[@AppSecEngineer]

Unlikely that there are unpublicised vulnerabilities in AWS itself, but the misconfigurations of services used by developers can result in vulnerabilities in your implementation on AWS typically

[@misplacedidentity1036]

Thank You for the video, please zoom out a little. It's distracting to see your head moving a lot. I cannot look away from the screen because if you're showing some configuration on the screen I would miss it.

[@AppSecEngineer]

Noted! Thanks for the feedback!!

[@mathewaju]

So disabling metadata service the soln?

[@AppSecEngineer]

Not necessarily. Disabling metadata is not an option if you need your Ec2 server to connect with internal AWS services like DynamoDB or S3. Its recommended that you use the IMDSv2 Service with the new AWS SDK to ensure that you're much more protected against SSRF flaws being able to access the Metadata over a simple GET request

[@rakeshgoudo7180]

How can we protect from SSRF attack in AWS ?

[@AppSecEngineer]

Youll see that we’ve explained in the video. Aside from securing the application against SSRF, the important thing is to leverage the IMDSv2 service for metadata so you have an additional layer of authentication to access the metadata service

[@kingofhavila9850]

@@AppSecEngineer thank u

[@yetbomb9630]

What browser or web application is that?

[@AppSecEngineer]

The vulnerable application we’re using is a one that we’ve built as a lab for AppSecEngineer. The IDE interface is the way we deliver all hands-on labs in AppSecEngineer. Check it out: appsecengineer.com

[@kingofhavila9850]

@@AppSecEngineer you forced vistors to accept cookies in your website 😒

[@AppSecEngineer]

@@kingofhavila9850 Necessary sometimes, you can always clear them though. Any specific reason you don't want to accept it?

[@beulahbillions5655]

So much noise. Time wasting.