devguard

Audits

Record each audit and its findings, correct every nonconformity and act on its cause, and close it only after you have checked that the corrective action worked.

An audit checks, with evidence, how far you meet a set of requirements (the audit criteria), for example in a certification, surveillance or internal audit. A finding is the result of evaluating the evidence against one requirement: a conformity, a nonconformity (the requirement is not met), an observation or an opportunity for improvement. devguard keeps a nonconformity open until someone records that its corrective action worked.

The tasks below follow the order of the work:

To plan which clauses your internal audits cover over the certification cycle, see the audit programme. Scripts and integrations: see API below.

Add an audit

  1. Open Audits and choose Add audit.
  2. Enter a Name. The Slug (the short name in the link) is filled from the name.
  3. Choose the Type: Certification, Re-certification, Internal, External or Other. Choose External for a surveillance audit. Certification and Re-certification would start a new three-year cycle in the audit programme.
  4. Choose the Framework you are audited against. Only adopted frameworks are offered.
  5. Under Clauses and controls in scope, tick what this audit will examine. Ticking a chapter ticks all of its clauses. For an internal audit, the box above the list shows the certification cycle and how many clauses are already audited or planned in it. Choose Not yet audited to see only the gaps.
  6. Set Started at and Ended at. Enter the Auditor: the person or the certification body. For an internal audit, choose someone who does not audit their own work. In a small company, swap areas with a colleague or ask an external auditor.
  7. Fill in Audit objectives, Audit scope and Audit criteria. Leave Audit conclusion empty until the audit is over.
  8. Choose Create. To change the audit later, open it and choose Edit.
The clause list in the audit form: the cycle from 02.09.2025 to 01.09.2028, counted from the end of the certification audit, 5 clauses audited and 18 not yet audited, and chapters 4 and 5 ticked.
The planned scope of an internal audit in December. The 5 audited clauses come from the October audit. The audit you edit does not count towards its own plan.

Watch out: pressing Enter in a one-line field, such as a date or the name, saves the form at once. Fields that you have not filled yet stay empty.

Audit scope is free text for locations, units and processes. Clauses and controls in scope is the list of requirements. Only the list counts in the audit programme.

Prepare a SOC 2 review period

A SOC 2 Type II report tests a period, often twelve months, and not only the days of the audit. Set the period before the fieldwork starts, so you see the gaps in time.

  1. Open the audit, choose Edit, and set Review period start and Review period end. The period can be at most 18 months.
  2. Open the Review period tab. For each control of the audit's framework, it lists what happened in the period: evidence files, integration check runs, process submissions used as evidence, and the policy versions in effect. Below the controls, Reviews lists the risk, asset, vendor and access reviews of the period.
  3. Look at the controls marked No evidence in period and at the exceptions: failed checks, expired files, and reviews that are unfinished, overdue or have rejected items. Fix them before the auditor asks. If your access role cannot see a source, a control that draws on it shows Not visible with your role instead, and its counts can be incomplete.
  4. Choose Export CSV to send the full list to the auditor.
The Review period tab for 21.10.2025 to 21.10.2026: 30 controls, none with exceptions, 30 without evidence in the period, and the first controls marked No evidence in period.
No control has evidence in this period yet. This is the list to work through before the auditor arrives.

How a finding is closed

A finding has three statuses: Open, In progress and Closed. You move it forward in the ... menu of the finding. Mark in progress appears while it is Open, and Close finding appears while it is In progress. A nonconformity shows Close finding only once its effectiveness check is recorded.

A nonconformity (major, minor or not graded) needs one more step before it can be closed: the effectiveness check. Someone checks that the corrective action works and records what the check showed. Without this record, devguard refuses to close the nonconformity. Observations, opportunities for improvement and conformities can be closed without a check, but you can record one for them too.

If the problem comes back, choose Reopen finding. The finding goes back to Open, and its verification is removed, because the corrective action did not work. For a finding of an audit, the History tab of the audit still shows who verified it and when.

