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.
- Vendor IT Security Assessment
- Process
- Correction and effectiveness
Correction and effectiveness
Keep containment, owned action and effectiveness review tied to the failure.
Step by step
-
Record nonconformance Reviewer
The Reviewer describes the failure, chooses severity and links the record to the inspection where it was found.
- Establish severity and origin.
- Updates Nonconformances, Inspections
-
Contain the issue Reviewer
The team records the containment state while immediate exposure is addressed. The description should still identify the original gap.
- Show the failure is under containment.
- Updates Nonconformances
-
Assign correction Corrective Action Owner
The Corrective Action Owner records root cause, the planned action and due date against the linked nonconformance.
- Name the owner and due date.
- Updates Corrective actions, Nonconformances, People
-
Carry out action Corrective Action Owner
The owner records implementation and completion, keeping the action's state current for follow-up.
- Record the root cause, action and completion.
- Updates Corrective actions
-
Check effectiveness Reviewer
The Reviewer tests whether the completed action addresses the original failure and approves closure only when the linked work is accepted.
- Decide whether to close corrective work.
- Updates Corrective actions, Nonconformances
ApprovalA person approves before the work moves on.
Who does what
Roles and permissions- Reviewer
- , Corrective Action Owner, Inspector, Admin
Set up Vendor IT Security Assessment your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.