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
- Audit follow-up
Audit follow-up
Plan a scoped audit and keep each finding visible through follow-up.
Step by step
-
Plan engagement Auditor
The Auditor records the audit number, scope, planned date and assigned auditor.
- Establish scope, date and auditor.
- Updates Audits, People
-
Perform audit Auditor
The Auditor works within the recorded scope and moves the audit into progress as observations are gathered.
- Show the engagement is in progress.
- Updates Audits
-
Record finding Auditor
A finding identifies the requirement, observation, severity, owner and due date under its audit.
- Tie the observation and owner to the audit.
- Updates Audit findings, Audits, People
-
Prepare reporting Auditor
The Auditor reviews linked findings before reporting the engagement's outcome.
- Review findings in the scope of the engagement.
- Updates Audits, Audit findings
-
Follow up Auditor
The finding owner addresses the issue; the Auditor checks the result and records a closed date for the finding when appropriate.
- Record the individual finding's closure date.
- Updates Audit findings
Who does what
Roles and permissions- Auditor
- , Reviewer, 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.