-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Header change detection construct #1422
Conversation
The build is failing for a strange reason 🤔
|
packages/header-change-detection/lib/header-change-detection.ts
Outdated
Show resolved
Hide resolved
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Few little housekeeping things and TS questions - looking good!
const securityHeaders = HEADERS?.split(",") || [] | ||
|
||
type Headers = Map<string, string | undefined> | ||
type URLHeaders = Map<string, Headers> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm wondering if commentary describing what the string key is here (the URL, right?) might make it clearer?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM! Nicely done 🕺
83307c7
83307c7
to
3e74aae
Compare
Description of the proposed changes
This is a big PR, apologies. Probably best to read the readme which describes the purpose of what I'm adding here. TL;DR: this is required for PCI DSS v4 11.6.1.
This creates a Lambda, DynamoDB table, and EventBridge schedule to check for header changes. The idea is that this construct can be added to any hosting stack to add the header change detection functionality.
Notes to reviewers
@toddhainsworth I've added you specifically for the Lambda function code review but feel free to review other areas as well.
🛈 When you've finished leaving feedback, please add a final comment to the PR tagging the author, letting them know that you have finished leaving feedback