Initial Access

The adversary is trying to get into your AWS environment. Initial Access consists of techniques that use various entry vectors to gain their initial foothold within an AWS environment. Techniques used to gain a foothold include exploiting weaknesses on public-facing web servers. Footholds gained through initial access may allow for continued access, like valid accounts and use of external remote services, or may be limited-use due to changing passwords.

Techniques

Techniques: 10
ID Name Description
T1538 Cloud Service Dashboard

An adversary may use a cloud service dashboard GUI with stolen credentials to gain useful information from an operational cloud environment, such as specific services, resources, and features. For example, the GCP Command Center can be used to view all assets, findings of potential security risks, and to run additional queries, such as finding public IP addresses and open ports.

Depending on the configuration of the environment, an adversary may be able to enumerate more information via the graphical dashboard than an API. This allows the adversary to gain information without making any API requests.

AWS Specific Content


A prerequisite for this technique is that a threat actor has already compromised the login credentials and gained control of an AWS identity with a login profile configured. Alternatively, a threat actor with control over long-term credentials can also generate a URL for access to the AWS Management Console for an IAM user without a login profile configured

A Cloud Service Dashboard is a GUI that provides access to cloud services. In AWS, the Cloud Service Dashboard is the AWS Management Console. Using a compromised AWS identity, threat actors can access the identitys AWS account using the AWS Management Console which provides a threat actor with a more intuitive way of navigating the AWS account and a more efficient way to view and interact with resources than with the AWS CLI. Note that the ability to view and access resources are still restricted to the permissions granted to the AWS identity that the threat actor has control over.

In some cases, accessing the AWS Management Console will be the Initial Access vector that the threat actor has used to attempt to gain access to the AWS account by obtaining the credentials for a root user, an IAM User, or an AWS IAM Identity Center user. Access to log in to the console is typically granted to an IAM user by creating a login profile and enabling console access, however, threat actors can also utilize scripts to create a URL for IAM users to log on to the AWS Management Console without a login profile. In this scenario, while it is still possible to log in to the AWS Management Console, the ability to view and edit resources in the AWS account is still bound by the permissions granted to the IAM or Identity Center user.

T1190 Exploit Public-Facing Application

Adversaries may attempt to take advantage of a weakness in an Internet-facing computer or program using software, data, or commands in order to cause unintended or unanticipated behavior. The weakness in the system can be a bug, a glitch, or a design vulnerability. These applications are often websites, but can include databases (like SQL), standard services (like SMB or SSH), network device administration and management protocols (like SNMP and Smart Install), and any other applications with Internet accessible open sockets, such as web servers and related services. Depending on the flaw being exploited this may include Exploitation for Defense Evasion [MITRE] .

If an application is hosted on cloud-based infrastructure and/or is containerized, then exploiting it may lead to compromise of the underlying instance or container. This can allow an adversary a path to access the cloud or container APIs (e.g., via the Cloud Instance Metadata API), exploit container host access via Escape to Host, or take advantage of weak identity and access management policies

For websites and databases, the OWASP top 10 and CWE top 25 highlight the most common web-based vulnerabilities.

T1190.A016 EC2 Hosted Application Compromise

AWS Specific Content


A prerequisite for this technique is an Amazon EC2 instance hosting a vulnerable application

The operating system and/or application running on an Amazon EC2 instance can be compromised due to an unpatched operating system or software, or through a misconfigured application. It is common for an adversary to search for web applications that are open to the internet and scan for and exploit vulnerabilities within the web application. Once the application is compromised, the threat actor can use the underlying EC2 instance for their computation requirements with the cost of the resources being attributed to the compromised account.

T1190.A019 Overly Permissive VPC Security Groups

AWS Specific Content


A prerequisite for this technique is that an AWS resource has been configured with unrestricted or overly permissive VPC Security Groups, that there is a network path to the vpc-attached resource, and that there is an active listener

A resource that has been configured to have unnecessarily overly permissive VPC security groups is susceptible to scanning, probing, and denial of service attempts against the resource. This configuration can also allow brute force logins to the resource and provides threat actors with the ability to continue attempted access without restriction.