Record a finding

  1. Open the audit and go to the Findings tab. Choose Add finding.
  2. Enter a Name and an Identifier that people can say in a meeting, for example "NC-5" or the clause number.
  3. Choose the Type and leave Status on Open. The types are listed under Finding types.
  4. Choose the Control: the requirement from the audit criteria that the finding is assessed against. The report prints it with the finding.
  5. Write the Statement: what was found, against which requirement, and the evidence the auditor saw.
  6. For a nonconformity, set a Deadline. Choose an Assignee (one person) or an Assignee role, not both.
  7. Choose Create. The finding appears on the audit and in the findings register.
The Add finding form: name Shared admin account on the firewall, identifier NC-005, type Minor nonconformity, status Open, source Audit, control A.5.17, deadline 15.01.2027, assignee role Head of IT, and the statement with its evidence.
A minor nonconformity with its control, a deadline and a role that owns it. The statement names the evidence.

Record conformities too. A conformity on a clause shows in the audit programme what was actually examined, even when nothing was wrong.

Correct a nonconformity and act on its cause

ISO/IEC 27001 clause 10.2 lists five steps after a nonconformity, and asks you to keep a record of them. The finding is that record:

  • a) React. Control and correct the problem, and deal with its consequences. Write this in Correction. For example, you removed the access of two leavers.
  • b) Decide what action is needed. Find the cause, and check whether similar nonconformities exist or could occur. Write both in Root cause.
  • c) Take the action. Write it in Corrective action, and add a task for each step under Tasks inside the finding. For example, you connected the system to single sign-on.
  • d) Check that it worked. This is the effectiveness check in the next task.
  • e) Change the ISMS if needed, for example a policy or a process. Add a task for it.
  1. When the work starts, open the ... menu of the finding and choose Mark in progress.
  2. In the same menu, choose Edit. Fill in Root cause, Correction and Corrective action, and choose Save.
  3. Under Objective evidence, attach evidence that the action was taken, such as an export or a ticket. You can link an existing evidence record or drop a file.
Finding A.5.18, a minor nonconformity in progress: the statement, the root cause, the correction and the corrective action side by side, and below them the note that it is not verified yet.
The finding is In progress. It cannot be closed yet, because nobody has checked that the corrective action works.

Check the corrective action and close the finding

  1. Give the corrective action time to work. Then check cases that happened after it took effect, for example all leavers since the change. The problem must not occur again.
  2. Open the ... menu of the finding and choose Verify effectiveness.
  3. In Verification note, write what you checked and what the check showed. Choose Record verification. devguard adds your name and the date. The auditor will ask for this record.
  4. Open the ... menu again and choose Close finding. If tasks of the finding are still open, devguard asks you to confirm.
The open menu of finding A.5.16: Edit, Mark in progress, Verify effectiveness and Archive, with Verify effectiveness highlighted.
The menu of a finding that is still Open. Verify effectiveness stays in the menu until a check is recorded.
Verify effectiveness first, then Close finding, both from the same menu. The shield next to Closed marks the recorded check.

Create the audit report

  1. Open the audit and write the Audit conclusion.
  2. Open Actions and choose Generate Report. The PDF report opens in Reports.

The report contains the audit details, the objectives, the scope, the criteria and the clauses in scope. For each finding, it shows the control, the linked evidence, the statement, the root cause, the correction, the corrective action and the verification. It ends with your conclusion and a note that the audit was based on a sample.

One finding in the PDF report: A.5.18 with its criterion, deadline and status Closed, the verification with date and note, the linked evidence EV-041, and the statement, root cause, correction and corrective action.
Each finding prints with its criterion, its evidence and the effectiveness check, in the form an auditor reads.

Use the findings register

Audits → Findings lists the findings of all audits in one place. It also lists findings that did not come from an audit:

  • A rejected item in a risk review, an asset review, a vendor review or an access review raises a finding with the source Review.
  • Raise finding on an incident or on a process submission opens the finding form with that record as its source. A nonconformity raised this way needs a deadline.
  • Add finding on the register creates a finding from any other source, such as a management review.
  1. Choose a status, such as Open, and a type to filter the list. Type in Filter by name... to search.
  2. Open a finding with the arrow at the end of its row.
  3. To archive a finding, open its ... menu and choose Archive. Findings cannot be deleted. Turn on Show archived to see them and restore them.
The findings register filtered to Open: findings from two audits and a SOC 2 assessment, NC-002 and NC-004 from process submissions, NC-003 from incident INC-001, NC-001 and OBS-006 from reviews, and one deadline in red because it has passed.
The register mixes all sources. A chip names the submission or the incident, and a red date marks an overdue finding.

Archive or delete an audit

  • Archive, in the ... menu of the audit list, hides the audit. Its findings leave Deadlines and the open findings on the dashboard. To restore it, choose Archived in the list.
  • Delete, in Actions on the audit or in the ... menu of the list, removes the audit. Its findings stay in the findings register and in Deadlines, without an audit.

Reference

Audit fields

FieldWhat it holds
Name, SlugThe name, and the short name used in the link. Both are required.
TypeCertification, Re-certification, Internal, External or Other. Required. Only internal audits appear in the audit programme.
FrameworkAn adopted framework. If you change it, the clauses in scope are cleared.
Clauses and controls in scopeThe clauses and controls of the framework that this audit examines.
Started at, Ended atThe audit dates. They decide whether the audit is planned, in progress or done.
AuditorThe person or body that does the audit.
Audit objectives, Audit scope, Audit criteria, Audit conclusionFormatted text (bold, italic, underline, lists). All four print in the report.
NotesPlain text for anything else.
Review period start, Review period endThe period a SOC 2 Type II report tests. At most 18 months.

An audit has the tabs Detail, Findings, Review period, Tasks, Comments and History. When the type or the dates of an audit change, the owners and admins get a notification.

Finding fields

FieldWhat it holds
Name, Slug, IdentifierThe name, the short name in the link, and a code such as NC-5. Required.
Type, Status, Finding sourceRequired. See Finding types. Status is Open, In progress or Closed. Source is Audit, Incident, Management review, Process, Review or Other.
AuditThe audit the finding belongs to. Optional.
ControlThe requirement from the audit criteria that the finding is assessed against.
DeadlineWhen the corrective action must be done.
Assignee or Assignee roleOne person or one role, not both.
Statement, Root cause, Correction, Corrective actionFormatted text.
NotesPlain text.

Finding types

TypeShort formAPI valueCheck needed before Closed
Major nonconformityMajor NCMAJOR_NONCONFORMITYYes
Minor nonconformityMinor NCMINOR_NONCONFORMITYYes
Nonconformity (not graded as major or minor)NCNONCONFORMITYYes
ObservationOBSOBSERVATIONNo
Opportunity for improvementOFIOPPORTUNITY_FOR_IMPROVEMENTNo
ConformityCCONFORMITYNo

Deadlines and reminders

A finding with a deadline appears in Deadlines until it is closed. The reminder goes to the assignee, or to every member of the assignee role. When nobody is assigned, the owners and admins get it. If the assignee role has no members, nobody is reminded.

Permissions

RoleAuditsFindings
Owner, adminCreate, edit, archive, deleteCreate, edit, verify, close, archive
MemberReadRead
AuditorReadRead
Organization tokenCreate, edit, archive, delete over the APICreate, edit, verify, close, archive over the API

Members can also write comments. The auditor role reads comments but cannot write them. A personal API token has the role of its owner.

Limits

On the Free plan you can keep 4 audits. Archived audits do not count, and restoring one counts again. There is no limit on findings.

Where audits appear elsewhere

  • The dashboard shows the current or next audit, the open findings and how many are overdue.
  • Deadlines lists every finding with a deadline that is not closed.
  • Reports creates the audit report.
  • The audit programme shows internal audits against the clauses of a framework.

API

  • Base URL: https://app.devguard.ch/api. All endpoints are in the API reference.
  • Authentication: an API token, sent as Authorization: Bearer <token>. Send JSON with Content-Type: application/json.
  • Names: in the API, a finding is an auditItem. The statement is findings, the root cause is causes and the corrective action is measures.
  • Scope: the API covers audits and findings. The programme, the review period and the report are in the app only. To plan the programme from a script, create audits with type set to INTERNAL, the frameworkId, scopeControlIds, started and ended: the programme reads them.
MethodPathPurposeOrganization id
GET/audits/List auditsquery, required
POST/audits/Create an auditbody, required
GET/audits/{id}/Read an audit with its findingsnot used
PATCH/audits/{id}/Update an auditnot used
POST/audits/{id}/archive/Archive an audit (/restore/ to undo)not used
DELETE/audits/{id}/Delete an auditnot used
GET/audit-items/List findingsquery, required
POST/audit-items/Create a findingbody, required
PATCH/audit-items/{id}/Update a findingnot used
POST/audit-items/{id}/verify/Record the effectiveness checkbody, required
POST/audit-items/{id}/archive/Archive a finding (/restore/ to undo)not used

Lists return { "items": [...], "total": 12, "page": 1, "limit": 100 }. limit is 100 at most, and 100 by default. GET /audit-items/ filters with filterByStatus (OPEN, IN_PROGRESS, CLOSED), filterByType (an API value from Finding types), filterByName, auditId and filterByArchived (active or archived). On an audit, scopeControlIds takes only ids of controls of the audit's own framework. Annex A controls belong to the Annex A framework, so they go on an audit of that framework.

A single finding comes back as one object, for example from POST /audit-items/ or verify. Shortened:

A finding
{
  "id": "…", "slug": "nc-5", "identifier": "NC-5",
  "name": "Shared admin account on the firewall",
  "type": "MINOR_NONCONFORMITY", "status": "OPEN",
  "source": "AUDIT", "auditId": "…", "controlId": "…",
  "deadline": "2027-01-15T00:00:00.000Z",
  "findings": "…", "causes": null,
  "correction": null, "measures": null,
  "verifiedAt": null, "verificationNote": null
}

PATCH is not a partial update for every field. On an audit, send name and slug every time. On a finding, send name, slug and identifier every time.

This call lists the open findings. DG_TOKEN is your API token and DG_ORG is your organization id:

List open findings
API=https://app.devguard.ch/api
AUTH="Authorization: Bearer $DG_TOKEN"

curl -sS -G "$API/audit-items/" -H "$AUTH" \
  --data-urlencode "organizationId=$DG_ORG" \
  --data-urlencode "filterByStatus=OPEN" \
  | jq '.items[] | {id, slug, identifier, name}'

To close a nonconformity, record the check first. Then set the status, and send the name, slug and identifier with it:

Verify, then close
curl -sS -X POST "$API/audit-items/$ID/verify/" \
  -H "$AUTH" -H "Content-Type: application/json" \
  -d "{\"organizationId\":\"$DG_ORG\",\"note\":\"Sample OK\"}"

curl -sS -X PATCH "$API/audit-items/$ID/" \
  -H "$AUTH" -H "Content-Type: application/json" \
  -d '{"name":"Shared admin account on the firewall",
       "slug":"nc-5","identifier":"NC-5",
       "status":"CLOSED"}'

verify replaces an earlier check on the same finding.

CodeWhen
400A slug is already in use, or a required field is missing.
400A linked id (audit, control, role, framework, scope control) is not in your organization, or not in the audit's framework.
400A nonconformity raised from an incident or a submission has no deadline.
400A finding has both an assignee and an assignee role.
400The review period ends before it starts, or is longer than 18 months.
403The id belongs to another organization (verify answers 404), your role cannot write, or the audit plan limit is reached (also on restore).
404The audit or the finding does not exist.
412A nonconformity would be closed, or created as closed, without a verification.

How is this guide?

On this page