Difference between revisions of "OWASP Security Busters"

Latest revision as of 15:08, 4 November 2019

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

PROJECT INFO
What does this OWASP project offer you?

RELEASE(S) INFO
What releases are available for this project?

what	is this project?
Name: Security Busters
Purpose: N/A
License: N/A
who	is working on this project?
Project Leader(s): Shruti Kulkarni @
how	can you learn more?
Project Pamphlet: Not Yet Created
Project Presentation:
Mailing list: N/A
Project Roadmap: Not Yet Created
Key Contacts
Contact Shruti Kulkarni @ to contribute to this project Contact Shruti Kulkarni @ to review or sponsor this project

current release
Not Yet Published
last reviewed release
Not Yet Reviewed

other releases

OWASP Documentation Project Template

The main deliverable of this project would be an assessment of the current privacy protection that is offered by popular web browsers for mobile devices (Android, iOS) and desktops. We will document amongst other things the following: a. browser details: name, version number, underlying OS

b. Protection against tracking mechanism, Tracking mechanism used (other than cookie)

c. Capability and usability in removing the tracking mechanism

d. Capability of the browser to show/list the data from the tracking mechanism

e. Presence of addons that list/delete the data

Description

This project would look at different browsers that are used by general population and understand the tracking mechanisms (other than cookies) employed by the browser. These tracking mechanisms are not visible like cookies and need to be explored by getting into developer tools on the browser This sort of tracking has an impact on privacy and to some extent on security. This project would also look at how these tracking mechanisms can be removed or at least how the contents of these tracking mechanisms can be deleted

Licensing

GNU General Public License

Roadmap

Q3, 2019

Start of the project
Identify team members
Design testbed (use of vms, use of phones)
Identify different browsers and their versions for testing

Q4, 2019

Implement testbed
Install browsers on VMS
Commence testing and document the results
Publicize the results on the wiki

The plan to start by replicating the experiments/methodology that is found here: Belloro, S., & Mylonas, A. (2018). I know what you did last summer: New persistent tracking mechanisms in the wild. IEEE Access, 6, 52779-52792. , and has been presented by Alexios to the London Chapter meeting in November 2018. Then, we plan to expand the work by including other tracking technologies and third-party software (i.e. addons) that can be used to enhance the protection that is offered by current browsers.

Getting Involved

Involvement in the development and promotion of Security busters 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: 1. Share the name of the browser on which you have noticed privacy issues 2. Let us know if you have identified any databases that store user information

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)

Project Leader

Shruti Kulkarni

Stefano Belloro

Alexios Mylonas

Related Projects

This is where you can link to other OWASP Projects that are similar to yours.

Classifications

@@ Line 13: / Line 13: @@
     |leader_name1=Shruti Kulkarni
     |[email protected]
+   |leader__name2=Stefano Belloro
+   |[email protected]
+   |leader__name3=Alexios Mylonas
+   |[email protected]
 }}
 ==OWASP Documentation Project Template==
 <span style="color:#ffffff">
 	The main deliverable of this project would be an assessment of the current privacy protection that is offered by popular web browsers for mobile devices (Android, iOS) and desktops. We will document amongst other things the following:
 a.	browser details: name, version number, underlying OS
@@ Line 30: / Line 35: @@
 ==Description==
-<span style="color:#ff0000">
+<span style="color:#ffffff">
-	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>
+This project would look at different browsers that are used by general population and understand the tracking mechanisms (other than cookies) employed by the browser. These tracking mechanisms are not visible like cookies and need to be explored by getting into developer tools on the browser
+This sort of tracking has an impact on privacy and to some extent on security.
+This project would also look at how these tracking mechanisms can be removed or at least how the contents of these tracking mechanisms can be deleted
+==Licensing==
+<span style="color:#ffffff">
-The Documentation Project Template is simply a sample project that was developed for instructional purposes that can be used to create default project pages for a Documentation 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 Documentation Project Template makes it easier for Project Leaders to create effective security projects and hence helps promote security.
+GNU General Public License
-Contextual custom dictionary builder with character substitution and word variations for pen-testers
+==Roadmap==
+<span style="color:#ffffff">
-==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.  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)}.
+Q3, 2019
+* Start of the project
+* Identify team members
+* Design testbed (use of vms, use of phones)
+* Identify different browsers and their versions for testing
+Q4, 2019
-==Roadmap==
+* Implement testbed
-<span style="color:#ff0000">
+* Install browsers on VMS
-As of <strong>November, 2013, the highest priorities for the next 6 months</strong> are:
+* Commence testing and document the results
-<strong>
+* Publicize the results on the wiki
-* Complete the first draft of the Documentation Project Template
-* Get other people to review the Documentation Project Template and provide feedback
-* Incorporate feedback into changes in the Documentation Project Template
-* Finalize the Documentation Project template and have it reviewed to be promoted from an Incubator Project to a Lab Project
-</strong>
-Subsequent Releases will add
+The plan to start by replicating the experiments/methodology that is found here:
-<strong>
+Belloro, S., & Mylonas, A. (2018). I know what you did last summer: New persistent tracking mechanisms in the wild. IEEE Access, 6, 52779-52792.
-* Internationalization Support
+, and has been presented by Alexios to the London Chapter meeting in November 2018. Then, we plan to expand the work by including other tracking technologies and third-party software (i.e. addons) that can be used to enhance the protection that is offered by current browsers.
-* Additional Unit Tests
-* Automated Regression tests
-</strong>
 ==Getting Involved==
-<span style="color:#ff0000">
+<span style="color:#ffffff">
-Involvement in the development and promotion of <strong>Documentation Project Template</strong> is actively encouraged!
+Involvement in the development and promotion of <strong>Security busters</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:
+. Share the name of the browser on which you have noticed privacy issues
+. Let us know if you have identified any databases that store user information
 | valign="top"  style="padding-left:25px;width:200px;border-right: 1px dotted gray;padding-right:25px;" |
@@ Line 94: / Line 102: @@
 == Project Leader ==
-<span style="color:#ff0000">
+<span style="color:#ffffff">
-	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.
+[mailto://shruti.kulkarni@owasp.org Shruti Kulkarni]
-</span>
+[mailto://stefano.[email protected] Stefano Belloro]
-[mailto://shruti.kulkarni@owasp.org Shruti Kulkarni]
+[mailto://alexios.mylonas@owasp.org Alexios Mylonas]
 == Related Projects ==

Difference between revisions of "OWASP Security Busters"

Latest revision as of 15:08, 4 November 2019

Project About

OWASP Documentation Project Template

Description

Licensing

Roadmap

Getting Involved

Project Resources

Project Leader

Related Projects

Classifications

Navigation menu

Personal tools

Namespaces

Variants

Views

More

Search

Navigation

Reference

Tools