<!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>Feb</journal-title>
      </journal-title-group>
    </journal-meta>
    <article-meta>
      <title-group>
        <article-title>Access Control Policy Administration supporting User-de ned Privacy Preferences</article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="author">
          <string-name>Thomas Trojer</string-name>
          <email>thomas.trojer@uibk.ac.at</email>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Ruth Breu (Supervisor)</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <aff id="aff0">
          <label>0</label>
          <institution>Institute of Computer Science, University of Innsbruck</institution>
          ,
          <country country="AT">Austria</country>
        </aff>
      </contrib-group>
      <pub-date>
        <year>2012</year>
      </pub-date>
      <volume>15</volume>
      <issue>2012</issue>
      <abstract>
        <p>The protection of medical records is understood to be an issue related to privacy and therefore closely bound to the patient her/himself, playing a crucial role in networked electronic health-care. Awarding users to have control over personal data stored and processed by information systems is important as it allows a user to communicate individual privacy concerns. Still, users self-maintaining controls of access to their personal data poses challenges regarding its implementation. A major issue is that users are typically non-security experts and have only limited knowledge of the context domain. Regarding our use-case patients may not be fully familiar with all activities related to information processing e.g., during a medical treatment, therefore not able to properly decide on privacy and authorization measures. In our work we discuss the development of access control authoring tools to allow nonexpert users to create, analyse and adjust personal privacy policies. We propose the integration of domain aspects into the development process of such tools. With extended knowledge about the domain the creation of policy rules can be bound to high-level activity descriptions and policy analysis can be performed in a domain-aware manner.</p>
      </abstract>
    </article-meta>
  </front>
  <body>
    <sec id="sec-1">
      <title>Motivation</title>
      <p>Modern information systems are able to store, retrieve an process vast amounts of
data. Further extended by networking capabilities and driven by the increased
personal use of information technology a wide range of data can be collected
and combined to form new processable content. The collection of data can be
critical without means of regulating access to it when requests for provisioning or
processing are made. With respect to the actual use-case, data can be considered
as e.g., con dential according to its content or sensitive in terms of identifying
individual persons.</p>
      <p>In a common use-case scenario a person responsible for security matters, like
an administrator, de nes access control policies which constitute appropriate
security measures for all protected resources. In the case of person-identifying
information, such policies do not necessarily re ect the conception of the
identied individual on how to access-protect these information. By declaring privacy
as a right about information self-determination, e.g., within the European Data</p>
      <p>Protection Directive1 an individual user is awarded a distinguished role within
privacy management processes. This can be interpreted as the required ability
of a user to in uence the de nition of enforceable access control policies which
constitute data privacy related to the user's personal conception.
1.1</p>
      <p>Use-case: Patient-centric Electronic Health-care
We consider a use-case from the Austrian e-Health initiative which started in
2006 as a governmental workgroup. A central goal of this initiative is the
establishment of a distributed shared electronic health-record for all citizens of
Austria. It has been shown that a holistic medical history of a patient improves
the health-care infrastructure from an economical perspective as well as from
a viewpoint of e ectiveness regarding medical treatments. Still, because of the
high degree of sensitivity which is observed in most medical data, privacy is a
concern of utmost importance to be tackled. In the context of this initiative we
want to contribute methods with a strong focus on patient-centricity by
establishing personal control over privacy-relevant health data.
2</p>
    </sec>
    <sec id="sec-2">
      <title>Problem statement</title>
      <p>A general problem question can be raised as follows: How can a user, considered
a non-security and non-domain expert, be supported during the declaration of
access control policies in a way that she/he is aware about consequences to certain
evaluation criteria, rst and foremost personal privacy and e.g., the e ectiveness
of the information system. Two potential user actions can be derived from this
problem question. First, a user has to be provided with tools to create access
control policies and second a currently active policy has to be visualized in a way
that the user can understand how it in uences the information ow of the system.
Visualizing active policies is especially important to allow a user to reconsider
the policies' appropriateness. Therefore a user is able to adjust a policy in a way
so that it ts her/his personal conception of access control.
3</p>
    </sec>
    <sec id="sec-3">
      <title>Contributions</title>
      <p>We contribute a framework using domain characteristics to develop user
