NEW
A documented set of rules governing the protection of information systems and data.
DESCRIPTION
A security policy formalizes expectations, controls, and responsibilities to protect information assets. It communicates obligations for access, handling, incident response, and compliance. Policies are supported by standards and procedures, reviewed regularly, and enforced through governance and audits. They help manage risk, meet regulatory requirements, and align stakeholders. Effective policies are clear, actionable, and measurable.
ALTERNATIVE DEFINITIONS
NIST Glossary
A set of rules and practices that specify or regulate how a system or organization provides security services to protect sensitive and critical system resources.
Focuses on rules and practices for providing security services.
IETF RFC 2196
A security policy is a formal statement of the rules by which people who are given access to an organization’s technology and information assets must abide.
Highlights formal statement and user obligations for asset access.
SANS Institute
An information security policy outlines an organization’s approach to protecting information assets and sets expectations for acceptable use and controls.
Emphasizes acceptable use and control expectations.
RELATED TERMS
Security Access Control Risk Management Compliance Procedures Control ISO-IEC 27001 NIST SP 800-53 Policy Exception
COMPETING TERMS
Security Standard
RELATIONS
- Broader: Policy
KNOWLEDGE AREAS
Data Security Data Privacy & Compliance Data Governance Infrastructure
TARGET AUDIENCE
Chief Information Security Officer Security Architect IT Manager Data Privacy Officer IT Auditor DevOps Engineer Cloud Architect Data Governance Manager
EXTERNAL SOURCES
- Wikipedia - Information security policy
- NIST - Security and privacy controls catalog
- ISO - ISO/IEC 27001 information security standard
- Center for Internet Security - CIS Controls for cybersecurity
TOP QUESTIONS
Why is a Security Policy essential?
It defines rules, responsibilities, and controls for protecting data, enabling governance and compliance.
Category: Relevancy
What are common mistakes in Security Policy authoring?
Overly vague language, lack of enforcement mechanisms, and policies not aligned to regulations or risk.
Category: Mistakes
How is a Security Policy maintained?
Review regularly, align with standards (NIST, ISO), audit compliance, and update for new threats.
Category: Management
What risks arise from weak Security Policies?
Increased breach likelihood, compliance fines, and operational confusion.
Category: Risk
What is a competing artifact to a Security Policy?
Security standards and procedures operationalize policies with detailed, testable requirements.
Category: Alternatives
How should access control be covered in a Security Policy?
Define roles, least privilege, segregation of duties, and review cycles for entitlements.
Category: Requirements
What hot topics shape Security Policies today?
Zero trust, privacy-by-design, supply chain security, and AI risk management.
Category: Topic
Where to start writing a Security Policy?
Use templates from SANS or CIS, map to NIST 800-53, and tailor to organizational risks.
Category: Example
How to test adherence to a Security Policy?
Perform audits, control testing, and metrics tracking; enforce via governance and incident reviews.
Category: Testing