Cybersecurity

Authorised assessments for schools and service providers. I find exploitable vulnerabilities in production systems, prove them end to end, and hand back severity-ranked fixes. The two engagements below are what that looks like in practice.

eSchool platform

My school's eSchool platform was the first sustained engagement — a production system used daily by staff and students. I worked from a regular user account. Could a student reach something they weren't meant to? Could an unauthenticated request still get away with something? Where had the platform assumed trust it never verified? Each question came back as a working proof, with a fix attached.

LMS of a physical-education platform

The second engagement was the LMS behind a physical-education platform, and it looked different from the first. I came in with a low-privilege account and tested how far it could be pushed; I looked at whether the upload and content-delivery paths could be abused, and at how much of the platform was visible before any login. Same rule as before: demonstrate first, write up second.

What gets delivered

Each engagement ends with a severity-ranked report. For every finding it says what the flaw is, how far an adversary could take it, and how to fix and verify the fix — the owner patches the worst first. The engagements stay anonymous and the reports stay with their owners. Nothing gets published that could be used against a system that hasn't patched yet.