Cloud security for teams building on AWS.
A clear picture of how your AWS environment is exposed, and what to change first.
In this practice
- AWS Cloud SecurityProtecting the applications, data and infrastructure you run on AWS.
- Cloud Security AssessmentA structured look at your cloud environment to find what is exposed and what that puts at risk.
- AWS Security Configuration ReviewA review of how your AWS services are configured against how they should be.
We work to: CIS AWS Foundations Benchmark, AWS Well-Architected Framework, Security Pillar.
The problem
Cloud accounts grow one quick decision at a time.
A bucket opened for a demo. A role given broad permissions to unblock a release. An admin port left reachable after a late fix. None of these looks like a security decision when it is made.
Added together, they are how most cloud exposure is created, and nobody on the team has the full list.
What we look at.
We read your AWS account the way an attacker would: what is reachable, what is over-permitted, and what would be quietly useful to someone who got in.
- Identity and access
- Who and what can do what. Over-permissive IAM roles, leaked access keys, accounts without MFA.
- Storage and data
- What is readable from outside. A storage bucket that is public and should not be.
- Network exposure
- What is reachable from the internet. An admin port that was never meant to be.
How it runs.
Four steps. You know the scope before any of it starts.
Agree the scope.
Which AWS accounts and environments are in, and which are out.
We review.
Configuration and exposure, across the areas above.
Findings, ranked.
What we found, ordered by the risk it carries.
Go through it together.
We take your engineers through what to change first.
What you have at the end.
- A clear answer to “what can be attacked?” for your AWS environment.
- A list of what is exposed, ranked by risk.
- A first set of changes your engineers can start on.
Questions we get asked.
Is this only for AWS?
Our cloud security practice is built around AWS. If you run workloads elsewhere, tell us, and we will say plainly whether we are the right fit.
What is the difference between the assessment and the configuration review?
The assessment is the broad view: how your cloud environment is exposed and what that puts at risk. The configuration review is the close view: how your AWS services are set up, compared with how they should be.
Do we have to fix everything you find?
No. Findings are ranked so you can start with the ones an attacker would use first and schedule the rest.
Start with your AWS account.
Tell us roughly what you run. We will suggest where to begin.