OWASP Visual Crime Scene and Security Incident Education Project

• Main
• FAQs
• Acknowledgements
• Road Map and Getting Involved
• Minimum Viable Product
• Project About

Introduction The OWASP Virtual Crime Scene and Security Incident Education ProjecT will create an accessible, configurable, incident scene simulation for digital forensic and cyber security incident training within an e-learning framework. Description The OWASP Virtual Crime Scene and Security Incident Education Project will develop and evaluate pedagogic practice, catering for the needs of a diverse student base drawn from HEI, cyber security, forensic and crime enforcement professionals whilst providing a unrivaled gameification experience. Scenarios, interactive objects and student transcripts will be accessed via a web interface to allow tutors to configure crime/incident scenes and provide feedback. The project will be hosted on a cloud computing platform where participants can make contributions, share applications, use and evaluate resources; allowing wide community engagement with minimal investment in infrastructure. Licensing Apache 2.0

Project Resources Mailing List virtual_world_design_and_requirements_documentation@lists.owasp.org Project Leader Adrian Winckles Related Projects Classifications News and Events 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.' 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. Volunteers 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. The OWASP Security Principles project is developed by a worldwide team of volunteers. A live update of project contributors is found here. The first contributors to the project were: Colin Watson who created the OWASP Cornucopia project that the template was derived from Chuck Cooper who edited the template to convert it from a documentation project to a Code Project Template YOUR NAME BELONGS HERE AND YOU SHOULD REMOVE THE PRIOR 3 NAMES 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 as well as areas that volunteers may contribute. 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. 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. Roadmap As of November, 2013, the highest priorities for the next 6 months are: 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 Subsequent Releases will add Internationalization Support Additional Unit Tests Automated Regression tests Getting Involved Involvement in the development and promotion of Code 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: Coding We could implement some of the later items on the roadmap sooner if someone wanted to help out with unit or automated regression tests Localization Are you fluent in another language? Can you help translate the text strings in the Code Project Template into that language? Testing Do you have a flair for finding bugs in software? We want to product a high quality product, so any help with Quality Assurance would be greatly appreciated. Let us know if you can offer your help. Feedback Please use the Code Project Template project mailing list for feedback about: What do like? What don't you like? What features would you like to see prioritized on the roadmap? This page is where you should indicate what is the minimum set of functionality that is required to make this a useful product that addresses your core security concern. Defining this information helps the project leader to think about what is the critical functionality that a user needs for this project to be useful, thereby helping determine what the priorities should be on the roadmap. And it also helps reviewers who are evaluating the project to determine if the functionality sufficiently provides the critical functionality to determine if the project should be promoted to the next project category. The Code Project Template must specify the minimum set of tabs a project should have, provide some an example layout on each tab, provide instructional text on how a project leader should modify the tab, and give some example text that illustrates how to create an actual project. It would also be ideal if the sample text was translated into different languages. 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 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

Navigation menu

Personal tools

• Log in
• Request account

Namespaces

• Page
• Discussion

Variants

Views

• Read
• View source
• View history

More

Search

Navigation

• Home
• About OWASP
• Acknowledgements
• Advertising
• Books
• Brand Resources
• Careers
• Chapters
• Downloads
• Events
• Funding
• Governance
• Initiatives
• Mailing Lists
• Merchandise
• Presentations
• Press
• Projects
• Supporting Partners
• Video

Reference

• Activities
• Attacks
• Code Snippets
• Controls
• Glossary
• How To...
• Java Project
• .NET Project
• Principles
• Technologies
• Threat Agents
• Vulnerabilities

Tools

• What links here
• Related changes
• Special pages
• Printable version
• Permanent link
• Page information

• Content is available under Creative Commons Attribution-ShareAlike unless otherwise noted.

• Privacy policy
• About OWASP
• Disclaimers

• Open Web Application Security Project, OWASP, Global AppSec, AppSec Days, AppSec California, SnowFROC, LASCON, and the OWASP logo are trademarks of the OWASP Foundation.