Think a QMS is just for accreditation? You might be missing the point.
Date: 19 November 2026
Author: Steve Cooper
Read Time: 4 mins
Lower Risk – Traceable Decisions – Better Outcomes.
Why every investigation, forensics, insider risk and incident response team should be using its Quality Management System, regardless of accreditation.
Mention “quality” to colleagues in forensics or insider risk and usually there’s a direct train of thought leading to accreditation; ISO/IEC 17025 or, in the UK, the Forensic Science Regulator’s Code of Practice being the standards that come up most often. If you’re not pursuing these accreditations, then there seems to be a pattern where Quality Management Systems (QMS) aren’t actively part of your workload.
I can understand why, but over the past 12 months I’ve spoken with law enforcement and corporate teams across the UK, Europe and the US (some of them very large global organisations) and I keep seeing the same thing. The teams have the NIMBUS QMS yet leave it untouched as there’s no requirement for accreditation.
Who changed the rule?
A few months back I was sitting with the Insider Risk team at a large financial organisation which had a very well-run insider risk programme. Their user behaviour analytics (UBA) tool watches for a defined set of risky behaviours and when one triggers, an alert opens a new case in NIMBUS.
As we were discussing opportunities for improving their current processes, one of the team asked me a question; did I have any ideas on how they could track changes to their UBA rules? Changes were being made on the back of incidents or when identified by various members of the team and these could be implemented by the administrator at any time. No prior review and no clear record.
The provenance of investigations is often fundamental to successful outcomes and in this instance, the rules that decide which employees get looked at (and which don’t) could shift totally under the radar with no governance and no audit trail. Now whether such a change would impact a simple internal HR investigation, I can’t say, but for tribunals or legal proceedings the question of “why was this person flagged and when did that behaviour become a break in organisational rules?” is likely one that deserves a defensible answer.
They did not have an answer. The irony was that the tool that was designed to give them one was already installed in their environment. They’d been avoiding actively using it because they “weren’t going for accreditation.”
What a QMS actually does
Take away the accreditation-specific language and a quality management system does a few quite ordinary things:
- It records how you say you operate. Policies and procedures are version controlled, so you can show exactly what the rules were on any given date.
- It provides a platform for internal checks. Policies are developed to assist organisations in managing risk; proactive internal audits provide the confidence that operations are as expected.
- It governs change. Ideas for improvement are captured, reviewed, approved and implemented, each with a named owner and a decision trail.
- It records when things go wrong. That includes investigation, what you found, recommendations for change and what was changed as a result.
- It gives leadership confidence. When the board asks, “are we in control of this?” you can show them evidence rather than just words.
Every one of those things matters to an insider risk programme, a corporate investigations team or a digital forensics unit. It doesn’t need accreditation to be worth having.
How a QMS can govern changes
So what did we sketch out as a potential way forward?
- The UBA tool would sit under a document-controlled policy that defines which behaviours are monitored and why.
- Any proposed change would start as an improvement action within their NIMBUS QMS.
- The suggestion gets logged, reviewed, developed and approved before an administrator implements any changes within the tool. Alongside this, a change request is raised against the policy and a new version is published.
- With that in place, any alert raised can be traced back to the exact version of the rule that triggered it, who approved that rule and why. Traceability, if you will…
A real problem, solved with a tool they already had.
Regardless of function, ask yourself;
- If a trigger was changed last year, could you show who approved it?
- Are your procedures properly version-controlled, or is it a case of “the latest copy on SharePoint”?
- When something goes wrong, is the investigation traceable and the fix recorded somewhere leadership can see?
- If a case were challenged tomorrow, could you reliably defend it with objective evidence? Could you prove which rules were in force when it was raised?
If any of those made you hesitate, you might just have a quality problem, whether or not you ever pursue accreditation.
Accreditation is the floor, not the ceiling
At BlackRainbow, we built the QMS in NIMBUS with accreditation in mind and it’s proven to do that job well. That being said, my most interesting conversations this year have been with teams that may never sit in front of an assessor and still need to prove their decisions were sound.
Accreditation proves you meet a given standard. Using your QMS properly is how you lower risk, improve outcomes and show you’re in control every day.
If yours is sitting idle, it might be time to take another look.
About the Author:

Steve Cooper is Product Manager at BlackRainbow, leading the development of solutions that help organisations manage digital evidence and forensic investigations more effectively. With 14 years of experience in policing and digital forensics, including leading a Digital Forensics Unit and supporting accreditation to ISO 17025 and the Forensic Science Regulator’s Codes of Practice, Steve works closely with practitioners to ensure technology meets the operational demands of modern investigations.

Share this post: