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 Audit Compliance
- Features
- Findings and remediation
Findings and remediation
Move a failed test through correction and retest.
OverviewCorrective Action Due Dates×
GRC Audit Compliance · Findings and remediation
New
Corrective Action Due Dates
Corrective actions
| Finding | Owner | Due at | Completed at | Status | Evidence | |
|---|---|---|---|---|---|---|
| FND-8405 | 12 Oct | Planned | EVD-477 | |||
| FND-2420 | 11 Oct | In progress | EVD-799 | |||
| FND-1376 | 04 Oct | Submitted | EVD-658 | |||
| FND-2785 | 10 Oct | Verified | EVD-998 | |||
| FND-4851 | 13 Oct | Planned | EVD-258 |
6 of 6 records
EVD-477Corrective actions · CA-55148
PlannedFindingFND-8405
Due at12 Oct
What you can do
Move a failed test through correction and retest
A finding identifies the assessment and control, records its severity and description, and starts open. The remediation record links the finding to an owner, due date, completion date, evidence and work status. The owner can move an action from planned through in progress to submitted. Independent retest evidence links back to the finding, identifies the reviewer and records a pass, fail or inconclusive result. A passing retest supports closure. The Independent Reviewer also decides on the submitted assurance review revision, and the resulting effects must be saved before closure completes.
How the work is organized
- Source record. Start with the assessment, risk or finding that owns the work and follow its references before changing a status.
- Named responsibility. Use the linked owner or reviewer so the next action is accountable to a person in the organization.
- Recorded result. Retain the date, status, decision or evidence that explains why the work moved forward.
The Operations Overview helps the team see assessments, tests, decisions and failed operations in one context. Open the underlying record before acting, especially when two assessments have similar subjects. The record number, organization and period should identify the intended case. Decisions and retests should point back to the source they cover.
What to agree during setup
Agree who owns an action when the control owner and assessment owner differ. Set a due date the owner can meet and define what evidence will show correction. Decide how a failed retest returns to the action owner. Keep the original finding and prior evidence available when dates or plans change. The team should rehearse these choices with a small, recognizable case before widening access. A named owner should check that a reviewer sees the right case and that a person outside the case cannot change it.
Check the handoff on an actual case
A tester finds approvals missing from sampled access changes. The finding is marked high severity and linked to the tested control. The Remediation Owner supplies the corrected procedure and evidence by the due date. An Independent Reviewer tests the corrected operation. If the retest fails, the finding stays open and the owner receives the result for further work. Walk the record from its first entry to the next person’s action. Check that dates, references and status tell the same story, and that evidence is available to the authorized reviewer. If the work is corrected, preserve the earlier result and the reason for the change. The team can then use the same handoff for a second case without relying on a side conversation.
What your team sees
- Open Findings — Unresolved issues by assessment, control and severity.
- Corrective Action Due Dates — Actions due with owner and submission status.
- Retests to Check — Failed and inconclusive independent checks.
Each view opens records with the fields needed for that decision. The person working the queue can compare the current status with the linked source, then open the record for its full history. A board or due-date list helps prioritize, while the recorded decision remains on the case.
Follow the work through
Follow assessment preparation, testing and findings, independent review and verified closure. Start with the process that owns the record on this page, then inspect the next handoff before releasing work to another role.
What it keeps track of
Data model- Findings
- Assurance findings raised against a control and assessment.
- Control test findings
- Findings raised from failed or inconclusive control tests.
- Corrective actions
- Remediation actions assigned to a finding owner.
- Remediation tracking
- Remediation actions assigned to findings, with due date and evidence.
- Retests
- Independent retest evidence that gates finding closure.
- Corrective action retests
- Independent retests that verify a corrective action and permit closure.
Who uses it
Permissions- Remediation Owner
- , Independent Reviewer, Assessment Owner.
- The Assessment Owner coordinates the case, while the Independent Reviewer makes the recorded assurance or retest decision when that stage applies.
- Admin
- Handles organizational access and receipt reconciliation.
Set up GRC Audit Compliance your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.