OWASP - User contributions [en]

OWASP - Cyber Security in the Boardroom

2017-05-21T12:00:51Z

Dinis.cruz:

Projects/Owasp Cyber Security at the Board Level Project About Page

2017-05-21T12:00:35Z

Dinis.cruz: Created page with "{{Template:Project About | project_name =Cyber Security at the Board Level Project | project_description = ..... .... .... | project_license =... | leader_name1 = Sherif Mans..."

{{Template:Project About
| project_name =Cyber Security at the Board Level Project
| project_description = .....
....
....
| project_license =...
| leader_name1 = Sherif Mansour
| leader_email1 = sherif.mansour@owasp.org
| leader_username1 =
| mailing_list_name =
}}

2016-10-29T15:59:01Z

Dinis.cruz:

=Owasp-DevSecCon Summit, England, April 2017=

OWASP is joining forces with DevSecCon to create a Summit focused on the collaboration between
Developers and Application Security.

This is not a conference with uni-directional presentations, this is a working summit with working sessions on areas like:
* Secure Coding,
* Security Testing/TDD
* DevOps,
* Threat Modeling
* Mobile Security
* IoT
* Risk & Governance
* Privacy & CTO/CISO requirements
* Secure Design
* Bug-bounties
* Browser Security
* AI for Attack & Defence
* DDoS
* Cyber Warfare
* AppSec Standards;
... and of course, working sessions on popular OWASP projects (lead by its leaders) such as:
* Zap,
* Top 10
* Dependency Checker
* OwaspSAMM
* OWASP Guides (Testing, ASVS, Core Review)
* AppSensor and dozens more.

Using the same model as the past two OWASP Summits in Portugal, this 5 day event will be a 16h day high energy experience, where the attendees are expected to work and collaborate really hard. Every working session will be thoroughly prepared and focused on actionable outcomes.

If you care about Application Security and want to collaborate with the key players in this industry, this is the event to be.

The Summit will occur in England, April 2017, with an entry ticket of $2000 (covering travel + hotel + accommodation + event fee). OWASP is funding a large number of its leaders and other deserving individuals to attend, so if you feel you can't afford this fee, or your company is not in a position to sponsor you, please contact the event organisers.

If you want to be involved, contact seba@owasp.org or dinis.cruz@owasp.org

== related sites ==

* GitHub: https://github.com/OWASP/owasp-devseccon-summit
* Slack: https://owasp.slack.com/archives/owasp-dsc-summit
* Tasks and questions: https://github.com/OWASP/owasp-devseccon-summit/issues

Owasp-DevSecCon-Summit

2016-10-24T19:59:07Z

Dinis.cruz:

Security Champions

2016-10-20T21:46:32Z

Dinis.cruz:

Security Champions are a key element of an AppSec team, since they create an cross-functional team focused on Application Security

'''What is an Security Champion?'''

* Security Champions are active members of a team that may help to make decisions about when to engage the Security Team
* Act as the "voice" of security for the given product or team
* Assist in the triage of security bugs for their team or area

'''What do they do?'''

* Actively participate in the AppSec JIRA and WIKI
* Collaborate with other security champions
** Review impact of 'breaking changes' made in other projects
* Attend weekly meetings
* Are the single point of contact for their assigned team
* Ensure that security is not a blocker on active development or reviews
* Assist in making security decisions for their team
** Low-Moderate security impact
*** Empowered to make decisions
*** Document decisions made in bugs or wiki
** High-Critical security impact
** Work with AppSec team on mitigations strategies
* Help with QA and Testing
** Write Tests (from Unit Tests to Integration tests)
** Help with development of CI (Continuous Integration) environments

Security Champions

2016-10-20T21:43:28Z

Dinis.cruz: Dinis.cruz moved page OWASP Security Champions Project to Security Champions: Better to start with a page (before making it a project)

=Main=

<div style="width:100%;height:160px;border:0,margin:0;overflow: hidden;">[[File:OWASP_Project_Header.jpg|link=]]</div>


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


<span style="color:#ff0000">
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.
</span>

==The OWASP Security Principles==


<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, 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, and project leaders should ensure that the description is meaningful.
</span>

Inevitably applications are designed with security principles architects knew about, security folks included. However, as this project demonstrates there are far more than just a 'few' principles, most of which never make it into the design.

For example, security design happens with perhaps a handful of principles:

* Least Privilege
* Perimeter Security
* Defence in Depth

