Day-to-Day Responsibilities
Study software, apps, devices or systems to find flaws such as weak input handling, poor authentication or insecure settings.
Test systems only in authorised environments: your own labs, practice platforms, or products where the owner has given written permission.
Work out whether a flaw can realistically be misused, how many users it affects, and how serious it is, often using a standard severity score.
Write clear reports for the developer or vendor with steps to reproduce the problem, the likely impact and a suggested fix.
Follow responsible disclosure: give the vendor reasonable time to patch before any details are shared publicly.
Retest after the fix is released to confirm the flaw is closed and no new problem was introduced.
Keep up with new attack techniques, published advisories and security tools, and share what you learn with the team.


