Glossary
Security audit
Definition
A security audit independently examines security records and practices against agreed requirements to identify gaps and necessary changes.
The result depends on the agreed scope, criteria and evidence examined. An audit provides findings about that work, not a guarantee that the business cannot be breached.
A customer may include “Security audit” in a supplier security questionnaire or spreadsheet. They want to understand whether this topic affects the service you provide and what safeguards or evidence support your answer.
A security audit examines evidence to determine whether security practices meet defined requirements. Those requirements may come from a policy, contract or named standard. NIST's security audit definition emphasises an independent examination of records and activities, including recommendations for changes.
The auditor sets a scope, gathers evidence and reports findings against the chosen criteria. That might involve interviewing the operations lead, inspecting account permissions or sampling completed access reviews. An internal audit can still be independent of the work being checked; it does not always require an outside firm.
For example, a small software supplier might ask someone outside day-to-day account administration to check whether departing staff lose access as its policy promises. The review compares employee departure records with account records and investigates exceptions rather than accepting the policy document alone.
An audit covers a defined scope and period, often using samples. A clean result cannot guarantee that every weakness has been found or that later activity remains compliant. Read the audit's scope, period, criteria, sample and unresolved findings together. A clean result cannot guarantee every weakness was found; a vulnerability scan or penetration test answers a different question. A vulnerability scan or penetration test answers a different question and should not automatically be treated as an audit.