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;" |

Table of content
 Description of the Secure code assurance tool (SCAT) and how it builds, verifies and assures secure software See how the SCAT single purpose screens integrate security into each of the SDLC phases How to import client specific risks, security requirements and tests 

What is the Secure code assurance tool (SCAT)
 SCAT is used by inhouse and third party development teams to build, verify and assure secure software

Build
  SCAT uses code level guidance to clearly instructs developers on how to correctly implement security requirements  

Description
 SCAT is used by inhouse and third party development teams to build, verify and assure secure software

Build
  SCAT uses code level guidance to clearly instructs developers on how to correctly implement security requirements </li> </ul>

Verify
 SCAT uses a combination of ZAP basic scans and security test plans to verify correct implementation of security requirements</li> </ul>

Assure
 SCAT centrally stores and publishes test results. Providing traceability through requirements and assurance evidence of correct implementation</li> </ul>

SCAT has the following governance objectives implemented by the following “first line of defense” functions

Benefits realisation: Enabling development teams to deliver at speed
 Promoting compliance to security requirements</li> Minimising the impact of audit and assurance</li> </ol>

Risk optimisation: Minimise the negative and maximise the positive consequences
 Informing risk based decision making</li> </ol>

Resource optimisation: Predictable, repeatable and consistent level of security across all teams
 Integrating security into the software development process</li> </ol> SCAT is a simple 5 screen MVC, C# web application with a small footprint that can be deployed without further complicating development environment</li> SCAT is part of three domains to consider when securing software development</li> 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. </ul>

See how developers use SCAT
See below how the Secure code assurance tool integrates security into software development phases 

Sprint planning phase</li>
Objective: Enabling developers to generate security requirements before development begins How <ol> <li>Link security risk and requirements to specific technologies</li> <li>Developers select technologies and get the lit of associated risks and security requirements</li> </ol> <ul> <li>Developers use the Identify risks screen to            <ol> <li>Select the application critical function they are developing/changing</li> <li>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 security requirements </ol> <li>Product owners use the Secure code requirements screen to            <ol> <li>Export security requirements for import into backlog management tools</li> </ol> </li> </ul>

<li>Development phase</li>
Objective: Consistent and correct implementation of security requirements across all teams How <ol> <li>Organisation approved secure code blocks for each security requirement</li> <li>ZAP basic vulnerability scan to verify understanding</li> </ol> <ul> <li>Developers use the Secure development screen to            <ol> <li>View and understand how to attack and prevent the risks associated with the critical function</li> <li>View the secure code requirements to protect against exploitation</li> <li>View the secure code block to implement the 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 security requirements and write secure code </ol> </li> </ul>

<li>Testing phase</li>
Objective: Guide the secure testing process How <ol> <li>Providing secure tests plans to test risk/li> <li>Successful test results from organisational test suite is centrally stored against each risk</li> </ol> <ul> <li>Testers use the Secure testing screen to            <ol> <li>View the test plans required to test the risk</li> <li>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 store testing evidence </ol> </li> </ul>

<li>Approval phase</li>
Objective: Streamline the approval and audit process How <ol> <li>Providing traceability through requirements by centrally publishing the risk alongside its secure test plan and test results/li> <li>Giving approvers and auditors all the information they require for their assessment</li> </ol> <ul> <li>Approvers use the Assurance evidence  screen to            <ol> <li>View relevant testing evidence alongside the risk, reducing the time assurance teams need to examine and approve releases</li> <li>View how many of the tests have test results and whether it falls within risk tolerance levels</li> See how the tool streamlines the approval process with centrally stored testing evidence </ol> </li> </ul>

<li>Risk management</li>
Objective: Enable risk managers to prioritise, plan and monitor mitigation efforts <ul> <li>Risk managers use the Application risk exposure screen to            <ol> <li>View each application critical function and the associated risks</li> <li>Identify where mitigation effort is required by viewing which risks require security requirements</li> <li>Identify where development effort is required by viewing which security requirements need secure code blocks</li> <li>Identify where extra testing effort is required by viewing which risks require security test plans</li> See how the Application landscape overview screen informs risk based decision making </ol> </li> </ul>

Preparation phase
When developing secure software we need to consider both standard secure code and client specific architectural requirements

Standard secure code requirements
<ul> <li>SCAT comes out the box with a standard OWASP secure code requirements map. This mapping need to be modified to the specific organisation requirements</li> <li>Information security and development team use the Internal mapping  screen to           <ol> <li>Map the security requirements to OWASP risks</li> <li>Map organisation approved secure code blocks to security requirements</li> <li>Map security test plans to OWASP risks</li> See how to setup the SCAT's internal mapping </ol> </li> </ul>

Client specific architectural requirements
<ul> <li>To generate these requirements we perform a risk assessment on client application landscape and identify</li> <ol> <li>Critical applications and functions</li> <li>Risk associated with each critical application function</li> <li>Architectural security requirements to secure each critical application functions</li> <li>Client specific secure code blocks to implement security requirements</li> <li>Secure test plans to verify risk has been mitigated</li> </ol> <li>Tool administrators use the Internal mapping  screen to <ol> <li>Create json files of the organisation specific risks, security requirements, secure code blocks and tests</li> <li>Import these into the SCAT</li> See how to import organisations specific risks, security requirements, secure code blocks and tests </ol> </ul>

Promoting compliance to security requirements
<ul> <li>Understand the security requirement: The tool maintains the following internal mapping allowing organisations to translate complex security requirements into code level and testing guidance</li> <ol> <li>Risks mapped to technologies and secure code requirements</li> <li>Secure code requirements (OWASP ASVS) mapped to secure code building block</li> <li>Secure test plans (OWASP testing guide) mapped to risks</li> <li>The second mapping is lifted from OWASP secure knowledge framework and duplicated in the SCAT. I hope to link with the SKF and remove the duplicate functionality from the SCAT tool</li> </ol> <li>Verify understanding: The tool also makes use of OWASP ZAP basic scan to scan localhost for vulnerabilities, confirming the correct implementation of security requirements </li> </ul>

Minimising the impact of audit and assurance
<ul> <li>In the testing and approval phase SCAT allows testers to 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> <li>For each application critical function, SCAT shows</li> <ol> <li>The risks that impact that application critical function</li> <li>Security requirements and secure code block to protect against the risk</li> <li>Test evidence proving risk has been mitigated to within tolerance</li> </ol> <li>Allowing risk teams see levels of exposure, easily compare it to tolerance levels. And prioritise and coordinate mitigation activities across teams and the whole application landscape</li> </ul>

Integrating security into the software development process
<ul> <li>SCAT wraps security theory, best practices and requirements into set of single purpose security screens. Then plots each of those screens to a specific software development phase</li> <li>Plotting security screens to specific software development phases provides development teams with concise information when and how they need it</li> </ul>

Licensing
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.

Project Resources
[Installation Package]

[Source Code]

Project Leader
Michael Bergman

Classifications

 * }