zenon/bachelorarbeit
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

Add reference for third-party cookies

Browse Source
This commit is contained in:
Tobias Eidelpes 2020-08-10 23:31:52 +02:00
parent 5c7c0a9a7a
commit ef891a1fe1
2 changed files with 36 additions and 13 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

28
methods.tex
View File

@ -248,18 +248,19 @@ The first standard for cookies was published in 1997
Cookies can be divided into two categories: first party cookies, which are Cookies can be divided into two categories: first party cookies, which are
created by the domain the user has requested and third party cookies, which are created by the domain the user has requested and third party cookies, which are
placed in the user's browser by other domains that are generally not under the placed in the user's browser by other domains that are generally not under the
control of the first party. Whereas first party cookies are commonly not used control of the first party \cite{barthThirdPartyCookies2011}. Whereas first
for tracking but for the aforementioned shopping cart functionality for example party cookies are commonly not used for tracking but for the aforementioned
or enabling e-commerce applications to function properly, third party cookies are shopping cart functionality for example or enabling e-commerce applications to
popular with data brokerage firms (e.g., Datalogix, Experian, Equifax), online function properly, third party cookies are popular with data brokerage firms
advertisers (e.g., DoubleClick) and---belonging to both of these categories in (e.g., Datalogix, Experian, Equifax), online advertisers (e.g., DoubleClick)
some cases---social media platforms (e.g., Facebook). The distinction between and---belonging to both of these categories in some cases---social media
these two categories is not always clear, however. Google Analytics for example platforms (e.g., Facebook) \cite{cahnWhatCommunityCookie2016}. The distinction
is considered to be a third party but offers their analytics services by setting between these two categories is not always clear, however. Google Analytics for
a first party cookie in the user's browser in addition to loading JavaScript example is considered to be a third party but offers their analytics services by
snippets from their servers. Therefore, categorizing cookies into those that setting a first party cookie in the user's browser in addition to loading
serve third party web content and those that serve first party web content JavaScript snippets from their servers. Therefore, categorizing cookies into
presents a more adequate approach. those that serve third party web content and those that serve first party web
content presents a more adequate approach.
Cookies are set either by calling scripts that are embedded in a web page (e.g., Cookies are set either by calling scripts that are embedded in a web page (e.g.,
Google's \texttt{analytics.js}) or by using the \gls{HTTP} Set-Cookie response Google's \texttt{analytics.js}) or by using the \gls{HTTP} Set-Cookie response
@ -412,7 +413,8 @@ same-origin policy disallowing interaction with other trackers. Because of this,
sharing data between multiple trackers is difficult, since there are no easy sharing data between multiple trackers is difficult, since there are no easy
ways to accurately match an accumulated profile history of one identifier to ways to accurately match an accumulated profile history of one identifier to
another. This problem has been solved by modern trackers by using a mechanism another. This problem has been solved by modern trackers by using a mechanism
called Cookie Synchronization or Cookie Matching. This technique allows multiple called Cookie Synchronization or Cookie Matching
\cite{googleinc.CookieMatchingRealtime2020}. This technique allows multiple
trackers to open an information sharing channel between each other without trackers to open an information sharing channel between each other without
necessarily having to know the web site the user visits. necessarily having to know the web site the user visits.

21
references.bib
View File

@ -163,6 +163,16 @@
type = {{{RFC}}} type = {{{RFC}}}
} }
@misc{barthThirdPartyCookies2011,
title = {Third-{{Party Cookies}}},
author = {Barth {$<$}abarth@eecs.berkeley.edu{$>$}, Adam},
year = {2011},
month = apr,
url = {https://tools.ietf.org/html/rfc6265\#section-7.1},
urldate = {2020-08-10},
note = {Accessed 2020-08-10}
}
@article{bashirDiffusionUserTracking2018, @article{bashirDiffusionUserTracking2018,
title = {Diffusion of {{User Tracking Data}} in the {{Online Advertising Ecosystem}}}, title = {Diffusion of {{User Tracking Data}} in the {{Online Advertising Ecosystem}}},
author = {Bashir, Muhammad Ahmad and Wilson, Christo}, author = {Bashir, Muhammad Ahmad and Wilson, Christo},
@ -548,6 +558,17 @@ Web cache timing attacks},
language = {en} language = {en}
} }
@misc{googleinc.CookieMatchingRealtime2020,
title = {Cookie {{Matching}} | {{Real}}-Time {{Bidding}}},
author = {Google Inc.},
year = {2020},
month = jun,
url = {https://developers.google.com/authorized-buyers/rtb/cookie-guide},
urldate = {2020-08-10},
journal = {Google Developers},
note = {Accessed 2020-08-10}
}
@article{gugelmannAutomatedApproachComplementing2015, @article{gugelmannAutomatedApproachComplementing2015,
title = {An {{Automated Approach}} for {{Complementing Ad Blockers}}' {{Blacklists}}}, title = {An {{Automated Approach}} for {{Complementing Ad Blockers}}' {{Blacklists}}},
author = {Gugelmann, David and Happe, Markus and Ager, Bernhard and Lenders, Vincent}, author = {Gugelmann, David and Happe, Markus and Ager, Bernhard and Lenders, Vincent},