What the work looks like
You pick one exploit attempt from our honeypot data, for example a request aimed at a known router or web-app flaw, and work out what it is: which CVE, which software and versions it affects, what an attacker gets if it works, and how much of that software is exposed online. Where needed you test it safely in an isolated lab. Then you write it up so someone running a small organisation's IT can tell whether they are affected and what to patch.
What you’ll do
- Pick up an exploit or CVE seen in our sensor data
- Work out what it targets, what it achieves and who it reaches
- Write it up for a non-specialist reader
- Spend about 20–30 minutes a day reviewing incoming reports with the rest of the team, and flag promising leads to your team lead.
What you’ll bring
- Experience with vulnerabilities, exploits or malware analysis
- Clear technical writing
What you’ll get
- Published work with your name on it
- Hands-on time with real investigation tooling and data
- A path to running your own investigations