Framework Secure Software

The Framework Secure Software defines a standard to help to improve secure software development:

  • For development teams, the framework helps to implement secure software development practices
  • For inspectors, the framework gives criteria to evaluate the security of software.
  • For purchasers, the secure software certificate makes the software’s security properties visible

Goals of the Framework

100% security is impossible, but the framework can evaluate if security is sufficiently implemented. The framework:

  • Covers all phases of the SDLC
  • Fits all software development methodologies
  • Is applicable to a wide range of software applications
  • Bridges the gap between non-technical requirements and technical implementation
  • Makes it possible to issue the secure software certificate.

Availability

The Framework Secure Software is available under an open source license;
This is indicative of the open nature of this initiative.

Download Framework

Certification

In December 2015 the first “Secure Software Certificate” has been issued by the Secure Software Alliance as the final result of a pilot.
The certificate is based on the Framework Secure Software. Based on the pilot, the SSA will finalize the certification methodology in the course of 2015. The certification process will cover the software development process as well as specific applications that are produced as a result. If you want more information about certification let us know.

How does it Work?

The framework is divided into four phases:

Context

In the context phase, the security requirements and security assumptions are determined. The context defines what `secure’ means for the software system. Using a systematic method, it is possible to check for missing security requirements.

Threats

Based on the above context, potential security problems (threats) are identified. Threats originate from the application’s behavior, its architecture and its implementation.

Implementation

For every threat, a countermeasure (mitigation) is created. Because threats are gathered systematically using a threat library, missing threats can be detected. Implementation The use of a secure coding standard helps to prevent security issues at the implementation level. A systematic code audit can check if the software is securely implemented.

Verification

For every mitigation, a verification is described. During development, these verifications provide feedback to the development team. The evaluation of these verifications gives an extra assurance that the mitigations are securely implemented.