What the work looks like
You turn what attackers actually try against our sensors into practical security advice. If our honeypots show login attempts on exposed remote-access services within minutes of going online, you explain what that means for a small organisation: what to stop exposing, where multi-factor authentication matters most, and how fast patches really need to go in. You back each recommendation with our data, map it to a framework, and write it for whoever looks after the IT, often one volunteer.
What you’ll do
- Turn observed attack patterns into specific controls
- Measure what each control buys against real attack timing
- Write practical guidance for small-organisation IT
- 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
- Interest in security controls and frameworks
- Practical, plain-language 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