<!DOCTYPE article PUBLIC "-//NLM//DTD JATS (Z39.96) Journal Archiving and Interchange DTD v1.0 20120330//EN" "JATS-archivearticle1.dtd">
<article xmlns:xlink="http://www.w3.org/1999/xlink">
  <front>
    <journal-meta>
      <journal-title-group>
        <journal-title>M.: Quality-of-Context and its use for
Protecting Privacy in Context Aware Systems. Journal of Software 3(3) (2008)
83{93
40. Samarati</journal-title>
      </journal-title-group>
    </journal-meta>
    <article-meta>
      <article-id pub-id-type="doi">10.1016/j.pmcj.2008.04.008</article-id>
      <title-group>
        <article-title>Privacy in Georeferenced Context-aware Services: A Survey</article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="author">
          <string-name>Daniele Riboni</string-name>
          <email>riboni@dico.unimi.it</email>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Linda Pareschi</string-name>
          <email>pareschi@dico.unimi.it</email>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Claudio Bettini</string-name>
          <email>bettini@dico.unimi.it</email>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <aff id="aff0">
          <label>0</label>
          <institution>EveryWare Lab, D.I.Co., University of Milano</institution>
          <addr-line>via Comelico 39, I-20135 Milano</addr-line>
          ,
          <country country="IT">Italy</country>
        </aff>
      </contrib-group>
      <pub-date>
        <year>2009</year>
      </pub-date>
      <volume>3468</volume>
      <abstract>
        <p>Location based services (LBS) are a speci c instance of a broader class of Internet services that are predicted to become popular in a near future: context-aware services. The privacy concerns that LBS have raised are likely to become even more serious when several context data, other than location and time, are sent to service providers as part of an Internet request. This paper provides a classi cation and a brief survey of the privacy preservation techniques that have been proposed for this type of services. After identifying the bene ts and shortcomings of each class of techniques, the paper proposes a combined approach to achieve a more comprehensive solution for privacy preservation in georeferenced context-aware services.</p>
      </abstract>
    </article-meta>
  </front>
  <body>
    <sec id="sec-1">
      <title>Introduction</title>
      <p>
        It is widely recognized that the success of context-aware services is conditioned
to the availability of e ective privacy protection mechanisms (see, e.g., [
        <xref ref-type="bibr" rid="ref1 ref2">1, 2</xref>
        ]).
Techniques for privacy protection have been thoroughly studied in the eld of
databases, in order to protect microdata released from large repositories.
Recently some of these techniques have been extended and integrated with new
ones to preserve the privacy of users of Location Based Services (LBS) against
possibly untrusted service providers as well as against other types of adversaries
[
        <xref ref-type="bibr" rid="ref3">3</xref>
        ]. The domain of service provisioning based on location and time of request
introduces novel challenges with respect to traditional privacy protection in
microdata release. This is mainly due to the dynamic nature of the service paradigm
which requires a form of online privacy preservation technique as opposed to an
o ine one used, for example, in the publication of a view from a database. In
the case of LBS, speci c techniques are also necessary to process the
spatiotemporal information describing location and time of request which is also very
dynamic. On the other hand, location and time are only two of the possibly
many parameters characterizing the context of an Internet service request.
Indeed, context information goes far beyond location and time, including data
such as personal preferences and interests, current activity, physiological and
emotional status, and data collected from body-worn or environmental sensors,
just to name a few. Privacy protection techniques speci cally developed for LBS
are often insu cient and/or inadequate when applied to generic context-aware
services.
      </p>
      <p>
        Consider, for instance, cryptographic techniques proposed for LBS (e.g., [
        <xref ref-type="bibr" rid="ref4 ref5">4,
5</xref>
        ]). These techniques provide strong privacy guarantees at the cost of high
computational overhead on both the client and server side; moreover, they introduce
expensive communication costs. Hence, while they may be pro tably applied
to simple LBS such as nearest neighbor services, it is unlikely that they would
be practical for complex context-aware services. On the other hand, obfuscation
techniques proposed for LBS (e.g., [
        <xref ref-type="bibr" rid="ref6 ref7">6, 7</xref>
        ]) are speci cally addressed to location
information; hence, those techniques cannot be straightforwardly applied to other
contextual domains. With respect to techniques based on identity anonymity in
LBS (e.g., [
        <xref ref-type="bibr" rid="ref8 ref9">8, 9</xref>
        ]) we point out that, since many other kinds of context data
besides location may help an adversary in identifying the owner of those data, the
amount of context data to be generalized in order to enforce anonymity is large.
Hence, even if ltering techniques can be used for improving the service response,
it could happen that in order to achieve the desired anonymity level, context data
become too general to provide the service at an acceptable quality level [
        <xref ref-type="bibr" rid="ref10">10</xref>
        ]. For
this reason, speci c anonymity techniques for generic context-aware services are
needed.
      </p>
      <p>Moreover, in pervasive computing environments context-aware services can
exploit data provided by sensors deployed in the environment that can constantly
monitor context data. Hence, if those context sources are compromised, an
adversary's inference abilities may increase taking advantage of the observation of
users' behavior and of up-to-date context information. Defense techniques for
privacy preservation proposed for LBS do not consider this kind of inference
capabilities, since location and time are the only contextual parameters that are
taken into account. As a result, protecting against the above mentioned kind of
attacks requires new techniques.</p>
      <p>In this paper we survey privacy protection techniques for georeferenced
contextaware services. As depicted in Figure 1, the general privacy threat we are facing
is the release of sensitive associations between a user's identity and the
information that she considers private. The actual privacy risk certainly depends on
the adversary's model; for the purpose of this survey, unless we mention speci c
attacks, we adopt the general assumption that an adversary may obtain service
requests and responses as well as publicly available information.</p>
      <p>We distinguish di erent types of defense techniques that can be used to
contrast the privacy threat.</p>
      <p>Network and cryptographic protocols. These are mainly used to avoid
that an adversary can access the content of a request or response while it is
transmitted as well as to avoid that a network address identi es the location
and/or the issuer of a request.</p>
      <p>Access control mechanisms. These are used to discriminate (possibly
based on context itself) the entites that can obtain certain context
information.
Obfuscation techniques. Under this name we group the techniques,
usually based on generalization or partial suppression, that limit the disclosure
of private information contained in a request. Intuitively, they control the
release of the second part of the association describing the privacy threat.
Identity anonymization techniques. These are techniques that aim at
avoiding the release of the rst part of the association, i.e., the identity of the
issuer. The goal is to make the issuer indistinguishable among a su ciently
large number of individuals.</p>
      <p>This classi cation may apply as well to defenses against LBS privacy threats,
however our description of available approaches and solutions will be focused
on those for more complex context-aware services. Sections 2, 3, 4, and 5
address each of the above types of defenses, respectively. Based on the weaknesses
emerged from the analysis of the existing techniques, in Section 6 we advocate
the use of a combined approach, present preliminary proposals, and illustrate
the general characteristics that a comprehensive combined approach may have.
Section 7 concludes the paper.
2</p>
    </sec>
    <sec id="sec-2">
      <title>Network and cryptographic protocols</title>
      <p>The development of context-aware services received impulse by technological
progresses in the area of wireless communications, mobile devices, and sensors.
The use of wireless channels, and more generally insecure channels, poses a rst
threat for the users' privacy since it makes easier for an adversary to acquire
service requests and responses by eavesdropping the communication or analyzing
tra c on the network. In the literature, several models have been proposed for
privacy preservation in context-aware systems. While some of them rely on a
centralized architecture with a single trusted entity in charge of ensuring the users'
privacy, other models rely on a decentralized architecture in which mobile devices
use direct communication channels with service providers. decentralized
architectures in which mobile communication channels with service providers. In both
cases, two natural countermeasures for privacy attacks are: a) implement secure
communication channels so that no third party can obtain requests/responses
while they are in transit, and b) avoid the recognition of the client's network
address, even by the service provider, which may be untrusted.</p>
      <p>
        In order to protect point-to-point communications, in addition to standard
wireless security, di erent cryptographic techniques can be applied. One
possibility is clearly for applications to rely on SSL to encrypt communication; an
alternative (or additional) possibility is to provide authentication, authorization
and channel encryption through systems like Kerberos ([
        <xref ref-type="bibr" rid="ref11">11</xref>
        ]). Kerberos is based
