1. Vendor IT Security Assessment
  2. Features
  3. Nonconformance and correction
Feature · Nonconformance and correction

Nonconformance and correction

Track failed inspection scope into containment and corrective work.

OverviewActions awaiting effectiveness review
Vendor IT Security Assessment · Nonconformance and correction

Actions awaiting effectiveness review

Corrective actions

New
NonconformanceOwnerActionCompleted atStatus
NNC-4170ACT-590Effectiveness Review
NNC-8711ACT-580Effectiveness Review
NNC-2808ACT-313Effectiveness Review
NNC-8271ACT-868Effectiveness Review
NNC-7665ACT-335Effectiveness Review
6 of 6 records
ACT-590Corrective actions · CA-82739
Effectiveness Review
NonconformanceNNC-4170
Example screen with sample data

What you can do

Keep the failure tied to its inspection

A failed inspection check is an observation. A nonconformance records the failure the team will manage: its detection date, severity, description, inspection and current state. The link back to the inspection lets the Reviewer and Corrective Action Owner inspect the original control results while they work through containment and investigation. It also keeps several failures from one inspection distinguishable as separate work when needed.

Corrective work is a separate record linked to the nonconformance. It holds the owner, root cause, action, due date, completion date and status. The owner can describe what they will change, then record implementation. Effectiveness review asks whether the action actually addressed the linked failure. Closing the action should follow that review rather than merely the presence of a completed date.

How the work is organized

  • Failure record. The nonconformance describes what was found and how severe it is.
  • Owned correction. The corrective action names a person and a due date for the response.
  • Effectiveness check. Review occurs after implementation and before closure.

What to agree during setup

Agree when a failed check becomes a nonconformance and who assigns severity. A critical failure and a minor one may need different urgency, but both should retain the inspection link and a clear description. Define what containment means for the team’s vendor assessment practice. The containment state should point to a real temporary measure, not just a label.

For corrective actions, agree what evidence the owner supplies, who reviews it, and how the Reviewer will test effectiveness. The action record has root cause and action text plus dates, so the team should make those entries specific enough to assess. Also decide how to handle a due action that is still implementing: the due list should lead to a follow-up, while the status explains the work remaining.

Check the handoff on an actual case

An inspection check fails because a requested access-control artifact does not match the inspected period. The Reviewer records the failure as a nonconformance, describes the issue and selects severity. The Corrective Action Owner opens that record, writes the root cause and planned response, and accepts a due date. The original failed check remains available through the inspection.

After the owner implements the action, the Reviewer compares the new evidence with the original requirement. If it still covers the wrong period, the work should remain in effectiveness review rather than close. If the evidence addresses the original failure, the Reviewer can approve closure. This rehearsal tests the relationship between the finding, the action and the person deciding the final outcome.

What your team sees

  • Open nonconformances — Failures in containment, investigation or disposition.
  • Corrective actions due — Owned actions at or past their due date.
  • Actions awaiting effectiveness review — Implemented work ready for a Reviewer decision.

Follow the work through

Use correction and effectiveness to rehearse owner and Reviewer responsibilities. The inspection review page shows where the originating result is checked.

What it keeps track of

Data model
Nonconformances
Failures raised from inspection results, with severity and containment state.
Corrective actions
Remediation work assigned to close a nonconformance, including effectiveness review.
Inspections
Security inspections performed against vendor and internal subject scope.
Inspection checks
Individual control checks captured during an inspection.
People
Internal staff who own or perform vendor security assessment work.

Who uses it

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.

How to get started