2006
DOI: 10.1007/11957454_6
|View full text |Cite
|
Sign up to set email alerts
|

Privacy Injector — Automated Privacy Enforcement Through Aspects

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
1
1

Citation Types

0
3
0
1

Year Published

2007
2007
2019
2019

Publication Types

Select...
4
2
2

Relationship

0
8

Authors

Journals

citations
Cited by 10 publications
(4 citation statements)
references
References 18 publications
0
3
0
1
Order By: Relevance
“…By considering personalization, this privacy policy can be replaced by a privacy preference in many cases to also reflect personal privacy demands. Such a privacy preference should be in place during the entire lifecycle of the personal data [155]. That is, even if the personal data is disseminated from the initial data controller to the others, the privacy preference of the original data subject should be simultaneously transmitted along with the data.…”
Section: B Compliance-enhancing Techniquesmentioning
confidence: 99%
“…By considering personalization, this privacy policy can be replaced by a privacy preference in many cases to also reflect personal privacy demands. Such a privacy preference should be in place during the entire lifecycle of the personal data [155]. That is, even if the personal data is disseminated from the initial data controller to the others, the privacy preference of the original data subject should be simultaneously transmitted along with the data.…”
Section: B Compliance-enhancing Techniquesmentioning
confidence: 99%
“…Ubiquitous health features and its ubiquitous environment suggest that trustworthiness and privacy are real concerns [ 9 , 10 ]. In ubiquitous health, it is difficult to understand the processing of data inside the systems [ 11 ], as systems do not always perform in accordance with their policies, and the privacy preferences of DS might conflict with the business objectives of the system [ 12 ]. As a result, the DS cannot assume that the existing legal framework guarantees the processing of PHI lawfully and according to the rules proposed by him or her [ 13 , 14 ].…”
Section: Introductionmentioning
confidence: 99%
“…In metadata approaches, privacy policies can be injected to application, tagged to the metadata, or added to the database or an active agent [ 50 ]. Berghe and Schunter’s “privacy injector” adds privacy rules to existing applications [ 11 ]. The EnCoRe architecture uses the sticky policy paradigm where the DS can stick machine-readable rules to the data before it is disclosed [ 48 ].…”
Section: Introductionmentioning
confidence: 99%
“…Τέτοιες προσεγγίσεις αφορούν για παράδειγµα τις ενσωµατωµένες λειτουργικότητες ελέγχου πρόσβασης της τεχνολογίας Enterprise JavaBeans (EJB) της Java [274], ή τη χρήση θεµατοστραφούς ανάπτυξης [275] για την ενσωµάτωση χαρακτηριστικών προστασίας της ιδιωτικότητας είτε Τεχνολογίες Υπηρεσιών, Ροών Εργασιών και Προστασίας Προσωπικών Δεδοµένων σε εφαρµογές κατά τα τελευταία στάδια της ανάπτυξής τους, είτε σε υφιστάµενες εφαρµογές. Μια τέτοια προσέγγιση αποτυπώνεται στην προδιαγραφή του Εργαλείου Έγχυσης Ιδιωτικότητας (Privacy Injector) [276], που περιλαµβάνει διαδικασίες για τη δηµιουργία, ενηµέρωση, χρήση και διατήρηση µεταδεδοµένων ιδιωτικότητας, καθώς και για την εφαρµογή τους σε συνδυασµό µε την υποκείµενη πολιτική ιδιωτικότητας. Άλλες προσεγγίσεις αφορούν τον ορισµό ειδικών γλωσσών προδιαγραφής, οι οποίες χρησιµοποιούνται για την επισηµείωση αφαιρετικών προδιαγραφών µε χαρακτηριστικά ασφάλειας και ιδιωτικότητας.…”
Section: μηχανική λογισµικού για ασφάλεια και ιδιωτικότηταunclassified