feat(lab11): hardened nginx + WAF sidecar#11
Merged
Merged
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.
Goal
This PR hardens the Nginx reverse proxy with TLS 1.3 and security headers, applies production-grade limits, and deploys a ModSecurity WAF sidecar with OWASP CRS to block attacks.
Changes
Testing
curlandopenssl s_client.seq/xargsand connection timeouts by sending partial payloads.?q=' OR 1=1--) with an HTTP 403 Forbidden (Rule 942100), while pure Nginx allowed the same payload to hit the backend.Artifacts & Screenshots
submissions/lab11.mdfor full command outputs, test evidence, and audit logs.Checklist