Risk
9/2/2010
01:44 PM
Connect Directly
LinkedIn
RSS
E-Mail
50%
50%

9 Steps To Enabling Remote Access, Safely

Security goes beyond encryption, authentication, and monitoring employees. We also need to ensure privileged users aren't betraying trust. Here's how.

As remote workers become more commonplace, their connections represent an increasingly vexing risk factor. For respondents to our InformationWeek Analytics 2010 Strategic Security Survey who said their companies are more vulnerable now than in 2009, 66% cited as the reason more ways to attack corporate networks, including wireless. Yet IT must ensure mobile workers have the access they need to be productive.

Here's one angle CIOs often overlook: Providing this level of 24/7 support translates to a lot of people with high access privileges working remotely--not just business users, but IT support staff as well.

Most of us have no choice but to open systems to the outside world. The challenge is to do so in a measured fashion, and in a way that allows you to track and audit access while protecting data. Here's our hit list of the top nine dangers that come with unfettered remote access, along with mitigation tips for each.

1| Danger: Running afoul of regulations Mitigation: Document the corporate data and intellectual property that you must protect

This exercise is basic--and vital. You can't even begin to audit and protect your organization's data until you know where all the important stuff resides. The results of a data discovery process can be leveraged across many different projects, including compliance, risk assessment, and data loss prevention (DLP) initiatives.

2| Danger: You can't easily correlate account activity and usage Mitigation: Rein in your account and password policy

Want an eye opener? Ask for a report on the number of general accounts in your directory services infrastructure. We're talking about those accounts called "Support" or "Payroll"--you know, the ones all 5,000 company employees seem to know the passwords to. If you're using general-purpose accounts for any authentication activities without carefully controlling access rights, you're playing Russian roulette. To the degree you can, eliminate them.

And while you're cracking down on anonymous accounts, give some thought to your password policy. Implementing strong passwords is arguably the easiest mitigation task on our list to execute. Sure, it might also be the one that generates the most hate mail to IT, but there's no getting around the fact that you can't let users select "password."

InformationWeek: September 6, 2010 Issue To read the rest of the article, download a free PDF of InformationWeek magazine
(registration required)

Comment  | 
Print  | 
More Insights
Register for Dark Reading Newsletters
White Papers
Flash Poll
Current Issue
Cartoon
Video
Slideshows
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2013-6306
Published: 2014-08-22
Unspecified vulnerability on IBM Power 7 Systems 740 before 740.70 01Ax740_121, 760 before 760.40 Ax760_078, and 770 before 770.30 01Ax770_062 allows local users to gain Service Processor privileges via unknown vectors.

CVE-2014-0232
Published: 2014-08-22
Multiple cross-site scripting (XSS) vulnerabilities in framework/common/webcommon/includes/messages.ftl in Apache OFBiz 11.04.01 before 11.04.05 and 12.04.01 before 12.04.04 allow remote attackers to inject arbitrary web script or HTML via unspecified vectors, which are not properly handled in a (1)...

CVE-2014-3525
Published: 2014-08-22
Unspecified vulnerability in Apache Traffic Server 4.2.1.1 and 5.x before 5.0.1 has unknown impact and attack vectors, possibly related to health checks.

CVE-2014-3563
Published: 2014-08-22
Multiple unspecified vulnerabilities in Salt (aka SaltStack) before 2014.1.10 allow local users to have an unspecified impact via vectors related to temporary file creation in (1) seed.py, (2) salt-ssh, or (3) salt-cloud.

CVE-2014-3587
Published: 2014-08-22
Integer overflow in the cdf_read_property_info function in cdf.c in file through 5.19, as used in the Fileinfo component in PHP before 5.4.32 and 5.5.x before 5.5.16, allows remote attackers to cause a denial of service (application crash) via a crafted CDF file. NOTE: this vulnerability exists bec...

Best of the Web
Dark Reading Radio
Archived Dark Reading Radio
Three interviews on critical embedded systems and security, recorded at Black Hat 2014 in Las Vegas.