Library / Security & Compliance
Security & Compliance
Scan GitHub for Exposed AWS Keys and Alert Slack
When you run it, it lists active AWS IAM access keys, searches GitHub for exposed copies, and reports matches to Slack.
What it does
# 🔐🕵️♂️ GitHub Scanner for Exposed AWS IAM Keys – Quick Overview ## ⚙️ Workflow at a Glance 1. 🔍 Automated Discovery Scans GitHub repositories for exposed AWS IAM access keys associated with your AWS account. 2. 🧠 Intelligent Filtering Processes only active access keys and eliminates duplicate findings. 3. 🚨 Risk Assessment Evaluates exposure severity and assigns risk levels (High/Medium/Low) based on findings. 4. 📣 Actionable Alerts Sends detailed Slack notifications with interactive buttons for immediate response. 5. 🛠️ Remediation Guidance Provides step-by-step instructions for securing compromised credentials. 6. 🔄 Continuous Monitoring Maintains ongoing surveillance to detect new exposures quickly. --- *🛡️ This workflow helps security teams quickly identify and respond to potential security breaches from exposed AWS credentials.*
The steps
- When clicking ‘Execute workflow’
- Split Users for Processing
- Get User Access Keys
- Filter Active Keys Only
- Search GitHub for Exposed Keys
- Aggregate Search Results
- Check For Compromised Keys
- Generate Security Report
- Continue Scanning
- Slack
- Format Slack Alert
- Prepare Github Search
- Rate Limit Wait
- List AWS Users1
16 steps in total.
Similar automations