Security Patterns

From Guidance Share

(Difference between revisions)
Jump to: navigation, search
Revision as of 18:15, 21 June 2008 (edit)
JD (Talk | contribs)

← Previous diff
Current revision (18:16, 21 June 2008) (edit)
JD (Talk | contribs)

 
Line 1: Line 1:
{| {|
| |
-[[image:InspectionCenter.gif]]+<!-- [[image:InspectionCenter.gif]] -->
|| ||
Security patterns are problem and solution pairs. Here you'll find four types of patterns: design, implementation, attack and vulnerability patterns. You can use the patterns to help shape your countermeasures and to help understand the potential security issues that your software faces. Design patterns help you solve key engineering issues that have cascading impact. Attack patterns help you understand the ways that software is attacked. Vulnerability patterns help you understand the ways that software is vulnerable to attacks. Use the patterns to help you leverage proven practices and to help you avoid known bad practices. Remember that patterns are starting points. Security patterns are problem and solution pairs. Here you'll find four types of patterns: design, implementation, attack and vulnerability patterns. You can use the patterns to help shape your countermeasures and to help understand the potential security issues that your software faces. Design patterns help you solve key engineering issues that have cascading impact. Attack patterns help you understand the ways that software is attacked. Vulnerability patterns help you understand the ways that software is vulnerable to attacks. Use the patterns to help you leverage proven practices and to help you avoid known bad practices. Remember that patterns are starting points.
Line 13: Line 13:
=== Design Patterns === === Design Patterns ===
* [[Security Design Patterns]] * [[Security Design Patterns]]
 +
=== Implementation Patterns === === Implementation Patterns ===

Current revision

Security patterns are problem and solution pairs. Here you'll find four types of patterns: design, implementation, attack and vulnerability patterns. You can use the patterns to help shape your countermeasures and to help understand the potential security issues that your software faces. Design patterns help you solve key engineering issues that have cascading impact. Attack patterns help you understand the ways that software is attacked. Vulnerability patterns help you understand the ways that software is vulnerable to attacks. Use the patterns to help you leverage proven practices and to help you avoid known bad practices. Remember that patterns are starting points.


Design Patterns


Implementation Patterns



Attack Patterns


Vulnerability Patterns





Personal tools