Awesome Open Source
Awesome Open Source

Documentation Status


Open Repository for the Open Security and Privacy Reference Architecture

Open publications for IT security and privacy are still rare. Despite the great work of the OWASP foundation many valuable resources for Security and Privacy are not open. Security and Privacy is technological complex and real risks mitigation is still problematic and expensive.

This reference architecture aims to enable you to create better and faster security and privacy solutions. This by reusing content that is provided in this reference architecture or by directing you to open (cc-by) resources to prevent reinventing the wheel. To encourage collaboration for this project this reference architecture is of course free and open (cc-by-sa).

This project is supported by the BM-Support Foundation,

Current status: We are working on a update for the 2020 hardcopy version of this 'Open Reference Architecture for Security and Privacy'. But the online version will always be up-to-date! So join the party and join the team to make this Open resource better!


We encourage all security professionals to improve this reference architecture. Join the team to:

  • Add security or privacy principles.
  • Add security or privacy models.
  • Help us create the largest OSS reference framework on OSS security and privacy applications and tools.
  • Create better graphics and text.
  • Add threat models that can be easily reused.
  • Improve criteria on selecting OSS solutions for security and privacy applications.
  • Create tools to speed up the process of making your security architectures or privacy designs with use of this reference architecture (and tools).

Your contributions to this Guide are greatly appreciated as long as contributions fit within the scope and goal of this security and privacy reference architecture. As an open project, this Open Reference Architecture for Security and Privacy shall always remain vendor-neutral and freely available for all to use. If you contribute you will of course get credit (mentioned in upcoming publications).

With the exception of typos and spelling mistakes (feel free to fix these and they’ll be merged), please observe the following guides:

  • Always open an issue first. This will allow us to determine whether or not the change should take place.
  • Explain your issue, and we will discuss it with you. If we agree the change is necessary we will mark it as TODO and will fix it when we get a chance, or we will allow a member of the community to supply the change with a pull request.
  • This reference architecture is intended to be a helpful resource aimed at professional security/privacy architects and engineers.
  • Contributions must fit within the scope and goal of this security and privacy reference architecture. Of course we like to discuss your input for changing scope or goals if needed!

For small corrections or input, just send me an email. For larger contributions, please create a pull request.


When you submit text to which you hold the copyright, you agree to license it under:

  • Creative Commons Attribution-ShareAlike 4.0 International License (CC BY-SA 4.0).

Get A Weekly Email With Trending Projects For These Topics
No Spam. Unsubscribe easily at any time.
python (54,388
security (1,908
security-tools (410
privacy (407
gdpr (54