
Newsletter
Laravel Security In Depth → Securing Laravel
Let's talk about all the changes: new name, new domain, and a purple logo...
Friendly Hacker, Speaker, and PHP & Laravel Security Specialist.🕵️ I hack stuff on stage for fun. 😈
Newsletter
Let's talk about all the changes: new name, new domain, and a purple logo...
In Depth
[InDepth#16] According to random folks on the internet (i.e. social media), "insecure functions" are a wide and varied concept. Let's take a look at the common themes across the different ideas...
Security Tips
[Tip#44] Check out that one simple trick... I mean... This is my favourite way to avoid XSS.
Security Tips
[Tip#43] It's essential for limiting bot attacks, and don't forget it on other sensitive routes like authentication...
In Depth
[InDepth#15] There is a false confidence about mass-assignment vulnerabilities that hides how easy it is for them to occur and be exploited...
Security Tips
[Tip#42] Validating single values is easy, but what about arrays?
Security Tips
[Tip#41] It's quite common to inject JSON into Blade templates for various use cases, but is it actually safe to do so? Not really...
Security Tips
[Tip#40] Let's complete the set of request input helpers and their security implications
Security Tips
[Tip #39] Why treat all user input as strings when you can pull out specific values and automatically cast them as the types you're expecting?
Security Tips
[Tip #38] Laravel is full of little helpers and features, and the Timebox is one that's often overlooked.
Security Tips
[Tip#37] If you need to generate passwords in your app, it's important to use a cryptographically secure algorithm. Laravel makes this easy by giving us the Str::password() helper!
In Depth
[InDepth#13] User input comes in many different forms, and sometimes your app will believe whatever your users tell it... especially if it's in a header!