Defending the Hornburg
summary
Use trusted managed infrastructure like Forge or a reputable VPS such as DigitalOcean, start with secure defaults in Laravel, and apply updates promptly; keep tested backups and a rehearsal incident‑response playbook (step‑by‑step restores). Rate‑limit login and API endpoints and put the site behind Cloudflare for DDoS mitigation; require MFA (auth apps or U2F keys over SMS) and enforce per‑action authorization. Ship monitoring/logging for noisy routes, hide admin tools behind VPN/IP allowlists, provide lockdown endpoints to disable features, and hire pentest/IR experts when needed.
AI-written summary · about
chapters (11)
- 0:00Start
- 2:25Helm’s Deep as trusted infrastructure
- 4:40Secure defaults and building on solid foundations
- 5:45Maintenance, updates, and patching
- 6:55The Glittering Caves, backups, and incident response
- 10:05Helm’s Dike, rate limiting, and DDoS protection
- 12:25The Deeping Wall and multi factor authentication
- 14:40The Hornburg, authorisation, and access control
- 15:15Monitoring, logging, and seeing the attack
- 16:25Defence in depth and layered security principles
- 18:00Final thoughts on preparation and resilience
related talks
26mThink Like an Adversary: OPSEC for Laravel Developers
27mLayered Security
59mEasily Digestible Security Pills
29mGraphQL Security Best Practices and Hardening
08mPractical web security
40mCloud Foundry Through the Eyes of a Hacker
51mPlaying to lose: making sensible security decisions by assuming the worst
01h 00mDefense-in-depth engineering