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!
WebAuthn, FIDO2 Infuse Browsers, Platforms with Strong Authentication
John Fontana, Standards & Identity Analyst, Yubico,  9/19/2018
Turn the NIST Cybersecurity Framework into Reality: 5 Steps
Mukul Kumar & Anupam Sahai, CISO & VP of Cyber Practice and VP Product Management, Cavirin Systems,  9/20/2018
NSS Labs Files Antitrust Suit Against Symantec, CrowdStrike, ESET, AMTSO
Kelly Jackson Higgins, Executive Editor at Dark Reading,  9/19/2018
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Current Issue
Flash Poll
The Risk Management Struggle
The Risk Management Struggle
The majority of organizations are struggling to implement a risk-based approach to security even though risk reduction has become the primary metric for measuring the effectiveness of enterprise security strategies. Read the report and get more details today!
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2018-17538
PUBLISHED: 2018-09-26
Axon (formerly TASER International) Evidence Sync 3.15.89 is vulnerable to process injection.
CVE-2018-11763
PUBLISHED: 2018-09-25
In Apache HTTP Server 2.4.17 to 2.4.34, by sending continuous, large SETTINGS frames a client can occupy a connection, server thread and CPU time without any connection timeout coming to effect. This affects only HTTP/2 connections. A possible mitigation is to not enable the h2 protocol.
CVE-2018-14634
PUBLISHED: 2018-09-25
An integer overflow flaw was found in the Linux kernel's create_elf_tables() function. An unprivileged local user with access to SUID (or otherwise privileged) binary could use this flaw to escalate their privileges on the system. Kernel versions 2.6.x, 3.10.x and 4.14.x are believed to be vulnerabl...
CVE-2018-1664
PUBLISHED: 2018-09-25
IBM DataPower Gateway 7.1.0.0 - 7.1.0.23, 7.2.0.0 - 7.2.0.21, 7.5.0.0 - 7.5.0.16, 7.5.1.0 - 7.5.1.15, 7.5.2.0 - 7.5.2.15, and 7.6.0.0 - 7.6.0.8 as well as IBM DataPower Gateway CD 7.7.0.0 - 7.7.1.2 echoing of AMP management interface authorization headers exposes login credentials in browser cache. ...
CVE-2018-1669
PUBLISHED: 2018-09-25
IBM DataPower Gateway 7.1.0.0 - 7.1.0.23, 7.2.0.0 - 7.2.0.21, 7.5.0.0 - 7.5.0.16, 7.5.1.0 - 7.5.1.15, 7.5.2.0 - 7.5.2.15, and 7.6.0.0 - 7.6.0.8 as well as IBM DataPower Gateway CD 7.7.0.0 - 7.7.1.2 are vulnerable to a XML External Entity Injection (XXE) attack when processing XML data. A remote atta...