Whitepaper-Achieving Least Privilege in AWS
Whitepaper-Achieving Least Privilege in AWS
Whitepaper-Achieving Least Privilege in AWS
PRIVILEGE IN AWS
LEAST PRIVILEGE IS A CRITICAL STEP IN
YOUR CLOUD SECURITY ROADMAP
In a survey of 300 CISOs across the United States, more than 70% of respondents
identied least-privilege as their most signicant challenge.
Securing identities and data in the cloud is extremely challenging, and many organizations
get it wrong. Yet recent events have proven that the risks associated with compromise of
identities and credentials cannot be taken lightly. The problem becomes increasingly acute
over time, as organizations expand their cloud footprint without establishing the capability
to effectively assign and manage permissions. As a result, users and applications tend to
accumulate permissions that far exceed technical and business requirements, creating a
large permissions gap.
The potential impact of lax authorization can be devastating. Attackers can use
compromised credentials with excessive permissions for misdemeanors like stealing time
and CPUs on your instances to mine Bitcoin. But excessive privileges can also enable a
threat actor to steal sensitive data or delete parts of the infrastructure.
The Capital One breach is the perfect example of the risks associated with excessive access
permissions. Before we continue, we must emphasize our great respect for the bank. Capital
One has pioneered cloud computing in the banking industry, and its story is one common to
trailblazers who test out new technologies.
In a nutshell, the problem stemmed, in part, from a vulnerable open-source Web Application
Firewall (WAF) that Capital One was using as part of its operations hosted in the cloud with
Amazon Web Services (AWS), its Cloud Security Provider (CSP). This vulnerability allowed the
attacker to obtain credentials to access any resource in the account to which that WAF
had access.
In AWS, exactly what access is associated with a set of credentials depends on the
permissions assigned to the entity. In the case of Capital One, the vulnerable WAF was
assigned excessive permissions. More specically, it was allowed to list all the les in
sensitive data buckets and read the contents of each of those les. These excessive
permissions allowed the attacker to get access to a sensitive S3 bucket.
Let’s take AWS as an example, since it is the most popular cloud platform and offers one of the most
granular, and complex Identity and Access Management (IAM) systems available. AWS IAM is a powerful tool
that allows you to securely congure access to AWS cloud resources. With more than 2,500 permissions
(and counting), IAM gives users ne-grained control over which actions can be performed on a given
resource in AWS.
In theory, the rst step to achieve least privilege is to dene a policy that reects what access guardrails
should be in place. Then, you should understand which permissions a given user or application has and
continue to map all the permissions actually being used. Comparing the two reveals the permission gap and
enables you to decide which permissions to keep and which to remove. Finally, the permissions deemed
excessive are removed or monitored.
In practice, however, the effort required to determine the precise permissions necessary for each
application in a complex environment like AWS IAM is prohibitively expensive and does not scale.
Even a simple task, like understanding the permissions granted to a single human user, can be
extremely challenging.
Solutions exist that automate the monitoring and mitigation of cloud identities risk and enforce least
privilege policies. Every cloud security stakeholder should be building such solutions into their strategy and
immediate action plan.
posture management (CSPM), each cloud identity’s baseline evolving threats GOVERNANCE SOLUTIONS KEEP
ACCESS RISK IN CHECK
cloud infrastructure
AND PROACTIVELY ENFORCE
LEAST PRIVILEGE POLICY