Method v.s. Madness: Developing Flexible Security Automation Workflows

How "method" and "madness" can feed into one another to strike a balance between a well-defined security testing methodology and free-flowing creative intuition.

Transcript

1. Developing Flexible Automation Workflows Method v.s. Madness
2. @mhmdiaa on Twitter, GitHub, etc https://mhmdiaa.com/projects Trickest’s Head of Workflows https://github.com/trickest https://trickest.com/blog Who Am I
3. Content, content, and more content YouTube Twitter Disclosed Reports Blogs Conference Talks GitHub Documentation Research
4. which is awesome BUT...
5. We Can’t Remember Everything
6. Yay, I got a new client/BBP invite Now what?
7. Prioritize What Matters
8. We’ve all been there…
9. Help Others
10. Accelerate learning and be a better researcher
11. Solution
12. Build a System around the knowledge
13. Not all systems are created equal
14. Memory Consume content, hope to recall it 01
15. —Someone who didn’t remember it, probably “I’ll just remember it!”
16. Archive - Keep track of valuable insights - By source (Twitter, YouTube, etc) 02
17. Archive - Keep track of valuable insights - By source (Twitter, YouTube, etc) 02
18. Archive - Keep track of valuable insights - By source (Twitter, YouTube, etc) 02
19. Methodology Structure by actionability 03
20. Automation - Remove the need for triggers - Scale, monitor, etc 04
21. Have a bias for action
25. Demo Time!
26. You can (and should) always iterate
32. • Have a bias for action • Start with the biggest time sinks • Don’t 100% rely on automation and cancel out your creativity • It’s a journey, not a sprint • Develop your skills • Frequently review your methodology and approach with objectivity • Help others Takeaways
33. Thanks! Questions?