Repository navigation
Conversation
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.
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-gaterequired 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 setsenabled = 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).