AWS PENETRATION TESTING
Identify security vulnerabilities, misconfigurations and assess their impact on your AWS environments through our pentest services.
Cloud-based move, whether it’s hybrid or cloud hosted, is a game changer for businesses. Flexibility, Pricing, Speedy setups and redundancy are a few top benefits of cloud computing model.
Depending upon the use of cloud sharing model, AWS security issues have varying impacts ranging from default configuration to internal attacks bypassing detection capabilities. A cloud based account compromise whether it’s your vendor or employee may lead to potentially disastrous results down to simple misconfiguration or secure hardening vulnerabilities.
For this reason, regular AWS pentesting assessments provide visibility into unknown areas shaping your business’ cloud security strategy.
AWS Pentesting and Vulnerability Scanning Techniques
The following list of assessment techniques is a high-level view based on the main components of AWS cloud infrastructure. Obviously, this includes more test cases when an assessment is conducted based on assets deployed and their implementation based on functionality to the cloud audience.
Lot of context including whether you require AWS vulnerability scanning or penetration testing is discussed and tailored during our scoping calls.
Penetration testing AWS environment against defined security standards
One of the biggest changes when it comes to traditional vs AWS (Amazon Web Services) infrastructure is the ownership change. In the last few months, AWS has updated their penetration testing authorisation policy (AWS penetration testing request when you ask us to carry out work) to allow pen tests without prior approval for 8 permitted services:
- Amazon EC2 instances, NAT Gateways, Elastic Load Balancers
- Amazon RDS
- Amazon CloudFront
- Amazon Aurora
- Amazon API Gateways
- AWS Lambda and Lambda Edge functions
- Amazon Lightsail resources
- Amazon Elastic Beanstalk environments
Anything that belongs to the below can’t be tested and is not allowed by AWS:
- DNS attacks via Amazon Route 53 zones
- Denial of Service (DoS), DDoS or any simulations
- Port floods, Protocol floods
- Login request or API request flooding
Our AWS Security Testing Services
Whether it’s for infrastructure as a service (IaaS), a platform as a service (PaaS) or software as a service (SaaS), we provide AWS pentest services for our customers across the globe.
SaaS Security Testing
Whether it’s the risk of regulatory fines, data breaches or product security for your customers, SaaS security testing is a must do before going live to ensure all vulnerabilities are remediated. Secure software is a critical component for SaaS vendors and this assurance helps achieve this objective.
AWS Penetration Testing
This refers to identifying and exploiting security vulnerabilities and misconfigurations to simulate real-world cyber attacks. This exercise is helpful to identify, assess and remediate the high impact risks to your cloud environment.
AWS Security Review
It is your responsibility to secure assets hosted in the cloud. This includes underlying infrastructure secure configuration baselines, policies and procedures against AWS services and other products serving your staff and users internally in the cloud.
Cloud Provider provides resources, securing it is your responsibility.
AWS Penetration Testing Methodology
Our security assessment approach involves benchmark based assessments as well as standard pentest methodology extended to include AWS specific security concerns and not use traditional pentesting as blanket methodology.
AWS specific threats
The following list includes contextual AWS cloud security threats identified exploited by our penetraton testers during the penetration tests carried out in the customer AWS accounts or cloud environments.
- Amazon Cognito authentication & authorisation used in mobile or web application
- Misconfiguration queues or topics utilising AWS CLI
- EC2 instances – Penetration testing of EC2 instances (Elastic Cloud Computing) is similar to performing security assessments such as virtual machines and operating systems security misconfigurations, file permissions and security vulnerabilities.
- AWS Storage – S3 buckets Bucket-level checks are needed to secure S3 buckets holding sensitive information especially reviewing the process of how anonymous, semi-public, etc permissions are granted for everyone, authenticated users and other groups within Amazon web services (AWS) account.
- ELB (Elastic Load Balancers) – ELB checks such as HTTP Request smuggling or security misconfigurations acorss AWS resources.
- Database security (Aurora, Redshift, RDS) checks covering public access, privilege access management and roles.
- EBS (Elastic block store) volumes and snapshots access