Difference between revisions of "OWASP Visual Crime Scene and Security Incident Education Project"

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 first contributors to the project were:

• Adrian Winckles

Project Process - following UIDM development process.

Pre-project activities, (UIDM stage 1) October – November 2014 •​Initial user engagement with digital forensics •​Confirm data protection procedures Outputs: Data protection policy, ethical submission document.

Work package one: Project set up and initial design (UIDM stage 1) December 2014 – February 2015 •​Establish website and blogging area •​Identify digital forensic evidence and security incident requirements •​Develop pedagogic and evaluation criteria •​Outline database and communication design •​Initial scenario and visitor centre Outputs: Workshop 1 event and report 'Ethics and IPR', project blog and community engagement and communication site, Introduction and dissemination of demonstration application.

Work Package two: Prototype development (UIDM stage 2) March 2015 – May 2015 •​Basic infrastructure implementation •​Implement reviewing and annotation to web application •​Develop induction and user training materials •​Contact and enrol collaborating institutions •​Enlist evaluation team and agree remit Outputs: Trial scenarios, prospective user support pack,

Work Package three: System prototyping and initial feedback, UIDM stages 2 /3, June 2015 – August 2015 •​Detailed Design and implementation of controls and assets for configurable scenarios. •​Evaluate basic infrastructure with respect to usability and learning •​Additional scenario types (digital forensic evidence extraction, live data acquisition, ) •​Students and staff users to test induction and usability Outputs: tutor support pack, Initial evaluation report, Workshop 2 event and report : Applications of Virtual Digital Evidence Forensic Scenarios

Work Package four Technical development (UIDM stage 3) September 2015 – November 2015 •​Incorporate feedback from users and external reviewers •​Development of richer scenarios with bots and pre-determined 'events'. •​Finalise user interface, control and reporting resources. •​Incorporate with forensics teaching Outputs: pedagogic evaluation report, Implementation technical report: Workshop 3 – Cyber Security Incident Workshop

Work Package five: Dissemination and Evaluation – UIDM stage 4, December 2015 - February 2016 •​Evaluation and feedback from 5 selected institutions •​Incorporation of feedback into project Outputs: Final project report, Open access to service for users and collaborators Student and tutor induction and usage packs Case study on embedding within digital forensic and cyber security teaching at partner institutions Workshop 4 event and report: 'student and tutor experiences' Continuing development and usage plan, technical and pedagogic collaboration packs Cumulative evaluation report with external evaluation feedback Dissemination conference papers

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

Project deliverables will include

Virtual World Design and Requirements Documentation Use Cases User guide Usability Documentation Test Plan

Unity Crime Scene Design templates Unity Security Incident Design templates Unity Digital Forensic Evidence Objects. Unity Security Incident Evidence Objects

Front End Web Application Source Code

Digital Evidence Forensic Images and Virtual machine templates Security Incident Virtual Machines