Add pii-protection skill - #193
Open
joaovictortinoco wants to merge 1 commit into
Open
Conversation
Protect PII in AWS logs and storage at the infrastructure layer without touching application code. Pairs CloudWatch Logs Data Protection (real-time masking of live logs) with Amazon Macie (PII discovery in S3), routing HIGH-severity findings through Security Hub -> EventBridge -> SNS. RFC: awslabs#192
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Adds a
pii-protectionskill toaws-dev-toolkit: stop PII leaks in AWS at theinfrastructure layer, no application code change required. Pairs CloudWatch Logs
Data Protection (real-time masking of sensitive fields in live logs) with Amazon
Macie (discovery of PII already at rest in S3), routing HIGH-severity findings
through Security Hub -> EventBridge -> SNS.
Why
The existing security skills (
security-review,iam,hipaa-assistant,well-architected) cover IAM, IaC scanning, and compliance frameworks — but noneaddress runtime data-protection: masking sensitive data already flowing into logs, or
discovering undiscovered PII in storage. Opinionated stance: protect at the infra
layer first, refactor code later.
RFC
Implements #192.
Notes
SKILL.md, dev-toolkit style (two-layer approach -> process -> gotchas-> output table). No
references/folder.Macie's 2-10 min finding lag,
cdk destroynot disabling Macie (ongoing billing),Macie per-GB cost, and
logs:Unmaskas the audit escape hatch.markdownlint-cli2anddprint checklocally against repo config.claude --plugin-dir ./solution-architecture/plugins/aws-dev-toolkit.