This site is the archived OWASP Foundation Wiki and is no longer accepting Account Requests.
To view the new OWASP Foundation website, please visit https://owasp.org
Difference between revisions of "Talk:Industry:Project Review/NIST SP 800-37r1 FPD Appendix I"
From OWASP
(→APPENDIX I SECURITY CONTROLS IN EXTERNAL ENVIRONMENTS) |
|||
| Line 13: | Line 13: | ||
"Application Security Procurement Language is freely available at [http://www.sans.org/appseccontract/]. These guidelines incorporate substantial language from the OWASP Secure Software Contract Annex, which is freely available at [https://www.owasp.org/index.php/OWASP_Secure_Software_Contract_Annex]. These ... enable buyers of custom software to more explicitly focus on the responsibilities of code writers for checking the code and for fixing security flaws before software is delivered. The sample procurement language ... addresses: | "Application Security Procurement Language is freely available at [http://www.sans.org/appseccontract/]. These guidelines incorporate substantial language from the OWASP Secure Software Contract Annex, which is freely available at [https://www.owasp.org/index.php/OWASP_Secure_Software_Contract_Annex]. These ... enable buyers of custom software to more explicitly focus on the responsibilities of code writers for checking the code and for fixing security flaws before software is delivered. The sample procurement language ... addresses: | ||
| − | * | + | *Personnel, Security Training, Background Checks of Developers, Vulnerabilities, Risks and Threats, and Application Development. |
| − | * | + | *Development environment: Secure Coding, Configuration Management, Distribution, Disclosure, and Evaluation. |
| − | * | + | *Testing: test planning, source code reviews, as well as vulnerability and penetration tests. |
*Patches and Updates, along with notification and testing of those modifications to the software. | *Patches and Updates, along with notification and testing of those modifications to the software. | ||
*Tracking Security Issues. - vendor ... “certification package” that establishes the security requirements, design, implementation, and test results were properly completed and all security issues were resolved appropriately. Its provisions include specifying that the developer is to warrant that the software shall not contain any code that does not support a software requirement and weakens the security of the application, including computer viruses, worms, time bombs, back doors, Trojan horses, Easter eggs, and all other forms of malicious code. It offers procurement language for how security issues will be investigated." | *Tracking Security Issues. - vendor ... “certification package” that establishes the security requirements, design, implementation, and test results were properly completed and all security issues were resolved appropriately. Its provisions include specifying that the developer is to warrant that the software shall not contain any code that does not support a software requirement and weakens the security of the application, including computer viruses, worms, time bombs, back doors, Trojan horses, Easter eggs, and all other forms of malicious code. It offers procurement language for how security issues will be investigated." | ||
| − | [https://buildsecurityin.us-cert.gov/swa/acqwg.html Acquisition and Outsourcing Working Group] | + | [https://buildsecurityin.us-cert.gov/swa/acqwg.html Acquisition and Outsourcing Working Group] |
<br>--[[User:Walter Houser|Walter Houser]] 23:22, 19 December 2009 (UTC) | <br>--[[User:Walter Houser|Walter Houser]] 23:22, 19 December 2009 (UTC) | ||
[[Category:GIC-NISTSP80037r1FPD]] | [[Category:GIC-NISTSP80037r1FPD]] | ||
Revision as of 23:38, 19 December 2009
PARTNERSHIPS, OUTSOURCING ARRANGEMENTS, SUPPLY CHAIN EXCHANGES
APPENDIX I SECURITY CONTROLS IN EXTERNAL ENVIRONMENTS
Software Assurance in Acquisition: Mitigating Risks to the Enterprise "... provides information on how to incorporate SwA considerations in key decisions and how to exercise due diligence throughout the acquisition process relative to potential risk exposures that could be introduced by the supply chain." [1]
"Application Security Procurement Language is freely available at [2]. These guidelines incorporate substantial language from the OWASP Secure Software Contract Annex, which is freely available at [3]. These ... enable buyers of custom software to more explicitly focus on the responsibilities of code writers for checking the code and for fixing security flaws before software is delivered. The sample procurement language ... addresses:
- Personnel, Security Training, Background Checks of Developers, Vulnerabilities, Risks and Threats, and Application Development.
- Development environment: Secure Coding, Configuration Management, Distribution, Disclosure, and Evaluation.
- Testing: test planning, source code reviews, as well as vulnerability and penetration tests.
- Patches and Updates, along with notification and testing of those modifications to the software.
- Tracking Security Issues. - vendor ... “certification package” that establishes the security requirements, design, implementation, and test results were properly completed and all security issues were resolved appropriately. Its provisions include specifying that the developer is to warrant that the software shall not contain any code that does not support a software requirement and weakens the security of the application, including computer viruses, worms, time bombs, back doors, Trojan horses, Easter eggs, and all other forms of malicious code. It offers procurement language for how security issues will be investigated."
Acquisition and Outsourcing Working Group
--Walter Houser 23:22, 19 December 2009 (UTC)
