Security Testing

A test planned around what matters, run by a qualified partner, and followed by a retest.

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

A regional health clinic

The test report nobody could use

The challenge. A clinic pays for a penetration test as part of a grant. The report arrives with ninety findings in a spreadsheet. The IT team does not know which matter, the director does not know what to tell the board, and six months later most findings are still open.

The insight. A test is useful in proportion to its plan and its follow-up. A good plan says what is in scope and why, what the clinic most needs to learn, and who will fix what by when. A good follow-up ranks findings by effect on patients and the business, and proves the fixes with a retest.

The decision. For the next round the clinic asked for a scoped test, a ranked report and a retest, and named an owner for each finding.

The action. We wrote the test plan from the clinic’s threat model: the patient portal, the remote-access path and the guest wireless. We brought in a qualified testing partner and set the rules of engagement. When the report came back we ranked the findings, reduced ninety to nine that mattered most and explained each in plain words. The IT team fixed them, and the partner retested.

The result. The board saw one page: nine findings, nine fixed and verified. The next test’s scope started from this one’s record.

What Security Medic does

Test plans

Scope, goals and rules of engagement for vulnerability scans, penetration tests, configuration reviews and tabletop exercises, drawn from the threat model.

Coordination with a qualified tester

We bring in and manage an independent testing partner, so the work is done by people who do it every day. Each firm presents its own credentials.

Results in plain words

Findings ranked by effect and effort, with an owner and a date for each, for the team and for leadership.

Retest and closure

Fixes checked by a retest, and the record kept for auditors and insurers.

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. The test plan comes from the design and the threat model.
  • Assess. The partner runs the test; we coordinate and keep it in scope.
  • Review. The report is ranked and explained for the people who decide.
  • Conform. The IT team or provider fixes the findings; the retest confirms.
  • Improve. Each cycle widens the scope as the basics are met.

The standards we draw on

NIST SP 800-115 for technical security testing, the Detect and Identify functions of the NIST Cybersecurity Framework 2.0, the OWASP testing guides for web applications, and the testing requirements inside rules such as PCI DSS and NYDFS Part 500.

Threat modelling →Quality control →Audit preparation →

Getting ahead of it

Plan a retest into every test from the start, and put the fix dates in the plan. The result is closed findings, not a report on a shelf.

Start with a free 30-minute call

Tell us what you want to learn. We will talk through the test that would tell you the most.

Book a free 30-minute call