AWSKeyLockdown - Automatically deactivate leaked AWS access keys fo

项目说明

<p align="center">
<picture>
<source media="(prefers-color-scheme: light)" srcset="
<source media="(prefers-color-scheme: dark)" srcset="
<img alt="Clutch Security" src="
</picture>
<h2 align="center">AWSKeyLockdown</h2>
</p>

<di="center">


</div>

AWSKeyLockdown is a security automation tool designed to enforce immediate deacti of AWS access keys associated with IAM users flagged by the AWSCompromisedKeyQuarantine. This tool directly addresses limitations in the AWS response to detected compromised credentials, ensuring enhanced security posture and operational integrity.

O

AWS provides mechanisms to detect exposed credentials, such as those inad committed to GitHub. Upon detection, AWS applies the AWSCompromisedKeyQuarantine to the compromised IAM user. However, this policy alone does not completely mitigate risks, as it may still permit certain pri operations. AWSKeyLockdown closes this gap by automatically deacti all access keys associated with the impacted user upon detection, effectively pre unauthorized actions and data exfiltration.

Key Features

Demonstrations

Local testing demo

![asciicast]()

Li demo

![asciicast]()

Getting Started

Pre-requisites

#### Cloudtrail

Cloudtrail must be enabled before this tool is used.

#### Pre-requisites for local testing

For local testing, AWSKeyLockdown can simulate a response without requiring actual exposure of AWS credentials. To facilitate testing, make the following changes to lambda_function.py

After making these changes, apply terraform templates.

Installation

Make sure to update aws_profile value in .tf with your aws profile.

Demo

#### Testing IAM User

Create a test IAM user. We will leak this user for testing.

Save the access key and aws secret key. It will be leaked to Github.

#### Li - Leak keys on Github

For a real world demo, leak the abo AWS access keys and secret keys to a public github repository.

#### Local Testing

If you don't want to leak aws access keys to Github, alterantively attach AWSCompromisedKeyQuarantineV2 policy to the testing IAM user.

Attach AWSCompromisedKeyQuarantineV2 manually to a demo user.

Conclusion

Wait for a while for the policies to apply and run get-caller-identity command. To avoid caching, run aws s3 ls and then run aws sts get-caller-identity.

Once the aws access key is leaked to Github or when AWSCompromisedKeyQuarantineV2 policy is attached to an IAM user, you will see all the access keys associated with the IAM user gets disabled pre attackers from escalations and exfiltrations.

Destroy resources

Terraform templates

Testing IAM User

Debugging

Future Enahancements

项目信息

开发语言：HCL

Star 数：24

技术要点

该项目属于防护思路方向的开源资源，代码结构清晰，适合安全研究人员学习参考。项目围绕Automatically deactivate leaked AWS access keys for IAM users flagged by the AWSCompromisedKeyQuarantineV* policy展开，提供了可运行的实现，对理解相关安全机制、工具原理与攻防技术具有较高的研究价值。

从技术实现角度看，此类项目的核心在于对底层原理的深入理解与工程化落地。开发者在研究过程中可以结合官方文档与社区讨论，梳理项目的初始化流程、核心模块职责与数据流转，逐步掌握其中的技术细节与设计思路。

使用与学习建议

1. 下载源码压缩包，解压到本地环境。

2. 根据项目类型准备对应的运行环境与依赖。

3. 按照 README 中的步骤完成配置与部署。

4. 在隔离的测试环境中运行验证，避免影响生产系统。

免责声明

本资源来源于开源社区，仅供安全研究、技术学习与合法授权范围内的攻防演练使用，请勿用于任何非法或侵害他人权益的用途。使用本项目产生的一切后果由使用者自行承担。