Free Guide To Cybersecurity & Data Protection Policies, Standards, Controls & More! 

The "ComplianceForge Reference Model" for writing documentation is entirely based on industry-recognized "best practices" according to terminology definitions from NIST, ISO, ISACA and AICPA. This approach is designed to encourage clear communication by clearly defining cybersecurity and privacy documentation components and how those are linked. This comprehensive view identifies the primary documentation components that are necessary to demonstrate evidence of due diligence and due care. It addresses the inter-connectivity of policies, control objectives, standards, guidelines, controls, risks, procedures & metrics. The Secure Controls Framework (SCF) fits into this model by providing the necessary cybersecurity and privacy controls an organization needs to implement to stay both secure and compliant. ComplianceForge simplified the concept of the hierarchical nature of cybersecurity and privacy documentation that visualizes the unique nature of these components, as well as the dependencies that exist.

To demonstrate that bold claim, we wrote the "START HERE: A guide to understanding cybersecurity and data protection documentation". This follows the schema shown above (the Hierarchical Cybersecurity Governance Framework (HCGF)) that demonstrates the linkages from policies all the way through metrics. The following guide is designed to demonstrate "what right looks like" for cybersecurity and privacy documentation, so that it is at the same time scalable, concise and provides comprehensive coverage. You can jump straight to the definitions on page 6 if you are curious. 

Not Sure Which Framework Is The "Best" Cybersecurity Framework For Your Needs?

The concept of a "best" cybersecurity framework is misguided, since the most appropriate framework to align with is entirely dependent upon your business model. The applicable laws, regulations and contractual obligations that your organiation must comply with will most often point you to one of these cybersecurity frameworks to kick off the discussion about "Which framework is most appropriate for our needs?":

• NIST Cybersecurity Framework (NIST CSF)
• ISO 27001/27002
• NIST SP 800-171 (e.g., CMMC compliance)
• NIST SP 800-53 (moderate or high baselines); or
• Secure Controls Framework (SCF) (cybersecurity & privacy metaframework / common controls framework)

• NIST 800-171 & CMMC Documentation Terminology Reference

  Complying with NIST SP 800-171 & CMMC can be hard enough without arguing over terminology. Terminolo...

• Comparing NIST SP 800-53 R5 vs FedRAMP R5 vs NIST SP 800-171 R2 vs NIST SP 800-171 R3 IPD

  Within the Defense Industrial Base (DIB), there is considerable confusion about the concept of "FedR...

• Word Crimes 4 - Threat vs Vulnerability vs Risk

  Threat vs Vulnerability vs RiskThreat, vulnerability and risk management practices are meant to achi...

• Word Crimes 3 - Policy vs Standard vs Control vs Procedure

  Policy vs Standard vs Control vs Procedure When it comes to cybersecurity compliance, words...

---