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 - Suggestive Dialogues
Luigi Lo Iacono, Peter Nehren
December 21, 2015
Suggestive Dialogues
| Name | Suggestive Dialogues |
| Sources | (Muñoz-Arteaga et al., 2009) |
| Synonyms | None |
| Context | The system must to provide users suggested actions to follow to mitigate the damages caused for some detected security threat. |
| Problem | How to facilitate the interpretation of a security alert and the reduction of damages caused by some detected threat? |
| Solution | By means of specific messages (without technical terms or irrelevant information) the users could be notified about the internal state of the system. The messages must include suggested actions to follow in case of eventuality. |
| Examples |  Source: (Muñoz-Arteaga et al., 2009) |
| Implementation | Notify about the internal state of the system and offer suggested actions. |
| Consequences | A suggested action represents a contribution to reduce misunderstands and makes easier the decision making. |
| Dependencies | None |
| Relationships | [Providing Recommendations] [Failing Safely] |
| Principles | [Path of Least Resistance] |
| Guidelines | None |
| Check lists | None |
| Use cases | None |
| Tags | Suggestive Dialogues, Providing Recommendations, Learnability, Fail Safety |
| 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