on a centralized entity, Key Distribution Center (KDC), in charge of
authenticating clients and servers in the network, and providing them with the keys
needed for encrypting the communications. The centralized model that inspires
Kerberos does not protect from attacks aimed at acquiring the control of the
KDC entity. Speci c solutions to communication protection also depend on the
considered architecture and adversary's model, and are outside the scope of this
paper.
      </p>
      <p>
        Di erent approaches ([
        <xref ref-type="bibr" rid="ref12 ref13">12, 13</xref>
        ]) aim at guaranteeing a certain degree of
anonymity working at the IP level. The Tarzan system ([
        <xref ref-type="bibr" rid="ref12">12</xref>
        ]) adopted a solution
based on a network overlay that clusters nodes in subnetworks called domains
on the base of their IP addresses. The IP hiding is achieved by the substitution
of the sender's IP with the pseudonym corresponding to its domain. Moreover,
when a node needs to send a packet, its communications are ltered by a
special server called mimic that is in charge of i) substituting the IP and other
information that could reveal the sender identity with the adequate pseudonym,
and ii) of setting a virtual path (tunnel ) that guarantees the communication
encryption.
      </p>
      <p>
        Most solutions presented in the literature apply a combination of routing
protocols for IP hiding, and cryptographic techniques ([
        <xref ref-type="bibr" rid="ref14">14</xref>
        ]) to protect from
eavesdropping over the communication channel. Onion Routing ([
        <xref ref-type="bibr" rid="ref15">15</xref>
        ]) implements
both the features of IP hiding and message encryption. In order to preserve
the sender's IP address, each message travels towards the receiver via a series
of proxies, called onion routers, which choose the next component of the path
setting an unpredictable route. Each router in the path re-encrypts the message
before forwarding it to the next router. However, even these solutions su er from
attacks aimed at acquiring the control of one or more nodes of the network.
      </p>
      <p>
        A di erent application of a privacy-preserving routing protocol is presented
in [
        <xref ref-type="bibr" rid="ref16">16</xref>
        ]: the proposed solution has been designed for protecting the user's privacy
while moving in smart environments. This solution is based on a hierarchy of
trusted servers where the leaves, called portals, are aware of the user's location,
while internal nodes are aware of services provided by the environment. The user
accesses the network through a portal and, according to her privacy preferences,
she is assigned to an internal node, called lighthouse, that has the task of ltering
and encrypting all the communications between the user and the service provider.
The lighthouse does not know the user's position but is aware of the next hop
in the server hierarchy composing the path to the user's portal. Similarly, the
portal does not know which service the user is asking for, but it is aware of the
path to the chosen lighthouse. The privacy preservation is achieved decoupling
position data from both the identity information and other context parameters.
However, this approach requires the servers in the hierarchy to be trusted and
it does not protect by privacy attacks performed acquiring the control of one of
the nodes in the structure.
      </p>
      <p>The use of cryptographic techniques can also be extended to hide from the
service provider the exact request parameters as well as the response. This
approach has been proposed in the area of LBS where location information is often
considered sensitive by users. In particular, solutions based on this approach aim
at retrieving the nearest neighbor (NN) point of interest (poi) with respect to
the user position at the time of the request.</p>
      <p>
        A rst solution was proposed in [
        <xref ref-type="bibr" rid="ref4">4</xref>
        ]: the authors propose a form of encrypted
query processing combining the use of a data structure suited for managing
spatial information with a cryptographic schema for the secret sharing. On the
server side, location data are handled through a directed acyclic graph (DAG),
whose nodes correspond to Voronoi regions obtained by a tessellation of the
space with respect to pois stored by the service provider. The query processing
is performed according to the protocol proposed in [
        <xref ref-type="bibr" rid="ref17">17</xref>
        ] that allows a client to
retrieve the correct Voronoi area without communicating its precise location.
The drawback of this solution is that, in order to resolve a NN query, the user
needs to send a number of queries that is proportional to the depth of the DAG
instead of a single request. The consequent communication overhead impacts on
the network tra c and on the response time, which are commonly considered
important factors in mobile computing.
      </p>
      <p>
        Recently, a cryptographic approach inspired by the Private Information
Retrieval (PIR) eld was proposed in [
        <xref ref-type="bibr" rid="ref5">5</xref>
        ]. The service provider builds a Voronoi
tessellation according to the stored pois, and superimposes on its top a regular
grid of arbitrary granularity. In order to obtain the response to a NN query the
privacy preservation mechanism relies on a PIR technique that is used for
encrypting the user query, and for retrieving part of the location database without
revealing spatial information. Some of the strong points of this solution are that
location data are never disclosed; the user's identity is confused among identities
of all users; and no trusted third party is needed to protect the users' privacy.
However, since mobile devices are often characterized by limited computational
capability, the query encryption and the answer processing performed at the
client side have a strong impact on service response time, network and power
consumption. In particular, when applied to context-aware services that perform
the adaptation on a wide set of heterogeneous context data, this technique may
result in unacceptable computation overhead both at the client and at the server
side.
      </p>
    </sec>
    <sec id="sec-3">
      <title>Access control in context-aware systems</title>
      <p>
        Pervasive computing environments claim for techniques to control release of
data and access to resources on the basis of the context of users, environment,
and hardware/software entities. In general, the problem of access control [
        <xref ref-type="bibr" rid="ref18">18</xref>
        ]
consists in deciding whether to authorize or not a requesting entity (subject )
to perform a given action on a given resource (object ). Access control
mechanisms have been thoroughly studied in many elds, including operating systems,
databases, and distributed systems. However, the characteristic features of
pervasive environments introduce novel issues that must be taken into account for
devising e ective access control mechanisms. In particular, di erently from
centralized organizational domains, pervasive environments are characterized by
the intrinsic decentralization of authorization decisions, since the object owners
(users, services, infrastructures) are spread through the environment, and may
adopt di erent policies regarding disclosure of private information. Hence,
speci c techniques to deal with the mobility and continuously changing context of
the involved entities are needed to adapt authorizations to the current situation.
      </p>
      <p>To this aim various techniques for context-aware access control have been
