Skip to content
[14] Organizational Security Policy

[14] Organizational Security Policy

By: Prasanna |

πŸ“˜ Topic: Organizational Security Policy

Domain: D1 – Security and Risk Management
Tags: #cissp


🧾 Definition

An organizational security policy is a high-level document that defines the organization’s security expectations, acceptable use, roles, and enforcement approach. It should be reviewed whenever the business changes materially.


πŸ”‘ Key Points

  • Policies set direction and define mandatory requirements.
  • Standards and procedures translate policy into technical and operational controls.
  • Policies should define roles, responsibilities, exceptions, and consequences of non-compliance.
  • They provide the foundation for audits, risk management, and regulatory alignment.

⚠️ CISSP Insight

  • A policy is only effective when it is approved, communicated, and enforced.
  • Security governance depends on policy clarity and leadership support.

βš”οΈ Key Difference / Trap

  • Policy vs Procedure vs Standard
    • Policy = high-level requirement
    • Standard = specific technical or operational expectation
    • Procedure = step-by-step implementation guidance
  • A written policy without enforcement is not enough

πŸ—οΈ Example

An organization publishes an Acceptable Use Policy that requires MFA for administrative access, prohibits unauthorized software, and defines monitoring and disciplinary actions.


πŸ“š References

  • NIST SP 800-12, Introduction to Information Security
  • ISO/IEC 27001:2022, Annex A 5.1 and 5.2
  • ISC2 CISSP CBK, Domain 1

πŸ” Quick Recall

  • Policy = rule and expectation
  • Standard = benchmark
  • Procedure = how to do it