Feature/lab11 - #7
Open
raaller wants to merge 5 commits into
Open
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
Deliver Lab 11 with a hardened Nginx reverse proxy, TLS 1.3, production edge controls, and a ModSecurity v3 + OWASP CRS WAF sidecar.
Changes
labs/lab11/reverse-proxy/nginx.conf: HTTP-to-HTTPS redirect, TLS 1.3 only, approved TLS 1.3 cipher suites, X25519, disabled session tickets and early data, and hardened session settings.labs/lab11/waf/Dockerfilewith the pinnedowasp/modsecurity-crs:4.25.1-nginx-alpine-ltsimage.labs/lab11/waf/docker-compose.override.ymlexposing the WAF on port8443and proxying accepted requests to the hardened Nginx endpoint over TLS.submissions/lab11.mdwith configuration excerpts, runtime evidence, security-header explanations, OCSP-stapling analysis, WAF evidence, and deployment tradeoffs.Testing
Nginx configuration validation
HTTP-to-HTTPS redirect
TLS 1.3, cipher suite, and key exchange
Security response headers
Login rate limiting
The six HTTP
401responses reached Juice Shop and the remaining 54 requests were rejected by Nginx with HTTP429.Slow-header timeout
The TLS socket test sent an incomplete HTTP request header and waited for the server to close the connection.
WAF configuration validation
SQL-injection probe without and with the WAF
The baseline Nginx endpoint forwarded the payload to Juice Shop, while the WAF rejected the same request before it reached the application.
OWASP CRS audit evidence
Rule
942100detected the SQL-injection payload at paranoia level 1, and rule949110enforced the HTTP403response.Artifacts & Screenshots
labs/lab11/reverse-proxy/nginx.conf— hardened reverse-proxy configuration.labs/lab11/waf/Dockerfile— pinned ModSecurity v3 and OWASP CRS 4.25.1 image.labs/lab11/waf/docker-compose.override.yml— WAF sidecar deployment and TLS upstream configuration.submissions/lab11.md— complete submission report with runtime proof and security analysis.Checklist
feat(lab11): hardened nginx + WAF sidecar)submissions/lab11.mdexists