Reporting Vulnerabilities & Defects ยท Lesson 1 of 2
You've found a vulnerability
Study notesAbout 3 minutes. A full lesson with quick checks is on its way.
In short
If you find a security vulnerability, report it straight away through the security process. Don't probe it further or tell anyone else.
In your work
Testing a client's member portal, you find you can see other members' invoices by changing a number in the address. You stop, write down the steps and report it to security, without downloading anything.
What the UK rules say
- Going beyond the access you're authorised for can be an offence under the Computer Misuse Act 1990, even with good intentions.
- The UK's Software Security Code of Practice expects vendors to run an effective vulnerability disclosure process, and the NCSC publishes a toolkit for one.
What to do
- Stop testing once you've confirmed the problem.
- Report it through the security process, with clear steps to reproduce it.
- Keep the details private until security says otherwise.
- Follow their instructions, including any fix or retest.
Watch out for
- Probing further 'to see how bad it is'.
- Mentioning it publicly, even vaguely, before it's fixed.
In your organisation
How do you report a vulnerability at your organisation, and does it publish a security contact for outsiders?
Your employer's own policies come first.
Sources
- legislation.gov.uk, Computer Misuse Act 1990, section 1 (opens in a new tab), checked 6 October 2026.
- GOV.UK (DSIT and NCSC), Software Security Code of Practice (opens in a new tab), checked 6 October 2026.
- NCSC, Vulnerability Disclosure Toolkit (opens in a new tab), checked 6 October 2026.
UK law and guidance, explained for learning. Not legal advice.
