Data Privacy & Secure Engineering Templates

While the European Union General Data Protection Regulation (EU GDPR) continues to make headlines for its requirements and the looming California Consumer Protection Act (CCPA) approaches, there are many other reasons to have program-level documentation to demonstrate how cybersecurity and privacy principles are designed and implemented by default. It goes beyond compliance and is just good business practice. 

Can You Honestly Answer HOW Data Privacy & Cybersecurity Are Implemented At Your Organization?

When you "peel back the onion" and prepare for an audit, there is a need to address "the how" for certain topics, such as how Security by Design (SbD) and Privacy by Design (PbD) principles are managed. While policies and standards are designed to describe WHY something is required and WHAT needs to be done, many companies fail to create documentation to address HOW the policies and standards are actually implemented. We did the heavy lifting and created a program-level document to address this need and the Secure Engineering & Data Privacy (SEDP) is that solution. 

 

Managing Data Privacy & Cybersecurity Principles Does Not Have To Be Hard

If you can use Microsoft Word and Excel, then you can perform both Security by Design (SbD) and Privacy by Design (PbD) by simply following the instructions and editing the template to suit your specific requirements. While this is a template, we did the hard work of creating the formatting, bringing together the correct scope of information that needs to be addressed!

Operationalize Security by Design (O-SbD)

Operationalize Privacy by Design (O-PbD)

Security by Design (SbD) requirements come from numerous sources. In this context, the most important are: International Organization for Standardization (ISO) National Institute for Standards & Technology (NIST) US Government (HIPAA & FedRAMP) Information Systems Audit and Control Association (ISACA) Cloud Security Alliance (CSA) Center for Internet Security (CIS) Open Web Application Security Project (OWASP)

Privacy by Design (PbD) requirements come from numerous sources. In this context, the most important are: Fair Information Practice Principles (FIPPs) European Union (EU) General Data Protection Regulation (GDPR) Organization for the Advancement of Structured Information Standards (OASIS)  International Organization for Standardization (ISO) National Institute for Standards & Technology (NIST) Information Systems Audit and Control Association (ISACA) US Government (HIPAA & FTC Act)

 

Professionally-Written, Editable NIST 800-160 & OASIS PMRM-Based Cybersecurity For Privacy by Design (C4P) Program

The Secure Engineering & Data Privacy (SEDP) product is designed to support your company’s existing policies and standards. Our solution is focused at the procedural and guideline levels.

• Efficient CMMC Scoping

  Determining the scope of controls (e.g., assessment boundary) is different than determining control...

• Are you a cyber criminal?

  As a Chief Information Security Officer (CISO) or cybersecurity director, it is likely that you been...

• New Standard For Third-Party Cybersecurity Assessments

  The release of the Cybersecurity & Data Protection Assessment Standards (CDPAS) is important to the...

• Cybersecurity Materiality & Key Controls

  There is a "materiality ecosystem" that exists within modern cybersecurity risk management discussio...

---