Endpoint

4/19/2017
04:20 PM
Connect Directly
Twitter
LinkedIn
Google+
RSS
E-Mail
50%
50%

3 Tips for Updating an Endpoint Security Strategy

How to face the process of navigating new threats, tools, and features to build an effective endpoint security strategy.

There is no one-size-fits-all approach to endpoint security, a space that has become inundated with products competing to solve a problem that has challenged businesses for years.

The last three to four years have driven the emergence of new options and ways of looking at endpoint security technology, says Mike Spanbauer, vice president of strategy at NSS labs. All of these tools rely on different features; all are suited for different strategies.

It's up to businesses to determine which tools are best to meet their needs based on their distinct approach to endpoint security.

"There is no such thing as perfect," Spanbauer says of choosing a tool. "This is one security control, in your grand security architecture, that must be complemented by a lot of secure technologies."

Securing the desktops within any organization, whether it's a large enterprise or SMB, comes with challenges. For businesses working to update their strategies, here are a few tips to keep in mind:

Prioritize your needs

To update an endpoint security strategy and pick the tools to support it, you need to determine your use cases, says Spanbauer. This will fall to the team who manages security tools and is responsible for handling the forensic parts of incident response.

"The teams with products that need to be supported will dictate which features really matter," he explains. For SMBs without dedicated incident response teams, he recommends developing more resilient backup processes in case of an attack.

Use cases for endpoint tech will also vary depending on your organization's data center and its data services, ports, protocols, architectures, and applications.

As businesses incorporate devices connected to the IoT, they will need to be increasingly aware of their larger attack surface, prioritize services and assets that need to be protected, and know where they are located.

Determine how to collaborate

On a broader level, it's important to establish a good working relationship with other data-conscious groups within the organization. Desktop support, for example, is an important collaborator for security teams.

While sometimes there can be contention among groups, Spanbauer acknowledges the importance of recognizing you're all on the same team. This means regular, dedicated interactions. He also advises building a workflow process so everyone knows how to partner with one another in the event of an emergency.

Have a backup plan

Even businesses taking all the right steps can suffer a breach. When they do, it's important to have their data backed up.

"Most enterprises have a backup" strategy" says Spanbauer. "I just don't believe it's strictly enforced."

He also emphasizes enforcing endpoint security practices; for example, logging out of administrative accounts for basic productivity that doesn't require administrative control. It's a simple step that could make a big difference: if you click a malicious Office attachment as an admin, you could accidentally give a hacker access to conduct a more sinister attack.

"It's convenient, it's easy, but as a best practice you shouldn't be writing Word documents or emails as an admin on your machine," he continues. "You have access to those apps without [administrative control]."

[Mike Spanbauer will be speaking about endpoint security strategy as part of his session "Updating Your Endpoint Security Strategy: Is the Endpoint a New Breed, Unicorn, or Endangered Species?" during Interop ITX, May 15-19, at the MGM Grand in Las Vegas. To learn more about his presentation, other Interop security tracks, or to register click on the live links.]

Related Content:

Kelly Sheridan is the Staff Editor at Dark Reading, where she focuses on cybersecurity news and analysis. She is a business technology journalist who previously reported for InformationWeek, where she covered Microsoft, and Insurance & Technology, where she covered financial ... View Full Bio

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
lizapleasant
50%
50%
lizapleasant,
User Rank: Apprentice
4/23/2017 | 5:59:50 AM
thanks
Thanks you a lot! I 'll implement it in my company!
6 Ways Greed Has a Negative Effect on Cybersecurity
Joshua Goldfarb, Co-founder & Chief Product Officer, IDRRA ,  6/11/2018
Weaponizing IPv6 to Bypass IPv4 Security
John Anderson, Principal Security Consultant, Trustwave Spiderlabs,  6/12/2018
'Shift Left' & the Connected Car
Rohit Sethi, COO of Security Compass,  6/12/2018
Register for Dark Reading Newsletters
White Papers
Video
Cartoon
Current Issue
Flash Poll
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2018-12026
PUBLISHED: 2018-06-17
During the spawning of a malicious Passenger-managed application, SpawningKit in Phusion Passenger 5.3.x before 5.3.2 allows such applications to replace key files or directories in the spawning communication directory with symlinks. This then could result in arbitrary reads and writes, which in tur...
CVE-2018-12027
PUBLISHED: 2018-06-17
An Insecure Permissions vulnerability in SpawningKit in Phusion Passenger 5.3.x before 5.3.2 causes information disclosure in the following situation: given a Passenger-spawned application process that reports that it listens on a certain Unix domain socket, if any of the parent directories of said ...
CVE-2018-12028
PUBLISHED: 2018-06-17
An Incorrect Access Control vulnerability in SpawningKit in Phusion Passenger 5.3.x before 5.3.2 allows a Passenger-managed malicious application, upon spawning a child process, to report an arbitrary different PID back to Passenger's process manager. If the malicious application then generates an e...
CVE-2018-12029
PUBLISHED: 2018-06-17
A race condition in the nginx module in Phusion Passenger 3.x through 5.x before 5.3.2 allows local escalation of privileges when a non-standard passenger_instance_registry_dir with insufficiently strict permissions is configured. Replacing a file with a symlink after the file was created, but befor...
CVE-2018-12071
PUBLISHED: 2018-06-17
A Session Fixation issue exists in CodeIgniter before 3.1.9 because session.use_strict_mode in the Session Library was mishandled.