Skip to content

RED PR - do not merge: GAP-02 regression - #3

Open
ashpearce wants to merge 2 commits into
mainfrom
red-pr-gap02
Open

ashpearce wants to merge 2 commits into
mainfrom
red-pr-gap02

Conversation

@ashpearce

@ashpearce ashpearce commented Sep 10, 2026 •

Copy link
Copy Markdown
Owner

Deliberate regression to prove the gate blocks a real HIPAA violation.

Sets enabled = false on the DynamoDB server_side_encryption block, which falls the table back to the AWS-owned key — no customer key custody, failing HIPAA 164.312(a)(2)(iv).

Expected: the grc-gate required check fails on the GAP-02 policy and the merge button is disabled. This PR is intentionally left open and unmerged.

First attempt removed only kms_key_arn; the provider back-filled it from state (Optional+Computed), the plan was a no-op, and the gate correctly passed — see WRITEUP finding 8. This commit sets enabled = false, which produces a real plan diff: the table would fall back to the AWS-owned key with no customer custody, failing HIPAA 164.312(a)(2)(iv).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant