# Audits and findings

An audit in Probo represents a defined review of an organization’s compliance program. It provides a place to scope the review, connect relevant controls, and collect the findings produced by that work.

## Audit scope

Define the audit independently from a framework. An audit may review all or part of a framework and can connect to controls and supporting program records. This keeps the review boundary explicit even when the organization operates several frameworks.

## Findings

Findings describe issues or observations identified during an audit or another review. Supported kinds include major nonconformity, minor nonconformity, observation, and exception. A finding can be linked to more than one audit when the same underlying issue affects multiple reviews.

Use a finding for the reviewed issue and tasks or internal controls for remediation work. This preserves the original conclusion while allowing owners, due dates, and implementation evidence to change as work progresses.

## Reports and evidence

Audit reports are generated from current audit records. Before sharing a report, verify the scope, linked controls, finding classification, and supporting evidence. Document publication and electronic signatures provide separate approval records when a report or policy requires formal sign-off.

## Automation

- [CLI audit](/docs/developers/cli/commands/audit) — Manage audits with prb audit
- [CLI finding](/docs/developers/cli/commands/finding) — Create and update findings from the command line
- [MCP audits and findings](/docs/developers/api/mcp/tools/catalog/audits-and-findings) — Operate audits and findings from supported AI tools
- [n8n Audit](/docs/developers/api/n8n/resources/audit) — Automate audit operations in n8n
- [n8n Finding](/docs/developers/api/n8n/resources/finding) — Automate finding operations in n8n