However, we regularly see designs without '''separation of privilege'''!

Think about that, most web applications today have all their eggs in a single basket. The business logic, the identities, passwords, products, policy enforcement, security rules are all found in the same application database that makes up the typical website! It is little wonder then, that attacks on the database have been so completely devastating, since there is no separation of privilege!

The aim of this project, is to identify and describe a minimum functional set of principles that must be present in a secure design.

==Description==


<span style="color:#ff0000">
This section must include a shorter description of what the project is, why the project was started, and what security issue is being helped by the project deliverable. This description will be used to promote the project so make sure the description represents your project in the best way possible.
</span>

'''Although this is a sample template, the project is real! [http://owasp.github.io/Security-Principles Please contribute to this project.]
'''

Over the course of my career, I have come across and collected a number of security ''aphorisms.'' These aphorisms constitute the fundamental principles of information security.

None of the ideas or truths are mine, and unfortunately, I did not collect the citations. Initially, I would like to identify the correct citations for each aphorism.

Additionally, many are re-statements of the same idea; thus, the 'collection of ideas' defines a fundamental principle. As such, I would also like to reverse engineer the principles from the aphorisms where appropriate, as well.

==Licensing==


<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.
</span>

'''The OWASP Security Principles are free to use. In fact it is encouraged!!!
'' Additionally, I also encourage you to contribute back to the project. I have no monopoly on this knowledge; however, we all have pieces of this knowledge from our experience. Let's begin by putting our individual pieces together to make something great. Great things happen when people work together.

The OWASP Security Principles are licensed under the http://creativecommons.org/licenses/by-sa/3.0/ Creative Commons Attribution-ShareAlike 3.0 license], so you can copy, distribute and transmit the work, and you can adapt it, and use it commercially, but all provided that you attribute the work and if you alter, transform, or build upon this work, you may distribute the resulting work only under the same or similar license to this one.


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

== What is OWASP Security Principles Project? ==


<span style="color:#ff0000">
Here you should add a short description of what your project actually does. What is the primary goal of your project, and why is it important?
</span>

The end goal is to identify, cite, and document the fundamental principles of information security. Once this is well organised, I think it would be great to publish this through the [http://scriptogr.am/dennis-groves/post/owasp-press OWASP Press]. Of course, it will always remain freely available, and any money collected will go directly into the project to absorb costs with any remaining funds going to the OWASP Foundation.

This document should serve as a guide to technical architects and designers outlining the fundamental principles of security.

== Presentation ==


<span style="color:#ff0000">
This is where you can link to slide presentations related to your project.
</span>

AppSec USA 2013 [https://github.com/OWASP/Security-Principles/tree/master/Presentations/AppSec%20NYC%202013]

== Project Leader ==


<span style="color:#ff0000">
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.
</span>

* [https://www.owasp.org/index.php/User:Dennis_Groves Dennis Groves]

== Related Projects ==


<span style="color:#ff0000">
This is where you can link to other OWASP Projects that are similar to yours.
</span>

* [[OWASP_CISO_Survey]]

== Openhub ==

* [https://www.openhub.net/orgs/OWASP OWASP Project Openhub]


| valign="top" style="padding-left:25px;width:200px;" |

== Quick Download ==


<span style="color:#ff0000">
This is where you can link to your repository.
</span>

The home of the OWASP Security Principles is on [https://github.com/OWASP/Security-Principles GitHub.] You are encourged to fork, edit and push your changes back to the project through git or edit the project directly on github.

However, if you like you may also download the master repository from the following links:
* [https://github.com/OWASP/Security-Principles/zipball/master .zip file.]
* [https://github.com/OWASP/Security-Principles/tarball/master .tgz file.]

== News and Events ==


<span style="color:#ff0000">
This is where you can link to press your project has been a part of. Appropriate press includes: Project Leader interviews, articles written about your project, and videos about your project.
</span>

* [20 Nov 2013] News 2
* [30 Sep 2013] News 1

== In Print ==


<span style="color:#ff0000">
This is where you place links to where your project product can be downloaded or purchased, in the case of a book.
</span>

This project can be purchased as a print on demand book from Lulu.com

==Classifications==


<span style="color:#ff0000">
Here is where you can let the community know what project stage your project is currently in, whether the project is a builder, breaker, or defender project, and what type of project you are running.
</span>

{| width="200" cellpadding="2"
|-
| align="center" valign="top" width="50%" rowspan="2"| [[File:New projects.png|100px|link=https://www.owasp.org/index.php/OWASP_Project_Stages#tab=Incubator_Projects]]
| align="center" valign="top" width="50%"| [[File:Owasp-builders-small.png|link=]]
|-
| align="center" valign="top" width="50%"| [[File:Owasp-defenders-small.png|link=]]
|-
| colspan="2" align="center" | [[File:Cc-button-y-sa-small.png|link=http://creativecommons.org/licenses/by-sa/3.0/]]
|-
| colspan="2" align="center" | [[File:Project_Type_Files_DOC.jpg|link=]]
|}

|}

=FAQs=


<span style="color:#ff0000">
Many projects have "Frequently Asked Questions" documents or pages. However, the point of such a document is not the questions. ''The point of a document like this are the '''answers'''''. The document contains the answers that people would otherwise find themselves giving over and over again. The idea is that rather than laboriously compose and post the same answers repeatedly, people can refer to this page with pre-prepared answers. Use this space to communicate your projects 'Frequent Answers.'
</span>

==How can I participate in your project?==
All you have to do is make the Project Leader's aware of your available time to contribute to the project. It is also important to let the Leader's know how you would like to contribute and pitch in to help the project meet it's goals and milestones. There are many different ways you can contribute to an OWASP Project, but communication with the leads is key.

==If I am not a programmer can I participate in your project?==
Yes, you can certainly participate in the project if you are not a programmer or technical. The project needs different skills and expertise and different times during its development. Currently, we are looking for researchers, writers, graphic designers, and a project administrator.

= Acknowledgements =

==Contributors==


<span style="color:#ff0000">
The success of OWASP is due to a community of enthusiasts and contributors that work to make our projects great. This is also true for the success of your project.
Be sure to give credit where credit is due, no matter how small! This should be a brief list of the most amazing people involved in your project.
Be sure to provide a link to a complete list of all the amazing people in your project's community as well.
</span>

The OWASP Security Principles project is developed by a worldwide team of volunteers. A live update of project [https://github.com/OWASP/Security-Principles/graphs/contributors contributors is found here].

The first contributors to the project were:

* [https://www.owasp.org/index.php/User:Dennis_Groves Dennis Groves]
* [https://github.com/sublimino Andrew Martin]
* [https://github.com/Lambdanaut Josh Thomas]
* '''YOUR NAME BELONGS HERE'''

= Road Map and Getting Involved =


<span style="color:#ff0000">
A project roadmap is the envisioned plan for the project. The purpose of the roadmap is to help others understand where the project is going. It gives the community a chance to understand the context and the vision for the goal of the project. Additionally, if a project becomes inactive, or if the project is abandoned, a roadmap can help ensure a project can be adopted and continued under new leadership.
</span>

<span style="color:#ff0000">
Roadmaps vary in detail from a broad outline to a fully detailed project charter. Generally speaking, projects with detailed roadmaps have tended to develop into successful projects. Some details that leaders may consider placing in the roadmap include: envisioned milestones, planned feature enhancements, essential conditions, project assumptions, development timelines, etc. You are required to have at least 4 milestones for every year the project is active.
</span>

As of October 2013, the priorities are:
* Finish the referencing for each principle.
* Update the Project Template.
* Use the OWASP Press to develop a book.
* Finish and publish the book on Lulu.

Involvement in the development and promotion of the OWASP Security Principles Project is actively encouraged!
You do not have to be a security expert in order to contribute.
Some of the ways you can help:
* Helping find references to some of the principles.
* Project administration support.
* Wiki editing support.
* Writing support for the book.

=Project About=


<span style="color:#ff0000">
This page is where you need to place your legacy project template page if your project was created before October 2013. To edit this page you will need to edit your project information template. You can typically find this page by following this address and substituting your project name where it says "OWASP_Example_Project". When in doubt, ask the OWASP Projects Manager.
Example template page: https://www.owasp.org/index.php/Projects/OWASP_Example_Project
</span>

{{:Projects/OWASP_Example_Project_About_Page}}


__NOTOC__ <headertabs />

[[Category:OWASP Project]] [[Category:OWASP_Builders]] [[Category:OWASP_Defenders]] [[Category:OWASP_Document]]

OWASP Security Champions Project

2016-10-20T21:43:28Z

Dinis.cruz: Dinis.cruz moved page OWASP Security Champions Project to Security Champions: Better to start with a page (before making it a project)

#REDIRECT [[Security Champions]]

Secure SDLC Cheat Sheet

2016-10-08T16:35:23Z

Dinis.cruz: added link to project

= DRAFT CHEAT SHEET - WORK IN PROGRESS =

= Background =

This cheat sheet provides a quick reference on the most important initiatives to build security into multiple parts of software development processes. This cheat sheet is based on the OWASP Software Assurance Maturity Model ([[OWASP_SAMM_Project|SAMM]]) which can be integrated into any existing SDLC.

SAMM is based around a set of 12 security practices, which are grouped into 4 business functions. Every security practice contains a set of activities, structured into 3 maturity levels. The activities on a lower maturity level are typically easier to execute and require less formalization than the ones on a higher maturity level.

The structure and setup of the '''SAMM maturity model''' are made to support:
# The '''assessment''' of the current software assurance posture
# The definition of the '''strategy''' (i.e. the target) that the organization should take
# The formulation of an implementation '''roadmap''' of how to get there and
# Prescriptive advice on how to '''implement''' particular activities.

In that sense, the value of SAMM lies in providing a means to know where your organization is on its journey towards software assurance, and to understand what is recommended to move to a next level of maturity. Note that SAMM does not insist that all organizations achieve maturity level 3 in every category. Indeed, you determine the target maturity level for each Security Practice that is the best fit for your organization and its needs. SAMM provides a number of templates for typical organizations to this end, but you can adapt these as you see fit.

= How to Apply =

A typical approach of using SAMM in an organization is as follows:

{| class="wikitable"
! scope="col" | Step
! scope="col" | Purpose
! scope="col" | Activities
! scope="col" | Resources
! scope="col" | Best Practices
|-
| Step 1 - '''Assess'''
| Ensure a proper start of the project
| '''Define the scope'''
Set the target of the effort (The entire enterprise, a particular application or project or team etc.)

'''Identify Stakeholders'''

Ensure that important stakeholders supposed to support and execute the project are identified and well aligned

'''Spread the word'''

Inform people about the initiative and provide them with information to understand what you will be doing
| '''Consider involving at least:'''
* Executive Sponsor
* Security Team
* Developers
* Architects
* Business Owners
* QA Testers
* Managers

The OpenSAMM main site: http://www.opensamm.org/

The model in .pdf: http://www.opensamm.org/
| Pre-screen software development maturity to have realistic expectations The smaller the scope, the easier the exercise
|-
| Step 2 - '''Assess'''
| Identify and understand the maturity of your chosen scope in each of the 12 software security practices
| '''Evaluate current practices'''
Organize interviews with relevant stakeholders to understand the current state of practice within your organization. You could evaluate this yourself if you understand the organization sufficiently well. SAMM provides lightweight and detailed assessments (where the latter is an evidence-based evaluation) – use the detailed one only if you want to have absolute certainty about the scores.

'''Determine maturity level'''

Based on the outcome of the previous activity, determine for each security practice the maturity level according to the SAMM maturity scoring system. In a nutshell, when all activities below and within a maturity level have
been implemented, this level can be used for the overall score. When extra higher-level activities have been implemented without reaching a full next level, add a “+” to the rating.
| The OpenSAMM toolbox http://LINK

Online Self Assessment Tool

https://ssa.asteriskinfosec.com.au

Both of these resources provide you with:
* Assessment questions
* Maturity level calculation
| Ensure consistent assessment for different stakeholders and teams by using the same questions and interviewer
Consider using different formats to gather data (e.g., workshops vs. interviews.
Ensure interviewees understand the particularities of activities.
Understand which activities are not applicable to the organization and take this into account in the overall scoring.
Anticipate/document whether you plan to award partial credit, or just document various judgement calls.
Repeat questions to several people to improve the assessment quality Consider making interviews anonymous to ensure honesty Don’t take questions too literally)
|-
| Step 3 - '''Set the target'''
| Develop a target score that you can use as a measuring stick to guide you to act on the “most important” activities for your situation
| '''Define the target'''

Set or update the target by identifying which activities your organization should implement ideally. Typically this will include more lower-level than higher-level activities. Predefined roadmap templates can be used as a source for inspiration. Ensure that the total set of selected activities makes sense and take into account dependencies between activities.

'''Estimate overall impact'''

Estimate the impact of the chosen target on the organization. Try to express in budgetary arguments.
| See the How-To-Guide for predefined templates Software Assurance Maturity Model (SAMM) Roadmap Chart Worksheet (part of the OpenSAMM Benchmarking as a comparative source)
| Take into account the organisation’s risk profile Respect dependencies between activities As a rough measure, the overall impact of a software assurance effort is estimated at 5 to 10% of the total development cost.
|-
| Step 4 - '''Define the plan'''
| Develop or update your plan to take your organization to the next level
| '''Determine change schedule'''
Choose a realistic change strategy in terms of number and duration of phases. A typical roadmap consists of 4-6 phases of 3 to 12 months.

'''Develop / Update the roadmap plan'''

Distribute the implementation of additional activities over the different roadmap phases, taking into account the effort required to implement them.. Try to balance the implementation effort over the different periods, and take dependencies between activities into account
| Software Assurance Maturity Model : A guide to building security into software development page 33:
http://www.opensamm.org/

Project Plan
http://www.opensamm.org/downloads/
| Identify quick wins and plan them early on Start with awareness/training Adapt to coming release cycles / key projects
|-
| Step 5 - '''Implement'''
| Work the plan
| '''Implement activities'''
Implement all activities that are part of this period. Consider their impact on processes, people, knowledge and tools. The SAMM model contains prescriptive advice on how to do this. OWASP projects may help to facilitate
this.
| Useful OWASP resources per activity are described at https://www.owasp.org
| Treat legacy software separately. Do not mandate migration unless really important. Avoid operational bottle-necks (in particular for the security team)
|-
| Step 6 - '''Roll out'''
| Ensure that improvements are available and effectively used within the organization
| '''Evangelize Improvements'''
Make the steps and improvements visible for everyone involved by organizing training and communicating.

'''Measure effectiveness'''

Measure the adoption and effectiveness of implemented improvements by analyzing usage and impact.
|
| Categorize applications according to their impact on the organization. Focus on high-impact applications. Use team champions to spread new activities throughout the organization
|}

As part of a quick start effort, the first four phases (preparation, assess, setting the target and defining the plan) can be executed by a single person in a limited amount of time (1 to 2 days). Making sure that this is supported in the organization, as well as the implementation and roll-out phases typically require much more time to execute.

= Final Notes =
The best way to grasp SAMM is to start using it. This document has presented a number of concrete steps and supportive material to execute these. Now it’s your turn. We warmly invite you to spend a day or two on following the first steps, and you will quickly understand and appreciate the added value of the model. Enjoy! Suggestions for improvements are very welcome. And if you’re interested, consider to join the mailinglist or become part of the OpenSAMM community

----

{{Cheatsheet_Navigation}}

[[Category:Cheatsheets]] [[Category:OWASP_Builders]]

2014-04-14T13:34:23Z

Dinis.cruz:

This task force is focused on cleaning up the OWASP Projects namely on:

"...send last warning and clean up of incubator projects that have not been updated in more than a year, especially without a first release. we give a chance to react otherwise they get set to inactive projects and the wiki starts to clear up..."

==Execution Power==

This task force exists on the assumption that it has a mandate from the OWASP leaders to act on behalf of the OWASP community on what is best for OWASP Projects.

If somebody (namely an OWASP Leader or Board member) disagree with any of the decisions made, he/she has two options:

a) join this Task Force
b) create another equivalent 'OWASP Projects group' and do a better job there

==Current Members==

* Johanna Curiel
* Samantha Groves
* Chuck
* Dinis Cruz

==OWASP Projects Task Force (Concept)==

This is a new type of OWAPS initiative, focused on 'getting things done', the concept is still evolving but here are the current (in draft) guiding principles:

# this 'task force is an invitation-only group' (to join the task force, requests should be made directly with existing task force members)
# all existing members have VETO power, and it is assumed that all decisions are backed up with all existing members
# only existing members can send the invitations
# there is a 1 month minimum activity required (or the member is temporarily out).
# invitations are automatically approved (since all members of the task force are admins of the group)
# there an one special member who has veto power the responsibility to enforce the 'one month contribution MIA scenario' (i.e. to kick out the 'non contributing members')

Task Force/OWASP Projects

2014-04-14T13:31:40Z

Dinis.cruz: /* OWASP Projects Task Force (Concept) */

Task Force/OWASP Projects

2014-04-14T13:31:18Z

Dinis.cruz:

Task Force/OWASP Projects

2014-04-14T13:25:15Z

Dinis.cruz: Created page with "Hello Johanna :)"

Hello Johanna :)

O2 Platform/Community

2013-11-06T15:59:58Z

Dinis.cruz: /* News */

<noinclude>[[O2|back to O2 Platform Home Page]]</noinclude>
==O2-Platform.com website (external to owasp)==

For more details on the O2 Platform see http://o2platform.wordpress.com website which currently being used to host the help files and documentation pages.

=== Mailing list===
The best place to keep updated with the lastest news and developers it to subscribe to the [https://groups.google.com/a/owasp.org/forum/#!forum/o2-platform OWASP O2 Platform Mailing list]

== News ==
'''Latest News:'''
* 2013/Nov/8 : Webinar "Using the O2 Platform to Automate Application Security Knowledge and Workflows"
* 2013/Jul/20: Released version 5.3 of the [https://o2platform.googlecode.com/files/O2%20Platform%20-%20Main%20O2%20Gui%20v5.3.exe O2 Platform main GUI]
* 2013/Feb/8 : Released version 5.1 of the [http://o2platform.googlecode.com/files/O2%20Platform%20-%20Main%20O2%20Gui%20v5.1.exe O2 Platform main GUI]
* 2013/Feb/8 : Helped [[UK]] Chapters to visualize its locations: [http://blog.diniscruz.com/2013/02/o2-script-to-create-google-static-map.html O2 Script to create Google Static map with OWASP UK Chapter locations]

O2 Platform/Community

2013-11-06T15:59:08Z

Dinis.cruz: /* O2-Platform.com website (external to owasp) */

<noinclude>[[O2|back to O2 Platform Home Page]]</noinclude>
==O2-Platform.com website (external to owasp)==

For more details on the O2 Platform see http://o2platform.wordpress.com website which currently being used to host the help files and documentation pages.

=== Mailing list===
The best place to keep updated with the lastest news and developers it to subscribe to the [https://groups.google.com/a/owasp.org/forum/#!forum/o2-platform OWASP O2 Platform Mailing list]

== News ==
'''Latest News:'''
* 2013/Jul/20: Released version 5.3 of the [https://o2platform.googlecode.com/files/O2%20Platform%20-%20Main%20O2%20Gui%20v5.3.exe O2 Platform main GUI]
* 2013/Feb/8 : Released version 5.1 of the [http://o2platform.googlecode.com/files/O2%20Platform%20-%20Main%20O2%20Gui%20v5.1.exe O2 Platform main GUI]
* 2013/Feb/8 : Helped [[UK]] Chapters to visualize its locations: [http://blog.diniscruz.com/2013/02/o2-script-to-create-google-static-map.html O2 Script to create Google Static map with OWASP UK Chapter locations]

OWASP O2 Platform

2013-11-06T15:57:31Z

Dinis.cruz:

= Main =
{{:O2_Platform/Main}}

= Downloads =
{{:O2_Platform/Download}}



= Community =
{{:O2_Platform/Community}}

= Project About =
{{:Projects/OWASP O2 Platform Project | Project About}}

<categorytree mode=pages>Manual</categorytree>

<headertabs />

[[Category:OWASP_O2_Platform|O2 Platform]]

O2 Platform/Screenshots

2013-11-06T14:17:30Z

Dinis.cruz: Created page with "This page has some screenshots"

This page has some screenshots

O2 Platform/Download

2013-11-06T14:16:51Z

Dinis.cruz:

'''Latest Release: April 2013 - v5.3''': [https://o2platform.googlecode.com/files/O2%20Platform%20-%20Main%20O2%20Gui%20v5.3.exe O2 Platform - Main O2 Gui] - this is a '''Windows Stand-Alone exe''' which will create a number of folders on first load (dependencies and temp files)

[[Image:O2Download_Button_6_22_2010_7_07_03_PM_tmp9E0.jpg| link=https://o2platform.googlecode.com/files/O2%20Platform%20-%20Main%20O2%20Gui%20v5.3.exe]]

'''Requirements:'': Windows and .NET Framework 4.0

'''Source code''': The source code for the O2 Platform is available for download at GitHub:

'''Git Hub repositories'''
* FluentSharp: https://github.com/o2platform/O2.FluentSharp
* O2 Platform Scripts: https://github.com/o2platform/O2.Platform.Scripts
* O2 Platform Projects: https://github.com/o2platform/O2.Platform.Projects
* Misc and Legacy projects: https://github.com/o2platform/O2.Platform.Projects.Misc_and_Legacy

...