Phishing Simulations Guide
User Manual:
Open the PDF directly: View PDF
.
Page Count: 9
| Download | |
| Open PDF In Browser | View PDF |
A QUICK REFERENCE GUIDE FOR ORGANISATIONS Don’t take the bait © Crown Copyright 2017 DISCLAIMER Reference to any specific commercial product, process or service by trade name, trademark, manufacturer, or otherwise, does not constitute or imply its endorsement, recommendation or favour by CPNI. The views and opinions of authors expressed within this document shall not be used for advertising or product endorsement purposes. To the fullest extent permitted by law, CPNI accepts no liability for any loss or damage (whether direct, indirect or consequential, and including but not limited to, loss of profits or anticipated profits, loss of data, business or goodwill) incurred by any person and howsoever caused arising from or connected with any error or omission in this document or from any person acting, omitting to act or refraining from acting upon, or otherwise using the information contained in this document or its references. You should make your own judgment as regards use of this document and seek independent professional advice on your particular circumstances. OVERVIEW Phishing simulations within organisations provide a way to better understand potential vulnerabilities of employees to phishing emails. In order to get the most out of simulation exercises, a structured and systematic approach should be used that will allow findings to be compared over time and across groups. This quick reference guide provides a starting point for designing phishing simulations according to a desired end-point and the particular questions that you are interested in understanding. This includes: o Identifying key questions that you would like to answer o Designing systematic simulations that enable these questions to be addressed © CROWN COPYRIGHT 2017 DON’T TAKE THE BAIT CPNI AND UNIVERSITY OF BATH 3 1. IDENTIFYING KEY QUESTIONS THAT YOU WOULD LIKE TO ANSWER When designing a phishing simulation, it is important to first consider what it is you want to know and how the data will be used. This will drive all elements of the design of your simulation. For example: Are some groups of employees more susceptible to phishing emails than others? If you are interested in knowing the answer to this you could divide personnel into groups according to their length of time in the organisation, their job role, their clearance level, or their location and then comparing response rates across these groups. This may be used to develop targeted initiatives for particular employee groups. Has employee susceptibility to phishing emails changed over time? If you are interested in knowing the answer to this you could undertake a simulation at a set point in time, undertake a second comparable simulation at a later date and then compare response rates across the two time points. This may be used to assess the impact of an intervention, such as the roll-out of new training between these time points. Are employees more susceptible to certain types of threat? If you are interested in knowing whether employees are more susceptible to particular types of phishing emails then you can compare responses to different types of phishing simulations. This may relate to the types of phishing emails that employees typically receive and will help identify particular vulnerabilities that your organisation may have. For example, internal versus external emails, or those which use different techniques (e.g. claiming to offer a reward versus a potential loss of access to an account). This can then be used to prioritise training and awareness campaigns in relation to these types of attack. Having decided on the key questions that you would like to answer, you can then move on to the design of a systematic simulation that addresses these. © CROWN COPYRIGHT 2017 DON’T TAKE THE BAIT CPNI AND UNIVERSITY OF BATH 4 2. DESIGNING SYSTEMATIC SIMULATIONS Once the key questions of interest have been determined, the best method to answer them using a phishing simulation can be identified. The questions will determine how many simulation emails are likely to be used, how different or similar these emails should be, and the sample size that is likely to be required. For all your questions of interest, it will be important to consider the following: How many people you are able to test (your sample size) What your measures of success will be These may include: o How many people click on a link (the click-rate) o How many people enter user credentials when prompted (the disclosure rate) o How many people report the email (the reporting rate) All of these aspects may impact on both the design of the simulation and the resources required to manage it. How often you are able to run phishing simulations (simulation frequency) The geographic distribution of your sample (are recipients based in one location or distributed across multiple locations?) Example questions and methods for testing three question types are provided on the next few pages. © CROWN COPYRIGHT 2017 DON’T TAKE THE BAIT CPNI AND UNIVERSITY OF BATH 5 EXAMPLE QUESTION A: Are newly recruited personnel more or less susceptible to phishing emails? QUESTION TYPE: Exploring response differences across groups Once you have chosen a group category (e.g. length of time in organisation), you can determine who will be included in each group (e.g. under 1 year, 1-4 years, 5 years or more). An equal number of people should be included in each group. The groups should be similar in all other aspects apart from your factor of interest (e.g. similar gender proportions, similar degree of training, similar job role proportions etc.). This is to ensure that any differences between the groups are due to your factor of interest and not something else. If possible, the same email should be sent to all groups. If this is not possible, then the emails should be as similar as possible (e.g. similar content, length, layout, use of images, sender address). Emails should also be sent to all of the groups over the same period of time. This is to make sure that any response differences are not due to other differences in the simulation exercise. Groups to consider when designing phishing simulations: o Length of service o Seniority e.g. grade if civil service, ranks, management, senior management o Location of office e.g. UK based or overseas branch o Department e.g. sales, R+D, finance © CROWN COPYRIGHT 2017 DON’T TAKE THE BAIT CPNI AND UNIVERSITY OF BATH 6 EXAMPLE QUESTION B: Has your recent awareness campaign on phishing emails had an impact? QUESTION TYPE: Exploring response differences over time If you have decided to focus on response differences over time, then you do not need to divide employees into separate groups (unless you are combining both group differences and changes over time). You may decide to compare responses before or after an intervention, or responses at different times of the week (e.g. Monday morning versus Friday afternoon). Ideally, this design involves sending emails that are as similar as possible to the same group of employees (e.g. the same people receive both simulation emails) at two different time points. However, if this is not possible, then employees who receive the email at time point 1 should be as similar as possible to those who receive the email at time point 2 (e.g. similar gender proportions, similar degree of training, similar job roles etc.). This is to reduce the chance that any response differences are due to contrasts in either the simulation email received or employee differences. © CROWN COPYRIGHT 2017 DON’T TAKE THE BAIT CPNI AND UNIVERSITY OF BATH 7 EXAMPLE QUESTION C: What type of phishing email is your organisation most vulnerable to? QUESTION TYPE: Exploring response differences across email types If you have chosen to focus on response differences across email types, then as above, differences in employees who receive the email and differences in when the email is received should be minimised as much as possible. The only difference should be the chosen aspect of the email itself. Ideally, only one email aspect should be changed (e.g. an email contains a logo versus not, or using an external versus internal looking email address). Each type of email can then either be sent to the same employees or different employees (if they have been matched for similarity). © CROWN COPYRIGHT 2017 DON’T TAKE THE BAIT CPNI AND UNIVERSITY OF BATH Finally, some additional tips to consider when designing your simulation: Keep it simple and don’t try to answer too many questions at once. The general rule is the more questions that you try to answer, the larger the sample that you will need. Use the largest sample size possible. In general, the more people who can be sent the simulation, the more robust your findings will be. Don’t try to do too much at once. Prioritise your questions of interest and keep it simple. Highlight the personal relevance of exercises to employees. Vulnerability in the workplace may be reflected in vulnerability at home. Provide learning and advice at the time of ‘clicking’. This may be in the form of redirection to advice pages or online training modules. Avoid sending the same simulation email to too many people working in close proximity, as responses are likely to be driven by how many others received the same email. © CROWN COPYRIGHT 2017 DON’T TAKE THE BAIT CPNI AND UNIVERSITY OF BATH
Source Exif Data:
File Type : PDF File Type Extension : pdf MIME Type : application/pdf PDF Version : 1.7 Linearized : Yes Create Date : 2017:02:17 12:05:45Z Creator : Adobe InDesign CC 2017 (Macintosh) Modify Date : 2017:10:19 09:41:18+01:00 Language : en-GB XMP Toolkit : Adobe XMP Core 5.4-c005 78.147326, 2012/08/23-13:03:03 Metadata Date : 2017:10:19 09:41:18+01:00 Creator Tool : Adobe InDesign CC 2017 (Macintosh) Instance ID : uuid:16e6e828-c821-4d12-a093-494015cf7623 Original Document ID : xmp.did:2dc0259b-154c-4361-bd9b-49fb17659ef4 Document ID : xmp.id:caa8e14f-0abf-4fa9-8ab1-a0e84354b89e Rendition Class : proof:pdf Derived From Instance ID : xmp.iid:4adb818a-17d8-493f-84e6-78dac268501d Derived From Document ID : xmp.did:eb0048dd-ec2a-4458-8faa-446ecc3b4790 Derived From Original Document ID: xmp.did:2dc0259b-154c-4361-bd9b-49fb17659ef4 Derived From Rendition Class : default History Action : converted History Parameters : from application/x-indesign to application/pdf History Software Agent : Adobe InDesign CC 2017 (Macintosh) History Changed : / History When : 2017:02:17 12:05:45Z Format : application/pdf Producer : Adobe PDF Library 15.0 Trapped : False Page Count : 9EXIF Metadata provided by EXIF.tools