![]() |
||||||||||||||||||||
EnCoRe News August 2011 |
||||||||||||||||||||
To access the hyperlinked material, read this newsletter online at http://tinyurl.com/3mowrrk |
||||||||||||||||||||
| Scroll through this issue to find the following... | ||||||||||||||||||||
| |
||||||||||||||||||||
| The EnCoRe R&D Service Framework for
Privacy Management |
HP Labs, Research and Development related to
Sticky Policies
|
8th FTRA International conference on Secure and Trust
Computing data management and Applications (STA2011) |
EnCoRe and the Identity Assurance programme | |||||||||||||||||
| Tags | Focus | EnCoRe Milestones | ||||||||||||||||||
![]() |
|
On 17th August 2011,
the EnCoRe implementation proved itself worthy. In a meeting held at HW's offices in July, WP5 (Compliance) and WP6 (Implementation) came together to agree a format for testing the core logic of EnCoRe's consent management controls. The process defined, allows for an extensible suite of testcases to be developed which can fully reset, configure and test the consent enforced access controls provided by the the EnCoRe core. This also includes testing the capabilities of notification, auditing, data sharing and flowdown of changed data subject consents and choices to shared data. This activity is in perfect line for validation of the EnCoRe core implementation which is now available as a fully integrated and operational prototype. |
||||||||||||||||||
![]() |
![]() |
![]() |
|
|||||||||||||||||
ContactTo contact us, read about the project, get to know the participants and download papers and deliverables, visit the EnCoRe website: www.encore-project.infoWe are Twittering, Follow us! ![]() |
Secondly, this Service Framework aims to provide a platform to HP Labs (and EnCoRe partners) for experimentation about innovative privacy management and consent/revocation solutions. Specifically, HP Labs are planning to use it to develop and deploy advanced solutions for: the tracking of whereabouts of personal data (via an enhanced version of the Data Registry component); the management of sticky policies by means of a variety of possible technical approaches. It will allow HP Labs to experiment with more complex scenarios than the ones investigated in the two current EnCoRe Case Studies (that are quite constraining). For example, we can consider more complex and richer interactions between multiple parties. Thirdly this Service Framework aims to provide a quick and agile platform to develop demonstrators for a variety of needs, including early prototypes of the overall system for the EnCoRe engagement with the Cabinet Office Identity Assurance Programme [3]. Finally, this Service Framework can be used as the foundation of an Open Source release of the EnCoRe toolkits. This option is currently being discussed within EnCoRe and various involved organisations: a decision will be made towards the end of 2011. [M. Casassa Mont, S. Pearson, V. Sharma, M. Filz] ![]() |
|
|
|||||||||||||||||
|
HP Labs Research and Development related to Sticky Policies
Our general approach is as follows, with respect to the EnCoRe architectural components: part of the user privacy choices are embedded into sticky policies by the User Consent and Revocation Assistant to ensure that they will be fulfilled by third parties receiving the data; the Privacy Enforcement and Obligation Management component enforces sticky policies associated with data along with any other policies mandated by the organisation; the External Workflow Manager interacts with the Data Registry to update data locations and related consent information, and to control onward flow. The sticky policies sent out from the EnCoRe system to other organizations specify the purposes of using the data and any obligations and prohibitions (including notification and deletion after a certain time), that have been specified by the user in their C&R preferences associated with that data. The Trust Authority functionality is distributed in the sense that the EnCoRe External Workflow Manager component controls sharing of the information associated with the sticky policies, and the Data Registry records how it has been distributed. Optionally, an external TA can also be involved to perform some additional checks if the External Workflow Manager is not able to make those directly. At the receiving party side, if EnCoRe enabled, there is a translation of the requirements expressed in the sticky policies into access and obligation policies into local access control and obligations policies to be enforced, along with the original data subjects’ privacy choices. If the receiving parties do not have EnCoRe compliant systems, then the External Workflow Manager assesses the extent to which the data may be released for a given purpose and controls release of the data accordingly, potentially sanitizing it if needed. In order to revoke consent, the users use the same mechanisms to edit their consent preferences as those they used to set them in the first place, i.e. via web-based User Interfaces: these preferences are automatically propagated throughout the EnCoRe system as well as beyond it, in a batched manner, to the other organizations involved, by leveraging the information stored in the Data Registry. This approach can be applied recursively, for a chain of organizations disclosing information between them. We have already surveyed existing techniques for sticky policy functionality and extended this to develop the core mechanisms for the management of sticky policies within the EnCoRe project and are currently implementing a PKI-based implementation of the required mechanisms. [S, Pearson, M. Casassa Mont, R. Saeed]
8th FTRA
International
Conference on Secure and Trust Computing, data
management, and Applications (STA 2011)The STA 2011 conference addressed the various theories and practical applications of secure and trust computing and data management in future environments and was the first conference after the merger of the SSDU, UbiSec and TRUST symposiums. It was held at Loutraki, Greece from 28th until 30th June 2011. As part of the conference, a one-day Security and Trust for Applications in Virutalised Environments (STAVE) workshop was held in order to focus on policy management issues within the cloud. This was of particular interest to EnCoRe as our mechanisms can apply in this context. Issues addressed by the conference included:
Siani Pearson (from EnCoRe) gave two presentations and chaired half the workshop. Her first presentation was on how accountability in the cloud can be enhanced via sticky policies, and this included discussion of what EnCoRe is and how we are implementing sticky policy techniques within EnCoRe. The co-authors on this paper were Marco Casassa Mont and Gina Kounga. Her second presentation described how natural language techniques can be classified, and furthermore used in a repeatable lifecycle linked to automated policy enforcement. Again, it was explained how EnCoRe-related mechanisms may be used as part of this process. The co-authors on this paper were Nick Papanikolaou and Marco Casassa Mont. There were a number of other papers presented of interest to EnCoRe, particularly relating to work carried out on policy management within the EU PASSIVE project.
Further details about the conference and workshop may be obtained via http://www.ftrai.org/sta2011/ and http://ict-passive.eu/stave/ respectively. [S. Pearson] ![]()
|
![]() |
||||||||||||||||||
|
||||