Principles, policies, and documentation for organizational security management
High-level statements that reflect management's intent. Define what should be done but not how. Approved by senior management.
Mandatory requirements that support policies. Specific and measurable. Define what must be done.
Minimum security configurations for systems. Platform-specific. Define the security floor.
Recommended practices. Not mandatory but suggested. Provide flexibility for compliance.
Step-by-step instructions. Tell exactly how to accomplish a task. Most detailed documentation.
Doing what a reasonable person would do in similar circumstances. Taking action to protect the organization.
Researching and understanding the risks before making decisions. Investigation and verification.
Remember: Due Diligence = Understand the risk | Due Care = Take action on the risk
| Framework | Type | Focus | Best For |
|---|---|---|---|
| ISO 27001/27002 | Certification | ISMS implementation & controls | International organizations |
| NIST CSF | Framework | Cybersecurity risk management | Critical infrastructure, US orgs |
| NIST 800-53 | Control Catalog | Federal system security | US Government, contractors |
| COBIT | Framework | IT governance & management | Enterprise IT alignment |
| CIS Controls | Best Practices | Prioritized cyber defense | Any organization, practical |
| SOC 2 | Audit/Report | Trust Service Criteria | Service organizations (SaaS) |
| CSA CCM | Control Matrix | Cloud security | Cloud service providers |
Order matters! In ethical conflicts, Canon I takes precedence over II, II over III, etc.