Wirtschaftsuniversität Wien Magisterarbeit - SemanticLab

More documents

Recommendations

Info

3.3.3. Summary The introduced privacy standards all fulfill different needs on different (technical) levels and perspectives. Whereas P3P is more consumer orientated and tries to inspire companies to make their privacy policy easily accessible via user-agents, EPAL takes a look at internal privacy needs of businesses. It helps businesses to make sure privacy is being enforced by giving them a way to express their internal privacy policies and to set-up industry-specific vocabularies. This empowers companies to share such a set of vocabularies which in return enables enterprises to enforce privacy policies during interbusiness transactions. XACML is a standard which deals with privacy-issues on a low level. Therefore it is, if not a basis, then at least a model for other privacy standards. 38
4. Requirements for Privacy Tools In this chapter, software quality requirements for privacy tools will be introduced. These defined requirements provide the basis for Chapter 5 where existing privacy tools will be evaluated according to these characteristics. The requirements for privacy tools are based on the following standards: • ISO/IEC 25030:2007 which “provides requirements and recommendations for the specification of software quality requirements” [ISO07] • Part one of ISO/IEC 9126:2001 which defines a quality model describing characteristics of internal and external quality and quality in use [ISO01a] • Part four of ISO/IEC 9126:2001 which defines “metrics for measuring attributes of quality in use defined in ISO/IEC 9126-1:2001” [ISO01b] • IEEE Std 830-199 Recommended Practice for Software Requirements Specifications which (among other things) aims at providing requirements which can be applied when selecting software [IEE98] Most of these standards were also addressed in [Boe08]. Although all standards have certain measurements in place to evaluate specific requirements or attributes (especially ISO/IEC 9126-4:2001), a textual description of the requirements as provided in Chapter 5 will suffice for the purpose of this thesis. However, this section will distinguish between generic software quality requirements (based on the above mentioned standards) and privacy specific requirements, especially the support of privacy standards and the prevention of threats. 4.1. Generic software quality requirements There has been a lot of research and standardization focused on software quality requirements as the above mentioned standards demonstrate. Although different software fulfills all kind of needs, some basic quality requirements remain the same. That is why generic software quality requirements - which also apply for privacy software - are going to be discussed in the following section. 4.1.1. Functionality ISO/IEC 9126:2001 defines functionality as “the capability of the software product to provide functions which meet stated and implied needs when the software is used under 39
Page 1: Wirtschaftsuniversität Wien Magist
Page 4 and 5: Contents Abbreviations vii Listings
Page 6 and 7: II. Applied part 53 6. Development
Page 8 and 9: Listings viii 3.1. HTTP response he
Page 10 and 11: List of Tables x 3.1. PURPOSE sub-e
Page 12 and 13: 1. Introduction This thesis address
Page 14 and 15: In addition, the applied part of th
Page 16 and 17: 2. Privacy Threats Privacy is the
Page 18 and 19: term friendly fraud relates to legi
Page 20 and 21: over iGoogle, search Wikipedia via
Page 22 and 23: collect a lot of personal data abou
Page 24 and 25: 2.4. Privacy sensitive technologies
Page 26 and 27: • Data necessary to identify the
Page 28 and 29: 3. Privacy Standards The following
Page 30 and 31: The well-known location method (whi
Page 32 and 33: • User Preferences: User-agents m
Page 34 and 35: Another important issue for policy
Page 36 and 37: 1 M i c r o s o f t Way< /DATA> Red
Page 38 and 39: 28 PURPOSE Plain Language Translati
Page 40 and 41: Finally, an example should be provi
Page 42 and 43: • There is a commercial P3P polic
Page 44 and 45: Element Value ruling allow user cat
Page 46 and 47: 3.3.1. XACML - an introduction Simi
Page 50 and 51: specified conditions” [ISO01a]. T
Page 52 and 53: applied to this characteristic too,
Page 54 and 55: Figure 5.1.: Microsoft Internet Exp
Page 56 and 57: 5.1.2. Firefox The Mozilla Foundati
Page 58 and 59: shortcuts and context-menu, users s
Page 60 and 61: 5.3. Proxies In this section, proxi
Page 62 and 63: 52 Figure 5.10.: The settings dialo
Page 64 and 65: 6. Development of a Privacy Plug-In
Page 66 and 67: • components directory: this dire
Page 68 and 69: Speaking of information it has to b
Page 70 and 71: Figure 6.2.: Displaying the P3P pol
Page 72 and 73: matches the users preferences befor
Page 74 and 75: Figure 6.4.: The privacy policy of
Page 76 and 77: is different from the one available
Page 78 and 79: access elements in a policy which i
Page 80 and 81: implementation available although t
Page 82 and 83: [Dro06] Dennis Drotar, Rachel Green
Page 84 and 85: [Kob07] Alfred Kobsa. Privacy-enhan
Page 86 and 87: [Oli04] Nadia Olivero and Peter Lun
Page 88 and 89: [Woo06] Jisuk Woo. The right not to
Page 90 and 91: M i c r o s o f t i s a premier spo
Page 92 and 93: 82
Page 94 and 95: B. E-Mail correspondence Subject :
Page 96: the Thank you , Renukesh M i c r o

Wirtschaftsuniversität Wien Magisterarbeit - SemanticLab

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?