These cookies are required for the website to function properly. They ensure security, enable basic features like page navigation, and store user session data. You cannot disable these cookies.
- GRC for Banking and Financial Services
- Features
- Control testing
Control testing
Record each sample, exception, result and evidence reference against an assessment.
OverviewControl test exceptions×
GRC for Banking and Financial Services · Control testing
New
Control test exceptions
Assessment tests
| Id | Parent | Control | Result | Exception count | Sample size | |
|---|---|---|---|---|---|---|
| IDD-761 | ASS-93469 | CNT-1988 | Fail | 25 | 20 | |
| IDD-525 | ASS-89497 | CNT-6754 | Inconclusive | 30 | 480 | |
| IDD-705 | ASS-31877 | CNT-8155 | Fail | 13 | 450 | |
| IDD-351 | ASS-12227 | CNT-1318 | Inconclusive | 26 | 670 | |
| IDD-780 | ASS-96619 | CNT-9883 | Fail | 10 | 390 |
6 of 6 records
IDD-761Assessment tests · AT-18808
FailParentASS-93469
ControlCNT-1988
Exception count25
Sample size20
Evidence referenceER-492
What you can do
Examine the control actually in scope
Each assessment test belongs to an assessment and a control. Its line number and revision keep it in the plan that the owner prepared. The tester records when testing occurred, the sample size, the exception count, the result and a reference to evidence. Pending, Pass, Fail and Inconclusive describe different outcomes; they should not be grouped into a single completed state.
Suppose the team samples payment approvals for a quarterly assessment. The sample size is the denominator for its exceptions. An exception count greater than the sample cannot be an accepted result. A passing result needs an evidence reference, so another person can examine the basis for the conclusion. If the evidence is incomplete, Inconclusive may be more faithful than Pass.
How the work is organized
- Planned line. Keep the test tied to the assessment revision and selected control.
- Observed result. Record the sample, exceptions, date, evidence reference and result together.
- Exception path. A failed or inconclusive test can lead to a finding on the same assessment and control.
What to agree during setup
Agree what constitutes a sample, when a test can be concluded and how the evidence reference resolves to a document or system of record. Set a naming convention for test lines so reviewers can compare the planned set with the executed set. Decide when the assessment moves from Testing to Review and who confirms that all intended lines have an outcome.
Evidence files can be attached to the assessment with a visibility choice. The attachment title, type, uploader and upload date should let the reviewer find the right item. A text reference on the test and an assessment attachment serve related purposes, but the team should agree how they point to the same evidence. Keep Internal material within the approved access scope.
Check the handoff on an actual case
Rehearse a test with a sample of twenty items and two exceptions. Record the date and evidence reference, then mark it Fail. Trace the resulting finding to this exact test’s assessment and control. Repeat the test submission with the same operation identifier and confirm it does not create another result or finding.
Try to record twenty-one exceptions against the same sample and a Pass with no evidence reference. Both should be refused before the reviewer receives the case. The reviewer should see the original plan, the observed result and the evidence path. A Pending test remains visible so a status change on the assessment does not hide unfinished examination.
What your team sees
- Control test exceptions — Examine failed and inconclusive results with their sample and evidence reference.
- Pending control tests — See planned lines that still need an outcome.
Follow the work through
What it keeps track of
Data model- Assessment tests
- Individual control tests executed under an assessment.
- Assessments
- Scoped assessment engagements driven through a status lifecycle.
- Controls
- Controls that mitigate a risk and are executed by a named owner.
- Findings
- Findings raised from failed or inconclusive control testing.
- Record attachments
- Evidence files attached to an assessment with a visibility scope.
Who uses it
Permissions- Assessment Owner
- , Control Owner, Independent Reviewer, Admin.
Set up GRC for Banking and Financial Services your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.