Simulated phishing

From Wikipedia, the free encyclopedia
Jump to navigation Jump to search

Simulated phishing or a phishing test is where deceptive emails, similar to malicious emails, are sent by an organisation to their own staff to gauge their response to phishing and similar email attacks. The emails themselves are often a form of training, but such testing is normally done in conjunction with prior training; and often followed up with more training elements. This is especially the case for those who "fail" by opening any email attachments, or clicking on any included weblinks - or if they were tricked into entering any credentials.

Rationale[edit]

There is wide acceptance within the IT security field that technical measures alone cannot stop all malicious email attacks, and that good training of staff is necessary.[citation needed] Simulated phishing allows the direct measurement of staff compliance, and when run regularly, can measure progress in user behavior. Phishing simulation is recommended by various official agencies, who often provide guidelines for designing such policies.[1] Phishing simulations are sometime compared to fire drills in giving staff regular practice in correct behaviour.[citation needed]

Ethics[edit]

Such campaigns need to be authorised at an appropriate level,[2] and carried out professionally.[3] If such a technique is used carelessly it may breach laws, attract law suits and antagonise or traumatise staff.

However, if employees are advised of a change to policy such that: "the company reserves the right to send deceptive "simulated phishing" email to staff from time to time to gauge staff security awareness and compliance", and training and guidance has been given in advance then such problems should not occur. Some organisations may choose to require users to give their consent by opting-in,[4] and others may allow staff the option to opt-out.[5]

The standard advice is that "failing' staff not be shamed in any way, but it is appropriate and reasonable to provide supportive followup training.[6][7][8]

Some techniques, which might be effective and in use by malicious actors, will be normally be avoided in simulated phishing for ethical or legal reasons. These would include emails with content likely to cause distress to the recipient,[3][6] or the use of third party trademarks;[3][6] although it is also sometimes argued that this is covered by "fair use".[9]

Methods[edit]

Such testing can be done in a number of ways.

  • Many vendors offer web-hosted platforms to do this, and some provide limited free "test" campaigns.[10]
  • A wide range of freely-available open-source tools allow more technical organisations to host and run their own testing.[11][12][13]
  • Some email service now have such testing as a built-in option.[14][15]

Because organisations generally have a set of multi-layered defences in place to prevent actual malicious phishing, simulations will often require some whitelisting to be put in place at email gateways, anti-virus software and web proxies to allow email to reach user desktops and devices and to be acted upon.

Frequency[edit]

Most advice is that testing should be at done several times per year, to give staff practice in responding correctly, and to provide management feedback on the progress in staff identifying and reporting potentially dangerous email.

See also[edit]

References[edit]

  1. ^ "Designing Phishing Simulations" (PDF). Center for the Protection of National Infrastructure. Retrieved 12 September 2018.
  2. ^ Kovacs, Eduard (23 August 2018). "Attack on DNC Part of Simulated Phishing Test". Security Week. Retrieved 12 September 2018.
  3. ^ a b c Cheng, Joey (18 March 2014). "Out-of-control Army phishing test results in new guidelines". DefenseSystems. Retrieved 12 September 2018.
  4. ^ "Simulated Phishing". Berkeley Lab. Retrieved 12 September 2018.
  5. ^ "Simulated Phishing Email Campaign". UC Santa Cruz. Retrieved 12 September 2018.
  6. ^ a b c Prendergast, Tom. "Is all fair in simulated phishing?". www.csoonline.com. Retrieved 9 September 2018.
  7. ^ Meijdam, Katrien. "Phishing as a Service: Designing an ethical way of mimicking targeted phishing attacks to train employees". Retrieved 10 September 2018.
  8. ^ R, Kate. "The Trouble with Phishing". National Cyber Security Centre. GCHQ. Retrieved 12 September 2018.
  9. ^ Calarco, Daniel. "Stop Phishing with Bad Fake Bait". EDUCAUSEreview. Retrieved 12 September 2018.
  10. ^ Korolov, Maria. "10 companies that can help you fight phishing". CSO Online. Retrieved 12 September 2018.
  11. ^ e.g GoPhish, King Phisher, The SocialEngineer Toolkit
  12. ^ Pauli, Darren (4 February 2016). "Go phish your own staff: Dev builds open-source fool-testing tool". The Register. Retrieved 12 September 2018.
  13. ^ "Phishing campaign simulators". Phishing Countermeasures. Retrieved 12 September 2018.
  14. ^ Ghosh, Debraj. "GA of Attack Simulator For Office 365 Threat Intelligence". Microsoft Tech Community. Retrieved 12 September 2018.
  15. ^ Lardinois, Frederic. "Microsoft launches a phishing attack simulator and other security tools". TechCrunch. Retrieved 12 September 2018.