Track 12 of 12
Working in security
Report it well, practise legally, and keep going.
Intermediate 4 lessons Prerequisite: Any of the security tracks. This one is about practice rather than tools.
The part that turns skill into work. What written authorisation actually means and why verbal permission is not enough, how to write a finding somebody can act on, what to do when you find a problem in something you do not own, and what certifications and labs do and do not prove. This is not legal advice, and the law differs by country.
By the end, you can write a finding, disclose a problem responsibly, and choose what to learn next on evidence.
Lessons in this track
- 01 Rules of engagement and the law Verbal permission is not authorisation. Write down the scope, the window and the limits before you touch anything.
- 02 Writing a finding someone can act on A finding is a title, what was observed, why it matters, how to reproduce it, and what to do. In that order, every time.
- 03 Responsible disclosure You will find a problem in something you do not own. Report it privately, give time for a fix, and keep a record of what you did.
- 04 Certifications, labs and what they actually prove A certification proves you passed an exam. Hands-on work is what gets read. Build a portfolio of things you actually did.