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.