Skip to content

Capability Tests

Capability tests illustration

Capability Tests is where you record a test of whether your organisation can actually do what its controls say: an incident response exercise, a continuity test, or another test. Use it after a tabletop exercise, a failover test or a restore drill, so the date, scenario, result and findings are on record for an auditor, and each finding is tracked to closure as a deficiency.

This page supports the SCRMS Prioritized Implementation Guide (PIG).

Supports PIG step 29.

Select Capability Tests in the sidebar, under CONTROLS & FRAMEWORKS.

Everyone in the organisation can see the tests. Only an editor or admin can record a test, correct one or add a finding.

  1. Select Record test.
  2. Enter a Title.
  3. Choose the Type: Incident response, Continuity or Other.
  4. Set Tested on: the day the test was run. It cannot be later than today.
  5. Describe the Scenario: what was tested, and how.
  6. Choose the Result: Passed, Passed with findings or Failed.
  7. Describe the Outcome: what happened, and what was learned.
  8. For each finding, select Add a finding and fill in its fields (see below).
  9. Select Record test.

What you’ll see: the test appears in the list and the counts update. Each finding is raised as a deficiency on the Deficiencies (POA&M) page.

ResultFindings needed
PassedNone. Passed means nothing was found
Passed with findingsAt least one
FailedAt least one

The form lists any problem under the fields and keeps Record test disabled until it is fixed. So a failed test needs at least one finding before you can record it.

Each finding takes the same fields as a deficiency:

FieldNotes
TitleRequired
ControlOptional. An SCF ID of a control in scope
RiskOptional. A risk from your Risk Register
PriorityCritical, High, Medium or Low
OwnerOptional. A member of the organisation
Due dateOptional
DescriptionOptional
Root causeOptional. Why the finding arose

Unlike a deficiency raised by hand, a finding needs neither a control nor a risk: the test is what it was found in. You can add up to 100 findings when you record a test, and remove one before saving.

Use this when a finding comes to light after the test was recorded.

  1. On the test’s row, select Add finding.
  2. If the test is recorded as Passed, choose what The test’s result becomes: Passed with findings or Failed. A finding on a passed test always corrects its result; both are saved together.
  3. Fill in the finding’s fields.
  4. Select Add finding.

What you’ll see: the finding is raised as a deficiency linked to the test, and the test’s finding count updates. A Passed test now reads Passed with findings (or Failed, if you chose that).

  1. On the test’s row, select Correct.
  2. Change the fields that are wrong, for example the Type if you recorded a continuity test as Incident response.
  3. Select Save.

Only the fields you change are saved. Findings are not edited here; add one with Add finding, and edit or close existing ones as deficiencies.

If you change the Result, it must still match the findings already recorded. Cancelled findings are not counted. To correct a Passed test to Failed, use Add finding instead: a passed test is corrected with its first finding.

CountWhat it shows
TESTSAll recorded tests
PASSEDTests recorded as Passed
PASSED WITH FINDINGSTests recorded as Passed with findings
FAILEDTests recorded as Failed
OPEN FINDINGSFindings, across all tests, that are still open

A row shows the title, the type, the result, the date tested and a finding summary, such as “2 findings, 1 open”. Select Details to see the scenario, the outcome, who recorded it and when, and the findings.

The findings under Details work exactly as on the Deficiencies page: an editor can Edit, Complete (with a retest note), Cancel deficiency or Reopen each one.

FilterOptions
TYPEAll, Incident response, Continuity, Other
RESULTAll, Passed, Passed with findings, Failed

The search box matches the title, scenario and outcome.

Every finding is a deficiency. On the Deficiencies (POA&M) page, a finding’s source reads Capability test finding. Select it to open the Capability Tests page with that test expanded. Use your browser’s Back button to return to the Deficiencies page.

Findings count towards the deficiency totals. A finding raised against a control also appears in that control’s Deficiencies panel on the GOVERNANCE tab.

MessageWhat to do
“tested_on cannot be in the future: record a test once it has run”Set Tested on to today or earlier
“A test that failed needs at least one finding” (or passed with findings)Add a finding, or change the result to Passed
“A test with N finding(s) did not simply pass…”Choose Passed with findings or Failed
“Finding N: title cannot be blank”Give that finding a title, or remove it
”… is not a control this organisation has in scope”Scope the control, or leave Control blank
”… is not a risk this organisation has assessed”Assess the risk first, or set Risk to None
Reopening a cancelled finding is refusedThe test reads Passed. Add a new finding first, which corrects the result