<!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 />
    <article-meta>
      <title-group>
        <article-title>Representation and Inference of Privacy Risks Using Semantic Web Technologies</article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="author">
          <string-name>Tomas Sander Systems Security HP Lab</string-name>
          <email>tomas.sander@hp.com</email>
          <xref ref-type="aff" rid="aff0">0</xref>
          <xref ref-type="aff" rid="aff1">1</xref>
          <xref ref-type="aff" rid="aff2">2</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Vaughn Dr</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
          <xref ref-type="aff" rid="aff1">1</xref>
          <xref ref-type="aff" rid="aff2">2</xref>
        </contrib>
        <aff id="aff0">
          <label>0</label>
          <institution>Douglas da Silva PUCRS Ipiranga Av. 6681, FACIN CEP 90619-900 Porto Alegre</institution>
          ,
          <country country="BR">Brazil</country>
        </aff>
        <aff id="aff1">
          <label>1</label>
          <institution>Princeton</institution>
          ,
          <addr-line>NJ 08540</addr-line>
          ,
          <country country="US">USA</country>
        </aff>
        <aff id="aff2">
          <label>2</label>
          <institution>Renata Vieira PUCRS Ipiranga Av. 6681, FACIN CEP 90619-900 Porto Alegre</institution>
          ,
          <country country="BR">Brazil</country>
        </aff>
      </contrib-group>
      <abstract>
        <p>This poster discusses domain ontologies on the privacy field for automatic risk identification and project qualification. It presents an ontology model for describing risks as an interpretation of privacy policies contextualized in project specifications.</p>
      </abstract>
      <kwd-group>
        <kwd>eol&gt;Ontologies</kwd>
        <kwd>privacy</kwd>
        <kwd>accountability</kwd>
        <kwd>risk assessment</kwd>
      </kwd-group>
    </article-meta>
  </front>
  <body>
    <sec id="sec-1">
      <title>1. INTRODUCTION</title>
      <p>
        Attention to privacy legislation is an important issue in IT
(information technology) projects to avoid lawsuits and loss of
consumer trust [
        <xref ref-type="bibr" rid="ref1">1</xref>
        ]. The privacy domain in IT and accountable
privacy management (APM) in organizations are explored in
several works, as follows. In [
        <xref ref-type="bibr" rid="ref2">2</xref>
        ] a taxonomy describes concepts
such as collection, processing, dissemination and invasion of
information. Knutson [
        <xref ref-type="bibr" rid="ref3">3</xref>
        ] presents basic principles to create
privacy awareness in software projects. This is done through the
identification of privacy goals that fulfill legal obligations, the
definition of a privacy core team with technical and legal experts
and the creation of guidelines to help developers to become
independent from the privacy experts. Similar concerns for
software design are endorsed within other work on privacy
awareness [
        <xref ref-type="bibr" rid="ref4">4</xref>
        ][
        <xref ref-type="bibr" rid="ref5">5</xref>
        ]. The KAoS Policy Ontologies (KPO) [
        <xref ref-type="bibr" rid="ref6">6</xref>
        ] defines
concepts such as actions, actors, groups, places, entities related to
actions, and policies. An integration of policies relating several
aspects of security is proposed in [
        <xref ref-type="bibr" rid="ref7">7</xref>
        ], including authorization and
privacy into semantic web services. The BDSG ontology,
mapping law statements to a machine interpretable language is
presented in [
        <xref ref-type="bibr" rid="ref8">8</xref>
        ] as a way to enforce privacy in enterprises using
ontologies to generate XACML [
        <xref ref-type="bibr" rid="ref9">9</xref>
        ] policies. Hecker [
        <xref ref-type="bibr" rid="ref10">10</xref>
        ] argues
that ontologies on the privacy field must enable interoperability,
determine the privacy level of a transaction and guide the
implementation of privacy functionalities without requiring
expertise from the domain. Hecker creates an ontology using
terms from privacy notions and concepts from the European
Parliament Directive 95/46/EC11. Hu [
        <xref ref-type="bibr" rid="ref11">11</xref>
        ] proposes that the
semantic model for EPAL privacy policies can be expressed as a
variety of combinations of ontologies and rules.
      </p>
      <p>Considering the importance of a proper representation of relevant
rules formulated for handling personal information, described in
laws, guidelines, policies, and other normative sources, we
propose an ontology describing data privacy risk related concepts,
based on project actions. In particular, we address the appropriate
usage of information under a set of rules based on the
identification of privacy risks when dealing with sensitive
information. An OWL ontology infers risks in terms of actions of
software projects and the effect of these actions over sensitive
information.
2. REPRESENTING PRIVACY RISKS
Our model includes concepts, such as personally identifiable
information (PII), sensitive information, user actions, location,
and risk levels. Restrictions and constructors to classify actions in
risk actions are described through object properties. Figure 1
shows some of the relevant identified classes.</p>
      <p>These are common concepts in documents, laws and guidelines of
