Discussion Locked

Threats against digital assets

0 helpful
2 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.
Tell us how your organization is prepared for threats against its digital assets, as featured in the June 25th Disaster Recovery e-newsletter. How does your organization work together to fulfill the needs of the disaster recovery plan?

2 replies

by lori g

This article says "There should be a methodology in place that allows you to simply switch the passwords".

How?! I need a methodology like that!

by miketalonnyc

The sentence in question was a bit of an over-simplification to meet space constraints on the column, however such methodologies can be put in place, and should probably be in place sooner rather than later.

In most cases, in the NT/2000 world, you can move in and change passwords that may have been breached via a workstation or server console that has the appropriate level of access rights once you are logged in.

Other operating systems will require additional methodology to implement security changes, and a change-request system should be in place for accountability after any security change no matter what OS you are using on your servers.

In any case, making sure that there are as few administrator or root level passwords as possible, and keeping close tabs on those passwords and who is using them, is a reasonable goal to attain.

Hope this helps clear things up.

Mike Talon

This discussion is closed to new replies.