OWASP Security Integration System



{| style="padding: 0;margin:0;margin-top:10px;text-align:left;" |-
 * valign="top" style="border-right: 1px dotted gray;padding-right:25px;" |

Instructions are in RED text and should be removed from your document by deleting the text with the span tags. This document is intended to serve as an example of what is required of an OWASP project wiki page. The text in red serves as instructions, while the text in black serves as an example. Text in black is expected to be replaced entirely with information specific to your OWASP project.

OWASP Tool Project Template
This section should include an overview of what the project is, why the project was started, and what security issue is being addressed by the project deliverable.

Problems this project addresses
 Low levels of compliance as developers and testers don’t understand the complex security requirements and don’t know how to write code to implement it or test it Development teams see approvers as a blocker. Approvers and assurance delay release while development teams do a blind scramble for evidence to prove they have met the security requirements Risk managers struggle to answer basic questions like what is the highest priority risk across our application landscape, and therefore cannot prioritise or coordinate mitigation efforts. Resulting in duplication of effort and inconsistent implementation across teams 

How does the Secure code assurance tool (SCAT) help
 SCAT is a secure code assurance tool for both inhouse and third party development teams  SCAT is designed to perform a “first line of defense” function for the software development teams  SCAT ensures development teams understand security requirements, correctly implements these, have the testing evidence proving correct implementation and provides insight into development and test.ing efforts  </ul>

Promoting compliance to security requirements
<ul> SCAT allows organisations to translate complex security requirements into code level and testing guidance for development teams. Enabling development teams to correctly and consistently implement these.</li> </ul>

Integrates security
<ul> SCAT wraps security theory, best practices and requirements into set of single purpose security screens. Then maps those screens to a specific SDLC phase. This mapping informs developers of the security requirements for that SDLC phase and gives them the tools to meet those requirements. </li> </ul>

Minimizes the impact of audit and assurance
<ul> SCAT allows testers stores testing evidence against the critical application function and its associated risk. Providing traceability through requirements and centrally storing and publishing test evidence.</li> </ul>

Informing risk based decision making
<ul> SCAT shows, for each application critical function, how many test plans have test evidence and how many security requirements have secure code blocks. Allowing risk teams see which application critical functions need more testing effort and how that testing effort can best be coordinated and prioritized across the appalachian landscape SCAT is a simple 5 screen MVC, C# web application with a small footprint that can be deployed to third party and inhouse development teams without further complicating development environment.</li> </ul>

Promoting compliance to security requirements
<ul> Firstly, understand the security requirement: The tool maintains the following internal mapping allowing organisations to translate complex security requirements into code level and testing guidance the development teams understand. Technologies used in the organisation to secure code requirements</li>  Secure code requirements (OWASP ASVS) to secure code building block </li> Secure test plans to OWASP top 10 risks (OWASP testing guide)</li> The first and second mapping lifted from SKF and duplicated in the SCAT. I hope to link with the SKF and remove the duplicate functionality from the SCAT tool. </li> </ol> Secondly, verify understanding: The tool also makes use of OWASP ZAP basic scan and simple risk training sandboxes to validate understanding and correct implementation</li> </ul>

Integrates security
<ul> In the sprint planning phase SCAT implements “shift left” and uses its internal mapping to generate security requirements before development begins</li> In the Development phase SCAT implements “best practices” that explain security requirements, provides code level and testing guidance to correctly implement them and basic automatic security tooling to verify understanding and correct implementation</li> In the Testing phase SCAT implements “traceability through requirements” and links security test evidence to the critical application function it tests</li> </ul>

How does the Secure code assurance tool help generate secure code
See below how the Security code assurance tool supports the phases of software development and contributes to producing secure software <ul>

Sprint planning phase</li>
<ul> Developers use the Identify risks screen  <li>To Select the application critical function they are developing\changing</li> <li>To identify the technologies they are using to develop\change the application critical function</li> <li>The Secure code assurance tools uses its internal mapping to automatically generate the security requirements associated with using this technology</li> See how to use the tools and its internal mapping to generate seurity requirements </ol> </li> </ul>

<li>Development phase</li>
<ul> <li>Developers use the Secure development screen <ol> <li>To see and understand how to attack and prevent the risks associated with the critical function</li> <li>To see the secure code requirements to protect against exploitation</li> <li>To see the secure code block to guide developers to implement security requirement</li> <li>After development run a ZAP basic scan to verify security requirements have been correctly implemented </li> See how the tool helps developers understand securty requirements and write secure code </ol> </li> </ul>

<li>Testing phase</li>
<ul> <li>Testers use the Secure testing screen <ol> <li>To see the OWASP test plans required to test the risk mitigation efforts</li> <li>To attach testing result to the test plan as control assurance evidence proving the risk has been mitigated</li> <li>The Secure code assurance tool does not integrate with any testing tools other than OWASP ZAP. Testing results generated outside of the secure code assurance tool is manually uploaded and stored</li> See how the tool helps testers test risk mitigation efforts and strore testing evidence </ol> </li> </ul>

<li>Approval phase</li>
<ul> <li>Approvers use the Assurance evidence  screen <ol> <li>To see relevant testing evidence alongside the risk, reducing the time assurance teams need to examine and approve releases</li> <li>To see how many of the tests have test results</li> See how the tool streamlines the approval process with centrally stored testing evidence </ol> </li> </ul>

<li>Risk management</li>
<ul> <li>Risk managers use the Application risk exposure screen <ol> <li>To see each application critical function and the associated risks</li> <li>To see the number of security requirements for each risk, and which of those requirements have secure code block. Allowing risk team to define where mitigation effort it required and monitors the progress of mitigation efforts</li> <li>To see the number of security tests for each risk. Allowing risk team to determine where extra testing effort is required and monitor test coverage and quality</li> See how the Application landscape overview screen informs risk based decision making </ol> </li> </ul>

Tool setup
<ul> <li>Tool setup The tool lists all application critical functions. And for each critical function it maintains an internal mapping that details the technologies, risks, security requirements, secure code blocks and tests. A basic mapping exists in the tool but needs to be customised for your environment.</li> <ol> <li>InfoSec, testing and development teams: Use the tools OWASP data mapping screen to modify the internal mapping. </li> </ol> </ul>

Parked
There are 3 domains to consider when securing software development. <ol> <li>The secure software development process: Involves securing the way an organisation develops software. So any development change dropped into the process comes out secure on the other end.</li> <li>Developing secure code: Helping the development team produce secure code. By supporting the development team at each phase of the software development process</li> <li>Continuous improvement:..........</li> </ol>

This OWASP project focuses on the Developing secure code domain and details the why and how behind the Secure code assurance tool. I've detailed the other domains in an article that will be published in the Nov/Dec issue of the ISC2 magazine, I will add a link here after publication.

Why the Secure code assurance tool

Producing secure software requires the input of a number of teams
<ol> <li>Information security: Needs to understand the technology behind the functional requirement and its associated risks. Then generate a list of security requirements to protect the technology against exploitation</li> <li>Development teams: Need to implement the technology, test it and record evidence proving the security requirements are met and </li> <li>Approvers: Need to review testing evidence against the organisations risk tolerance levels. Then accept the risk associate with the functional requirement by approving the release</li> <li>Compliance and Assurance: Need to review the testing evidence collected by the development teams and verify its consistency, traceability and quality</li> <li>IT risk: Needs to manage and monitor risk mitigation efforts </li> </ol>

Why is producing secure software so hard and how does the Secure code assurance tool help?
<ol> <li>Complex environments: Development, security, risk, compliance and assurance teams need to combine their GDPR, ISO, risk tolerances level, OWASP ASVS, security testing, JAVA and .Net knowledge, filter it, and generate security requirements for each critical application function. The process of aligning the knowledge and efforts of these teams is time consuming and slows down the development process</li> How does the tool help <ul> <li>Centrally stores security requirements and links these to the technologies used in the organisation environment. Allowing developers to select the technology used to implement their functional requirement and automatically get a list of relevant security requirements</li> <li>Benefit: Developers can generate the security requirements themselves, without waiting on the security, risk, compliance and assurance teams. This will speed up the requirements generation process make it consistent and repeatable across all teams</li> </ul> <li>Huge number of complex security requirements: Development teams do not understand the complicated security requirements therefore cannot correctly implement or test them. Also, the flexibility of development languages almost guarantee that every developer will implement the security requirement differently</li> How does the tool help <ul> <li>Stores a language specific and approved secure code building block against each security requirement. These guide developers towards constantly implementing the security requirements</li> <li>Stores a set of OWASP tests against each risk. Guiding the testing team on how to correctly validate the security requirement has been met</li> <li>Allows developers to run an "on demand" OWASP ZAP basic scan on their code. Enabling an immediate feedback loop to verify they have correctly implemented the security requirements</li> <li>Allows developers to open an "on demand" risk training sandbox environment. Training developers how to exploit and defend against the risk</li> </ul> <li>Compliance: Approvers review testing evidence to make sure development teams have complied to the ever increasing security and regulatory requirements. But finding the relevant testing evidence generated by testers or in CI\CD pipelines is a lengthy process that blocks the release</li> How does the tool help <ul> <li>Centrally stores testing evidence alongside the risk and application critical function. Allowing approvers to quickly see if the critical application function has been tested and mitigated according to risk tolerance</li> </ul> <li>Risk management of the application landscape: Risk managers cannot</li> <ol> <li>see which security requirements do not have secure code blocks</il> <li>see which risks need test plans or have not been tested</li> <li>see how a single security test can be re-used to test a different application risk</li> <li>see where mitigation efforts will have the most impact</li> </ol> How does the tool help <ul> <li>Provides a dashboard view of application landscape giving risk managers the information they need to prioritise and manage risk efforts </li> </ul> </ol>

Description
This is where you need to add your more robust project description. A project description should outline the purpose of the project, how it is used, and the value it provides to application security. Ideally, project descriptions should be written in such a way that there is no question what value the project provides to the software security community. This section will be seen and used in various places within the Projects Portal. Poorly written project descriptions therefore detract from a project’s visibility, so project leaders should ensure that the description is meaningful.

How does the Secure code assurance tool help generate secure code
See below how the Security code assurance tool supports the phases of software development and contributes to producing secure software <ul>

<li>Sprint planning phase</li>
<ul> <li>Developers use the Identify risks screen <ol> <li>To identify the technologies used to implement the application critical function</li> <li>The Secure code assurance tools internal mapping will automatically generate the security requirements associated with using this technology</li> See how to use the tools and its internal mapping to generate seurity requirements </ol> </li> </ul>

<li>Development phase</li>
<ul> <li>Developers use the Secure development screen <ol> <li>To see and understand how to attack and prevent the risks associated with the critical function</li> <li>To see the secure code requirements to protect against exploitation</li> <li>To see the secure code block to guide developers to implement security requirement</li> <li>After development run a ZAP basic scan to verify security requirements have been correctly implemented </li> See how the tool helps developers understand securty requirements and write secure code </ol> </li> </ul>

<li>Testing phase</li>
<ul> <li>Testers use the Secure testing screen <ol> <li>To see the OWASP test plans required to test the risk mitigation efforts</li> <li>Associate an automated testing tool with the test plan. The secure coding tool allows testers to bulk update test results form the testing tool</li> <li>To attach testing result to the test as control assurance evidence proving the risk has been mitigated</li> <li>The Secure code assurance tool does not integrate with any testing tools other than OWASP ZAP. Testing results are generated outside of the secure coding tool and manually stored</li> See how the tool helps testers test risk mitigation efforts and strore testing evidence </ol> </li> </ul>

<li>Approval phase</li>
<ul> <li>Approvers use the Assurance evidence  screen <ol> <li>To see relevant testing evidence alongside the risk, reducing time assurance teams need to examine and approve releases</li> <li>To see how many of the tests have test results</li> See how the tool streamlines the approval process with centrally stored testing evidence </ol> </li> </ul>

<li>Risk management</li>
<ul> <li>Risk managers use the Application risk exposure screen <ol> <li>To see each application critical function and the associated risks</li> <li>To see the number of security requirements for each risk, and which of those requirements have secure code block. Allowing risk team to define where mitigation effort it required and monitors the progress of mitigation efforts</li> <li>To see the number of security tests for each risk. Allowing risk team to determine where extra testing effort is required and monitor test coverage and quality</li> See how the Application landscape overview screen informs risk based decision making </ol> </li> </ul>

What does the Secure coding tool do? The secure coding tool, goes beyond theory and procedure and attempts to implement a planned control integration effort. The Secure coding tool is written in MVC \ MySQL and consists of 5 screens each serving a specific stakeholder

<ol> <li>Information security stakeholder: Filters the security requirements according to the functional requirement: Streamlining security requirements generation </li> <li>Dev team stakeholder: Provides secure code blocks to implement the security requirement: Providing code level guidance for developers towards correctly implementing security requirements</li> <li>Dev team stakeholder: Provides security test plans to testing the security requirements: Guiding testers towards correctly verifying security requirements are met</li> <li>Compliance and assurance stakeholder: Provides a central store for testing results: Promoting traceability through requirements and serving as a quick reference screen for assurance to view control assurance evidence, speeding up the approval process and minimising its impact on responsiveness to market</li> <li>IT risk stakeholder: Provides IT risk with an overview of each applications exposure to OWASP TOP 10 risks: Informing risk based decision making and prioritising</li> </ol>

How does the secure coding tool do it? The secure coding tool, goes beyond theory and procedure and attempts to implement a planned control integration effort. The Secure coding tool is written in MVC \ MySQL and consists of 5 screens each serving a specific stakeholder <ol> <li>Information security stakeholder: Filters the security requirements according to the functional requirement: Streamlining security requirements generation </li> <li>Dev team stakeholder: Provides secure code blocks to implement the security requirement: Providing code level guidance for developers towards correctly implementing security requirements</li> <li>Dev team stakeholder: Provides security test plans to testing the security requirements: Guiding testers towards correctly verifying security requirements are met</li> <li>Compliance and assurance stakeholder: Provides a central store for testing results: Promoting traceability through requirements and serving as a quick reference screen for assurance to view control assurance evidence, speeding up the approval process and minimising its impact on responsiveness to market</li> <li>IT risk stakeholder: Provides IT risk with an overview of each applications exposure to OWASP TOP 10 risks: Informing risk based decision making and prioritising</li> </ol>

For a more detailed look at the inner workings of the tool and a brief instructional video please take a look at my linkedIn article Secure coding tool

Licensing
A project must be licensed under a community friendly or open source license. For more information on OWASP recommended licenses, please see OWASP Licenses. While OWASP does not promote any particular license over another, the vast majority of projects have chosen a Creative Commons license variant for documentation projects, or a GNU General Public License variant for tools and code projects. This example assumes that you want to use the AGPL 3.0 license.

This program is free software: you can redistribute it and/or modify it under the terms of the link GNU Affero General Public License 3.0 as published by the Free Software Foundation, either version 3 of the License, or (at your option) any later version. OWASP XXX and any contributions are Copyright &copy; by {the Project Leader(s) or OWASP} {Year(s)}.

Roadmap
As of November, 2013, the highest priorities for the next 6 months are:
 * Complete the first draft of the Tool Project Template
 * Get other people to review the Tool Project Template and provide feedback
 * Incorporate feedback into changes in the Tool Project Template
 * Finalize the Tool Project template and have it reviewed to be promoted from an Incubator Project to a Lab Project

Subsequent Releases will add
 * Internationalization Support
 * Additional Unit Tests
 * Automated Regression tests

Getting Involved
Involvement in the development and promotion of Tool Project Template is actively encouraged! You do not have to be a security expert or a programmer to contribute. Some of the ways you can help are as follows:


 * valign="top" style="padding-left:25px;width:200px;border-right: 1px dotted gray;padding-right:25px;" |

Project Resources
This is where you can link to the key locations for project files, including setup programs, the source code repository, online documentation, a Wiki Home Page, threaded discussions about the project, and Issue Tracking system, etc.

Installation Package

Source Code

What's New (Revision History)

Documentation

Wiki Home Page

Issue Tracker

Slide Presentation

Video

Project Leader
A project leader is the individual who decides to lead the project throughout its lifecycle. The project leader is responsible for communicating the project’s progress to the OWASP Foundation, and he/she is ultimately responsible for the project’s deliverables. The project leader must provide OWASP with his/her real name and contact e-mail address for his/her project application to be accepted, as OWASP prides itself on the openness of its products, operations, and members.

Michael Bergman

Related Projects
This is where you can link to other OWASP Projects that are similar to yours.
 * OWASP_Code_Project_Template
 * OWASP_Documentation_Project_Template

Classifications

 * }