Security Principles

Tweet Good security principles should be reused. So save time and prevent extra risks by using good security principles for your new product. Why reinvent the wheel again? You can also all download security principles to reuse them off-line in


Software Assurance Maturity Model (SAMM) – Self Assessment

Click here to start the SAMM self assessment test again. The Software Assurance Maturity Model (SAMM) is an open framework to help organizations formulate and implement a strategy for software security that is tailored to the specific risks facing the


Security Specifications

Creating security specifications can be hard and complex. We created a tool that will give you a head start with this development step. Having good security requirements is important. Always. Use our on-line tool to select the security principles and

Open Reference Architecture for Security and Privacy

Using this book gives creating your security solution a head start!

Free Download!

Minimizing security risks can be hard, expensive and often fails. IT Security is a complex field. People, processes and technology are crucial parts of an architecture to reduce risks. Our certified experts love to solve your cyber security challenges. Detecting what is not good with your current security is the simple work. You can find many companies that will launch automated test suites based on open source tools that will tell you that you are not secure enough. However the real challenge is designing solutions that are secure.

We create security architectures and security models and, design cyber security solutions that will work for your business and users and reduce your security risks.

Good security does not have to be complex. So kill the complexity to lower your security risks!

In our opinion a good system security model defines minimal:

  • attack vectors (as answer on the ‘what information objects¬† must be secured’ question)
  • roles and permissions
  • the interactions, dependencies and relations
  • identify trust boundaries
  • software architecture and hosting architecture used (including all for security relevant technical dependencies)
  • availability measures, backup, logging and audit requirements and refer to data classifications schemas defined in the security policies.

A context specific security model is used as a key reference point during information system design and development.

All our security architects are  permanently trained and are Togaf and CISSP certified.

Contact us for more information!

Complexity is the Enemy of Security