Security is job zero. At least, that's what we say. In reality, business value comes first most of the time and security only becomes a job once either an audit must be performed, or perhaps when it's already too late.
So, let's make security quick and easy! Prowler 3 is our weapon of choice since it is a breeze to run and can export a nice HTML that we can give to management.
To keep things quick and easy, we're going to run Prowler from AWS CloudShell. If you don't know what AWS CloudShell is, log on to the AWS console for the account that you want to scan and press the commandline-ish-button-thing as pictured below:
Once logged in, you'll have a command line that has the same permissions as the user you've just launched it with. If you already have Python3.9 installed (enter
python3.9 --version to test) you can skip the next part. If you don't, we first need to install Python 3.9. Copy and paste the following into AWS Cloud Shell, and press enter:
sudo yum -y install gcc openssl-devel bzip2-devel libffi-devel
tar zxf Python-3.9.16.tgz
sudo make altinstall
After installing Python 3.9 (which I have to admit, might take our allotted 5 minutes), we can continue installing Prowler. Enter the following commands, and again, don't forget to press enter:
pip3.9 install prowler
Currently, the latest version of Prowler is
3.1.2, so that's what's installed for me:
So, let's run that 5 minute security audit!
Enter the following command, replacing
eu-west-1 with the region of your choice, and read on while it's running.
prowler aws -f eu-west-1 -M html
After running this command, Prowler should be authoring your AWS account against 247 checks.
In the command, we're using the
-f flag to tell Prowler to run only in eu-west-1
-M flag to ask Prowler to only export the results in HTML.
Removing both flags will have Prowler run in all active AWS regions, as well as export the results in JSON and CSV.
Much more options are available, and instructions can be found using the
Viewing the report
Once Prowler is finished, it should show a summary, as well as the path that the HTML has been saved to.
The summary for my (mostly empty) AWS account looked like this:
I'm very interested in the critical results, so let's copy the path to the HTML file, and click
Actions in the upper right corner menu, then
Download file and paste the path, so your HTML report is downloaded.
Once opened, your report should look a bit like this:
As you can see, Prowler reports on the context like the AWS account, region and role that was used to perform the scan, as well as an overview of the assessment.
As I was most interested in the critical findings, I used the
Filters button to only show results with status
FAIL and severity
critical. The missing MFA config was no surprise when I first ran Prowler, but I was especially charmed by the critical finding that Prowler generated for my Lambda function.
You see, when I created the Lambda function for this post, I did something I see people do a lot: I put a clear text password in my environment, as shown below.
For all checks that are performed, Prowler will also explain the
Risk for failure, a
Recommendation for mitigation and a link to the AWS documentation with instructions. Everything you need to understand why there's so much red in the results, how to turn them green and most importantly; why.
Prowler is an awesome tool to get a quick security assessment of your AWS (Or Azure!) environment. Outside what this blog covers, Prowler has much more features and options available, like sending results to AWS Security Hub or scheduling Prowler to run daily from inside a container.
Even though I'm positive Prowler is something that should be in your toolset, we must be aware that it does not paint a full picture. Prowler only reviews your AWS infrastructure and not your application. Also, it does not verify if some best practices, like blocking all public access for S3, are configured.