interfaces for access control policy authoring. Further this framework includes a policy
analysis component capable of providing users with feedback during their actions
within the policy authoring process. A central step to be performed is therefore
the modeling of domain entities and their relationships as well as the
annotation of the domain model with attributes from the access control domain. In
the context of our use-case we identify e.g., a medical practitioner or pharmacist
as subjects of access control, whereas medical records or referrals are considered
1see Directive 95/46/EC, http://ec.europa.eu/justice/policies/privacy/
law/index_en.htm
resources to be protected by access control. A basic API to work with domain
entities and access control policy elements can be generated from that model.</p>
      <p>
        Based on this model we designed a generic authoring process [
        <xref ref-type="bibr" rid="ref10">10</xref>
        ] that leads
to the creation of access control policies. This process allows for policy creation
and adaptation, which can be triggered by the user.
      </p>
      <p>In this work we want to emphasize two research directions in order to reach
our objective of providing a non-expert user with access control authoring tools
to establish privacy policies. These are described in the following sections.
3.1</p>
      <p>
        Scenario-based Access Control Policy Authoring
John Carroll [
        <xref ref-type="bibr" rid="ref3">3</xref>
        ] coined the term scenarios as stories about people and their
activities, e.g., related to the tasks of their work. We propose scenario-based
authoring as a method to create and further visualize access control policies in
a usable way. This is important as users typically lack of knowledge about the
underlying access control concepts and therefore have to be supported during
the authoring process [
        <xref ref-type="bibr" rid="ref12 ref2">12, 2</xref>
        ].
      </p>
      <p>
        The rst step of our approach regards the elicitation of typical working
activities of the domain. Only working activities which involve information processing
in an arbitrary way are considered as they can be related to access control. In
our context we tackled this step by performing a case-study about stakeholders
and some of their activities in the domain of electronic health records in Austria
[
        <xref ref-type="bibr" rid="ref9">9</xref>
        ]. Next the selected working activities have to be translated to our template
language. A template consists of the attributes identifying and describing the
working activity in natural language and further a set of access control rules
which are written to the user policy once a template instance is executed. User
control is established via user interface form input elds which represent domain
and environment information (e.g. time, date, location or cardinalities) and are
bound to variables used within the policy rules of the template. Fig. 1 shows
a basic scenario from our electronic health-care use-case, namely, the selection
of a family practitioner performed by a citizen stakeholder. In this example two
inputs are provided, the name of the family practitioner and whether all
documents (i.e. also all future ones) shall be accessible or only the ones currently
stored about a patient. By executing a template instance one permit-rule is
created allowing the selected practitioner (i.e. the subject of the access control
target) to access patient health records. Similarly a query can be formed to
visualize a selected family practitioner to the user by asking who is permitted to
read all documents.
      </p>
      <p>The template language including access control rules and queries are
currently developed and described in a formal way. With this work we target the
eld of usable security.
3.2</p>
      <p>Domain-based Access Control Policy Analysis
We see two situations where a user may be encouraged to reconsider her/his
access control settings and to adjust them if necessary. First, if the representation
of currently active settings can be provided in a readable way the user is able to
detect di erences between these settings and her/his intended settings. Therefore
we propose to use scenario-based policy templates (see Section 3.1) to increase
understandability of a user policy.</p>
      <p>
        Besides a user adjusting her/his policy based on a manual interpretation,
policies may also carry con icts or in uence arbitrary system properties and
the user in a negative way. Therefore we identify a second situation for
adjusting a policy, namely triggered by feedback of a performed policy analysis. In
general policy analysis is extensively discussed in literature (see e.g., [
        <xref ref-type="bibr" rid="ref1 ref7 ref8">7, 8, 1</xref>
        ]),
but mainly based on con ict detection regarding the interplay of di erent policy
rules. Work, as e.g., done by Michael LeMay [
        <xref ref-type="bibr" rid="ref6">6</xref>
        ] and Katie Fisler [
        <xref ref-type="bibr" rid="ref4">4</xref>
        ] consider a
