Quality Control

Work is done when the evidence shows it meets the design.

Already have an IT provider? Here's how we work together.

A manufacturer closing a list of security fixes

Done, according to the ticket

The challenge. A manufacturer’s IT provider reports that all twelve items from the last assessment are closed. At the next review, two are found only half done: multi-factor sign-in covers the office but not the plant-floor remote tool, and the backup runs but has never been restored.

The insight. A ticket marked closed shows that someone believes the work is done. Quality control means each fix has acceptance criteria written before the work, evidence collected after it, and a person other than the builder who checks.

The decision. The company added an acceptance line to every fix: what will be true, how we will show it, and who will check.

The action. We rewrote the twelve items with acceptance criteria and asked the IT provider to attach evidence for each. We checked the evidence, reopened the two that fell short, and watched a restore from backup end to end. We now use the same rule for our own reports: a second review of facts and wording before they go to a client.

The result. Eleven items passed on evidence and one, the restore, was fixed and re-checked. The company’s record shows who checked what and when.

What Security Medic does

Acceptance criteria

Each fix or deliverable defined by what will be true when it is done, before the work starts.

Independent checking

A person other than the builder reviews the evidence, and where it matters, watches the control work.

An evidence register

Dated proof for each control, with an owner, so audits and renewals draw on one record.

Internal audit and assurance advisory

Audit program design, risk-based audit planning, quality assurance programs and conformance with the IIA Global Internal Audit Standards, for organizations building or maturing an independent assurance function.

Review of our own work

Our assessments and reports get a second review of facts, sources and wording before delivery.

Where this sits in the cycle

Every client goes through the same six steps, from a town office to a family at home. The Security Medic method

  1. 1. Govern
  2. 2. Design
  3. 3. Assess
  4. 4. Review
  5. 5. Conform
  6. 6. Improve
  • Design. Acceptance criteria are part of the design of each fix.
  • Assess. Evidence is collected and tested against the criteria.
  • Review. Results are reported honestly, including items that fall short.
  • Conform. This is the heart of the Conform step: prove it meets the design.
  • Improve. Misses feed the next round of criteria, and the standard rises.

The standards we draw on

The Govern and Identify functions of the NIST Cybersecurity Framework 2.0 for oversight and improvement, NIST SP 800-53A for assessment procedures, and the evidence expectations of audit frameworks such as SOC 2 and ISO/IEC 27001. We prepare clients for those audits; an independent firm performs them.

Audit preparation →Security testing →Working with your IT provider →

Getting ahead of it

Ask for acceptance criteria on the next fix before it starts, and the evidence is already collected when an auditor or insurer asks.

Start with a free 30-minute call

Tell us what has been marked done. We will talk through how to check it.

Book a free 30-minute call