Skip to content

Latest commit

 

History

History

personacards

Folders and files

NameName
Last commit message
Last commit date

parent directory

..
 
 
 
 
 
 
 
 
 
 
 
 

Personas are helpful when thinking about privacy threats to an application as a whole. It provides a bird's eye view of threats - you will not need a data flow diagram at this stage.

This is a table-top game to model privacy threats based on the Personas Framework.

How to Create a Persona

How to Diagram

The above figure shows an overview of the steps.

Step 1: Review the framework

Print out the following set of cards: Threat Actors(red), Threat Mechanisms(blue), and Threat Impact(orange), possibly 4-6 cards on a letter-sized page. We have made these low vision and colorblind friendly - if you would like to request additional accessible set of cards, please let us know.

Actor Mechanism Impact

Under threat actor, IA stands for "Inside Aggressive", IN stands for "Inside Neutral", OA stands for "Outside Aggressive", and ON stands for "Outside Neutral".

Under threat impact, cards that are marked as "Implicit-O" or "Explicit-O" stand for harm to organization, while "Implicit-I" and "Explicit-I" stand for harm to individuals. Each card with have a category and a description.

Step 2: Select relevant categories

Select cards from the three decks that are relevant to your application. For example, if your application does not have any customer or employee data, then probably impact to individuals would be less important.

If you do not see a card that might be relevant, please submit an issue so that we can update.

Step 3: Select a card from each category

Personas work as a combination of threat actors, mechanisms, and impact. Make sure to cover all combinations of the three to cover threats. Pick one card from each category, and then mix and match to create additional scenarios.

Step 4: Create personas

Combine the cards to create a persona embedded in a scenario.

Here is an example. Let our application be an HR management application. Let us consider Threat Actor: IA - Inside Attacker, Threat Mechanism: Identifiability, and Threat Impact: Implicit-I. Now think of a scenario, "Inside attacker uses identifiable data from application to leak confidential health documents". Try other combinations with the same threat actor, and changing out the mechanisms, and impact.

Step 5: Apply personas

Make a list of which personas are applicable to your application. You can use the template available here as well.

Template