Security and usability designing secure systems that people can use
Human factors and usability issues have traditionally played a limited role in security research and secure systems development. Security experts have largely ignored usability issues--both because they often failed to recognize the importance of human factors and because they lacked the expertise...
| Otros Autores: | , , |
|---|---|
| Formato: | Libro electrónico |
| Idioma: | Inglés |
| Publicado: |
Beijing ; Sebastopol, California :
O'Reilly
[2005]
|
| Edición: | 1st edition |
| Colección: | Theory in practice (Sebastopol, Calif.)
|
| Materias: | |
| Ver en Biblioteca Universitat Ramon Llull: | https://discovery.url.edu/permalink/34CSUC_URL/1im36ta/alma991009627119906719 |
Tabla de Contenidos:
- Security and Usability; Audience for This Book; Structure of This Book; Conventions Used in This Book; Safari Enabled; How to Contact Us; Acknowledgments; I. Realigning Usability and Security; 1.2. Patching; 1.3. Configuration; 1.4. Conclusion; 1.5. About the Author; Two. Why Do We Need It? How Do We Get It?; 2.2. Product: Human Factors, Policies, and Security Mechanisms; 2.2.2. Awkward Behaviors; 2.2.3. Beyond the User Interface; 2.3. Process: Applying Human Factors Knowledge and User-Centered Approaches to Security Design; 2.3.2. A Process for Designing Usable Secure Systems
- 2.4. Panorama: Understanding the Importance of the Environment2.4.2. Building a Security Culture; 2.5. Conclusion; 2.6. About the Authors; Three. Design for Usability; 3.2. Balance Security and Usability; 3.2.2. Exploit Differences in Physical Location; 3.2.3. Vary Security with the Task; 3.2.4. Increase Your Partnership with Users; 3.2.4.2. Exploit the special skills of users; 3.2.4.3. Remove or reduce the user&s burden; 3.2.5. Achieve Balanced Authentication Design; 3.2.5.2. The Doctor and password madness; 3.2.6. Balance Resource Allocation; 3.3. Balance Privacy and Security
- 3.4. Build a Secure Internet3.4.1.2. Within the Ramparts; 3.4.1.3. The Town Wall; 3.4.1.4. Beyond the Town Wall; 3.4.2. Ringworld Interface; 3.5. Conclusion; 3.6. About the Author; Four. Usability Design and Evaluation for Privacy and Security Solutions; 4.1.2. Usability in Requirements; 4.1.3. Usability in Design and Development; 4.1.4. Usability in Postrelease; 4.2. Case Study: Usability Involvement in a Security Application; 4.2.2. The User Tests; 4.2.2.2. Test 2; 4.2.2.3. Test 3; 4.2.3. The Return on Investment (ROI) Analysis
- 4.3. Case Study: Usability Involvement in the Development of a Privacy Policy Management Tool4.3.2. Step Two: Performing In-Depth Interview Research; 4.3.3. Step Three: Designing and Evaluating a Privacy Policy Prototype; 4.3.4. Step Four: Evaluating Policy Authoring; 4.4. Conclusion; 4.5. About the Authors; Five. Designing Systems That People Will Trust; 5.1.2. The Nature of Trust in the Digital Sphere; 5.2. The Trust-Risk Relationship; 5.2.2. Trust and Credibility; 5.3. The Time-Course of Trust; 5.4. Models of Trust; 5.4.2. Bhattacherjee&s Model of Trust
- 5.4.3. Lee, Kim, and Moon&s Model of Trust5.4.4. Corritore&s Model of Trust; 5.4.5. Egger&s Model of Trust; 5.4.6. McKnight&s Model of Trust; 5.4.7. Riegelsberger&s Model of Trust; 5.4.8. Looking at the Models; 5.5. Trust Designs; 5.6. Future Research Directions; 5.7. About the Authors; II. Authentication Mechanisms; 6.1.2. Human Factors; 6.1.3. Security; 6.1.4. Context and Environment; 6.2. Authentication Mechanisms; 6.2.2. What the User Knows-Memometrics; 6.2.2.2. Cultural passwords (cued recall); 6.2.3. What the User Recognizes-Cognometrics; 6.2.3.2. Position-based systems
- 6.2.4. What the User Holds
