OWASP Security Busters

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)