Difference between revisions of "Implement and elaborate resource policies and security technologies"

From OWASP
Jump to: navigation, search
m
 
(5 intermediate revisions by 3 users not shown)
Line 1: Line 1:
 +
{{Template:SecureSoftware}}
 +
 +
==Overview==
  
 
Purpose:
 
Purpose:
Line 24: Line 27:
 
As with most development, implementers should build software to specification. Even when security is a concern, this is not different. As is the case when implementing traditional features, the implementer should ensure that all coding guidelines are met - especially security guidelines.
 
As with most development, implementers should build software to specification. Even when security is a concern, this is not different. As is the case when implementing traditional features, the implementer should ensure that all coding guidelines are met - especially security guidelines.
  
==Categories==
 
  
 
[[Category:Activity]]
 
[[Category:Activity]]
 +
[[Category:CLASP Activity]]
 +
[[Category:BP4 Implement secure development practices]]
 +
[[Category:OWASP_CLASP_Project]]

Latest revision as of 06:35, 29 May 2006


Overview

Purpose:

  • Implement security functionality to specification

Role:

  • Implementer

Frequency:

  • As necessary


Review specified behavior

The developer should identify any remaining ambiguities in the specification of security properties or technologies, including any further information necessary to build a concrete implementation.

Perceived ambiguities should be addressed with the designer.

Implement specification

As with most development, implementers should build software to specification. Even when security is a concern, this is not different. As is the case when implementing traditional features, the implementer should ensure that all coding guidelines are met - especially security guidelines.