recently proposed. Context-aware access control strategies fall in two main
categories. The rst category is the one of techniques aimed at granting or denying
access to resources considering the context of the requesting user and of the
resource (see, e.g., [19{21]). The second category is the one of techniques aimed
at controlling the release of user's context data on the basis of the context of
the requesting entity and of the user herself. In this section we concentrate on
techniques belonging to the latter category. On the contrary, techniques
belonging to the former category are outside the scope of this paper, and will not be
reviewed; however, we point out that, since those techniques imply the release of
users' context data to the access control mechanism, generally they also adopt
strategies to enforce users' privacy policies.</p>
      <p>
        Proposed context-aware access control mechanisms can be roughly classi ed
in those that derive from discretionary (DAC) [
        <xref ref-type="bibr" rid="ref22">22</xref>
        ] and those that derive from
role-based (RBAC) [
        <xref ref-type="bibr" rid="ref23">23</xref>
        ] access control. In DAC systems, the owner of each
object is in charge of stating policies to determine the access privileges on the basis
of the subject identity. These techniques are well suited to domains in which
subjects do not belong to a structured organization (e.g., they are well suited to
generic Internet services), since they are released from the burden of managing
groups or roles of subjects. On the other hand, techniques based on RBAC (in
which the access privileges depend on the subject role) are well suited to
structured organization domains (like, e.g., hospitals, companies), since the de nition
of functional roles simpli es the management of access control policies.
      </p>
      <p>
        Other techniques related to access-control in context-aware systems include
the use of access-rights graphs and hidden constraints (e.g., [
        <xref ref-type="bibr" rid="ref24">24</xref>
        ]) as well as
zeroknowledge proof theory [
        <xref ref-type="bibr" rid="ref25">25</xref>
        ] (e.g., [
        <xref ref-type="bibr" rid="ref26">26</xref>
        ]). These are called secret authorization
mechanisms, since they allow an entity to certify to a veri er the possession
of private information (e.g., context data) revealing neither the authorization
policies nor the secret data.
      </p>
      <p>In the following we brie y describe the access control techniques for
contextawareness derived from DAC and RBAC models, respectively.</p>
      <p>
        Techniques derived from DAC. Even early approaches to discretionary
access control allowed the expression of conditions to constrain permissions on the
basis of the spatial and temporal characterization of the subject. For instance,
in a bank setting, access to customer accounts could be acknowledged to
authorized personnel only during working hours and from machines located within
the bank. More recently, access control techniques speci cally addressed to the
protection of location information (e.g., [
        <xref ref-type="bibr" rid="ref27">27</xref>
        ]) have been proposed. However, the
richness and dynamics of contextual situations that may occur in pervasive and
mobile computing environments claim for the de nition of formal languages to
express complex conditions on a multitude of context data, as well as su ciently
expressive languages to represent the context itself. To this aim, Houdini [
        <xref ref-type="bibr" rid="ref28">28</xref>
        ]
provides a comprehensive formal framework to represent dynamic context data,
integrate them from heterogeneous sources, and share context information on the
basis of users' privacy policies. In particular, privacy policies can be expressed
considering the context of the data owner (i.e., the user) and the context of the
subject. As an example, a user of a service for locating friends could state a
policy to disclose her current location to her friends only if her mood is good and
her current activity is not working. Privacy policies in Houdini are expressed in
a restricted logic programming language supporting rule chaining but no cycles.
Rules preconditions express conditions on context data, while postconditions
express permissions to access contextual information; reasoning with the resulting
language has low computational complexity. Policy con ict resolution is based
on explicit rule priorities.
      </p>
      <p>
        Another relevant proposal, speci cally addressed to the preservation of
mobile customers privacy, can be found in [
        <xref ref-type="bibr" rid="ref29">29</xref>
        ]. That work proposes an access control
system aimed at controlling the release of private data based on time, location,
and customer's preferences. For instance, a user could state a policy to disclose
her location and pro le information only during the weekend and if she is in a
mall, and only in exchange for a discount coupon on items in her shopping list.
The proposed solution is based on an intermediary infrastructure in charge of
managing location and pro les of mobile users and to enforce their privacy
policies. A speci c index structure as well as algorithms are presented to e ciently
enforce the proposed techniques.
      </p>
      <p>
        Techniques derived from RBAC. Many other existing approaches to
contextaware access control are based on an extension of the RBAC model. As
anticipated before, RBAC systems are well-suited to structured organization domains.
However, the baseline RBAC model is not adequate to pervasive and mobile
computing domains, which are characterized by the dynamics of situations that may
determine the role played by a given entity in a given context. For this
reason, various proposals have been made to extend RBAC policies with contextual
conditions (see, e.g., [
        <xref ref-type="bibr" rid="ref19">19</xref>
        ]), and in particular with spatio-temporal constraints
(e.g., [
        <xref ref-type="bibr" rid="ref30">30</xref>
        ]). More recently, this approach has been applied to the privacy
protection of personal context data. A proposal in this sense is provided by the
UbiCOSM middleware [
        <xref ref-type="bibr" rid="ref31">31</xref>
        ], which tackles the comprehensive issue with
mechanisms to secure the access not only to services provided by ubiquitous
infrastructures, but also to users' context data, based on contextual conditions and
roles. The context model of UbiCOSM distinguishes between the physical
dimension, which describes the spatial characterization of the user, and the logical
dimension, which describes other data such as the user's current activity and
device capabilities. For instance, the context TouristAtMuseum is composed by the
physical context AtMuseum (characterized by the presence of the user within the
physical boundaries of a museum) and by the logical context Tourist (which
denes the user's role as the one of a tourist). Users can declare a policy to control
the release of a personal context data as the association between a permission
and a context in which the permission applies. Simple context descriptions can be
composed in more complex ones by means of logical operators, and may involve
the situation of multiple entities. For instance, in order to nd other tourists
that share her same interests, a user could state a policy to disclose her cultural
preferences to a person only if their current context is TouristAtMuseum and
they are both co-located with a person that is a friend of them both.
      </p>
      <p>
        Another worth-mentioning system is CoPS [
        <xref ref-type="bibr" rid="ref32">32</xref>
        ], which provides ne-grained
mechanisms to control the release of personal context data, as well as techniques
to identify misuse of the provided information. In particular, policies in CoPS are
organized in a hierarchical manner, on the basis of the priority level of the policy
(i.e., organization-level, user-level, default). Permissions depend on the context
and the role of the subject. CoPS supports both administrator and user-de ned
roles. While the former re ect the hierarchical structure of the organization, the
latter can be used to categorize entities in groups, in order to simplify the policy
management by users. The system adopts a con ict resolution mechanism based
on priorities and on the speci city of access control rules. Moreover, a trigger
mechanism can be set up to control the release of particular context data against
the frequency of the updates; this technique can be used, for instance, to notify
the user in the case someone tries to track her movements by continuously polling
her location.
      </p>
      <p>Open issues and remarks. As emerged from the above analysis of the
stateof-the-art, the main strong point of techniques derived from DAC consists in the
e ciency of the reasoning procedures they employ to evaluate at run-time the
access privileges of the requesting entity. This characteristic makes them very well
suited to application domains characterized by strict real-time requirements, like
telecommunication and Internet services. On the other hand, the roles
abstraction adopted by techniques derived from RBAC can be pro tably exploited not
only in structured organizational domains but also in open environments (like
ambient intelligence systems), since heterogeneous entities can be automatically
mapped to prede ned roles on the basis of the contextual situation to determine
their access privileges.</p>
      <p>
        Nevertheless, some open issues about context-aware access control systems
are worth to be considered. In particular, like in generic access control systems,
a formal model to represent policies and automatically recognize inconsistencies
(especially in systems supporting the de nition of negative authorizations) is
needed; however, only part of the techniques proposed for context-aware
computing face this issue. This problem is further complicated by the fact that the
privacy policy of a subject may con ict with the privacy policy of an object
owner. Proposed solutions for this issue include the use of techniques for secret
authorization, like proposed in [
        <xref ref-type="bibr" rid="ref24">24</xref>
        ]. Moreover, an evident weakness of these
systems consists in their rigidity: if strictly applied, an access control policy either
grants or denies access to a given object. This weakness is alleviated by the use
of obfuscation techniques (reported in Section 4) to disclose the required data
at di erent levels of accuracy on the basis of the current situation.
      </p>
      <p>
        A further critical issue for context-aware access control systems consists in
devising techniques to support end users in self-de ning privacy policies. Indeed,
manual policy de nition by users is an error-prone and tedious task. For this
reason, straightforward techniques to support users' policy de nition consists
in making use of user friendly interfaces and default policies, like in Houdini
and in CoPS, respectively. However, a more sophisticated strategy to address
this problem consists in the adoption of statistical techniques to automatically
learn privacy policies on the basis of the past decisions of the user. To this
aim, [
        <xref ref-type="bibr" rid="ref33">33</xref>
        ] propose the application of rough set theory to extract access control
policies based on the observation of the user's interaction with context-aware
applications during a training period.
      </p>
      <p>As a nal remark, we point out that context-aware access control systems
do not protect privacy in the case the access to a service is considered a private
information by itself (e.g., because it reveals particular interests or habits about
the user). To address this issue, techniques aimed at enforcing anonymity exist
and are reviewed in Section 5.
4</p>
    </sec>
    <sec id="sec-4">
      <title>Obfuscation of context data</title>
      <p>
        In some cases, the strict application of access control mechanisms (i.e., either
deny or allow access to a given context data in a given situation) may be a too
rigid strategy. For instance, consider the user of a service that redirects incoming
calls and messages on the basis of the current activity. Suppose that the service is
not completely trusted by the user; hence, since she considers her current activity
(e.g., MeetingCustomers ) a sensitive information, whether to allow or deny the
access to her precise current activity may be unsatisfactory. Indeed, denying
access to that data would determine the impossibility to take advantage of that
service, while allowing access could result in a privacy violation. In this case, a
more exible solution is to obfuscate [
        <xref ref-type="bibr" rid="ref34">34</xref>
        ] the private data before communicating
it to the service provider in order to decrease the sensitivity level of the data. For
instance, the precise current activity MeetingCustomers could be obfuscated to
the more generic activity BusinessMeeting. This solution is based on the intuition
that each private data is associated to a given sensitivity level, which depends
on the precision of the data itself; generally, the lesser the data is precise, the
lesser it is sensitive. Obfuscation techniques have been applied to the protection
of microdata released from databases (e.g., [
        <xref ref-type="bibr" rid="ref35">35</xref>
        ]).
      </p>
      <p>Several techniques based on obfuscation have also been proposed to preserve
the privacy of users of context-aware services. These techniques are generally
coupled with an access control mechanism to tailor the obfuscation level to be
enforced according to the trustiness of the subject and to the contextual
situation. However, in this section we concentrate on works that speci cally address
context data obfuscation. The main research issue in this eld is to devise
techniques to provide adequate privacy preservation while retaining the usefulness
of the data to context-awareness purposes. We point out that, di erently from
techniques based on anonymity (reviewed in Section 5), techniques considered
in this section do not protect against the disclosure of the user's identity.</p>
      <p>
        Various obfuscation-based techniques to control the release of location
information have been recently proposed (see, e.g., [
        <xref ref-type="bibr" rid="ref6 ref7">36, 6, 7</xref>
        ]), based on generalization
or perturbation of the precise user's position. One of the rst attempts to
support privacy in generic context aware systems through obfuscation mechanisms
is semantic eWallet [37], an architecture to support context-awareness by means
of techniques to retrieve users' context data while enforcing their privacy
preferences. Users of the semantic eWallet may express their preferences about the
accuracy level of their context data based on the requester's identity and on the
context of the request. That system supports both abstraction and falsi cation
of context information. By abstraction, the user can decide to generalize the
provided data, or to omit some details about it. For instance, a user involved in a
BusinessMeeting could decide to disclose her precise activity to a colleague only
during working hours and if they both are located within a company building;
activity should be generalized to Meeting in the other cases. On the other hand, by
falsi cation the user can decide to deliberately provide false information in order
to mask her precise current context in certain situations. For instance, a CEO
could reveal to her secretary that she is currently AtTheDentist, while telling to
the other employees that she is involved in a BusinessMeeting. In the
semantic eWallet, context data are represented by means of ontologies. Obfuscation
preferences are encoded as rules whose preconditions include a precise context
data and conditions for obfuscation, and postconditions express the obfuscated
context data to be disclosed if the preconditions hold.
      </p>
      <p>While in the semantic eWallet the mapping between precise and obfuscated
information must be explicitly stated case-by-case, a more scalable approach
to the de nition of obfuscation preferences is proposed in [38]. That work copes
with the multi-party ownership of context information in pervasive environments
by proposing a framework to retrieve context information and distributing it on
the basis of the obfuscation preferences stated by the data owner. It is worth
to note that in the proposed framework the owner of the data is not
necessarily the actual proprietary of the context source; instead, the data owner is the
person whom the data refers to. For instance, the owner of data provided by
a server-side positioning system is the user, not the manager of the positioning
infrastructure; hence, the de nition of obfuscation preferences about personal
location is left to the user. Obfuscation preferences are expressed by conditions on
the current context, by speci c context data, and by a maximum detail level at
which that data can be disclosed in that context. The level of detail of a context
data refers to the speci city of that data according to a prede ned obfuscation
ontology. Context data in an obfuscation ontology are organized as nodes into
a hierarchy, such that parent nodes represent more general concepts with
respect to their children; e.g., the activity MeetingCustomers has parent activity
BusinessMeeting, which in turn has parent activity Working. For instance, an
obfuscation preference could state to disclose the user's current activity with a
level 2 speci city in the case the requester is Bob and the request is made during
working hours. In the case those conditions hold, the released data is calculated
by generalizing the exact current activity up to the second level of the Activity
obfuscation ontology (i.e., up to the level of the grandchildren of the root node),
or to a lower level if the available information is less speci c than that stated
by the preference. Since manually organizing context data in an obfuscation
ontology could be unpractical, a technique to automatically discover reasoning
modules able to derive the data at the required speci city level is also presented.</p>
      <p>Based on the consideration that the quality of a context information (QoC,
intended as its closeness to the physical reality it describes) is a strong indicator
of privacy sensitiveness, Sheikh et al. propose the use of QoC to enforce users'
privacy preferences [39]. In that work, the actual quality of the disclosed context
data is negotiated between service providers and users. When a service provider
needs a data regarding a user's context, it speci es the QoC that it needs for that
data in order to provide the service. On the other hand, the user speci es the
maximum QoC she is willing to disclose for that data in order to take advantage
of the service. Service requirements and user's privacy preferences are
communicated to a middleware that is in charge of verifying if they are incompatible
(i.e., if the service requires a data to a quality the user is not willing to provide).
If this is not the case, obfuscation mechanisms are applied on that data in order
to reach the quality level required by the service provider. QoC is speci ed on
the basis of ve indicators, i.e., precision, freshness, spatial and temporal
resolution, and probability of correctness. Each context data is associated with ve
numerical values that express the quality of the data with respect to each of
the ve indicators. Given a particular context situation, a user can specify her
privacy preferences for a context data by de ning the maximum quality level for
each of the ve indicators that she is willing to disclose in that situation. For
instance, the user of a remote health monitoring service could state to disclose
vague context information to the caregivers when in a non-emergency context,
while providing accurate data in the case of emergency.</p>
      <p>One inherent weakness of obfuscation techniques for privacy in
contextawareness is evident: if the service provider requires a context data to a quality
that the user is not willing to disclose, access to that service is not possible. In
order to overcome this issue, anonymization techniques (presented in Section 5)
have been proposed, which protect from the disclosure of the user's identity,
while possibly providing accurate context information.</p>
    </sec>
    <sec id="sec-5">
      <title>Identity anonymization techniques</title>
      <p>While obfuscation techniques aim at protecting the right-hand side of the
sensitive association (SA) (see Figure 1), the goal of techniques for identity
anonymization is to protect the left-hand side of the SA in order to avoid that an adversary
re-identi es the issuer of a request.</p>
      <p>In the area of database systems, the notion of k-anonymity has been
introduced [40] to formally de ne when, upon release of a certain database view
containing records about individuals, for any speci c sensitive set of data in the
view, the corresponding individual can be considered indistinguishable among
at least k individuals. In order to enforce anonymity it is necessary to determine
which attributes in a table play the role of quasi-identi ers (qi), i.e., data that
joined with external knowledge may help the adversary to restrict the set of
candidate individuals. Techniques for database anonymization adopt generalization
of qi values and/or suppression of records in order to guarantee that the set of
released records can be partitioned in groups of at least k records having the
same value for qi attributes (called qi-groups). Since each individual is assumed
to be the respondent of a single record, this implies that there are at least k
candidate respondents for each released record.</p>
      <p>
        The idea of k-anonymity has also been applied to de ne a privacy metric
in location based services, as a speci c kind of context-aware services [
        <xref ref-type="bibr" rid="ref8">8</xref>
        ]. In
this case, the information being released is considered the information in the
service request. In particular, the information about the user's location may be
used by an adversary to re-identify the issuer of the request if the adversary has
access to external information about users' location. Attacks and defense
techniques in this context have been investigated in several papers, among which [
        <xref ref-type="bibr" rid="ref8 ref9">8,
9</xref>
        ]. Moreover, a formal framework for the categorization of defense techniques
with respect to the adversary's knowledge assumptions has been proposed in [
        <xref ref-type="bibr" rid="ref3">3</xref>
        ].
According to that categorization, when the adversary performs his attack using
information contained in a single request the attack is said to be single-issuer ;
otherwise, when the adversary may compare information included in requests
by multiple users, the attack is said to be multiple-issuers. Moreover, cases in
which the adversary can acquire information only during a single time granule
are called static (or snapshot ), while contexts in which the adversary may observe
multiple requests issued by the same users in di erent time granules are called
dynamic (or historical ). A possible technique to enforce anonymity in LBS is to
generalize precise location data in a request to an area including a set (called
anonymity set [41]) of other potential issuers. An important di erence between
the anonymity set in service requests and the qi-group in databases is that while
the qi-group includes only identities actually associated to a record in the table,
the anonymity set includes also users that did not issue any request but that are
potential issuers with respect to the adversary's external knowledge.
      </p>
      <p>With respect to identity anonymization in generic context-aware systems,
it is evident that many other kinds of context data besides location may be
considered qi. Hence, a large amount of context data must be generalized in
order to enforce anonymity. As a consequence, the granularity of generalized
context data released to the service provider could be too coarse to provide the
service at an acceptable quality level. In order to limit the information loss due
to the generalization of context data, four di erent personalized anonymization
models are proposed in [42]. These models allow a user to constrain the maximum
level of location and pro le generalization still guaranteeing the desired level of
anonymity. For instance, a user could decide to constrain the maximum level of
location generalization to an area of 1 km2, while imposing no constraints on the
level of generalization of her pro le.</p>
      <p>As outlined in the introduction, sensing technologies deployed in pervasive
environments can be exploited by adversaries to constantly monitor the users'
behavior, thus exposing the user to novel kinds of privacy attacks, like the one
presented in [43]. In that work it is shown that even enforcing k-anonymity, in
particular cases the attacker may recognize the actual issuer of a service request
by monitoring the behavior of the potential issuers with respect to service
responses. For example, consider a pervasive system of a gym, suggesting exercises
on the basis of gender, age, and physiological data retrieved from body-worn
sensors. Even if users are anonymous in a set of k potential issuers, the attacker
can easily recognize the issuer of a particular request if she starts to use in a
reasonable lapse of time a machine the system suggested to her, which was not
suggested to any other potential issuer. The proposed solution relies on an
intermediary entity that lters all the communications between users and service
providers, calculates the privacy threats corresponding to possible alternatives
suggested by the service (e.g., the next exercise to perform), and automatically
lters unsafe alternatives.</p>
      <p>A further issue to be considered is the defense against the well-known problem
of homogeneity [44] identi ed in the eld of databases. Homogeneity attacks can
be performed if all the records belonging to a qi-group have the same value of
sensitive information. In this case it is clear that the adversary may easily violate
the users' privacy despite anonymity is formally enforced. The same problem
may arise as well in context-aware services in the case an adversary recognizes
that all the users in an anonymity set actually issued a request with the same
value of private information. To our knowledge, a rst e ort to defend against
such attacks in context-aware systems has been presented in [45]. That proposal
aims at protecting from multiple-issuers historical attacks by applying a bounded
generalization of both context data and service parameters.
6</p>
    </sec>
    <sec id="sec-6">
      <title>Towards a comprehensive framework for privacy protection in context-aware systems</title>
      <p>Based on the weaknesses emerged from the analysis of the proposed techniques,
in this section we advocate the use of a combined approach to address the
comprehensive issue of privacy in context awareness; we present existing proposals,
and we illustrate the logical design of a framework intended to solve most of the
identi ed problems.</p>
      <p>On the need for a combined approach The analysis of the
state-of-theart reported in the previous sections has shown that each of the proposed
approaches, even if e ective in a particular scenario and under particular
assumptions, fails in providing a solution to the general problem. In particular:
cryptographic techniques for private information retrieval presented up to
the time of writing are unfeasible to complex context-aware services, due to
problems of bandwidth and computational resources consumption;
protecting communication privacy between the context source and the
context data consumer (e.g., the service provider) is useless in the case the
context data consumer is untrusted;
access control techniques (possibly coupled with obfuscation) are ine ective
in the case the access to a service is a sensitive information by itself, since
they do not protect from the disclosure of the user's identity. Moreover, they
do not prevent a malicious subject to adopt reasoning techniques in order to
derive new sensitive information based on data it is authorized to access;
techniques for identity anonymity rely on the exact knowledge about the
external information available to an adversary. However, especially in pervasive
and mobile computing scenarios, such knowledge is very hard to obtain, and
adopting worst-case assumptions about the external information leads to a
signi cant degradation of the quality of released context data.</p>
      <p>These observations claim for the combination of di erent approaches in order to
protect against the di erent kind of attacks that can be posed to the privacy of
users taking advantage of context-aware services.</p>
      <p>Proposed techniques Proposals to combine di erent approaches in a common
framework have been recently presented.</p>
      <p>In [46], an architecture for privacy-conscious context aggregation and
reasoning is illustrated. The proposed solution adopts client-side reasoning modules to
abstract raw context data into signi cant descriptions of the user's situation
(e.g., current activity and stereotype) that can be useful for adaptation. Release
of private context information is controlled by context-aware access control
policies, and the access to context information by service providers is mediated by a
trusted intermediary infrastructure in charge of enforcing anonymity. Moreover,
cryptographic techniques are used to protect communications inside the user
trusted domain.</p>
      <p>Papadopoulou et al. present in [47] a practical solution to enforce anonymity.
In that work, no assumptions about the external knowledge available to an
adversary are made; hence, the proposed technique does not formally guarantee
a given anonymity level. For this reason, the anonymization technique is coupled
with access control and obfuscation mechanisms in order to protect privacy in
the case an adversary is able to discover the user's identity. That technique is
applied using the virtual identity metaphor. A virtual identity is essentially the
subset of context data that a user is willing to share with a third party in a
given situation; in addition, since anonymity is not formally guaranteed, part</p>
      <p>CONTEXT-AWARE SERVICE PROVIDER</p>
      <p>LOCATION</p>
      <p>SERVER
credentials context data service parameters</p>
      <p>anonymous / encrypted communication
CONTEXT-AWARE
PRIVACY MODULE</p>
      <p>ANONYMOUS
AUTHENTICATION</p>
      <p>CONTEXT- SECRET AUTHORIZATION
AWARE
CAOCNCTERSOSL ID ANONYMIZER</p>
      <p>spatio-temporal
information / statistics
of the shared context data can be obfuscated on the basis of privacy policies in
order to hide some sensible details. For instance, a person could decide to share
her preferences regarding shopping items and leisure activities, as well as her
obfuscated location, when she is on vacation (using a tourist virtual identity),
while hiding those information when she is traveling for work (using a worker
virtual identity). With respect to the problem introduced by multiple requests
issued by the same user, speci c techniques are presented to avoid that di erent
virtual identities can be linked to the same (anonymous) user by an adversary.</p>
      <p>While the above mentioned works try to protect the privacy of users accessing
a remote service, the AnonySense system [48] is aimed at supporting privacy in
opportunistic sensing applications, i.e., applications that leverage opportunistic
networks formed by mobile devices to acquire aggregated context data in a
particular region. To reach this goal, the geographic area is logically partitioned into
tiles large enough to probabilistically gain k-anonymity; i.e., regions visited with
high probability by more than k persons during a given time granule.
Measurements of context data are reported by mobile nodes specifying the tile they refer
to and the time interval during which they were acquired. Moreover, in order to
provide a second layer of privacy protection, obfuscation is applied on the sensed
data by fusing the values provided by at least l nodes (l k) before
communicating the aggregated data to the application. Cryptographic techniques are
used to enforce anonymous authentication by users of the system.
Towards a comprehensive framework We now illustrate how existing
techniques can be extended and combined in a logical multilayer framework, which
is graphically depicted in Figure 2. This framework is partially derived from
the preliminary architecture described in [46]. However, the model presented
here is intended to provide a more comprehensive privacy solution, addressing
problems regarding sensor and pro le data aggregation and reasoning (including
obfuscation), context-aware access control and secret authorization, anonymous
authentication, identity anonymity, and anonymous/encrypted communication.
Clearly, the actual techniques to be applied for protecting privacy depend on
the current context (users' situation, available services, network and
environmental conditions). However, we believe that this framework is exible enough
to provide e ective privacy protection in most pervasive and mobile computing
scenarios. The framework is composed of the following layers:</p>
      <p>Sensors layer: This layer includes body-worn and environmental sensors
that communicate context data to the upper layers through encrypted
channels using energy-e cient cryptographic protocols (e.g., those based on
elliptic curves [49] like in Sun SPOT sensors [50]). We assume that this layer
is within the trusted domain of the user (i.e., sensors do not deliberately
provide false information).</p>
      <p>User device layer: This layer is in charge of managing the user's pro le
information (i.e., context data that are almost static, like personal
information, interests and preferences) and privacy policies. Upon update of this
information by the user, the new information is communicated to the
upper layer. Moreover, this layer is in charge of fusing context data provided
by body-worn sensors and to communicate them in an aggregated form to
the upper layer on a per-request basis (e.g., when those data are required
by a service for performing adaptation). This layer is deployed on the user's
device, which is assumed to be trusted (traditional security issues are not
addressed here); communications with the upper layer are performed through
encrypted channels.</p>
      <p>Context provider layer: This layer is in charge of fusing sensor data
provided by the lower layers, including those provided by sensors that are not
directly under the communication range of the user device. Moreover,
according to the user's policies, it performs context reasoning and obfuscation
for privacy and adaptation purposes, as described in [46]. It communicates
user's credentials, privacy policies, and context data to the upper layer on a
per-request basis through encrypted channels. This layer belongs to the user's
trusted domain; depending on the device capabilities, it can be deployed on
the user's device itself, or on another trusted machine.</p>
      <p>Context-aware privacy module layer: This layer is in charge of
anonymously authenticating the user on the upper layer, and to enforce her
contextaware access control policies, possibly after a phase of secret negotiation with
the third party. Moreover, depending on the user's policies, it can possibly
anonymize the user's identity on the basis of (either precise or statistical)
trusted information received from the upper layer (e.g., spatio-temporal
information about users received from a trusted location server). Protocols for
anonymous/encrypted communication are adopted to provide credentials,
context data and service parameters to the upper layer. This layer belongs
to the user's trusted domain. Depending on device capabilities and on
characteristics of the actual algorithms it adopts (e.g., to enforce anonymity), this
layer can be implemented on the user's device, on another trusted machine,
or on the infrastructure of a trusted entity (e.g., the network operator).
Services layer: This layer is composed of context-aware service providers
and other infrastructural services (e.g., location servers). Typically, this layer
is assumed not to belong to the user's trusted domain, even if particular
services can be trusted by the user (e.g., a network operator location server).
7</p>
    </sec>
    <sec id="sec-7">
      <title>Conclusions</title>
      <p>Through a classi cation into four main categories of techniques, we have
described the state of the art of privacy preservation for georeferenced
contextaware services. While previous work has also proposed the combination of
techniques from two or more categories, we claim that a deeper integration is needed
and we propose an architecture for a comprehensive framework towards this goal.
Clearly, there is still a long way to go in order to re ne the architecture, work out
the details of its components, implement and integrate the actual techniques, and
test the framework on real applications. Moreover, there are still several other
aspects, not considered in our paper, that deserve investigation. For example, since
there are well-known techniques for context reasoning, they may have to be taken
into account, since released context data may determine the disclosure of other
context data, possibly leading to privacy leaks that were previously unidenti ed.
Furthermore, computationally expensive techniques (e.g., those making use of
ontological reasoning or complex cryptographic algorithms) pose serious
scalability issues that may limit their applicability in real-world scenarios. Finally,
since the access to context data of real users is generally unavailable for privacy
reasons, sophisticated simulation environments are needed to evaluate the actual
e ectiveness of privacy preservation mechanisms in realistic situations.</p>
    </sec>
    <sec id="sec-8">
      <title>Acknowledgments</title>
      <p>This work was partially supported by National Science Foundation (NSF) under
grants N. CNS-0716567 and N. IIS-0430402, and by Italian MIUR under grant
InterLink II04C0EC1D.</p>
    </sec>
  </body>
  <back>
    <ref-list>
      <ref id="ref1">
        <mixed-citation>
          1.
          <string-name>
            <surname>Palen</surname>
            ,
            <given-names>L.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Dourish</surname>
            ,
            <given-names>P.</given-names>
          </string-name>
          :
          <article-title>Unpacking \privacy" for a networked world</article-title>
          .
          <source>In: Proceedings of the 2003 Conference on Human Factors in Computing Systems (CHI</source>
          <year>2003</year>
          ), ACM (
          <year>2003</year>
          )
          <volume>129</volume>
          {
          <fpage>136</fpage>
        </mixed-citation>
      </ref>
      <ref id="ref2">
        <mixed-citation>
          2.
          <string-name>
            <surname>Lederer</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Hong</surname>
            ,
            <given-names>J.I.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Dey</surname>
            ,
            <given-names>A.K.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Landay</surname>
            ,
            <given-names>J.A.</given-names>
          </string-name>
          :
          <article-title>Personal privacy through understanding and action: ve pitfalls for designers</article-title>
          .
          <source>Personal and Ubiquitous Computing</source>
          <volume>8</volume>
          (
          <issue>6</issue>
          ) (
          <year>2004</year>
          )
          <volume>440</volume>
          {
          <fpage>454</fpage>
        </mixed-citation>
      </ref>
      <ref id="ref3">
        <mixed-citation>
          3.
          <string-name>
            <surname>Bettini</surname>
            ,
            <given-names>C.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Mascetti</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Wang</surname>
            ,
            <given-names>X.S.</given-names>
          </string-name>
          :
          <article-title>Privacy Protection through Anonymity in Location-based Services. Handbook of Database Security: Applications and Trends (</article-title>
          <year>2008</year>
          )
          <volume>509</volume>
          {
          <fpage>530</fpage>
        </mixed-citation>
      </ref>
      <ref id="ref4">
        <mixed-citation>
          4.
          <string-name>
            <surname>Atallah</surname>
            ,
            <given-names>M.J.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Frikken</surname>
            ,
            <given-names>K.B.</given-names>
          </string-name>
          :
          <article-title>Privacy-Preserving Location-Dependent Query Processing</article-title>
          .
          <source>In: ICPS '04: Proceedings of the The IEEE/ACS International Conference on Pervasive Services, IEEE Computer Society</source>
          (
          <year>2004</year>
          )
          <volume>9</volume>
          {
          <fpage>17</fpage>
        </mixed-citation>
      </ref>
      <ref id="ref5">
        <mixed-citation>
          5.
          <string-name>
            <surname>Ghinita</surname>
            ,
            <given-names>G.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Kalnis</surname>
            ,
            <given-names>P.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Khoshgozaran</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Shahabi</surname>
            ,
            <given-names>C.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Tan</surname>
            ,
            <given-names>K.L.</given-names>
          </string-name>
          :
          <article-title>Private queries in location based services: anonymizers are not necessary</article-title>
          .
          <source>In: Proceedings of the ACM SIGMOD International Conference on Management of Data (SIGMOD</source>
          <year>2008</year>
          ), ACM (
          <year>2008</year>
          )
          <volume>121</volume>
          {
          <fpage>132</fpage>
        </mixed-citation>
      </ref>
      <ref id="ref6">
        <mixed-citation>
          6.
          <string-name>
            <surname>Ardagna</surname>
            ,
            <given-names>C.A.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Cremonini</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Damiani</surname>
            ,
            <given-names>E.</given-names>
          </string-name>
          , De Capitani di Vimercati,
          <string-name>
            <given-names>S.</given-names>
            ,
            <surname>Samarati</surname>
          </string-name>
          ,
          <string-name>
            <surname>P.</surname>
          </string-name>
          :
          <article-title>Location Privacy Protection Through Obfuscation-Based Techniques</article-title>
          .
          <source>In: Proceedings of the 21st Annual IFIP WG 11.3 Working Conference on Data and Applications Security (DBSec'07)</source>
          . Volume
          <volume>4602</volume>
          of Lecture Notes in Computer Science., Springer (
          <year>2007</year>
          )
          <volume>47</volume>
          {
          <fpage>60</fpage>
        </mixed-citation>
      </ref>
      <ref id="ref7">
        <mixed-citation>
          7.
          <string-name>
            <surname>Yiu</surname>
            ,
            <given-names>M.L.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Jensen</surname>
            ,
            <given-names>C.S.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Huang</surname>
            ,
            <given-names>X.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Lu</surname>
          </string-name>
          , H.:
          <article-title>SpaceTwist: Managing the TradeO s Among Location Privacy, Query Performance, and Query Accuracy in Mobile Services</article-title>
          .
          <source>In: Proceedings of the 24th International Conference on Data Engineering (ICDE</source>
          <year>2008</year>
          ), IEEE Computer Society (
          <year>2008</year>
          )
          <volume>366</volume>
          {
          <fpage>375</fpage>
        </mixed-citation>
      </ref>
      <ref id="ref8">
        <mixed-citation>
          8.
          <string-name>
            <surname>Gruteser</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Grunwald</surname>
            ,
            <given-names>D.</given-names>
          </string-name>
          :
          <article-title>Anonymous Usage of Location-Based Services Through Spatial and Temporal Cloaking</article-title>
          .
          <source>In: Proc. of the 1st International Conference on Mobile Systems, Applications and Services (MobiSys)</source>
          ,
          <source>USENIX Association</source>
          (
          <year>2003</year>
          )
          <volume>31</volume>
          {
          <fpage>42</fpage>
        </mixed-citation>
      </ref>
      <ref id="ref9">
        <mixed-citation>
          9.
          <string-name>
            <surname>Gedik</surname>
            ,
            <given-names>B.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Liu</surname>
            ,
            <given-names>L.</given-names>
          </string-name>
          :
          <article-title>Protecting Location Privacy with Personalized k-Anonymity: Architecture and Algorithms</article-title>
          .
          <source>IEEE Transactions on Mobile Computing</source>
          <volume>7</volume>
          (
          <issue>1</issue>
          ) (
          <year>2008</year>
          )
          <volume>1</volume>
          {
          <fpage>18</fpage>
        </mixed-citation>
      </ref>
      <ref id="ref10">
        <mixed-citation>
          10.
          <string-name>
            <surname>Aggarwal</surname>
            ,
            <given-names>C.C.</given-names>
          </string-name>
          :
          <article-title>On k-Anonymity and the Curse of Dimensionality</article-title>
          .
          <source>In: Proceedings of the 31st International Conference on Very Large Data Bases (VLDB)</source>
          ,
          <source>ACM</source>
          (
          <year>2005</year>
          )
          <volume>901</volume>
          {
          <fpage>909</fpage>
        </mixed-citation>
      </ref>
      <ref id="ref11">
        <mixed-citation>
          11.
          <string-name>
            <surname>Neuman</surname>
            ,
            <given-names>B.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Ts</surname>
          </string-name>
          'o, T.:
          <article-title>Kerberos: an authentication service for computer networks</article-title>
          .
          <source>Communications Magazine, IEEE</source>
          <volume>32</volume>
          (
          <issue>9</issue>
          ) (
          <year>Sep 1994</year>
          )
          <volume>33</volume>
          {
          <fpage>38</fpage>
        </mixed-citation>
      </ref>
      <ref id="ref12">
        <mixed-citation>
          12.
          <string-name>
            <surname>Freedman</surname>
            ,
            <given-names>M.J.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Morris</surname>
          </string-name>
          , R.:
          <article-title>Tarzan: a peer-to-peer anonymizing network layer</article-title>
          .
          <source>In: CCS '02: Proceedings of the 9th ACM conference on Computer and communications security</source>
          ,
          <source>ACM</source>
          (
          <year>2002</year>
          )
          <volume>193</volume>
          {
          <fpage>206</fpage>
        </mixed-citation>
      </ref>
      <ref id="ref13">
        <mixed-citation>
          13.
          <string-name>
            <surname>Reiter</surname>
            ,
            <given-names>M.K.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Rubin</surname>
            ,
            <given-names>A.D.</given-names>
          </string-name>
          :
          <article-title>Anonymous web transactions with crowds</article-title>
          .
          <source>Commun. ACM</source>
          <volume>42</volume>
          (
          <issue>2</issue>
          ) (
          <year>1999</year>
          )
          <volume>32</volume>
          {
          <fpage>48</fpage>
        </mixed-citation>
      </ref>
      <ref id="ref14">
        <mixed-citation>
          14.
          <string-name>
            <surname>Dingledine</surname>
            ,
            <given-names>R.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Mathewson</surname>
            ,
            <given-names>N.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Syverson</surname>
            ,
            <given-names>P.</given-names>
          </string-name>
          :
          <article-title>Tor: the second-generation onion router</article-title>
          .
          <source>In: SSYM'04: Proceedings of the 13th conference on USENIX Security Symposium</source>
          , USENIX Association (
          <year>2004</year>
          )
          <volume>21</volume>
          {
          <fpage>21</fpage>
        </mixed-citation>
      </ref>
      <ref id="ref15">
        <mixed-citation>
          15.
          <string-name>
            <surname>Goldschlag</surname>
            ,
            <given-names>D.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Reed</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Syverson</surname>
            ,
            <given-names>P.</given-names>
          </string-name>
          :
          <article-title>Onion routing</article-title>
          .
          <source>Commun. ACM</source>
          <volume>42</volume>
          (
          <issue>2</issue>
          ) (
          <year>1999</year>
          )
          <volume>39</volume>
          {
          <fpage>41</fpage>
        </mixed-citation>
      </ref>
      <ref id="ref16">
        <mixed-citation>
          16.
          <string-name>
            <surname>Al-Muhtadi</surname>
          </string-name>
          , J.,
          <string-name>
            <surname>Campbell</surname>
            ,
            <given-names>R.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Kapadia</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Mickunas</surname>
            ,
            <given-names>M.D.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Yi</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          :
          <article-title>Routing Through the Mist: Privacy Preserving Communication in Ubiquitous Computing Environments</article-title>
          .
          <source>In: Proceedings of the 22 nd International Conference on Distributed Computing Systems (ICDCS'02)</source>
          , IEEE Computer Society (
          <year>2002</year>
          )
          <fpage>74</fpage>
        </mixed-citation>
      </ref>
      <ref id="ref17">
        <mixed-citation>
          17.
          <string-name>
            <surname>Atallah</surname>
            ,
            <given-names>M.J.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Du</surname>
            ,
            <given-names>W.</given-names>
          </string-name>
          :
          <article-title>Secure multi-party computational geometry</article-title>
          .
          <source>In: WADS '01: Proceedings of the 7th International Workshop on Algorithms and Data Structures</source>
          , Springer-Verlag (
          <year>2001</year>
          )
          <volume>165</volume>
          {
          <fpage>179</fpage>
        </mixed-citation>
      </ref>
      <ref id="ref18">
        <mixed-citation>
          18.
          <string-name>
            <surname>Samarati</surname>
            ,
            <given-names>P.</given-names>
          </string-name>
          , De Capitani di Vimercati, S.: Access Control:
          <article-title>Policies, Models, and Mechanisms</article-title>
          .
          <source>In: Foundations of Security Analysis and Design, Tutorial Lectures</source>
          . Volume
          <volume>2171</volume>
          of Lecture Notes in Computer Science., Springer (
          <year>2001</year>
          )
          <volume>137</volume>
          {
          <fpage>196</fpage>
        </mixed-citation>
      </ref>
      <ref id="ref19">
        <mixed-citation>
          19.
          <string-name>
            <surname>Kumar</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Karnik</surname>
            ,
            <given-names>N.M.</given-names>
          </string-name>
          , Cha e, G.:
          <article-title>Context sensitivity in role-based access control</article-title>
          .
          <source>Operating Systems Review</source>
          <volume>36</volume>
          (
          <issue>3</issue>
          ) (
          <year>2002</year>
          )
          <volume>53</volume>
          {
          <fpage>66</fpage>
        </mixed-citation>
      </ref>
      <ref id="ref20">
        <mixed-citation>
          20.
          <string-name>
            <surname>Covington</surname>
            ,
            <given-names>M.J.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Fogla</surname>
            ,
            <given-names>P.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Zhan</surname>
            ,
            <given-names>Z.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Ahamad</surname>
            ,
            <given-names>M.:</given-names>
          </string-name>
          <article-title>A Context-Aware Security Architecture for Emerging Applications</article-title>
          .
          <source>In: Proceedings of the 18th Annual Computer Security Applications Conference (ACSAC</source>
          <year>2002</year>
          ), IEEE Computer Society (
          <year>2002</year>
          )
          <volume>249</volume>
          {
          <fpage>260</fpage>
        </mixed-citation>
      </ref>
      <ref id="ref21">
        <mixed-citation>
          21.
          <string-name>
            <surname>Toninelli</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Montanari</surname>
            ,
            <given-names>R.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Kagal</surname>
            ,
            <given-names>L.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Lassila</surname>
            ,
            <given-names>O.</given-names>
          </string-name>
          :
          <string-name>
            <surname>Proteus: A Semantic ContextAware Adaptive Policy</surname>
          </string-name>
          <article-title>Model</article-title>
          .
          <source>In: Proceedings of the 8th IEEE International Workshop on Policies for Distributed Systems and Networks(POLICY</source>
          <year>2007</year>
          ), IEEE Computer Society (
          <year>2007</year>
          )
          <volume>129</volume>
          {
          <fpage>140</fpage>
        </mixed-citation>
      </ref>
      <ref id="ref22">
        <mixed-citation>
          22.
          <string-name>
            <surname>Sandhu</surname>
            ,
            <given-names>R.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Samarati</surname>
            ,
            <given-names>P.</given-names>
          </string-name>
          : Access Control:
          <article-title>Principles and Practice</article-title>
          .
          <source>IEEE Communications 32(9)</source>
          (
          <year>1994</year>
          )
          <volume>40</volume>
          {
          <fpage>48</fpage>
        </mixed-citation>
      </ref>
      <ref id="ref23">
        <mixed-citation>
          23.
          <string-name>
            <surname>Sandhu</surname>
            ,
            <given-names>R.S.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Coyne</surname>
            ,
            <given-names>E.J.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Feinstein</surname>
            ,
            <given-names>H.L.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Youman</surname>
            ,
            <given-names>C.E.</given-names>
          </string-name>
          :
          <article-title>Role-Based Access Control Models</article-title>
          .
          <source>IEEE Computer 29(2)</source>
          (
          <year>1996</year>
          )
          <volume>38</volume>
          {
          <fpage>47</fpage>
        </mixed-citation>
      </ref>
      <ref id="ref24">
        <mixed-citation>
          24.
          <string-name>
            <surname>Hengartner</surname>
            ,
            <given-names>U.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Steenkiste</surname>
            ,
            <given-names>P.</given-names>
          </string-name>
          :
          <string-name>
            <surname>Avoiding Privacy Violations Caused by ContextSensitive Services</surname>
          </string-name>
          .
          <source>Pervasive and Mobile Computing</source>
          <volume>2</volume>
          (
          <issue>3</issue>
          ) (
          <year>2006</year>
          )
          <volume>427</volume>
          {
          <fpage>452</fpage>
        </mixed-citation>
      </ref>
      <ref id="ref25">
        <mixed-citation>
          25.
          <string-name>
            <surname>Brands</surname>
            ,
            <given-names>S.A.</given-names>
          </string-name>
          :
          <article-title>Rethinking Public Key Infrastructures and Digital Certi cates: Building in Privacy</article-title>
          . MIT Press (
          <year>2000</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref26">
        <mixed-citation>
          26.
          <string-name>
            <surname>Wang</surname>
            ,
            <given-names>C.D.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Feng</surname>
            ,
            <given-names>L.C.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Wang</surname>
            ,
            <given-names>Q.</given-names>
          </string-name>
          :
          <article-title>Zero-Knowledge-Based User Authentication Technique in Context-aware System</article-title>
          .
          <source>Multimedia and Ubiquitous Engineering</source>
          ,
          <year>2007</year>
          . MUE '07. International Conference on (
          <year>April 2007</year>
          )
          <volume>874</volume>
          {
          <fpage>879</fpage>
        </mixed-citation>
      </ref>
      <ref id="ref27">
        <mixed-citation>
          27.
          <string-name>
            <surname>Hengartner</surname>
            ,
            <given-names>U.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Steenkiste</surname>
            ,
            <given-names>P.</given-names>
          </string-name>
          :
          <article-title>Access control to people location information</article-title>
          .
          <source>ACM Trans. Inf. Syst. Secur</source>
          .
          <volume>8</volume>
          (
          <issue>4</issue>
          ) (
          <year>2005</year>
          )
          <volume>424</volume>
          {
          <fpage>456</fpage>
        </mixed-citation>
      </ref>
      <ref id="ref28">
        <mixed-citation>
          28.
          <string-name>
            <surname>Hull</surname>
            ,
            <given-names>R.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Kumar</surname>
            ,
            <given-names>B.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Lieuwen</surname>
            ,
            <given-names>D.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Patel-Schneider</surname>
            ,
            <given-names>P.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Sahuguet</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Varadarajan</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Vyas</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          :
          <article-title>Enabling Context-Aware and Privacy-Conscious User Data Sharing</article-title>
          .
          <source>In: Proceedings of the 2004 IEEE International Conference on Mobile Data Management (MDM'04)</source>
          , IEEE Computer Society (
          <year>2004</year>
          )
          <volume>187</volume>
          {
          <fpage>198</fpage>
        </mixed-citation>
      </ref>
      <ref id="ref29">
        <mixed-citation>
          29.
          <string-name>
            <surname>Atluri</surname>
            ,
            <given-names>V.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Shin</surname>
          </string-name>
          , H.:
          <article-title>E cient Security Policy Enforcement in a Location Based Service Environment</article-title>
          .
          <source>In: Proceedings of Data and Applications Security XXI, 21st Annual IFIP WG 11.3 Working Conference on Data and Applications Security</source>
          . Volume
          <volume>4602</volume>
          of Lecture Notes in Computer Science., Springer (
          <year>2007</year>
          )
          <volume>61</volume>
          {
          <fpage>76</fpage>
        </mixed-citation>
      </ref>
      <ref id="ref30">
        <mixed-citation>
          30.
          <string-name>
            <surname>Atluri</surname>
            ,
            <given-names>V.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Chun</surname>
            ,
            <given-names>S.A.</given-names>
          </string-name>
          :
          <article-title>A geotemporal role-based authorisation system</article-title>
          .
          <source>International Journal of Information and Computer Security</source>
          <volume>1</volume>
          (
          <issue>1</issue>
          {2) (
          <year>2007</year>
          )
          <volume>143</volume>
          {
          <fpage>168</fpage>
        </mixed-citation>
      </ref>
      <ref id="ref31">
        <mixed-citation>
          31.
          <string-name>
            <surname>Corradi</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Montanari</surname>
            ,
            <given-names>R.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Tibaldi</surname>
            ,
            <given-names>D.</given-names>
          </string-name>
          :
          <article-title>Context-Based Access Control Management in Ubiquitous Environments</article-title>
          .
          <source>In: Proceedings of the 3rd IEEE International Symposium on Network Computing and Applications (NCA</source>
          <year>2004</year>
          ), IEEE Computer Society (
          <year>2004</year>
          )
          <volume>253</volume>
          {
          <fpage>260</fpage>
        </mixed-citation>
      </ref>
      <ref id="ref32">
        <mixed-citation>
          32.
          <string-name>
            <surname>Sacramento</surname>
            ,
            <given-names>V.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Endler</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Nascimento</surname>
            ,
            <given-names>F.N.:</given-names>
          </string-name>
          <article-title>A Privacy Service for Contextaware Mobile Computing</article-title>
          .
          <source>In: Proceedings of the First International Conference on Security and Privacy for Emerging Areas in Communications Networks (SECURECOMM '05)</source>
          , IEEE Computer Society (
          <year>2005</year>
          )
          <volume>182</volume>
          {
          <fpage>193</fpage>
        </mixed-citation>
      </ref>
      <ref id="ref33">
        <mixed-citation>
          33.
          <string-name>
            <surname>Zhang</surname>
            ,
            <given-names>Q.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Qi</surname>
            ,
            <given-names>Y.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Zhao</surname>
            ,
            <given-names>J.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Hou</surname>
            ,
            <given-names>D.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Zhao</surname>
            ,
            <given-names>T.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Liu</surname>
            ,
            <given-names>L.</given-names>
          </string-name>
          :
          <article-title>A Study on Context-aware Privacy Protection for Personal Information</article-title>
          .
          <source>In: Proceedings of the 16th IEEE International Conference on Computer Communications and Networks (ICCCN</source>
          <year>2007</year>
          ), IEEE Computer Society (
          <year>2007</year>
          )
          <volume>1351</volume>
          {
          <fpage>1358</fpage>
        </mixed-citation>
      </ref>
      <ref id="ref34">
        <mixed-citation>
          34.
          <string-name>
            <surname>Bakken</surname>
            ,
            <given-names>D.E.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Parameswaran</surname>
            ,
            <given-names>R.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Blough</surname>
            ,
            <given-names>D.M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Franz</surname>
            ,
            <given-names>A.A.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Palmer</surname>
            ,
            <given-names>T.J.</given-names>
          </string-name>
          :
          <article-title>Data Obfuscation: Anonymity and Desensitization of Usable Data Sets</article-title>
          .
          <source>IEEE Security &amp; Privacy</source>
          <volume>2</volume>
          (
          <issue>6</issue>
          ) (
          <year>2004</year>
          )
          <volume>34</volume>
          {
          <fpage>41</fpage>
        </mixed-citation>
      </ref>
      <ref id="ref35">
        <mixed-citation>
          35.
          <string-name>
            <surname>Xiao</surname>
            ,
            <given-names>X.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Tao</surname>
            ,
            <given-names>Y.</given-names>
          </string-name>
          :
          <article-title>Personalized privacy preservation</article-title>
          .
          <source>In: SIGMOD '06: Proceedings of the 2006 ACM SIGMOD international conference on Management of data</source>
          , ACM Press (
          <year>2006</year>
          )
          <volume>229</volume>
          {
          <fpage>240</fpage>
        </mixed-citation>
      </ref>
    </ref-list>
  </back>
</article>