hunt-cloud-misconfig

Detecting public AWS S3 buckets and RDS snapshots involves scanning your cloud infrastructure for misconfigurations like public access settings. This skill validates findings by attempting actual data read operations to confirm exposure.

Validating Lambda function misconfigurations for unauthenticated access requires testing actual execution paths. This skill performs remote code execution validation against detected endpoints to eliminate false positives from scan results.

Yes, you need valid AWS and Azure credentials to scan and validate misconfigurations in S3 buckets and Azure storage accounts. The validation process performs actual data read and write operations requiring authenticated access.

Checking Azure storage accounts for misconfigurations involves scanning public access settings and validating exposure through actual blob read operations. This approach confirms real data breach risks rather than just flagging configuration anomalies.

Validating cloud infrastructure misconfigurations through RCE and data writes requires valid credentials and careful execution to avoid altering production data. Limitations include potential security alert triggers during active validation and the scope of accessible resources.

Yes, cloud misconfiguration detection works with both AWS and Azure storage services simultaneously. It scans S3 buckets and Azure storage accounts in a single pass, validating findings using boto3 and azure-storage-blob libraries.