the domain for privacy assurance and accountable software
development1. Properties are used to relate actions to contextual
information, examples are:</p>
      <p>Information Transfer has origin Country
Information Transfer has destination Country
PII is sensitive information in location Geo
Action involves information Information</p>
      <p>
        Action has secondary action Action
Based on Argentina’s provision [
        <xref ref-type="bibr" rid="ref12">12</xref>
        ], which presents a
classification of risks as low, moderate and high, we exemplify
risk inference as follows. Figure 2 shows Risk_Action classes.
      </p>
      <p>In our model, privacy risks are inferred from project related
information. Consider an instance of a project in the ontology,
which refers to actions that manipulate information, such as name,
address and social security number. This project instance is
asserted using the relations: involves action, involves
information, has origin, has destination, and is sensitive
information in location, as shown below.</p>
      <p>project involves action
information access
information transfer
information access involves information
name
address
social security number
information transfer involves information
name
address
social security number
information transfer has origin</p>
      <p>USA
information transfer has destination</p>
      <p>Portugal
social security number is sensitive information in location</p>
      <p>USA
With these facts asserted in the ontology, an instance involving
social security number will be classified as Sensitive
Information in the USA as a consequence of a SWRL codified
rule. In this way, the action will be inferred as high risk action:
Sensitive Information Access and Sensitive Information
Transfer.</p>
    </sec>
    <sec id="sec-2">
      <title>3. FINAL REMARKS</title>
      <p>Ontologies on the privacy domain are useful to provide ways to
