Difference between revisions of "OWASP Security Integration System"

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.

Project About

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. Some readers may be discouraged from looking further at the project if they do not understand the significance of the security concern that is being addressed, so provide enough context so the average reader will continue on with reading the description. You shouldn't assume the reader will understand the objective by providing security terminology, e.g. this project builds cryptographic algorithms, but should also endeavor to explain what they are used for.

The OWASP Tool Template Project is a template designed to help Project Leaders create suitable project pages for OWASP Projects. By following the instructional text in red (and then deleting it) it should be easier to understand what information OWASP and the project users are looking for. And it's easy to get started by simply creating a new project from the appropriate project template.

Introduction</br> Secure coding is an umbrella term that covers the requirements of IT risk, assurance, Information security and compliance. </br> This means that when the development team codes a functional requirement they must not only consider the functional requirement and getting it to market before competitors but also the risks that functionality exposes the organisation too.

What is the problem the secure coding tool is tying to fixing? </br> When the development team codes, for example, a functionality that requires a ASW RDS.

1. Firstly, the dev teams need to read and understand all 99 articles of the GDPR: to make sure, for example, the data is categorised and user consent is stored
2. Secondly, the dev teams need to read and understand the 114 controls listed in ISO 27002 (if the use ISO): To make sure the solution can be safely integrated into the organisations information security management system (ISMS) and for example, application logs are in a format that can be consumed and reported to the SEIM
3. Thirdly the dev teams needs to select form the 99 GDPR articles and the 114 ISO controls those that apply to the solution, perform a risk assessment on the selected controls, write security test plans to test selected controls
4. Fourthly the dev teams need to select an appropriate and approved technical implementation for the selected security control
5. An only then begin development
</br> Development teams cannot perform these security tasks within a reasonable time frame, let alone a two week sprint cycle By this time the 2 week sprint cycle has elapsed and The solution(s)

There are 2 ways to ensure development teams meet these varied requirements. 1. Without control integration: Dev teams read and understand the GDPR, ISO 27002, familiarise themselves with the organisation ISMS requirements and also, keep up to date with the technical changes in the development language they use. <p>This usually results in dev teams being referred to 50 page policy documents and told "Please implement this and we will check it after"

2. With a planned control integration effort:

We write a very simple tool that 1. Filters the security requirements according to the functional requirement: Streamlining security requirements generation 2. Provides secure code blocks to implement the security requirement: Guiding developers towards correctly implementing security requirements 3. Provides security test plans to testing the security requirements: Guiding testers towards correctly verifying security requirements are met 4. 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 5. Provides IT risk with an overview of each applications exposure to OWASP TOP 10 risks: landscape and how each aand gives them to development teams when they need it and in a format they need it.

The secure coding tool is an attempt to follow the second way. Before we summerise what the tool does its important to know that the tool is part of a system of components to secure software development. Other components of the system include governance and vulnerability management. I've detailed these components in a different article that will be published in the Nov/Dec issue of the ISC2 magazine. </p> After reading this short article, please take a look at the video link below to see the tool in action.

Summary of the tool functionality: Developers Testers Approvers \Assurance IT risk

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.

The Tool Project Template is simply a sample project that was developed for instructional purposes that can be used to create default project pages for a Tool project. After copying this template to your new project, all you have to do is follow the instructions in red, replace the sample text with text suited for your project, and then delete the sections in red. Doing so should make it clearer to both consumers of this project, as well as OWASP reviewers who are trying to determine if the project can be promoted to the next category. The information requested is also intended to help Project Leaders think about the roadmap and feature priorities, and give guidance to the reviews as a result of that effort.

Creating a new set of project pages from scratch can be a challenging task. By providing a sample layout, with instructional text and examples, the OWASP Tool Project Template makes it easier for Project Leaders to create effective security projects and hence helps promote security.

Contextual custom dictionary builder with character substitution and word variations for pen-testers

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 © 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:

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