policy model together with the domain where policies are deployed on. Based
on these works we propose the de nition of high-level evaluation criteria which
interact. These criteria can be attached to the policy authoring activity leading
to a balancing act during access control con guration in order to satisfy best all
evaluation criteria. In our previous work [
        <xref ref-type="bibr" rid="ref9">9</xref>
        ] we considered privacy and
information system e ectiveness as evaluation criteria to be balanced. There, based on
a domain model and models for each evaluation criteria, domain-aware analysis
rules integrating all evaluation aspects can be generated.
      </p>
      <p>For our use-case we de ned a trivial privacy model consisting of permissions
and restrictions and an information system e ectiveness model. This e
ectiveness model consists of personal relationships between subjects and needs-to-know
relations between subjects and protected resources (see Fig. 2). Regarding
privacy the lack of a permission can be interpreted as increased privacy. On the
other hand the absence of one or both the personal relationship or the
needsto-know relation decreases the need of the information system to be e ective
towards these attributes. E.g. a family practitioner earns an associated personal
relationship connecting her/him to the patient, further needs-to-know relations
to all patient's data are established. Now, a patient restricting this practitioner
from reading any data would obviously contribute to the her/his privacy, still
the health-care information system would not e ectively operate anymore. An
e ectiveness warning with detailed information about its reasons is provided to
the user, which in turn may react on it by adjusting her/his settings.</p>
      <p>&lt;&lt;stereotype&gt;&gt;
Personal relationship
[Association, Class]
from</p>
      <p>to
&lt;&lt;stereotype&gt;&gt;
Subject
[Class]
Core policy entities
defined for
&lt;&lt;stereotype&gt;&gt;
Resource
[Class]
&lt;&lt;stereotype&gt;&gt;</p>
      <p>Access target
defined by
defined by
defined by
Effectiveness model
&lt;&lt;stereotype&gt;&gt;
Needs to know
[Association]
references
refined by
&lt;&lt;stereotype&gt;&gt;</p>
      <p>Action
[Class]
based on
e.g. conditions,
obligations, etc.
&lt;&lt;enumeration&gt;&gt;
Access decision
Permit
Deny
In an ongoing project with our industry partner ITH-icoserve for healthcare
technology, a subsidiary company of Siemens and a local hospital provider, we
are developing an access control policy authoring application based on a secured
IHE-based infrastructure 2 for shared patient health-records.</p>
      <p>
        Currently we have considered access control enforcement based on IHE XDS2
and auxiliary pro les [
        <xref ref-type="bibr" rid="ref10 ref5">5, 10</xref>
        ], for which our industry partner is an implementer
and tested for conformity and interoperability. Further a prototypical
authoring portal application was developed [
        <xref ref-type="bibr" rid="ref9">9</xref>
        ]. In order to let the policy authoring
re ect the actual domain, we employ a model-driven process which generates a
policy API based on a domain and access control model [
        <xref ref-type="bibr" rid="ref11">11</xref>
        ]. Our approach for
domain-aware policy analysis, which is based on balancing of evaluation criteria
will also build upon the policy API. Evaluation criteria we currently consider
is the correlation between permitted or restricted access, personal relationships
between stakeholders and the importance to have certain data available to
speci c stakeholders. In future work we also want to study other criteria, e.g., the
purpose-relatedness of permitted data accesses.
      </p>
      <p>2see IHE IT-Infrastructure
Technical_Framework/index.cfm#IT</p>
      <sec id="sec-3-1">
        <title>Technical</title>
      </sec>
      <sec id="sec-3-2">
        <title>Framework,</title>
        <p>http://www.ihe.net/</p>
        <p>Generally we apply methods from design science to develop the
