topic.security_policy.group.bib

@comment{{This file has been generated by bib2bib 1.96}}
@comment{{Command line: /usr/bin/bib2bib -c topic:"security_policy" -ob topic.security_policy.group.bib groupbib.bib}}
@phdthesis{MoritzBeckerPhD,
  author = {Moritz Y. Becker},
  title = {Cassandra: flexible trust management and its application to electronic health records},
  school = {University of Cambridge},
  year = {2005},
  optkey = {},
  opttype = {},
  optaddress = {},
  month = oct,
  note = {Published as UCAM-CL-TR-648},
  optannote = {},
  pdf = {http://www.cl.cam.ac.uk/TechReports/UCAM-CL-TR-648.html},
  abstract = {
The emergence of distributed applications operating on large-scale, heterogeneous and decentralised networks poses new and challenging problems of concern to society as a whole, in particular for data security, privacy and confidentiality. Trust management and authorisation policy languages have been proposed to address access control and authorisation in this context. Still, many key problems have remained unsolved. Existing systems are often not expressive enough, or are so expressive that access control becomes undecidable; their semantics is not formally specified; and they have not been shown to meet the requirements set by actual real-world applications.

This dissertation addresses these problems. We present Cassandra, a role-based language and system for expressing authorisation policy, and the results of a substantial case study, a policy for a national electronic health record (EHR) system, based on the requirements of the UK National Health Service’s National Programme for Information Technology (NPfIT).

Cassandra policies are expressed in a language derived from Datalog with constraints. Cassandra supports credential-based authorisation (eg between administrative domains), and rules can refer to remote policies (for credential retrieval and trust negotiation). The expressiveness of the language (and its computational complexity) can be tuned by choosing an appropriate constraint domain. The language is small and has a formal semantics for both query evaluation and the access control engine.

There has been a lack of real-world examples of complex security policies: our NPfIT case study fills this gap. The resulting Cassandra policy (with 375 rules) demonstrates that the policy language is expressive enough for a real-world application. We thus demonstrate that a general-purpose trust management system can be designed to be highly flexible, expressive, formally founded and meet the complex requirements of real-world applications. 
},
  topic = {security_policy}
}
@techreport{UCAM-CL-TR-628,
  author = {Becker, Moritz Y.},
  title = {{A formal security policy for an NHS electronic health
         	   record service}},
  year = 2005,
  month = mar,
  opturl = {http://www.cl.cam.ac.uk/techreports/UCAM-CL-TR-628.pdf},
  institution = {University of Cambridge, Computer Laboratory},
  number = {UCAM-CL-TR-628},
  topic = {security_policy},
  abstract = {
  The ongoing NHS project for the development of a UK-wide electronic health records service, also known as the ‘Spine’, raises many controversial issues and technical challenges concerning the security and confidentiality of patient-identifiable clinical data. As the system will need to be constantly adapted to comply with evolving legal requirements and guidelines, the Spine’s authorisation policy should not be hard-coded into the system but rather be specified in a high-level, general-purpose, machine-enforceable policy language.

We describe a complete authorisation policy for the Spine and related services, written for the trust management system Cassandra, and comprising 375 formal rules. The policy is based on the NHS’s Output-based Specification (OBS) document and deals with all requirements concerning access control of patient-identifiable data, including legitimate relationships, patients restricting access, authenticated express consent, third-party consent, and workgroup management. },
  pdf = {http://www.cl.cam.ac.uk/techreports/UCAM-CL-TR-628.pdf},
  topic = {security_policy}
}