Audits

An Audit represents each execution of an audit against an Auditable Entity. For example, if an Auditable Entity is audited every two years, a separate child Audit instance must be created for each two-year period, such as 2022 and 2024. An organization might audit various processes. For example, you might audit an entity, a specific regulatory requirement, or a data center physical security.

The Audit object is configured as a self-contained object type and a folder is automatically created for each Audit instance. With this configuration, you can copy template audits and audit components from a library to the audit hierarchy without object naming conflicts.

Planning and scheduling of the Audit resources is done at the Audit level.

High-level Audit progress can be tracked by monitoring the Status values and Date values on the Audit. Key audit milestones can be tracked by adding fields that represent completion dates for each of the key milestones to track.

Use the Audit object to manage the audit process across your enterprise. The Audit identifies a holding point to capture information such as scope, objectives, timing information, review, execution, and approval roles. You can track a subset of audits that you are undertaking in a planning horizon, or all audits in the audit universe.