A policy is an authoritative, high-level statement of what an organization expects. In cybersecurity, policies set security objectives and internal rules for protecting information assets. They turn business needs, identified risks, and applicable external requirements into direction that people can follow consistently. section 4.2.3 section 4.4
Policies are mandatory within the organization, but they are not the same as laws. Laws and regulations impose external obligations; standards provide criteria; policies state what the organization requires; procedures give step-by-step instructions for carrying out those requirements. Guidelines offer advice rather than mandatory rules. section 4.1 section 4.3.4
|
Governance Element
|
Enforceability
|
Scope
|
|
Laws and Regulations
|
Mandatory
|
External
|
|
Standards
|
Mandatory
once adopted
|
External or
Internal
|
|
Policies
|
Mandatory
|
Internal
|
|
Procedures
|
Mandatory
|
Internal
|
|
Guidelines
|
Not
mandatory
|
Internal
|
Compare where governance requirements come from and whether they are mandatory. Notice that policies are both internal and mandatory. section 4.1
A policy should say why it exists and who or what it covers. Its audience may be everyone or a particular group: acceptable use concerns all employees, while server hardening chiefly concerns IT administrators. Because policies carry organizational authority, creating or changing them typically requires senior management approval. section 4.2.3 section 16.2.2 section 16.2.3
|
Policy
|
Purpose of the Policy
|
Audience
|
|
Acceptable Use Policy
|
Establish rules for the appropriate,
authorized, and ethical use of organizational information and information
systems.
|
All employees, IT
|
|
Access Control Policy
|
Define how
access to systems and data is granted, managed, and reviewed, based on the
principle of least privilege.
|
All
employees
|
|
Password Policy
|
Define
requirements for creating, managing, and protecting passwords to ensure
strong authentication and reduce the risk of unauthorized access.
|
All
employees
|
|
Data Classification Policy
|
Define
classification levels and processes used to categorize data based on
sensitivity and criticality.
|
All
employees, IT
|
|
Data Backup Policy
|
Define how
data is backed up, stored, and restored to ensure availability and recovery
in case of data loss or system failure.
|
IT, Security
teams
|
|
Retention Policy
|
Define how
access to systems and data is granted, managed, and reviewed, based on the
principle of least privilege.
|
IT, Security
teams, Management
|
Browse common security policies by purpose and intended audience, including acceptable use, access control, passwords, data classification, and backups. section 4.2.3
From a rule to a control
A password policy can define what counts as a strong password. System hardening then puts that requirement into practice through technical controls such as password complexity rules and account lockout settings. The policy sets the expectation; the controls help enforce it. A policy alone does not secure a system. section 15.2.1




















