Software Security for Buyers and Government - SAFECode: Difference between revisions
From GCA ACT
Jump to navigationJump to search
(Updated description via script) Tag: Reverted |
(Updated via script) Tag: Manual revert |
||
| Line 1: | Line 1: | ||
=Description=<br> | =Description= | ||
There is no “secret sauce” for creating secure software. It is achieved through the successful execution of a holistic, scalable assurance process that should be transparent to those seeking to evaluate the security of the software they use.=More Information= | <br> | ||
There is no “secret sauce” for creating secure software. It is achieved through the successful execution of a holistic, scalable assurance process that should be transparent to those seeking to evaluate the security of the software they use. SAFECode | |||
<br> | |||
=More Information= | |||
<br> | <br> | ||
https://safecode.org/category/resource-buyers-and-government/ | https://safecode.org/category/resource-buyers-and-government/ | ||
Latest revision as of 05:02, 23 April 2024
Description
There is no “secret sauce” for creating secure software. It is achieved through the successful execution of a holistic, scalable assurance process that should be transparent to those seeking to evaluate the security of the software they use. SAFECode
More Information
https://safecode.org/category/resource-buyers-and-government/
