Fix picomatch audit vulnerability and complete security hardening verification
Override picomatch to 4.0.4 to resolve high-severity ReDoS (GHSA-c2c7-rcm5-vvqj), verify all security hardening tasks (gitleaks, pnpm audit, Docker non-root, Caddy headers, scanner blocking), sync specs, and archive the change. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
This commit is contained in:
parent
433886772f
commit
b6908fb288
10 changed files with 604 additions and 28 deletions
|
|
@ -2,32 +2,32 @@
|
|||
|
||||
- [x] 1.1 Add security headers block to Caddyfile: HSTS, X-Content-Type-Options, X-Frame-Options, Referrer-Policy, Permissions-Policy
|
||||
- [x] 1.2 Add Content-Security-Policy header (permissive initial policy allowing React Router inline scripts, OSM tiles, Sentry, WebSocket)
|
||||
- [ ] 1.3 Test headers with securityheaders.com or curl after deploy
|
||||
- [x] 1.3 Test headers with securityheaders.com or curl after deploy
|
||||
|
||||
## 2. Scanner Blocking
|
||||
|
||||
- [x] 2.1 Add Caddy path matcher for common scanner targets (.env*, .git*, wp-*, admin*, config.*, backup*)
|
||||
- [x] 2.2 Return 403 for matched paths before reverse_proxy
|
||||
- [ ] 2.3 Verify scanner paths return 403, normal paths still work
|
||||
- [x] 2.3 Verify scanner paths return 403, normal paths still work
|
||||
|
||||
## 3. CI Secret Scanning
|
||||
|
||||
- [x] 3.1 Add gitleaks/gitleaks-action@v2 step to CI workflow
|
||||
- [x] 3.2 Create .gitleaks.toml with allowlist for Sentry DSNs (public values)
|
||||
- [ ] 3.3 Verify gitleaks passes on current codebase
|
||||
- [x] 3.3 Verify gitleaks passes on current codebase
|
||||
|
||||
## 4. Dependency Auditing
|
||||
|
||||
- [x] 4.1 Add `pnpm audit --audit-level=high` step to CI workflow
|
||||
- [x] 4.2 Create .github/dependabot.yml for weekly pnpm dependency updates
|
||||
- [ ] 4.3 Verify pnpm audit passes on current codebase
|
||||
- [x] 4.3 Verify pnpm audit passes on current codebase
|
||||
|
||||
## 5. Docker Hardening
|
||||
|
||||
- [x] 5.1 Add non-root user to Journal Dockerfile runtime stage
|
||||
- [x] 5.2 Add non-root user to Planner Dockerfile runtime stage
|
||||
- [x] 5.3 Add non-root user to BRouter Dockerfile
|
||||
- [ ] 5.4 Test containers start and serve correctly as non-root
|
||||
- [x] 5.4 Test containers start and serve correctly as non-root
|
||||
|
||||
## 6. Server Hardening
|
||||
|
||||
|
|
@ -42,7 +42,7 @@
|
|||
|
||||
## 8. Verify
|
||||
|
||||
- [ ] 8.1 Run securityheaders.com scan on trails.cool and planner.trails.cool
|
||||
- [ ] 8.2 Verify scanner paths return 403 in production
|
||||
- [ ] 8.3 Verify CI passes with all new scanning steps
|
||||
- [ ] 8.4 Verify Docker containers run as non-root
|
||||
- [x] 8.1 Run securityheaders.com scan on trails.cool and planner.trails.cool
|
||||
- [x] 8.2 Verify scanner paths return 403 in production
|
||||
- [x] 8.3 Verify CI passes with all new scanning steps
|
||||
- [x] 8.4 Verify Docker containers run as non-root
|
||||
Loading…
Add table
Add a link
Reference in a new issue