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
Mobile Banking Malware Up 50% in First Half of 2019
Kelly Sheridan, Staff Editor, Dark Reading,  1/17/2020
Active Directory Needs an Update: Here's Why
Raz Rafaeli, CEO and Co-Founder at Secret Double Octopus,  1/16/2020
New Attack Campaigns Suggest Emotet Threat Is Far From Over
Jai Vijayan, Contributing Writer,  1/16/2020
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Current Issue
The Year in Security: 2019
This Tech Digest provides a wrap up and overview of the year's top cybersecurity news stories. It was a year of new twists on old threats, with fears of another WannaCry-type worm and of a possible botnet army of Wi-Fi routers. But 2019 also underscored the risk of firmware and trusted security tools harboring dangerous holes that cybercriminals and nation-state hackers could readily abuse. Read more.
Flash Poll
How Enterprises are Attacking the Cybersecurity Problem
How Enterprises are Attacking the Cybersecurity Problem
Organizations have invested in a sweeping array of security technologies to address challenges associated with the growing number of cybersecurity attacks. However, the complexity involved in managing these technologies is emerging as a major problem. Read this report to find out what your peers biggest security challenges are and the technologies they are using to address them.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2019-20399
PUBLISHED: 2020-01-23
A timing vulnerability in the Scalar::check_overflow function in Parity libsecp256k1-rs before 0.3.1 potentially allows an attacker to leak information via a side-channel attack.
CVE-2020-7915
PUBLISHED: 2020-01-22
An issue was discovered on Eaton 5P 850 devices. The Ubicacion SAI field allows XSS attacks by an administrator.
CVE-2019-20391
PUBLISHED: 2020-01-22
An invalid memory access flaw is present in libyang before v1.0-r3 in the function resolve_feature_value() when an if-feature statement is used inside a bit. Applications that use libyang to parse untrusted input yang files may crash.
CVE-2019-20392
PUBLISHED: 2020-01-22
An invalid memory access flaw is present in libyang before v1.0-r1 in the function resolve_feature_value() when an if-feature statement is used inside a list key node, and the feature used is not defined. Applications that use libyang to parse untrusted input yang files may crash.
CVE-2019-20393
PUBLISHED: 2020-01-22
A double-free is present in libyang before v1.0-r1 in the function yyparse() when an empty description is used. Applications that use libyang to parse untrusted input yang files may be vulnerable to this flaw, which would cause a crash or potentially code execution.