|
Part I Privacy and Identity Management |
|
|
|
1 An Introduction to Privacy-Enhancing Identity Management |
|
|
3 | (24) |
|
|
|
|
|
|
4 | (2) |
|
1.2 A Scenario -- Alice Goes Shopping |
|
|
6 | (1) |
|
1.3 PRIME Enabled Shopping |
|
|
7 | (10) |
|
1.3.1 Phase 1: Buyer Beware |
|
|
8 | (1) |
|
1.3.2 Phase 2: Pre-sales -- Starting from Maximum Privacy |
|
|
9 | (1) |
|
1.3.3 Phase 3: Ordering- Informed Consent and Purpose Limitation |
|
|
10 | (3) |
|
1.3.4 Phase 4: After-Sales and Delivery -- Retaining Control: Policy Enforcement |
|
|
13 | (1) |
|
1.3.5 Phase 5: Customer Relationship -- Building the Relationship |
|
|
14 | (1) |
|
1.3.6 Phase 6: Beyond Being a Connoisseur -- Alice's Other Identities |
|
|
15 | (2) |
|
|
17 | (3) |
|
1.4.1 Concepts and Human-Computer Interaction |
|
|
18 | (1) |
|
|
18 | (1) |
|
|
19 | (1) |
|
|
20 | (1) |
|
1.5 Requirements for Identity Management Systems |
|
|
20 | (7) |
|
|
23 | (4) |
|
Part II Setting the Stage |
|
|
|
2 Overview and Introduction Part II |
|
|
27 | (6) |
|
|
|
27 | (2) |
|
2.2 An Approach From Three Perspectives |
|
|
29 | (1) |
|
|
30 | (3) |
|
|
33 | (20) |
|
|
|
|
|
|
33 | (1) |
|
3.2 The Concept of (Online) Identity |
|
|
34 | (1) |
|
3.3 Asymmetric Perspectives |
|
|
35 | (3) |
|
3.3.1 The Enterprise-Centric View on Identity Management |
|
|
35 | (1) |
|
3.3.2 A User-Centric View on Identity Management |
|
|
36 | (1) |
|
3.3.3 Combining the Perspectives |
|
|
37 | (1) |
|
3.4 Evolving Identity Management Systems |
|
|
38 | (2) |
|
3.5 Existing Identity Management Applications |
|
|
40 | (3) |
|
|
40 | (1) |
|
|
41 | (1) |
|
|
42 | (1) |
|
3.5.4 Microsoft Cardspace |
|
|
42 | (1) |
|
|
43 | (1) |
|
3.6 Complicating the Online Identity Landscape |
|
|
43 | (7) |
|
3.6.1 The Internet as a Social Environment |
|
|
44 | (1) |
|
3.6.2 Customer Empowerment |
|
|
44 | (1) |
|
3.6.3 Identity-Related Crime and Misbehaviour |
|
|
45 | (1) |
|
3.6.4 The Expanding Internet: Always-On and Everywhere |
|
|
46 | (1) |
|
3.6.5 The Internet of Things and the Citizens of Tomorrow |
|
|
47 | (1) |
|
3.6.6 Identifying the Individual in the Era of the Internet of Things |
|
|
48 | (2) |
|
|
50 | (3) |
|
4 The Need for Privacy-Enhancing Identity Management |
|
|
53 | (20) |
|
|
|
|
|
|
53 | (1) |
|
4.2 Individual Perspective |
|
|
54 | (6) |
|
|
55 | (2) |
|
|
57 | (1) |
|
4.2.3 Personal Development |
|
|
58 | (1) |
|
4.2.4 Behaviour, Health, and Emotions |
|
|
59 | (1) |
|
4.3 Organisational Perspective |
|
|
60 | (4) |
|
|
60 | (3) |
|
4.3.2 Government Services |
|
|
63 | (1) |
|
|
64 | (6) |
|
4.4.1 The Determination of Privacy in Social Context |
|
|
65 | (1) |
|
4.4.2 The Contribution of Privacy-Enhanced IdM to Society |
|
|
66 | (4) |
|
|
70 | (3) |
|
5 Regulating Identity Management |
|
|
73 | (18) |
|
|
|
|
|
|
73 | (1) |
|
5.2 A Brief History of European Data Protection Regulation |
|
|
74 | (5) |
|
5.2.1 The EU Data Protection Directive |
|
|
76 | (2) |
|
5.2.2 The ePrivacy Directive |
|
|
78 | (1) |
|
5.2.3 Other Relevant Directives |
|
|
79 | (1) |
|
5.3 Principles of Data Processing |
|
|
79 | (7) |
|
5.3.1 Principles on Processing of Personal Data |
|
|
80 | (3) |
|
5.3.2 Rights of the Data Subject |
|
|
83 | (2) |
|
5.3.3 Specific Requirements for Electronic Communications Systems or Applications |
|
|
85 | (1) |
|
5.4 Applicability Issues of the Current Legal Framework |
|
|
86 | (3) |
|
5.4.1 An Old Directive for New Technologies |
|
|
86 | (1) |
|
5.4.2 The Role of the ePrivacy Directive with Regard to the Challenges Posed by New Technologies |
|
|
87 | (2) |
|
|
89 | (2) |
|
6 User-Centric Privacy-Enhancing Identity Management |
|
|
91 | (16) |
|
|
|
|
|
|
|
91 | (1) |
|
6.2 Sources of the User-Perspective Requirements |
|
|
92 | (13) |
|
6.2.1 Audience Segregation |
|
|
92 | (2) |
|
|
94 | (8) |
|
6.2.3 Adoption of Privacy-Enhanced IdM in Society |
|
|
102 | (3) |
|
|
105 | (2) |
|
7 Privacy-Enhancing Identity Management in Business |
|
|
107 | (34) |
|
|
|
|
107 | (1) |
|
7.2 Business Model for Privacy Enhancement |
|
|
108 | (16) |
|
7.2.1 Privacy Adoption Drivers |
|
|
108 | (5) |
|
7.2.2 Process Maturity for Privacy |
|
|
113 | (7) |
|
7.2.3 Risk Analysis for Data Privacy |
|
|
120 | (2) |
|
7.2.4 Privacy Impact on Business Process Design |
|
|
122 | (2) |
|
7.3 Cost Benefit Analysis of Privacy |
|
|
124 | (3) |
|
7.4 Requirements from a Business Perspective |
|
|
127 | (2) |
|
|
129 | (12) |
|
|
131 | (10) |
|
Part III What Technology Can Do for Privacy and How |
|
|
|
8 Introduction: Privacy, Trust, and Identity Management |
|
|
141 | (10) |
|
|
|
|
|
142 | (5) |
|
|
143 | (1) |
|
8.1.2 Establishing Trust and Managing Privacy |
|
|
144 | (1) |
|
8.1.3 Understanding Trust |
|
|
144 | (3) |
|
|
147 | (4) |
|
|
151 | (138) |
|
|
|
151 | (7) |
|
9.1.1 Motivation and Goals |
|
|
151 | (2) |
|
9.1.2 Realizing the Goals: Technology |
|
|
153 | (3) |
|
|
156 | (2) |
|
|
158 | (1) |
|
9.2 Architecture Overview |
|
|
158 | (15) |
|
9.2.1 One Party in the System |
|
|
158 | (1) |
|
9.2.2 Parties and Interactions |
|
|
159 | (4) |
|
|
163 | (7) |
|
|
170 | (3) |
|
|
173 | (26) |
|
|
174 | (2) |
|
|
176 | (1) |
|
9.3.3 Formulae in First-Order Logic |
|
|
176 | (1) |
|
|
177 | (1) |
|
|
177 | (1) |
|
|
178 | (1) |
|
|
179 | (2) |
|
9.3.8 Certification Metadata |
|
|
181 | (1) |
|
9.3.9 Conditional Release |
|
|
182 | (2) |
|
9.3.10 Anonymity Revocation |
|
|
184 | (1) |
|
|
184 | (4) |
|
9.3.12 Automated Reasoning |
|
|
188 | (3) |
|
|
191 | (3) |
|
9.3.14 Matching Data against Requests |
|
|
194 | (2) |
|
9.3.15 Further Discussion |
|
|
196 | (3) |
|
9.4 Data Representation Based on Our Model |
|
|
199 | (11) |
|
9.4.1 Identifier Relationships |
|
|
200 | (1) |
|
9.4.2 Identity Relationships |
|
|
201 | (5) |
|
|
206 | (2) |
|
|
208 | (1) |
|
9.4.5 Data Statements and Requests |
|
|
209 | (1) |
|
9.5 Identity Management Concepts |
|
|
210 | (2) |
|
|
210 | (2) |
|
9.6 Data Exchange Architecture |
|
|
212 | (30) |
|
9.6.1 Roles in an Attribute Exchange Scenario |
|
|
214 | (1) |
|
9.6.2 Private Certificate Systems |
|
|
215 | (1) |
|
9.6.3 High-Level Architecture |
|
|
216 | (1) |
|
9.6.4 Component Interlace |
|
|
217 | (17) |
|
|
234 | (3) |
|
9.6.6 Aspects of System Architecture |
|
|
237 | (5) |
|
9.7 Authorization Policies |
|
|
242 | (18) |
|
9.7.1 Paradigms of Authorization Systems |
|
|
242 | (1) |
|
|
243 | (1) |
|
|
244 | (1) |
|
9.7.4 Language Extensions |
|
|
245 | (6) |
|
|
251 | (1) |
|
9.7.6 Associating Policies with Resources |
|
|
252 | (6) |
|
9.7.7 Architectural Integration |
|
|
258 | (2) |
|
9.8 Data Handling Policies |
|
|
260 | (11) |
|
|
260 | (4) |
|
9.8.2 Association of Policies with Data |
|
|
264 | (3) |
|
|
267 | (3) |
|
9.8.4 Concrete Realization in the PRIME Prototype |
|
|
270 | (1) |
|
9.9 Negotiation -- Exchange of Data |
|
|
271 | (14) |
|
|
272 | (2) |
|
|
274 | (2) |
|
9.9.3 Policy-Driven Negotiation |
|
|
276 | (1) |
|
9.9.4 A Round of Negotiation |
|
|
277 | (8) |
|
|
285 | (4) |
|
|
285 | (1) |
|
|
286 | (3) |
|
10 Pseudonyms and Private Credentials |
|
|
289 | (20) |
|
|
|
|
|
289 | (1) |
|
10.2 The Idemix Private Credential System |
|
|
290 | (2) |
|
10.2.1 Basic Principles of Strong Authentication |
|
|
290 | (1) |
|
10.2.2 Balancing Anonymity and Accountability |
|
|
291 | (1) |
|
|
292 | (8) |
|
10.3.1 Required Properties When Showing a Certificate |
|
|
292 | (2) |
|
10.3.2 Cryptographic Primitives |
|
|
294 | (3) |
|
10.3.3 Cryptography for the Controlled Release of Certified Data |
|
|
297 | (3) |
|
10.1 Building Applications Using Idemix |
|
|
300 | (8) |
|
10.4.1 An Anonymous Credential System |
|
|
300 | (2) |
|
10.4.2 Anonymity Revocation |
|
|
302 | (1) |
|
10.4.3 Balancing Anonymity and Accountability Using e-Cash Techniques |
|
|
303 | (2) |
|
10.4.4 Application Scenarios |
|
|
305 | (3) |
|
|
308 | (1) |
|
11 Privacy Models and Languages: Access Control and Data Handling Policies |
|
|
309 | (22) |
|
|
Sabrina De Capitani di Vimercati |
|
|
|
|
309 | (1) |
|
11.2 Privacy Policy Categories |
|
|
310 | (1) |
|
|
311 | (2) |
|
11.4 Access Control Model and Language |
|
|
313 | (7) |
|
|
313 | (2) |
|
|
315 | (1) |
|
11.4.3 Description of the Access Control Language |
|
|
316 | (4) |
|
11.5 Data Handling Model and Language |
|
|
320 | (6) |
|
11.5.1 Description of the Data Handling Language |
|
|
322 | (4) |
|
|
326 | (3) |
|
|
329 | (2) |
|
12 Privacy Models and Languages: Obligation Policies |
|
|
331 | (32) |
|
|
12.1 Introduction to Privacy Obligation Policies |
|
|
331 | (1) |
|
12.2 Analysis of Privacy Obligations |
|
|
332 | (4) |
|
12.3 Requirements and Constraints |
|
|
336 | (3) |
|
12.4 Model of Privacy Obligations |
|
|
339 | (7) |
|
|
340 | (1) |
|
|
341 | (1) |
|
|
342 | (3) |
|
12.4.4 Relationships with AC/DHP Policies |
|
|
345 | (1) |
|
12.5 Privacy Obligation Policies: Language |
|
|
346 | (6) |
|
12.6 Parametric Obligation Policies |
|
|
352 | (9) |
|
12.6.1 Parametric Obligation Policies: Model |
|
|
353 | (2) |
|
12.6.2 Parametric Obligation Policies: Reference Scenario |
|
|
355 | (1) |
|
12.6.3 Parametric Obligation Policies: Language |
|
|
355 | (6) |
|
|
361 | (1) |
|
12.8 Next Steps and Future R&D Work |
|
|
361 | (2) |
|
13 Privacy Models and Languages: Assurance Checking Policies |
|
|
363 | (14) |
|
|
|
363 | (2) |
|
|
364 | (1) |
|
13.1.2 Natural Language Examples |
|
|
364 | (1) |
|
13.1.3 Overview of Different Potential Approaches |
|
|
365 | (1) |
|
13.2 Defining Trust Constraints: A Lower Level Representation |
|
|
365 | (3) |
|
13.3 Defining Clauses as First Class Objects: A Higher-Level Representation |
|
|
368 | (5) |
|
|
368 | (2) |
|
13.3.2 Examples of Clauses |
|
|
370 | (1) |
|
|
371 | (1) |
|
|
371 | (1) |
|
13.3.5 Representation of Assurance Policies in XML Format |
|
|
372 | (1) |
|
|
373 | (2) |
|
13.5 Next Steps and Future R&D Work |
|
|
375 | (2) |
|
14 Privacy-Aware Access Control System: Evaluation and Decision |
|
|
377 | (20) |
|
|
Sabrina De Capitani di Vimercati |
|
|
|
|
|
377 | (2) |
|
14.2 Interplay between Parties |
|
|
379 | (2) |
|
14.3 A Privacy-Aware Access Control Architecture |
|
|
381 | (3) |
|
14.3.1 Access Control Decision Function |
|
|
381 | (2) |
|
|
383 | (1) |
|
|
384 | (1) |
|
14.5 A Privacy-Aware Access Control System Prototype |
|
|
385 | (4) |
|
|
386 | (2) |
|
|
388 | (1) |
|
14.6 Performance Analysis |
|
|
389 | (5) |
|
14.6.1 The Evaluation Flow |
|
|
390 | (1) |
|
14.6.2 Performance Results |
|
|
391 | (3) |
|
|
394 | (3) |
|
15 Privacy-Aware Identity Lifecycle Management |
|
|
397 | (30) |
|
|
15.1 Privacy-Aware Identity Lifecycle Management: Principles and Concepts |
|
|
397 | (2) |
|
15.1.1 Obligation Management Framework |
|
|
397 | (2) |
|
15.2 Obligation Management System |
|
|
399 | (22) |
|
|
399 | (1) |
|
15.2.2 System Architecture |
|
|
400 | (4) |
|
15.2.3 Implementation Details |
|
|
404 | (7) |
|
|
411 | (2) |
|
15.2.5 Event Management Framework |
|
|
413 | (1) |
|
|
414 | (3) |
|
15.2.7 Administration GUI |
|
|
417 | (4) |
|
|
421 | (1) |
|
15.3 Scalable Obligation Management System |
|
|
421 | (5) |
|
15.3.1 Scalable Obligation Management Framework |
|
|
421 | (2) |
|
15.3.2 System Architecture |
|
|
423 | (3) |
|
15.4 Discussion and Conclusions |
|
|
426 | (1) |
|
16 Privacy Assurance Checking |
|
|
427 | (30) |
|
|
|
|
427 | (6) |
|
16.1.1 Scenarios Considered |
|
|
429 | (1) |
|
16.1.2 How Assurance Checking Fits in with the PRIME Approach |
|
|
430 | (2) |
|
16.1.3 Assurance Control Framework: Overview |
|
|
432 | (1) |
|
16.2 Privacy Compliance Checking System |
|
|
433 | (19) |
|
|
433 | (1) |
|
|
433 | (4) |
|
|
437 | (4) |
|
16.2.4 Implementation Details |
|
|
441 | (2) |
|
16.2.5 Mapping and Capability Validation |
|
|
443 | (2) |
|
16.2.6 Description of Protocol |
|
|
445 | (4) |
|
16.2.7 Role of Third Parties within the Trust Chain |
|
|
449 | (2) |
|
16.2.8 Extension to B2B Scenarios |
|
|
451 | (1) |
|
16.3 Comparison with Related Work |
|
|
452 | (3) |
|
16.4 Next Steps and Future R&D Work |
|
|
455 | (1) |
|
|
455 | (2) |
|
17 Security/Trustworthiness Assessment of Platforms |
|
|
457 | (28) |
|
|
|
|
457 | (1) |
|
|
457 | (5) |
|
17.2.1 Trust in an Organisation |
|
|
458 | (1) |
|
|
459 | (1) |
|
17.2.3 Determining Trustworthiness |
|
|
459 | (3) |
|
|
462 | (1) |
|
17.3 Assessing the Impact of Computer Systems in Relation to On-Line Trust |
|
|
462 | (3) |
|
17.3.1 Analysis of Online Trust |
|
|
462 | (1) |
|
17.3.2 How On-Line Trust Is Underpinned by Social and Technological Mechanisms |
|
|
463 | (1) |
|
|
464 | (1) |
|
17.4 Deploying Trusted Technologies |
|
|
465 | (4) |
|
17.4.1 Trusted Computing Technology |
|
|
465 | (1) |
|
17.4.2 How Trusted Platforms Can Provide Persistent and Dynamic Trust |
|
|
466 | (2) |
|
|
468 | (1) |
|
17.5 Use of Trusted Computing to Enhance Privacy |
|
|
469 | (8) |
|
|
469 | (1) |
|
17.5.2 How Trusted Computing Platform Technology Can Enhance Privacy |
|
|
469 | (1) |
|
17.5.3 Privacy Enhancing Safeguards of Trusted Computing Technology |
|
|
470 | (2) |
|
17.5.4 How Such Building Blocks Can Be Used |
|
|
472 | (2) |
|
17.5.5 Potential Negative Privacy Implications of Trusted Computing |
|
|
474 | (2) |
|
17.5.6 Concluding Remarks |
|
|
476 | (1) |
|
17.6 PRIME Platform Trust Manager (PTM) |
|
|
477 | (5) |
|
17.6.1 Trust Handler (TH) |
|
|
480 | (1) |
|
17.6.2 Trust Real-Time Monitor (TRM) |
|
|
480 | (1) |
|
17.6.3 Platform Trust Status (PTS) |
|
|
480 | (1) |
|
17.6.4 Trust Communicator (TC) |
|
|
481 | (1) |
|
17.6.5 Reputation Manager (RM) |
|
|
482 | (1) |
|
17.6.6 Trust Wrapper (TW) |
|
|
482 | (1) |
|
17.7 Reputation Management |
|
|
482 | (1) |
|
17.7.1 Objective Reputation Assessment |
|
|
482 | (1) |
|
17.7.2 Privacy Preferences and Privacy Obligations |
|
|
483 | (1) |
|
|
483 | (2) |
|
18 Further Privacy Mechanisms |
|
|
485 | (72) |
|
|
|
|
|
|
|
|
|
|
|
|
185 | (317) |
|
|
487 | (3) |
|
18.1.2 Persistent Data and Statistical Databases |
|
|
490 | (2) |
|
18.1.3 Data-Flow in Networks |
|
|
492 | (2) |
|
|
494 | (8) |
|
|
502 | (19) |
|
|
502 | (2) |
|
18.2.2 Analysis of Some Anonymization Examples in Europe and the USA |
|
|
504 | (6) |
|
18.2.3 Requirements for a Suitable Implementation |
|
|
510 | (5) |
|
18.2.4 A Generic Anonymization Architecture |
|
|
515 | (3) |
|
|
518 | (1) |
|
|
519 | (1) |
|
|
520 | (1) |
|
18.3 Anonymous Communication |
|
|
521 | (22) |
|
|
522 | (4) |
|
18.3.2 Techniques find Approaches |
|
|
526 | (14) |
|
18.3.3 Threats in Anonymous Communication |
|
|
540 | (3) |
|
|
543 | (1) |
|
18.4 Unobsaervable Content Access |
|
|
543 | (14) |
|
18.4.1 Private Information Retrieval and Oblivious Transfer |
|
|
545 | (1) |
|
18.4.2 Access Control for Unobservable Services |
|
|
546 | (1) |
|
18.4.3 Location-Based Services |
|
|
547 | (8) |
|
18.4.4 Conclusion and PRIME Perspective |
|
|
555 | (2) |
|
19 Reputation Management as an Extension of Future Identity Management |
|
|
557 | (12) |
|
|
|
|
|
557 | (2) |
|
19.2 Model of Reputation Systems |
|
|
559 | (4) |
|
|
559 | (1) |
|
19.2.2 Reputation Network |
|
|
560 | (3) |
|
19.3 Reputation within BluES'n |
|
|
563 | (2) |
|
19.3.1 Characteristics of a Reputation System in the Context of Collaborative eLearning |
|
|
563 | (1) |
|
19.3.2 Basic Design of the Reputation System |
|
|
563 | (2) |
|
19.4 Reputation as Service for PRIME Applications |
|
|
565 | (3) |
|
19.4.1 Necessary Infrastructure |
|
|
565 | (1) |
|
|
566 | (2) |
|
|
568 | (1) |
|
20 Human-Computer Interaction |
|
|
569 | (28) |
|
|
|
|
|
|
|
|
509 | (61) |
|
|
570 | (3) |
|
20.2.1 User-Friendly Representation of Policy Management with the Help of Default Settings |
|
|
571 | (1) |
|
|
571 | (1) |
|
20.2.3 Mapping Legal Privacy Requirements |
|
|
572 | (1) |
|
20.2.4 Mediation of Trust |
|
|
573 | (1) |
|
20.3 Challenge I: User-Friendly Representation of Complex PET Concepts |
|
|
573 | (8) |
|
20.3.1 Simplified Policy Handling |
|
|
574 | (3) |
|
20.3.2 UI Paradigms for Presenting Privacy Preferences |
|
|
577 | (4) |
|
20.4 Challenge II: Secure Interfaces |
|
|
581 | (1) |
|
20.5 Challenge III: Mapping Legal Privacy Requirements |
|
|
582 | (9) |
|
20.5.1 Obtaining Informed Consent |
|
|
582 | (5) |
|
20.5.2 Enhancing Transparency |
|
|
587 | (4) |
|
20.6 Challenge IV: Mediation of Trust |
|
|
591 | (2) |
|
|
593 | (4) |
|
20.7.1 Disclosing Data Using Anonymous Credentials |
|
|
593 | (1) |
|
20.7.2 Notification about Incidents |
|
|
593 | (1) |
|
20.7.3 Linkability Computation |
|
|
594 | (1) |
|
20.7.4 How Ontologies Can Be Utilised for UI Design |
|
|
594 | (3) |
|
|
597 | (12) |
|
|
|
|
597 | (2) |
|
|
598 | (1) |
|
|
599 | (1) |
|
21.2 Early Security Validation with CC |
|
|
599 | (8) |
|
21.2.1 Evaluation and the Common Criteria |
|
|
599 | (1) |
|
21.2.2 Basic Preconditions for an Evaluation |
|
|
600 | (1) |
|
21.2.3 Implemented Security Functions |
|
|
601 | (1) |
|
|
601 | (1) |
|
|
602 | (1) |
|
21.2.6 The Documentation of the Test Results |
|
|
603 | (1) |
|
21.2.7 Evaluation Process |
|
|
603 | (1) |
|
21.2.8 Experience with CC-Based Project Evaluation |
|
|
604 | (1) |
|
21.2.9 Integrated Prototype |
|
|
604 | (1) |
|
|
605 | (1) |
|
21.2.11 eLearning Prototype |
|
|
605 | (2) |
|
|
607 | (2) |
|
22 Requirements for Identity Management from the Perspective of Multilateral Interactions |
|
|
609 | (44) |
|
|
|
|
|
|
|
|
609 | (2) |
|
22.1.1 Objective of the Chapter |
|
|
609 | (1) |
|
22.1.2 User-Controlled Identity Management: From Chaum to PRIME |
|
|
610 | (1) |
|
22.2 Multilateral Interactions Using the Example of a Collaborative eLearning System |
|
|
611 | (2) |
|
22.2.1 Multilateral Interactions |
|
|
611 | (1) |
|
|
611 | (2) |
|
22.3 Building Blocks of a Privacy-Enhancing Identity Management System for MLI |
|
|
613 | (8) |
|
22.3.1 Pseudonyms and Partial Identities |
|
|
614 | (1) |
|
22.3.2 Relationship Information |
|
|
614 | (1) |
|
22.3.3 Searching for and Finding of Interaction Partners |
|
|
615 | (1) |
|
22.3.4 Trust Management and Reputation |
|
|
616 | (1) |
|
22.3.5 Awareness Information |
|
|
617 | (1) |
|
22.3.6 Context, and History |
|
|
617 | (1) |
|
|
618 | (1) |
|
22.3.8 Negotiation and Enforcement of Privacy Policies and Preferences |
|
|
619 | (1) |
|
22.3.9 Workflows and Behaviour Patterns |
|
|
619 | (1) |
|
22.3.10 External Regulations |
|
|
620 | (1) |
|
|
621 | (32) |
|
22.4.1 Overview of Building Blocks |
|
|
621 | (1) |
|
22.4.2 Building Blocks in the Model of David Chaum |
|
|
622 | (1) |
|
22.4.3 Research Questions |
|
|
623 | (4) |
|
|
627 | (26) |
|
|
|
|
653 | (4) |
|
|
24 Collaborative E-Learning |
|
|
657 | (22) |
|
|
|
|
|
|
|
|
24.1 The Collaborative eLearning System BluES'n |
|
|
657 | (4) |
|
24.1.1 Democratisation of an eLearning Environment |
|
|
657 | (2) |
|
24.1.2 Need for Privacy and How PRIME Helps |
|
|
659 | (2) |
|
24.2 Intra-Application Partitioning of Personal Data |
|
|
661 | (4) |
|
24.2.1 Necessity and General Goals |
|
|
661 | (1) |
|
24.2.2 Concept for the Support of IAP |
|
|
662 | (1) |
|
24.2.3 Realisation within the CeL Prototype |
|
|
663 | (1) |
|
|
664 | (1) |
|
24.3 Policy- and Credential-Based Access Control |
|
|
665 | (2) |
|
24.3.1 Necessity for Privacy-Enhancing Access Control |
|
|
665 | (1) |
|
24.3.2 Realisation within the CeL Prototype |
|
|
665 | (1) |
|
|
666 | (1) |
|
24.4 Privacy-Aware and Usable Application Design |
|
|
667 | (6) |
|
24.4.1 Management of Aliases |
|
|
668 | (1) |
|
|
669 | (2) |
|
24.4.3 GUI Components: InfoCenter and Echobar |
|
|
671 | (1) |
|
24.4.4 Adapted "Send Personal Data"-Dialogue |
|
|
672 | (1) |
|
24.5 Summary -- The Final CeL Prototype |
|
|
673 | (3) |
|
24.0 Beyond PRIME -- An Outlook |
|
|
676 | (3) |
|
25 Location-Based Services |
|
|
679 | (18) |
|
|
|
|
|
679 | (1) |
|
25.2 Privacy in Location-Based Services |
|
|
679 | (2) |
|
|
681 | (2) |
|
|
681 | (1) |
|
|
682 | (1) |
|
25.4 The Concept of a Location Intermediary |
|
|
683 | (2) |
|
25.5 Prototype Development |
|
|
685 | (1) |
|
25.6 PRIME Principles in a Restricted Mobile Environment |
|
|
686 | (1) |
|
25.7 First Prototype Version |
|
|
687 | (3) |
|
|
687 | (1) |
|
|
687 | (3) |
|
25.8 Second Prototype Version |
|
|
690 | (2) |
|
|
690 | (1) |
|
|
690 | (2) |
|
|
692 | (1) |
|
25.10 Possible Deployment |
|
|
693 | (1) |
|
|
694 | (3) |
|
|
697 | (24) |
|
|
|
|
|
697 | (10) |
|
26.1.1 Definition of "Health" by the World Health Organization (WHO) |
|
|
698 | (1) |
|
26.1.2 Continuity of Care and Impact on Individual's Life |
|
|
698 | (1) |
|
26.1.3 Health and Lifestyle Management |
|
|
699 | (1) |
|
20.1.4 The Self Care Medication Regimen and the Opportunity for Privacy-Enhanced Processes and Services |
|
|
700 | (6) |
|
26.1.5 Reference Context for Privacy-Enhanced Process and Service Re-engineering Based on the PRIME Concepts Applied to Self Cave Drug Therapy Management |
|
|
706 | (1) |
|
26.2 A Healthcare Demonstrator: Objectives and Scenario |
|
|
707 | (4) |
|
|
707 | (1) |
|
|
708 | (2) |
|
26.2.3 Collaboration with Other European Research Initiatives |
|
|
710 | (1) |
|
26.3 Application Requirements |
|
|
711 | (2) |
|
26.4 Application Demonstrator Architecture |
|
|
713 | (6) |
|
26.4.1 Demonstrator Components |
|
|
713 | (1) |
|
20.4.2 Privacy-Enhanced Online Drug Purchase: Information Flow |
|
|
713 | (4) |
|
26.4.3 Data Track and Obligations: Ensuring User Control |
|
|
717 | (2) |
|
|
719 | (2) |
|
27 Airport Security Controls: Prototype Summary |
|
|
721 | (14) |
|
|
|
721 | (1) |
|
27.2 The Reason Behind the Prototype |
|
|
722 | (1) |
|
27.3 The Trusted Traveler Use Case Scenario |
|
|
723 | (1) |
|
27.3.1 Privacy Enhancements |
|
|
724 | (1) |
|
27.4 Trusted Traveler "Smart Card" and Data Stored Thereiu |
|
|
724 | (1) |
|
27.5 The ASC Prototype Stages |
|
|
725 | (10) |
|
|
725 | (2) |
|
|
727 | (1) |
|
27.5.3 Entering the Passenger Restricted Area (PRA) |
|
|
728 | (3) |
|
|
731 | (1) |
|
|
732 | (1) |
|
27.5.6 The Use of Cryptography |
|
|
733 | (2) |
|
28 Privacy and Identity Management Requirements: An Application Prototype Perspective |
|
|
735 | (24) |
|
|
|
|
|
735 | (1) |
|
28.2 Users' Interests and Requirements |
|
|
736 | (6) |
|
|
736 | (3) |
|
28.2.2 Control of Data Flow |
|
|
739 | (2) |
|
28.2.3 Easy-to-Use Technology |
|
|
741 | (1) |
|
28.2.4 Reliable Service Provision |
|
|
742 | (1) |
|
28.3 Service Providers' Interests and Requirements |
|
|
742 | (3) |
|
28.3.1 Flexible Business Models |
|
|
743 | (1) |
|
28.3.2 Customer Loyalty and Trust |
|
|
743 | (1) |
|
|
743 | (1) |
|
28.3.4 Trusted Payment Partners |
|
|
744 | (1) |
|
|
745 | (1) |
|
|
745 | (1) |
|
28.4 Network Operators' Interests and Requirements |
|
|
745 | (2) |
|
28.4.1 Flexible Business Models |
|
|
746 | (1) |
|
28.4.2 Easy Integration of Third-Party Services |
|
|
746 | (1) |
|
|
747 | (1) |
|
28.4.4 Customer Loyalty and Trust |
|
|
747 | (1) |
|
28.4.5 Leveraging Existing Infrastructural Assets |
|
|
747 | (1) |
|
28.4.6 Enabling New Applications |
|
|
747 | (1) |
|
28.5 Developer Requirements |
|
|
747 | (1) |
|
|
747 | (1) |
|
|
748 | (1) |
|
28.5.3 Integration into Existing Frameworks |
|
|
748 | (1) |
|
|
748 | (11) |
|
|
751 | (8) |
|
Part V Conclusion and Outlook |
|
|
|
29 Conclusion and Outlook |
|
|
759 | (10) |
|
|
|
|
759 | (1) |
|
|
760 | (9) |
|
29.2.1 Further Research on Identity Management |
|
|
760 | (1) |
|
29.2.2 Making Privacy Real |
|
|
761 | (1) |
|
29.2.3 Including the Social Value of Privacy |
|
|
762 | (1) |
|
|
763 | (2) |
|
|
765 | (4) |
|
|
|
|
769 | (6) |
|
30.1 Access Control and Release Language: XML Schema |
|
|
769 | (2) |
|
30.2 Data Handling Language: XML Schema |
|
|
771 | (4) |
Author Index |
|
775 | |