Banner Image

Vulnerability Assessment and Penetration Scanning for AWS cloud hosted applications

Given the increasing focus on cybersecurity, supply chain risk and compliance requirements – businesses are being asked to provide evidence of independent cybersecurity testing for cloud-hosted applications. Given the continued need for organizations to meet such requests for various reasons including SOC-2 compliance, HIPAA, FISMA or FedRAMP compliance, we have developed a standardized offering to help assess the current state of the security posture of an AWS hosted application. Our Security Review Report (SRR) includes an assessment of cloud configuration risks using the stackArmor ThreatAlert cybersecurity platform.

Security Review Report  (SRR)

stackArmor has years of experience in security assessment and authorizations in compliance with NIST, FISMA, FedRAMP and HIPAA standards and has developed the Security Review Report (SRR) artifact as a first step for organizations to assess their risk posture. The SRR rapidly and cost-effectively detects and helps remediate issues commonly found in AWS cloud based workloads and applications. The Security Review Report includes the following components:

  • Review of the architecture of the hosting environment to ensure that the right AWS technologies have been used
  • An internal vulnerability scan of the hosting environment
  • An external penetration scan of the hosting environment
  • An attestation letter on the methodology and findings reported

The infographic shows how a full-stack architecture review typically consists of the environment, application(s), data, operating system and the cloud platform that must be protected.  The actual current state of the security state is assessed by reviewing the structure, evaluating the software on the platform and the external exposure and threat surface available for attacks from the outside. The stackArmor Security Review Report (SRR) is a great light-weight starting point for organizations trying to assess their security posture.

Architecture Review

Creating a robust and secure architecture on AWS EC2 requires understanding core principles that ensure that the hosting environment is secure and robust to meet business and security standards for online systems. The architecture review consists of the following key elements:

  • Access management and control through means such as VPN, SSH, Bastion host, RDP or similar means to ensure that privileged users such as administrators and developers are securely accessing the environment.
  • Segmentation of the various layers of the application including using Application or Elastic Load Balancers (for public facing sites), private sub-nets for web servers, separate security groups and subnets for database servers and services.
  • Data protection policies including the use TLS/https for encrypting data in motion including reviewing TLS termination end points. Using AES-256 encryption for data at rest in EBS volumes or S3 buckets. Reviewing database encryption especially of sensitive data fields.
  • Continuous Monitoring configuration and setup through the use of cloud-native services such as Amazon CloudWatch, CloudTrail, Config, Macie and external services such as Splunk.
  • High-availability and fault tolerance using Multiple-Availability Zones, and architecting for redundancy.

Misconfigurations Scan

AWS cloud services need to be configured to ensure that security best practices are followed. Given that a lot of organizations may not be familiar with some of these best practices, stackArmor performs a scan of the configuration and setup using the EC2 API’s and covers key services to detect potential misconfigurations. The stackArmor ThreatAlert scan reviews the various settings and configurations of AWS components and services.  A sample of the services and their misconfigurations are illustrated in the table below.

  Misconfiguration Severity ScoreCloud-specific Sub- category
Non-VPC RDS Security Group contains private RFC-1918 CIDR   8   Security Group
RDS Security Group network larger than   /24   3   Security Group
RDS Security Group subnet mask is /010Security Group
RDS Security Group contains Group
ELB is Internet accessible.1Elastic Load Balancer
SSL listener is not using the ELBSecurity Policy-2014-10 policy   N/A   Elastic Load Balancer
Custom listener policies are discouraged.8Elastic Load Balancer
ELBSecurityPolicy-2011-08 is vulnerable and deprecated   10   Elastic Load Balancer
ELBSecurityPolicy-2014-01 is vulnerable to poodle bleed   10   Elastic Load Balancer
Unknown reference policy.10Elastic Load Balancer
SSLv2 is enabled10Elastic Load Balancer
SSLv3 is enabled10Elastic Load Balancer
Server Defined Cipher Order is Disabled.   10   Elastic Load Balancer
Deprecated Cipher Used.10Elastic Load Balancer

Vulnerability Scan

The internal vulnerability scan is performed using tools to help identify presence of vulnerabilities as reported to the NIST’s CVE database by various vendors. Tools such as Amazon Inspector, Tenable Nessus or OpenSCAP are commonly used to detect such vulnerabilities. The findings are grouped into Critical, High, Medium and Low’s. The best practice is to remediate Critical and High. With a plan of action to remediate Medium’s and Low’s. It is very common for such vulnerabilities to show up in the system due to delays in applying patches that typically includes a yum update for Linux systems or a WSUS update for Windows. AWS services such as Amazon Systems Manager provides a native patching solution that provide a systematic solution.

Penetration Scan

An external penetration scan helps identify vulnerabilities in the exposed web application. Typically, this scan is performed in anonymous mode and authenticated mode. The penetration scan helps detect issues such as SQL injection, XSS, click-jacking and other common web application related vulnerabilities. The penetration scan is typically performed using tools such as Tenable Nessus or Metasploit amongst others.

Prior to beginning any scanning activity, it is important to follow the prescribed protocol and procedures mandated by AWS that includes submitting a request form and getting approvals.

All of the results from the architecture review, internal vulnerability scan, external penetration scan and remediation information are provided in a formal report along with an attestation letter. Typically 2 scans are included – one is a preliminary scan to assess the current state to allow the SaaS provider to remediate the findings and a second remediation scan is done to confirm that the findings have been remediated.

If you a SaaS provider going for a SOC 2 audit, or need to demonstrate an independent cybersecurity risk assessment of your AWS hosted mobile or web application please ask us for more information and a sample of a Security Review Report (SRR). Send us an email at solutions @ stackArmor dot com or contact us by filling this form.

Contact Us Please write to us at solutions at stackarmor dot com