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.

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!
US Turning Up the Heat on North Korea's Cyber Threat Operations
Jai Vijayan, Contributing Writer,  9/16/2019
Fed Kaspersky Ban Made Permanent by New Rules
Dark Reading Staff 9/11/2019
NetCAT Vulnerability Is Out of the Bag
Dark Reading Staff 9/12/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-16395
PUBLISHED: 2019-09-17
GnuCOBOL 2.2 has a stack-based buffer overflow in the cb_name() function in cobc/tree.c via crafted COBOL source code.
CVE-2019-16396
PUBLISHED: 2019-09-17
GnuCOBOL 2.2 has a use-after-free in the end_scope_of_program_name() function in cobc/parser.y via crafted COBOL source code.
CVE-2019-16199
PUBLISHED: 2019-09-17
eQ-3 Homematic CCU2 before 2.47.18 and CCU3 before 3.47.18 allow Remote Code Execution by unauthenticated attackers with access to the web interface via an HTTP POST request to certain URLs related to the ReGa core process.
CVE-2019-16391
PUBLISHED: 2019-09-17
SPIP before 3.1.11 and 3.2 before 3.2.5 allows authenticated visitors to modify any published content and execute other modifications in the database. This is related to ecrire/inc/meta.php and ecrire/inc/securiser_action.php.
CVE-2019-16392
PUBLISHED: 2019-09-17
SPIP before 3.1.11 and 3.2 before 3.2.5 allows prive/formulaires/login.php XSS via error messages.