A command line security audit tool for Amazon Web Services
Cloud Security Audit is a command line tool that scans for vulnerabilities in your AWS Account. In easy way you will be able to identify unsecure parts of your infrastructure and prepare your AWS account for security audit.
Currently Cloud Security Audit does not support any package managers, but the work is in progress.
First of all you need to download Cloud Security Audit to your GO workspace:
$GOPATH $ go get github.com/Appliscale/cloud-security-audit
$GOPATH $ cd cloud-security-auditThen build and install configuration for the application inside cloud-security-audit directory by executing:
cloud-security-audit $ make allIf you're using MFA you need to tell Cloud Security Audit to authenticate you before trying to connect by using flag --mfa.
Example:
$ cloud-security-audit --service s3 --mfa --mfa-duration 3600
To perform audit on all EC2 instances, type:
$ cloud-security-audit --service ec2
You can narrow the audit to a region, by using the flag -r or --region. Cloud Security Audit also supports AWS profiles -
to specify profile use the flag -p or --profile.
+---------------+---------------------+--------------------------------+-----------------------------------+----------+
| AVAILABILITY | EC2 | VOLUMES | SECURITY | |
| | | | | EC2 TAGS |
| ZONE | | (NONE) - NOT ENCRYPTED | GROUPS | |
| | | | | |
| | | (DKMS) - ENCRYPTED WITH | (INCOMING CIDR = 0.0.0.0/0) | |
| | | DEFAULT KMSKEY | | |
| | | | ID : PROTOCOL : PORT | |
+---------------+---------------------+--------------------------------+-----------------------------------+----------+
| eu-central-1a | i-0fa345j6756nb3v23 | vol-0a81288qjd188424d[DKMS] | sg-aaaaaaaa : tcp : 22 | App:some |
| | | vol-0c2834re8dfsd8sdf[NONE] | sg-aaaaaaaa : tcp : 22 | Key:Val |
+---------------+---------------------+--------------------------------+-----------------------------------+----------+- First column
AVAILABILITY ZONEcontains information where the instance is placed - Second column
EC2contains instance ID. - Third column
Volumescontains IDs of attached volumes(virtual disks) to given EC2. Suffixes meaning:[NONE]- Volume not encrypted.[DKMS]- Volume encrypted using AWS Default KMS Key. More about KMS you can find here
- Fourth column
Security Groupscontains IDs of security groups that have too open permissions. e.g. CIDR block is equal to0.0.0.0/0(open to the whole world). - Fifth column
EC2 TAGScontains tags of a given EC2 instance to help you identify purpose of this instance.
You can find more information about encryption in the following documentation:
To perform audit on all S3 buckets, type:
$ cloud-security-audit --service s3
Cloud Security Audit supports AWS profiles - to specify profile use the flag -p or --profile.
+------------------------------+---------+---------+-------------+------------+
| BUCKET NAME | DEFAULT | LOGGING | ACL | POLICY |
| | | | | |
| | SSE | ENABLED | IS PUBLIC | IS PUBLIC |
| | | | | |
| | | | R - READ | R - READ |
| | | | | |
| | | | W - WRITE | W - WRITE |
| | | | | |
| | | | D - DELETE | D - DELETE |
+------------------------------+---------+---------+-------------+------------+
| bucket1 | NONE | true | false | false |
+------------------------------+---------+---------+-------------+------------+
| bucket2 | DKMS | false | false | true [R] |
+------------------------------+---------+---------+-------------+------------+
| bucket3 | AES256 | false | true [RWD] | false |
+--------------------------- --+---------+---------+-------------+------------+- First column
BUCKET NAMEcontains names of the s3 buckets. - Second column
DEFAULT SSEgives you information on which default type of server side encryption was used in your S3 bucket:
NONE- Default SSE not enabled.DKMS- Default SSE enabled, AWS KMS Key used to encrypt data.AES256- Default SSE enabled, AES256.
- Third column
LOGGING ENABLEDcontains information if Server access logging was enabled for a given S3 bucket. This provides detailed records for the requests that are made to an S3 bucket. More information about Server Access Logging can be found here - Fourth column
ACL IS PUBLICprovides information if ACL (Access Control List) contains permissions, that make the bucket public (allow read/writes for anyone). More information about ACLs here - Fifth column
POLICY IS PUBLICcontains information if bucket's policy allows any action (read/write) for an anonymous user. More about bucket policies here R, W and D letters describe what type of action is available for everyone.
You can find more about securing your S3's in the following documentations: