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 "OWASP Cloud Security Mentor"

From OWASP
Jump to: navigation, search
m (Populating the wiki page with the project proposal)
m (Adding overview, description, project timeline and open source license)
Line 9: Line 9:
  
 
==OWASP Code Project Template==
 
==OWASP Code Project Template==
−
<span style="color:#ff0000">
+
With the rise of cloud computing, a lot of companies have moved their workload to the cloud. Cloud allows organizations of all sizes to manage their application lifecycle more effectively and efficiently. Because of its design, Cloud has its own set of unique security challenges. There is already an abundance of documentation and open source projects to raise awareness about cloud-specific security issues. Sometimes, consuming this information may feel like drinking from a firehose. This project aims to teach the cloud security fundamentals in a consolidated and actionable manner. The primary goal of the project is to empower cloud defenders with practical cloud security knowledge. This project provides hands-on cloud security tutorials that the audience can conveniently consume in their public cloud accounts to learn at their own pace. The target audience for this project are system administrators, software developers, and solutions architects.<span style="color:#ff0000">
−
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.
+
==Description==
−
</span>
+
The project would deliver a code repository which would describe various cloud hardening principles. The repository would also contain an application utility to demonstrate common cloud vulnerabilities and with the recommended fixes. At a high-level, the project would be divided into multiple Cloud resources such as Storage, Compute, etc. Inside these folders, there will be subfolders describing various vulnerabilities applicable to the cloud resource. Inside these subfolders, we will have one folder for each public cloud provider to demonstrate the vulnerability as well as the recommended security fix.  
−
 
 
−
The OWASP Code 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.
 
  
−
==Description==
+
The audience would follow these steps to learn about a cloud vulnerability:
 +
# Go to the directory for the vulnerability
 +
# Go through the content to learn about the vulnerability and hardening recommendations.
 +
# Choose a public cloud service provider from the directory.
 +
# Run the vulnerable cloud deployment template to deploy a vulnerable cloud resource
 +
# Use the utility to exploit the vulnerability.
 +
# Deploy the hardened cloud deployment template to fix the vulnerability.
 +
# Rerun the exploit code, this time it would fail.
 
<span style="color:#ff0000">
 
<span style="color:#ff0000">
−
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. 
 
−
</span>
 
  
−
The Code 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.
+
==Licensing==
 +
Apache License 2.0<span style="color:#ff0000">
 +
==Roadmap==
 +
2019 Q1:
 +
* Seek input on the project proposal from other members of the community
 +
* Come up with the design and architecture for the technological framework that would be used for authoring cloud security tutorials
  
−
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.
+
2019 Q2:
 +
* Choose a cloud service, a set of applicable vulnerabilities, and a public cloud service provider for the initial implementation.
 +
* Complete a PoC for the generic technological framework using a cloud vulnerability identified step #1.
  
−
Contextual custom dictionary builder with character substitution and word variations for pen-testers
+
2019 Q3:
 +
* Improve the framework engineering fundamentals (reliability, performance, logging, etc.) if required
 +
* Leverage the framework for authoring tutorials for all chosen vulnerabilities from step #1 of the 2019 Q2 plan
  
−
==Licensing==
+
2019 Q4:
 +
* Continue with the 2019 Q3 #2 objective
 +
* Extend the project to cover other cloud resources under the chosen public cloud provider
 
<span style="color:#ff0000">
 
<span style="color:#ff0000">
−
A project must be licensed under a community friendly or open source license.  For more information on OWASP recommended licenses, please see [https://www.owasp.org/index.php/OWASP_Licenses 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.
 
−
</span>
 
−
 
−
This program is free software: you can redistribute it and/or modify it under the terms of the [http://www.gnu.org/licenses/agpl-3.0.html 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==
 
−
<span style="color:#ff0000">
 
−
As of <strong>November, 2013, the highest priorities for the next 6 months</strong> are:
 
−
<strong>
 
−
* Complete the first draft of the Code Project Template
 
−
* Get other people to review the Code Project Template and provide feedback
 
−
* Incorporate feedback into changes in the Code Project Template
 
−
* Finalize the Code Project template and have it reviewed to be promoted from an Incubator Project to a Lab Project
 
−
</strong>
 
−
 
−
Subsequent Releases will add
 
−
<strong>
 
−
* Internationalization Support
 
−
* Additional Unit Tests
 
−
* Automated Regression tests
 
−
</strong>
 
  
 
==Getting Involved==
 
==Getting Involved==
−
<span style="color:#ff0000">
+
If you would like to contribute, then please reach out to the project leader.
−
Involvement in the development and promotion of <strong>Code Project Template</strong> 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;" |
 
| valign="top" style="padding-left:25px;width:200px;border-right: 1px dotted gray;padding-right:25px;" |

Revision as of 07:40, 29 January 2019

OWASP Project Header.jpg

Project About

PROJECT INFO
What does this OWASP project offer you? 		RELEASE(S) INFO
What releases are available for this project?
what is this project?
Name: N/A
Purpose: N/A
License: N/A
who is working on this project?
Project Leader(s): N/A
how can you learn more?
Project Pamphlet: Not Yet Created
Project Presentation:
Mailing list: N/A
Project Roadmap: Not Yet Created
Key Contacts
  • Contact the GPC to contribute to this project
  • Contact the GPC to review or sponsor this project
current release
pending
last reviewed release
pending


other releases


OWASP Code Project Template

With the rise of cloud computing, a lot of companies have moved their workload to the cloud. Cloud allows organizations of all sizes to manage their application lifecycle more effectively and efficiently. Because of its design, Cloud has its own set of unique security challenges. There is already an abundance of documentation and open source projects to raise awareness about cloud-specific security issues. Sometimes, consuming this information may feel like drinking from a firehose. This project aims to teach the cloud security fundamentals in a consolidated and actionable manner. The primary goal of the project is to empower cloud defenders with practical cloud security knowledge. This project provides hands-on cloud security tutorials that the audience can conveniently consume in their public cloud accounts to learn at their own pace. The target audience for this project are system administrators, software developers, and solutions architects.

Description

The project would deliver a code repository which would describe various cloud hardening principles. The repository would also contain an application utility to demonstrate common cloud vulnerabilities and with the recommended fixes. At a high-level, the project would be divided into multiple Cloud resources such as Storage, Compute, etc. Inside these folders, there will be subfolders describing various vulnerabilities applicable to the cloud resource. Inside these subfolders, we will have one folder for each public cloud provider to demonstrate the vulnerability as well as the recommended security fix.

The audience would follow these steps to learn about a cloud vulnerability:

  1. Go to the directory for the vulnerability
  2. Go through the content to learn about the vulnerability and hardening recommendations.
  3. Choose a public cloud service provider from the directory.
  4. Run the vulnerable cloud deployment template to deploy a vulnerable cloud resource
  5. Use the utility to exploit the vulnerability.
  6. Deploy the hardened cloud deployment template to fix the vulnerability.
  7. Rerun the exploit code, this time it would fail.

Licensing

Apache License 2.0

Roadmap

2019 Q1:

  • Seek input on the project proposal from other members of the community
  • Come up with the design and architecture for the technological framework that would be used for authoring cloud security tutorials

2019 Q2:

  • Choose a cloud service, a set of applicable vulnerabilities, and a public cloud service provider for the initial implementation.
  • Complete a PoC for the generic technological framework using a cloud vulnerability identified step #1.

2019 Q3:

  • Improve the framework engineering fundamentals (reliability, performance, logging, etc.) if required
  • Leverage the framework for authoring tutorials for all chosen vulnerabilities from step #1 of the 2019 Q2 plan

2019 Q4:

  • Continue with the 2019 Q3 #2 objective
  • Extend the project to cover other cloud resources under the chosen public cloud provider

Getting Involved

If you would like to contribute, then please reach out to the project leader.

Project Resources

Installation Package

Source Code

What's New (Revision History)

Documentation

Wiki Home Page

Issue Tracker

Slide Presentation

Video

Project Leader

Ashish Kurmi

Related Projects

Classifications

Project Type Files CODE.jpg
Incubator Project Owasp-breakers-small.png
Owasp-defenders-small.png
Affero General Public License 3.0

Retrieved from "https://wiki.owasp.org/index.php?title=OWASP_Cloud_Security_Mentor&oldid=246895"