Security compliance glossary: controls, evidence, SOC 2, ISO 27001 and more

Plain-English definitions of compliance terms: controls, evidence, readiness, statement of applicability, SOC 2 reports, ISO 27001 certification, policies.

Glossary · Updated · by the Controlkeep team

Short definitions of the terms used in security compliance work, with notes on how each appears in Controlkeep. These are general explanations, not legal or audit advice. For what the starter frameworks are and aren't, read the note about the starter frameworks.

Frameworks

Framework. A structured set of requirements or criteria for security, such as SOC 2 or ISO/IEC 27001.

SOC 2. A reporting framework of the AICPA (American Institute of Certified Public Accountants). An independent auditor issues a report on a company's controls against the Trust Services Criteria. It is a report, not a certificate.

Type I and Type II. In SOC 2, a Type I report describes controls at a point in time; a Type II report also covers how they operated over a period.

ISO/IEC 27001. A standard for information security management systems published by ISO and IEC. Organisations can be certified against it by an accredited certification body.

Annex A. The list of reference controls in ISO/IEC 27001.

Statement of Applicability (SoA). In ISO 27001 work, the document listing which controls apply, why, and their status. Controlkeep's "not applicable" justifications help prepare one.

Starter framework. In Controlkeep, an original, simplified set of control objectives written in our own words and grouped the way SOC 2 or ISO 27001 are commonly organised. Not the official text, not complete, and not a certification.

The register

Control. A safeguard your organisation operates, such as "access is reviewed every 90 days".

Control owner. The person responsible for a control operating and its evidence being current.

Control status. Not started, in progress, implemented, or not applicable.

Not applicable (with justification). A control that doesn't apply to your organisation, with a written reason. Controlkeep requires the reason.

Review cycle. How often a control is reviewed. Controlkeep tracks the next review date and emails a weekly list of overdue reviews.

Readiness. In Controlkeep, implemented controls divided by applicable controls, per framework. It reflects what your team marked, not an assessment.

Control matrix. A table with one row per control: status, justification, owner, review dates and evidence. Controlkeep exports it as CSV.

Evidence

Evidence. Records showing a control operates: exports, screenshots, tickets, reports, notes. See the evidence collection guide.

Evidence mapping. Linking one piece of evidence to every control it supports.

Evidence expiry. The date after which time-bound evidence is stale. Controlkeep's weekly email lists it 30 days ahead.

Audit period. The time span an audit covers; evidence should fall inside it.

Sample. A subset of records an auditor tests, such as a few leavers from the period.

SHA-256 hash. A fingerprint of a file. Controlkeep's audit bundle lists one per evidence file, so it's clear exactly what was provided.

Policies

Policy. A written rule the organisation commits to, such as an access control policy.

Policy version. Each approved change. Controlkeep keeps every version.

Acknowledgement. A member confirming they have read a policy version. Controlkeep asks every member after approval and reminds after 7 days.

Placeholder. A highlighted decision in a starter policy, such as how quickly leavers lose access, that you must fill in before approving.

AI draft, needs review. Controlkeep's label for policy text tailored by AI. Drafts that claim a certification or compliance status are rejected.

People and process

Auditor. An independent professional who examines controls and evidence and issues a report or certification decision.

Security questionnaire. A customer's list of questions about your security practices, often answered from the control matrix.

Gap. A requirement with no implemented control or no current evidence. The control matrix makes gaps visible.

Remediation. The work to close a gap: implementing a control, fixing a process, or collecting evidence.

Risk register. A list of risks with their likelihood, impact and treatment. Often kept alongside the control register.

Audit log. Controlkeep's record of important actions in the workspace, included in the JSON audit bundle.

Try Controlkeep free

A working control register: owners, evidence, policies and reviews in one place, with exports your auditor can read. The Free plan needs no card; you can export or delete your data any time.