Skip to content

Lab 9: Trivy/ZAP scans, security headers middleware, govulncheck CI#1223

Open
selysecr332 wants to merge 12 commits into
inno-devops-labs:mainfrom
selysecr332:feature/lab9
Open

Lab 9: Trivy/ZAP scans, security headers middleware, govulncheck CI#1223
selysecr332 wants to merge 12 commits into
inno-devops-labs:mainfrom
selysecr332:feature/lab9

Conversation

@selysecr332

Copy link
Copy Markdown

Summary

Lab 9 — DevSecOps (Mahmoud Hassan, selysecr332)

  • Task 1: Trivy image/fs/config scans + CycloneDX SBOM (aquasec/trivy:0.59.1); triage of all HIGH/CRITICAL findings in submissions/lab9.md
  • Task 2: OWASP ZAP baseline (ghcr.io/zaproxy/zaproxy:2.16.1); security headers middleware on all routes + unit tests; before/after ZAP evidence (finding 10021 resolved)
  • Bonus: govulncheck@v1.1.4 job added to .github/workflows/ci.yml with red/green demo logs
  • Upgraded builder image to golang:1.24.13-alpine to address stdlib CVEs

Key files

  • app/middleware.go — security headers middleware
  • security/scripts/run-trivy.sh, run-zap-baseline.sh
  • security/reports/ — scan artifacts + SBOM
  • submissions/lab9.md — triage tables + design questions

Test plan

  • go test ./... passes
  • Trivy scans captured in security/reports/
  • ZAP before/after: 10021 (X-Content-Type-Options) gone after rebuild
  • govulncheck ./... green on final branch

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant