Patterns
- Active Warnings
- Attractive Options
- Complete Delete
- Conveying Threats & Consequences
- Create a Security Lexicon
- Create Keys When Needed
- Delayed Unrecoverable Action
- Detailed Notifications About Security
- Direct Access to UI Components
- Disable by Default
- Disable of Services
- Disclose Significant Deviations
- Distinguish Between Run and Open
- Distinguish Internal Senders
- Distinguish Security Levels
- Email-Based Identification and Authentication
- Explicit Item Delete
- Explicit User Audit
- Failing Safely
- General Notifications About Security
- Immediate Notifications
- Immediate Options
- Indirect Access to UI Components
- Informative Dialogues
- Install Before Execute
- Key Continuity Management
- Levels of Severity
- Leverage Existing Identification
- Localization of Specific Areas
- Migrate and Backup Keys
- Noticeable Contextual Indicators
- Providing Recommendations
- Quick Description of UI Components
- Redundant Notifications
- Reset to Installation
- Restricted Areas Notification
- Security Features Used by the System
- Security Features Used by the User
- Send S/MIME-Signed Email
- Separating Content
- Sequential Access to UI Components
- Suggestive Dialogues
- System’s Security Tasks
- The Absence of Indicators
- Track Received Keys
- Track Recipients
- Warn When Unsafe
Patterns are based on scientific sources.
Usable Security Pattern - Detailed Notifications About Security
Luigi Lo Iacono, Peter Nehren
December 21, 2015
Detailed Notifications About Security
| Name | Detailed Notifications About Security |
| Sources | (Muñoz-Arteaga et al., 2009) |
| Synonyms | None |
| Context | The interface must provide options to obtain detailed information about the system for general or specific topics. |
| Problem | How to enable the user to get specific information about the security of the system? |
| Solution | Include links in the notifications presented to the end users so that they can obtain specific information about the security features of the system, and detected threats if needed. |
| Examples |  Source: (Muñoz-Arteaga et al., 2009) |
| Implementation | Provide ways for users to get more specific information about security features of the system. |
| Consequences | This alternative avoids showing irrelevant information through the interface, reducing space, and contributing to maintain an aesthetic design. |
| Dependencies | None |
| Relationships | [Direct Access to UI Components] |
| Principles | [Visibility] |
| Guidelines | None |
| Check lists | None |
| Use cases | None |
| Tags | Detailed Notifications, Direct Access to UI Components, Accessability |
| Log history | [12/21/2015]: Added to repository |
References
Muñoz-Arteaga, J., González, R.M., Martin, M.V., Vanderdonckt, J., Álvarez-Rodriguez, F., Calleros, J.G., 2009. A method to design information security feedback using patterns and hCI-security criteria, in: Computer-Aided Design of User Interfaces VI. Springer London, pp. 283–294. doi:10.1007/978-1-84882-206-1_26