Challenge
Security guidance and live application flows needed to remain usable on small screens while enforcing origin, input, session, and content boundaries.
Frontend + application security
Security-aware public web platform
A responsive cybersecurity experience combining accessible public content, threat intelligence, hardened mutations, session-aware routes, and resilient UI states.
Technical response
Use server-side API mediation, bounded validation, rate limits, hardened headers, accessible controls, reduced-motion support, and explicit empty and error states.
Outcome
The codebase includes tested security utilities, a Django-backed contact path, responsive public routes, and production build checks without a Supabase runtime dependency.
04
Architecture
The delivery path.
- 01Accessible interface
- 02Next.js route handlers
- 03Validation + rate limits
- 04Django API
- 05Operational records
05
Security
Controls in context.
- Same-origin mutations
- Bounded request bodies
- Request fingerprinting
- No-store sensitive responses
06
Evidence map
Where the claims can be inspected.
These repository paths are references, not public downloads. They make the scope of each statement explicit.
- web/src/lib/security
- web/src/app/api/contact/route.ts
- docs/corporate-website.md