share vocabulary and better understand a particular domain and its
related concepts. Our research is aimed at building models that
infer risks automatically from the specification of project features.
Such knowledge intensive areas require advanced knowledge
management technologies. A privacy core team is necessary to
create and maintain such systems based on dynamically changing
knowledge. Our model presents concepts and relations where
actions involving data related to personal information and their
1 A hyperbolic view of the ontology is available at
http://www.inf.pucrs.br/~ontolp/Visualizacao/Privacy_Risks/Privacy_risks.html.
contexts (time, place) are related to risks. The proposed approach
is intended to guide managers with risk assessment. The model is
also designed to help privacy experts to formalize risky situations
in organizations. As future work we plan to map our concepts to
other similar ontologies, linking for instance, our action concepts
to action concepts of KAoS. We are also considering the
processing of textual knowledge sources such as laws and
guidelines to ease the identification of relevant domain
information.</p>
    </sec>
  </body>
  <back>
    <ref-list>
      <ref id="ref1">
        <mixed-citation>
          [1]
          <string-name>
            <surname>Mont</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Thyne</surname>
          </string-name>
          , R.:
          <article-title>Privacy policy enforcement in enterprises with identity management solutions</article-title>
          .
          <source>In: PST '06</source>
          , vol.
          <volume>380</volume>
          , pp.
          <fpage>1</fpage>
          --
          <lpage>12</lpage>
          . ACM, New York (
          <year>2006</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref2">
        <mixed-citation>
          [2]
          <string-name>
            <surname>Solove</surname>
            ,
            <given-names>D. J.:</given-names>
          </string-name>
          <article-title>A Taxonomy of Privacy</article-title>
          . University of Pennsylvania Law Review, vol.
          <volume>154</volume>
          , no.
          <issue>3</issue>
          , p.
          <fpage>477</fpage>
          , (
          <year>2006</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref3">
        <mixed-citation>
          [3]
          <string-name>
            <surname>Knutson</surname>
            ,
            <given-names>T. R.</given-names>
          </string-name>
          <year>2007</year>
          .
          <article-title>Building Privacy into Software Products</article-title>
          and
          <article-title>Services</article-title>
          .
          <source>IEEE Security and Privacy</source>
          , vol.
          <volume>5</volume>
          , no.
          <issue>3</issue>
          , pp.
          <fpage>72</fpage>
          --
          <lpage>74</lpage>
          (
          <year>2007</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref4">
        <mixed-citation>
          [4]
          <string-name>
            <surname>Duncan</surname>
            ,
            <given-names>G.</given-names>
          </string-name>
          :
          <article-title>ENGINEERING: Privacy By Design</article-title>
          .
          <source>Science</source>
          <volume>317</volume>
          (
          <issue>5842</issue>
          ),
          <volume>1178</volume>
          , (
          <year>2007</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref5">
        <mixed-citation>
          [5]
          <string-name>
            <surname>Ye</surname>
            ,
            <given-names>X.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Zhu</surname>
            ,
            <given-names>Z.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Peng</surname>
            ,
            <given-names>Y.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Xie</surname>
            ,
            <given-names>F.</given-names>
          </string-name>
          :
          <article-title>Privacy Aware Engineering: A Case Study</article-title>
          .
          <source>Journal of Software</source>
          , vol.
          <volume>4</volume>
          , no.
          <issue>3</issue>
          , pp.
          <fpage>218</fpage>
          --
          <lpage>225</lpage>
          (
          <year>2009</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref6">
        <mixed-citation>
          [6]
          <string-name>
            <surname>Bradshaw</surname>
            ,
            <given-names>J.</given-names>
          </string-name>
          et al.:
          <article-title>Representation and reasoning for DAML-based policy and domain services in KAoS and nomads</article-title>
          . In: AAMAS '
          <fpage>03</fpage>
          .
          <string-name>
            <surname>Melbourne</surname>
          </string-name>
          ,
          <string-name>
            <surname>Australia</surname>
          </string-name>
          (
          <year>2003</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref7">
        <mixed-citation>
          [7]
          <string-name>
            <surname>Kagal</surname>
            ,
            <given-names>L.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Paoucci</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Srinivasan</surname>
            ,
            <given-names>N.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Denker</surname>
            ,
            <given-names>G.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Finin</surname>
            ,
            <given-names>T.</given-names>
          </string-name>
          , and
          <string-name>
            <surname>Sycara</surname>
          </string-name>
          , T.:
          <article-title>Authorization and Privacy for Semantic Web Services</article-title>
          ,
          <source>In: AAAI Spring Symposium on Semantic Web Services</source>
          (
          <year>2004</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref8">
        <mixed-citation>
          [8]
          <string-name>
            <surname>Abou-Tair</surname>
            ,
            <given-names>D.D.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Berlik</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Kelter</surname>
            ,
            <given-names>U.</given-names>
          </string-name>
          :
          <article-title>Enforcing Privacy by Means of an Ontology Driven XACML Framework</article-title>
          .
          <source>In: IAS</source>
          <year>2007</year>
          ,
          <source>Third International Symposium on Information Assurance and Security</source>
          , pp.
          <fpage>279</fpage>
          --
          <lpage>284</lpage>
          (
          <year>2007</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref9">
        <mixed-citation>
          [9]
          <string-name>
            <given-names>OASIS</given-names>
            <surname>XACML Technical</surname>
          </string-name>
          <article-title>Committee</article-title>
          .:
          <string-name>
            <surname>eXtensible Access Control Markup Language</surname>
          </string-name>
          (
          <year>2003</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref10">
        <mixed-citation>
          [10]
          <string-name>
            <surname>Hecker</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Dillon</surname>
            ,
            <given-names>T. S.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Chang</surname>
            ,
            <given-names>E.</given-names>
          </string-name>
          <article-title>Privacy Ontology Support for E-Commerce, IEEE Internet Computing</article-title>
          , vol.
          <volume>12</volume>
          , no.
          <issue>2</issue>
          , pp.
          <fpage>54</fpage>
          --
          <lpage>61</lpage>
          (
          <year>2008</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref11">
        <mixed-citation>
          [11]
          <string-name>
            <surname>Hu</surname>
            ,
            <given-names>Y.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Guo</surname>
            ,
            <given-names>H.</given-names>
          </string-name>
          , and
          <string-name>
            <surname>Lin</surname>
            ,
            <given-names>A. G.</given-names>
          </string-name>
          :
          <article-title>Semantic Enforcement of Privacy Protection Policies via the Combination of Ontologies and Rules</article-title>
          .
          <source>In: SUTC</source>
          <year>2008</year>
          , vol.
          <volume>00</volume>
          . IEEE Computer Society, Washington, DC, pp.
          <fpage>400</fpage>
          --
          <lpage>407</lpage>
          (
          <year>2008</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref12">
        <mixed-citation>
          [12]
          <string-name>
            <surname>Ministerio de Justicia</surname>
          </string-name>
          , Seguridad e Derechos Humanos, Presidencia de la Nación Argentina. Dirección
          <string-name>
            <surname>Nacional de Protección de Datos Personales</surname>
          </string-name>
          (
          <year>2006</year>
          )
        </mixed-citation>
      </ref>
    </ref-list>
  </back>
</article>