aforementioned artifacts for patient-controlled access control. Usable methods for
authoring and analysis of policies are our main focus. Further we will perform
additional case studies to justify the application of these approaches within our
use-case. As human interaction with the authoring application is a central part
of this work, therefore we will also conduct a usability study to evaluate the
usefulness of working scenarios and templates to maintain access control policies.
A fully features authoring portal application is planned to be integrated into a
health information system built by our industry partner and deployed to our
regional health-care infrastructure. This will consist of templates for adapting
authorization policies as well as policy analysis to inform a citizen about the
consequences of certain access control settings. Finally the deployed system has
to be evaluated regarding its performance and user acceptance.</p>
      </sec>
    </sec>
  </body>
  <back>
    <ref-list>
      <ref id="ref1">
        <mixed-citation>
          1.
          <string-name>
            <given-names>E.</given-names>
            <surname>Bertino</surname>
          </string-name>
          ,
          <string-name>
            <given-names>B.</given-names>
            <surname>Catania</surname>
          </string-name>
          , E. Ferrari, and
          <string-name>
            <given-names>P.</given-names>
            <surname>Perlasca</surname>
          </string-name>
          .
          <article-title>A logical framework for reasoning about access control models</article-title>
          .
          <source>In Proceedings of the sixth ACM symposium on Access control models and technologies</source>
          ,
          <source>SACMAT '01</source>
          ,
          <year>2001</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref2">
        <mixed-citation>
          2.
          <string-name>
            <given-names>S.</given-names>
            <surname>Brosto</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M. A.</given-names>
            <surname>Sasse</surname>
          </string-name>
          ,
          <string-name>
            <given-names>D.</given-names>
            <surname>Chadwick</surname>
          </string-name>
          ,
          <string-name>
            <given-names>J.</given-names>
            <surname>Cunningham</surname>
          </string-name>
          ,
          <string-name>
            <given-names>U.</given-names>
            <surname>Mbanaso</surname>
          </string-name>
          , and
          <string-name>
            <given-names>S.</given-names>
            <surname>Otenko. R-What</surname>
          </string-name>
          ?
          <article-title>Development of a Role-Based Access Control (RBAC) Policy-Writing Tool for e-Scientists</article-title>
          .
          <source>Software: Practice and Experience</source>
          ,
          <volume>35</volume>
          (
          <issue>9</issue>
          ):
          <volume>835</volume>
          {
          <fpage>856</fpage>
          ,
          <year>July 2005</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref3">
        <mixed-citation>
          3.
          <string-name>
            <given-names>J.</given-names>
            <surname>Carroll</surname>
          </string-name>
          .
          <article-title>Five reasons for scenario-based design</article-title>
          .
          <source>Interacting with Computers</source>
          ,
          <volume>13</volume>
          (
          <issue>1</issue>
          ):
          <volume>43</volume>
          {
          <fpage>60</fpage>
          ,
          <year>2000</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref4">
        <mixed-citation>
          4.
          <string-name>
            <given-names>K.</given-names>
            <surname>Fisler</surname>
          </string-name>
          and
          <string-name>
            <given-names>S.</given-names>
            <surname>Krishnamurthi</surname>
          </string-name>
          .
          <article-title>A model of triangulating environments for policy authoring</article-title>
          .
          <source>In Proceeding of the 15th ACM symposium on Access control models and technologies</source>
          ,
          <source>SACMAT '10</source>
          ,
          <year>2010</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref5">
        <mixed-citation>
          5.
          <string-name>
            <given-names>B.</given-names>
            <surname>Katt</surname>
          </string-name>
          ,
          <string-name>
            <given-names>T.</given-names>
            <surname>Trojer</surname>
          </string-name>
          ,
          <string-name>
            <given-names>R.</given-names>
            <surname>Breu</surname>
          </string-name>
          ,
          <string-name>
            <given-names>T.</given-names>
            <surname>Schabetsberger</surname>
          </string-name>
          , and
          <string-name>
            <given-names>F.</given-names>
            <surname>Wozak</surname>
          </string-name>
          .
          <article-title>Meeting ehr security requirements: Seaas approach</article-title>
          .
          <source>In EFMI STC</source>
          <year>2010</year>
          . Accepted,
          <year>June 2010</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref6">
        <mixed-citation>
          6.
          <string-name>
            <surname>M. LeMay</surname>
            ,
            <given-names>O.</given-names>
          </string-name>
          <string-name>
            <surname>Fatemieh</surname>
            , and
            <given-names>C. A.</given-names>
          </string-name>
          <string-name>
            <surname>Gunter</surname>
          </string-name>
          .
          <article-title>PolicyMorph: interactive policy transformations for a logical attribute-based access control framework</article-title>
          .
          <source>In Proceedings of the 12th ACM symposium on Access control models and technologies</source>
          ,
          <source>SACMAT '07</source>
          ,
          <year>2007</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref7">
        <mixed-citation>
          7.
          <string-name>
            <given-names>E.</given-names>
            <surname>Lupu</surname>
          </string-name>
          and
          <string-name>
            <given-names>M.</given-names>
            <surname>Sloman</surname>
          </string-name>
          .
          <article-title>Con icts in Policy-based Distributed Systems Management</article-title>
          .
          <source>IEEE Transactions on Software Engineering</source>
          ,
          <volume>25</volume>
          ,
          <year>1999</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref8">
        <mixed-citation>
          8.
          <string-name>
            <surname>J. D.</surname>
          </string-name>
          <article-title>Mo ett and M. S. Sloman. Policy con ict analysis in distributed system management</article-title>
          ,
          <year>1993</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref9">
        <mixed-citation>
          9.
          <string-name>
            <given-names>T.</given-names>
            <surname>Trojer</surname>
          </string-name>
          ,
          <string-name>
            <given-names>B.</given-names>
            <surname>Katt</surname>
          </string-name>
          ,
          <string-name>
            <given-names>T.</given-names>
            <surname>Schabetsberger</surname>
          </string-name>
          ,
          <string-name>
            <given-names>R.</given-names>
            <surname>Breu</surname>
          </string-name>
          , and
          <string-name>
            <given-names>R.</given-names>
            <surname>Mair</surname>
          </string-name>
          .
          <article-title>Considering privacy and e ectiveness of authorization policies for shared electronic health records</article-title>
          .
          <source>In ACM IHI</source>
          <year>2012</year>
          (in press),
          <year>2012</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref10">
        <mixed-citation>
          10.
          <string-name>
            <given-names>T.</given-names>
            <surname>Trojer</surname>
          </string-name>
          ,
          <string-name>
            <given-names>B.</given-names>
            <surname>Katt</surname>
          </string-name>
          ,
          <string-name>
            <given-names>T.</given-names>
            <surname>Schabetsberger</surname>
          </string-name>
          ,
          <string-name>
            <given-names>R.</given-names>
            <surname>Mair</surname>
          </string-name>
          , and
          <string-name>
            <given-names>R.</given-names>
            <surname>Breu</surname>
          </string-name>
          .
          <article-title>The Process of Policy Authoring of Patient-controlled Privacy Preferences</article-title>
          . In eHealth
          <year>2011</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref11">
        <mixed-citation>
          11.
          <string-name>
            <given-names>T.</given-names>
            <surname>Trojer</surname>
          </string-name>
          ,
          <string-name>
            <given-names>B.</given-names>
            <surname>Katt</surname>
          </string-name>
          ,
          <string-name>
            <given-names>F.</given-names>
            <surname>Wozak</surname>
          </string-name>
          , and
          <string-name>
            <given-names>T.</given-names>
            <surname>Schabetsberger</surname>
          </string-name>
          .
          <article-title>An Authoring Framework for Security Policies: A Use-case within the Healthcare Domain</article-title>
          .
          <source>In eHealth</source>
          <year>2010</year>
          ,
          <year>2010</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref12">
        <mixed-citation>
          12.
          <string-name>
            <given-names>T.</given-names>
            <surname>Whalen</surname>
          </string-name>
          ,
          <string-name>
            <given-names>D.</given-names>
            <surname>Smetters</surname>
          </string-name>
          , and
          <string-name>
            <given-names>E. F.</given-names>
            <surname>Churchill</surname>
          </string-name>
          .
          <article-title>User experiences with sharing and access control. In CHI '06 extended abstracts on Human factors in computing systems</article-title>
          ,
          <source>CHI EA '06</source>
          , pages
          <fpage>1517</fpage>
          {
          <fpage>1522</fpage>
          , New York, NY, USA,
          <year>2006</year>
          . ACM.
        </mixed-citation>
      </ref>
    </ref-list>
  </back>
</article>