This project demonstrates how to perform a security assessment of an AWS environment using Prowler, an open-source cloud security auditing tool. The assessment evaluates the account against AWS security best practices and multiple compliance frameworks, then prioritizes findings and recommends remediation.
- Assess the AWS account security posture.
- Identify misconfigurations and security gaps.
- Evaluate compliance against industry frameworks.
- Prioritize risks.
- Produce remediation recommendations.
- Cloud Provider: AWS
- Authentication: AWS IAM Identity Center (SSO)
- Assessment Tool: Prowler v5
- Regions: All supported AWS regions
- Checks Executed: 614
| Tool | Purpose |
|---|---|
| Prowler | AWS security assessment |
| AWS CLI | Authentication and API access |
| IAM Identity Center | Secure SSO authentication |
| PowerShell | Scan automation |
- Define assessment scope.
- Authenticate using AWS IAM Identity Center.
- Execute a baseline Prowler scan.
- Review generated findings.
- Classify risks using a documented methodology.
- Prioritize remediation activities.
- Document accepted risks.
| Metric | Result |
|---|---|
| Checks Executed | 614 |
| Failed | 305 |
| Passed | 131 |
- IAM
- CloudTrail
- GuardDuty
- Security Hub
- AWS Config
cloud-security-audit/
├── docs/
├── evidence/
├── reports/
├── remediation/
├── scripts/
├── .gitignore
└── README.md
- AWS Security Assessment
- IAM Security
- Cloud Logging
- Threat Detection
- Security Monitoring
- Compliance Mapping
- Risk Analysis
- Security Documentation
- Remediation Planning
- Enable AWS Security Hub.
- Enable GuardDuty organization-wide.
- Configure AWS Config managed rules.
- Integrate findings into AWS Security Hub.
- Automate recurring scans with CI/CD.
This project was conducted in a controlled AWS environment for educational and portfolio purposes. Any sensitive account information has been omitted or redacted.