T1199 Trusted Relationship

Adversaries may breach or otherwise leverage organizations who have access to intended victims. Access through trusted third party relationship abuses an existing connection that may not be protected or receives less scrutiny than standard mechanisms of gaining access to a network.

Organizations often grant elevated access to second or third-party external providers in order to allow them to manage internal systems as well as cloud-based environments. Some examples of these relationships include IT services contractors, managed security providers, infrastructure contractors (e.g. HVAC, elevators, physical security). The third-party provider's access may be intended to be limited to the infrastructure being maintained, but may exist on the same network as the rest of the enterprise. As such, Valid Accounts [MITRE] used by the other party for access to internal network systems may be compromised and used.

In Office 365 environments, organizations may grant Microsoft partners or resellers delegated administrator permissions. By compromising a partner or reseller account, an adversary may be able to leverage existing delegated administrator relationships or send new delegated administrator offers to clients in order to gain administrative control over the victim tenant.

T1199.A002 Role Assumption and Federated Access

AWS Specific Content


A prerequisite for this technique is that a threat actor has already gained control of an AWS identity with the permissions to perform the actions in the AWS CloudTrail Event Name(s) section, and that the AWS identity is permitted by the role it is attempting to assume.

A role is an IAM identity that you can create in your account that has specific permissions. Roles and users are both AWS identities with permissions policies that determine what the identity can and cannot do in AWS. However, instead of being uniquely associated with one person, a role is intended to be assumed by anyone who needs it. Also, a role does not have standard long-term credentials such as a password or access keys associated with it. Instead, when you assume a role, it provides you with temporary security credentials for your role session.

With access to an AWS identity that has the appropriate permissions, threat actors can use the sts:AssumeRole action to get credentials in another AWS account if cross account roles are present. When using AWS Organizations, the management account creates one of these cross account roles in the member account by default. The AssumeRole action is also performed when an identity is provided federated access into an AWS account, for example, through AWS Identity Center

T1078 Valid Accounts

Adversaries may obtain and abuse credentials of existing accounts as a means of gaining Initial Access, Persistence, Privilege Escalation, or Defense Evasion. Compromised credentials may be used to bypass access controls placed on various resources on systems within the network and may even be used for persistent access to remote systems and externally available services, such as VPNs, Outlook Web Access, network devices, and remote desktop. Compromised credentials may also grant an adversary increased privilege to specific systems or access to restricted areas of the network. Adversaries may choose not to use malware or tools in conjunction with the legitimate access those credentials provide to make it harder to detect their presence.

In some cases, adversaries may abuse inactive accounts: for example, those belonging to individuals who are no longer part of an organization. Using these accounts may allow the adversary to evade detection, as the original account user will not be present to identify any anomalous activity taking place on their account.

The overlap of permissions for local, domain, and cloud accounts across a network of systems is of concern because the adversary may be able to pivot across accounts and systems to reach a high level of access (i.e., domain or enterprise administrator) to bypass access controls set within the enterprise.

T1078.A002 Account Root User

AWS Specific Content


A prerequisite for this technique is that a threat actor has already gained control of an AWS account root user.

This technique identifies when a threat actor uses the root user to perform unauthorized actions. When you first create an Amazon Web Services (AWS) account, you begin with an identity that has complete access to the AWS services and resources in the account. This identity is called the AWS account root user. The email address and password that you used to create your AWS account are the credentials you use to sign in as your root user. The account root user has complete access to the AWS services and resources in the account, and if compromised by a threat actor, would give the adversary complete access to the AWS account.

T1078.A001 IAM Users

AWS Specific Content


A prerequisite for this technique is that a threat actor has already gained control of an AWS IAM user.

This technique identifies when a threat actor uses an IAM user to perform unauthorized actions through either long-term credentials or through the AWS Management Console. An IAM user is an entity that you create in your AWS account. The IAM user represents the human user or workload who uses the IAM user to interact with AWS resources. An IAM user consists of a name and credentials.

An IAM user with administrator permissions is not the same as the AWS account root user. For more information about the root user, see AWS account root user