Skip to content
SOC 2 Compliance Software

Home / Glossary / Information security policy

Glossary, read 12 Nov 2026

Information security policy in a SOC 2 examination, defined with a sourced example

All termsRead the guides

The definition of Information security policy

Policies are the written commitments an auditor tests the real system against. Each control the auditor samples traces back to a statement in a policy: access is approved, changes are reviewed, incidents are reported. If the policy says quarterly and the practice is annual, that is a deviation and it goes in the report.

NIST SP 800-53 control PL-1 lists what a policy should address: purpose, scope, roles, responsibilities, management commitment, coordination among organizational entities and compliance. It also asks for a named official to manage the policy and procedures. A one-page policy from a template with no owner and no approval date misses most of that.

The error teams make most often is promising more than they do. Policies written to sound mature set a bar you then have to clear every week of the window. Write what you will actually run, get management approval with a date, and review it at the interval the policy itself states.

A sourced example

NIST SP 800-82 Rev. 3, quoted on the CSRC glossary, says: "In general, policies provide answers to the questions 'what' and 'why' without dealing with 'how.' Policies are normally stated in terms that are technology-independent." A SOC 2 policy follows that split: the policy says access is reviewed, and a separate procedure says who does it and how often. NIST CSRC glossary, security policy, read 12 Nov 2026.

Sources

  1. NIST CSRC glossary, security policy, read 12 Nov 2026
  2. NIST SP 800-53 Rev. 5 control catalog (OSCAL), read 12 Nov 2026

Last reviewed 12 Nov 2026.