Take the 2-minute tour ×
Information Security Stack Exchange is a question and answer site for Information security professionals. It's 100% free, no registration required.

In software engineering, a design pattern is a general reusable solution to a commonly occurring problem within a given context in software design. Wikipedia lists many different design patterns for example, but security is never mentioned.

Open SAMM includes the following question in the audit checklist for Secure Architecture: Are project teams provided with prescriptive design patterns based on their application architecture?

I never came across any established security design patterns that are considered state of the art from the community. Am I missing something here or are there no such security design patterns?

share|improve this question
add comment

2 Answers

up vote 4 down vote accepted

The thing about security is that it's never a one-size-fits-all sort of deal. Because of that you always have to adapt designs to apply to the threats you're willing to counter. A good security design pattern is just a good software design pattern.

If you take a look at Wikipedia it lists a few: http://en.wikipedia.org/wiki/Security_Patterns

There is also an interesting website I came across while Googling: http://www.securitypatterns.org/patterns.html

Or if you take a look at CERT ( http://www.cert.org/archive/pdf/09tr010.pdf ) it lists a few. Here are some just from it's list of figures:

  • Defer to Kernel Pattern
  • Secure Factory Pattern Structure
  • Secure Strategy Factory Pattern Structure
  • Secure Builder Factory Pattern Structure
  • Secure Chain of Responsibility Pattern Example
  • Secure Chain of Responsibility Pattern Structure
  • Secure State Machine Pattern Structure
  • Secure State Machine Example Code Collaboration Diagram
  • Secure Visitor Pattern Structure
  • Secure Visitor Example Code Collaboration Diagram
  • Secure Logger Pattern Structure
  • Clear Sensitive Information Pattern Structure
  • Structure of the Input Validation Pattern
share|improve this answer
    
These patterns are mostly relevant for applets and other situations when your code executes in untrusted environment. They are generally useless for, say, web apps. –  Vitaly Osipov Nov 28 '12 at 4:09
add comment

While we wait for this book, you can read and postulate the writings of Rohit Sethi in [PDF] Securing the Core JEE Patterns2 [PDF].

Also be sure to check out the project he runs on a Security Analysis of Core J2EE Design Patterns.

share|improve this answer
add comment

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.