Attacks/Breaches
3/26/2009
03:15 PM
Connect Directly
RSS
E-Mail
50%
50%
Repost This

Top-Down Password Protection

New tools can corral administrator-level access, but plan ahead to avoid costly downtime.

Chances are good that many of your servers share administrator passwords that haven't been changed in a long time. Chances also are good that these passwords are well-known to many staff members--including some former ones.

If that doesn't scare you, it should: Anyone who knows the passwords could log in and have complete control over servers and applications, and you'd have no ability to track who made changes or accessed data.

The problems with poor administrative password management extend beyond insiders to external threats as well. Penetration testers have proven that there's a way into nearly every network, and once attackers find it--often in a typical user's desktop--they can reverse-engineer the passwords on the system and discover the local administrator password. If this password is common to other systems, as it often is, attackers can then use it to access other systems and move through the network.

InformationWeek Reports

Just as bad, at many companies there's only one system administrator who knows a critical password. This situation is dangerous, as the case of Terry Childs shows. Childs, you may remember, was a network administrator in San Francisco who last year was accused of locking top administrators out of the city's network. At the time, he was the only person with passwords to many of the city's routers.

Account Ability
The dangers of administrator accounts are well known, but few organizations have a comprehensive way to manage these all-powerful accounts. It's not that organizations want to leave themselves open to vulnerability and accountability issues. The problem is that privileged accounts are difficult to manage because there are so many of them. Every server and workstation has a local administrator account, as do most applications. Even services running on servers, such as a backup agent or a Web server, use privileged accounts to function. All the routers, switches, and firewalls on your network do, too.

DIG DEEPER
An Inside Job?
If your network's been hacked, forensics can help you discover how.
Ideally, passwords for these accounts should all be unique and should be changed frequently. In the real world, that's just not practical. But now is a particularly good time to start figuring out who has access to what: The sad fact is that the threat level from former workers will likely remain high as companies lay off higher-level employees to survive the economic downturn.

Some organizations use a low-tech approach to secure administrator accounts, constructing elaborate systems where privileged account passwords are stored in sealed envelopes in a fireproof safe, with a paper record of when they were accessed. These measures are probably better than nothing, but they don't fully address password access control and user accountability, and can quickly become unworkable for larger installations.

Impact Assessment: Privelaged Account Management Tools

(click image for larger view)

Previous
1 of 3
Next
Comment  | 
Print  | 
More Insights
Register for Dark Reading Newsletters
White Papers
Flash Poll
Current Issue
Video
Slideshows
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2011-0460
Published: 2014-04-16
The init script in kbd, possibly 1.14.1 and earlier, allows local users to overwrite arbitrary files via a symlink attack on /dev/shm/defkeymap.map.

CVE-2011-0993
Published: 2014-04-16
SUSE Lifecycle Management Server before 1.1 uses world readable postgres credentials, which allows local users to obtain sensitive information via unspecified vectors.

CVE-2011-3180
Published: 2014-04-16
kiwi before 4.98.08, as used in SUSE Studio Onsite 1.2 before 1.2.1 and SUSE Studio Extension for System z 1.2 before 1.2.1, allows attackers to execute arbitrary commands via shell metacharacters in the path of an overlay file, related to chown.

CVE-2011-4089
Published: 2014-04-16
The bzexe command in bzip2 1.0.5 and earlier generates compressed executables that do not properly handle temporary files during extraction, which allows local users to execute arbitrary code by precreating a temporary directory.

CVE-2011-4192
Published: 2014-04-16
kiwi before 4.85.1, as used in SUSE Studio Onsite 1.2 before 1.2.1 and SUSE Studio Extension for System z 1.2 before 1.2.1, allows attackers to execute arbitrary commands as demonstrated by "double quotes in kiwi_oemtitle of .profile."

Best of the Web