Dark Reading is part of the Informa Tech Division of Informa PLC

This site is operated by a business or businesses owned by Informa PLC and all copyright resides with them.Informa PLC's registered office is 5 Howick Place, London SW1P 1WG. Registered in England and Wales. Number 8860726.

Threat Intelligence

5/11/2018
10:30 AM
Connect Directly
LinkedIn
RSS
E-Mail vvv
100%
0%

The New Security Playbook: Get the Whole Team Involved

Smart cybersecurity teams are harnessing the power of human intelligence so employees take the right actions.

It's common to see the posters in airports, buses, and subways: "If you see something, say something." Over the years, thousands of people have tipped off the police to physical security risks. It's worked so well that New York City's Metropolitan Transportation Authority has launched nine generations of the ad campaign.

Now, smart cybersecurity teams are stealing a page from that playbook, harnessing the power of human intelligence to write a brand-new playbook for their organizations, training users to recognize cyberthreats and take the right actions. It's a collaborative approach to defense in depth, the yin to technology's yang, and a way to turn your users into a layer of protection.

Step 1: Drill Users in the Basics
Many companies tend to cover the security fundamentals intermittently, during new-hire orientation or security awareness month. That's hardly enough. Organizations need to educate users constantly.

Employees should know to verify links or attachments before clicking; it's the simplest way to avoid being infected with malware. If an email recipient knows the sender but wasn't expecting the attachment or link, he or she should contact the sender and ask about it. An ounce of inconvenience is worth a ton of pain.

Employees should learn to practice good cyber hygiene, starting with keeping the operating system and software applications current on any devices, in addition to downloading antivirus/anti-spyware software, configuring automatic updates, and securing their home Wi-Fi.

Before using e-commerce sites, employees should look for "HTTPS" in their browser's URL field. If they don't see these signs of encryption, they shouldn't enter logins or personal information. When an email, say from a user's bank, contains an e-commerce link, the user shouldn't click but instead manually enter the bank's URL.

Organizations should advise employees not to use public computers or Wi-Fi when they shop online, as public Wi-Fi is open and insecure. Also, employees should enable two-factor authentication when online shopping sites offer it.

Of course, security analysts already know these things, but plenty of users don't. That's why the first step is to drill them in the basics.

Step 2: Help Them Recognize Social Engineering
Social engineering comes in many flavors. Step 2 deals with good old-fashioned scams, such as someone in an airport coffee shop looking over your shoulder to steal your network login credentials.   

These days, most social engineering scams land in employees' in-boxes, as email is the preferred attack vector. With most breaches starting out as malicious emails, organizations need to train users to recognize the tactic.

One way to start: help employees be aware of the emotions scammers take advantage of. When users receive emails and are tempted to click, what are they feeling? The thrill of some promised reward? The fun of social sharing? The fear of missing instructions from HR?

The answer could be any of those emotions. One study revealed that phishing motivators are a rich mix of personal messages and business communications — in other words, the contents of a typical in-box.

Here's an example. An account payable specialist gets an urgent email that seems to come from a senior VP. The VP wants her to wire $100,000 to a vendor's account, ASAP. An untrained employee might authorize the transfer. An employee trained in email security would ask a few questions, starting with, "Do we really respond to fund transfer requests via email?"

The biggest companies in the world — along with smaller and midsized firms, government agencies, schools, and more — run formal training to help users recognize and report the latest tactics. Some organizations have "bounty" programs to give employees rewards, cash, or free swag for reporting a verified scam.

All social engineering targets human beings. That's why you need a strategy to harden your human assets.

Step 3: Help Users Help You Fight Malware
The easiest way to penetrate defenses is through employees. Conversely, employees are the last line of defense when technology fails, which happens all the time.

Imagine this subject line: "Free Coffee." Think it would work? It has, at many organizations. So has "Holiday Party Pics" or "Your Package Delivery." People are human. Unless they are trained to be aware of their emotions when reading an email, they'll take a break from work to click on something fun and potentially malicious.

Before the incident response team can identify which users received an email loaded with malware and mitigate the threat, they have to know about it. Someone within the organization — an employee with the benefit of proper security training — has to report the email.

The kind of anti-phishing training explained in step two is a solid way to proceed with step three as well. Companies that have run these programs for years create scenarios for social engineering and malware delivery alike.

It's kind of like in the real world, where employees face real threats. In the new security playbook, you need all of them to become field intelligence agents. To see something, report it, and join your security team.

Related Content:

John "Lex" Robinson has over 30 years' experience in information technology with a focus on value innovation, strategic planning, and program delivery. In addition, he has consulted and managed product and service delivery teams for both small businesses and global Fortune 20 ... View Full Bio
Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
AI Is Everywhere, but Don't Ignore the Basics
Howie Xu, Vice President of AI and Machine Learning at Zscaler,  9/10/2019
Fed Kaspersky Ban Made Permanent by New Rules
Dark Reading Staff 9/11/2019
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Current Issue
7 Threats & Disruptive Forces Changing the Face of Cybersecurity
This Dark Reading Tech Digest gives an in-depth look at the biggest emerging threats and disruptive forces that are changing the face of cybersecurity today.
Flash Poll
The State of IT Operations and Cybersecurity Operations
The State of IT Operations and Cybersecurity Operations
Your enterprise's cyber risk may depend upon the relationship between the IT team and the security team. Heres some insight on what's working and what isn't in the data center.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2019-16319
PUBLISHED: 2019-09-15
In Wireshark 3.0.0 to 3.0.3 and 2.6.0 to 2.6.10, the Gryphon dissector could go into an infinite loop. This was addressed in plugins/epan/gryphon/packet-gryphon.c by checking for a message length of zero.
CVE-2019-16320
PUBLISHED: 2019-09-15
Cobham Sea Tel v170 224521 through v194 225444 devices allow attackers to obtain potentially sensitive information, such as a vessel's latitude and longitude, via the public SNMP community.
CVE-2019-16321
PUBLISHED: 2019-09-15
ScadaBR 1.0CE, and 1.1.x through 1.1.0-RC, has XSS via a request for a nonexistent resource, as demonstrated by the dwr/test/ PATH_INFO.
CVE-2019-16317
PUBLISHED: 2019-09-14
In Pimcore before 5.7.1, an attacker with limited privileges can trigger execution of a .phar file via a phar:// URL in a filename parameter, because PHAR uploads are not blocked and are reachable within the phar://../../../../../../../../var/www/html/web/var/assets/ directory, a different vulnerabi...
CVE-2019-16318
PUBLISHED: 2019-09-14
In Pimcore before 5.7.1, an attacker with limited privileges can bypass file-extension restrictions via a 256-character filename, as demonstrated by the failure of automatic renaming of .php to .php.txt for long filenames, a different vulnerability than CVE-2019-10867 and CVE-2019-16317.