[Tip#21] It may seem strange but non-production mail can be a security risk.
[Tip#20] Laravel's helpers are great, but make sure you know everything they do before you use them.
[InDepth#8] Policy Objects are incredibly powerful. Use them.
[Tip#19] Because all randomness should be cryptographically secure.
Security Discussion: Are Routes Sensitive Information?For this week’s security discussion, I want to pose an interesting question: Are routes sensitive information? Routes contain a map of your enti…
[Tip#18] Dependencies are security risks, especially if you have a lot of them or don't keep them updated...
[InDepth#7] Content Security Policies are an incredibly powerful security feature built into the browser, and as it turns out, they are also pretty easy…
[Tip#17] It's easy to forget to update the admins list when it changes...
Security Discussion: Why aren't you using a Content Security Policy?This week I want to discuss Content Security Policies (CSP). I’ve had them on my list to tackle in an In Depth for a while, and getting a feelin…
[Tip#16] Ever clicked a link that looked legitimate, but took you somewhere unexpected?
Laravel Security In Depth: Timing Attacks[InDepth#6] You can use response timing to infer important information... in this post we dive into timing attacks in Password Resets and more. 
[Tip#15] Because we don't already have enough to worry about, without also needing to factor in other characters and emoji too...