1. Penetration Test Management
  2. Features
  3. Audits and findings
Feature · Audits and findings

Audits and findings

Connect requirement findings to an audit scope, owner and due date.

OverviewAudit findings due
Penetration Test Management · Audits and findings

Audit findings due

Audit findings

New
AuditRequirementFindingSeverityOwnerDue date
ADT-10622RQR-446FND-962Observation14 Oct
ADT-87616RQR-877FND-267Minor15 Oct
ADT-27611RQR-655FND-337Major03 Oct
ADT-98610RQR-494FND-203Observation10 Oct
ADT-75312RQR-265FND-885Minor07 Oct
6 of 6 records
RQR-446Audit findings · AF-35089
Observation
AuditADT-10622
FindingFND-962
Due date14 Oct
Closed at15 Oct
Example screen with sample data

What you can do

Audits and findings in daily work

An audit records its scope, planned date, assigned auditor and reporting status. Findings under the audit identify the requirement, describe the issue, classify severity, assign an owner and carry a due date. The audit may progress from Planned to in progress, Reporting and Closed while the findings retain their own dates and closure information.

How the work is organized

  • Plan the audit. Auditor records the scope, planned date and assigned auditor.
  • Describe the requirement. Record the finding text, severity, owner and due date under the right audit.
  • Check closure separately. The audit status and a finding’s close date answer different questions; inspect both during reporting.

What to agree during setup

Agree how auditors state the requirement being assessed and how the finding text distinguishes an observation from a Major issue. An owner should be able to understand what has to be addressed and when. The auditor should review outstanding finding due dates before treating the audit report as complete.

Auditor should compare the finding’s audit reference with the planned scope before assigning follow-up. A finding due today may already have a close date, so inspect that date before calling it outstanding. Agree when the audit itself enters Reporting and when its completed date is recorded. The finding owner needs a clear requirement and a due date to act.

Check the handoff on an actual case

Plan an audit for a named scope and assign an auditor. Record a requirement finding with a Major severity, a person owner and a due date. Move the audit to Reporting, then inspect the finding as the due date approaches. Open the linked audit to check its number and scope, then use the finding’s close date to trace its outcome.

Ask the person receiving the work to open the record without extra explanation. They should be able to tell what the current state means, which evidence supports it, and what decision they are expected to make. If they cannot, revise the entry and repeat the handoff with the same case.

When a finding has a close date, open the audit reference before treating it as resolved for reporting. The due-date screen includes dated findings even when that close date is present. Auditor should use the finding and its linked audit together to explain what was assessed, who owned the follow-up and when it ended.

What your team sees

  • Audit findings due — Auditors can inspect findings whose due dates have arrived, including ones with a close date.
  • Draft documents for review — Admin can prepare document versions for a separate review.

Follow the work through

See the related process for the handoff, decision and rehearsal. Review roles before granting access and the data model when preparing records.

What it keeps track of

Data model
Audits
Planned and completed audits with scope, auditor and reporting status.
Audit findings
Findings raised against an audit requirement, with severity, owner and due date.
People
Team members who perform inspections, own corrective actions, audit and acknowledge controlled documents.

Who uses it

Permissions
Auditor
, Admin.

Set up Penetration Test Management your way.

Start free, then use Proto to change fields, steps and approvals before your team goes live.

How to get started