2021 OWASP Top Ten: Insecure Design

[@BerniesBastelBude]

good examples - thx for explanation; I like this series!

[@devcentral]

...and thanks for the comment! :-) Glad you enjoyed the video!!

[@proFFessor90]

this one kinda confuses me a lot. it looks like it can be described as "logical/flow issues". need to take a closer look, atm this one is weird

[@huy19437]

How do they know the others request from Attackers is actually one?

[@medhasni6432]

So it s just a business logic error, right?

[@Sminthsonth]

indeed

[@barebears289]

Thank you😄

[@aishatalha5373]

can we detect these with the help of any Software or tool maybe ?

[@aubreyking3685]

You bet. Any DAST or web app scanner searches for these out of the gates. We are partnered with several companies for importing scan data from these tools for our F5 Advanced Web Application Firewall. In this way, you get to understand the holes in your applications and then protect them appropriately while they get fixed. App development times can be lengthy, but WAF policy can be applied in minutes from a scan like that.

[@mistmedia3712]

OWASP ZAP is definitely a big one if not the biggest

[@petersdicki5688]

How do you write backwards?

[@devcentral]

Thanks for the comment! Here's how we produce these: kzbin.info/www/bejne/i2iokH9qrKiDisU

[@winkyty89]

@@devcentral but the label on the shirt stays the same... in the right position... i'm so confused, but thx for the video anyway

[@devcentral]

@@winkyty89 yep...stage tricks! We had shirts with reverse logos on the wrong side, so when we flip the image, all is well! :)