
Subscribe to
Computerworld
or
Other Security Stories
April 12, 2002 (Computerworld) -- Have you ever wondered what the best ways are to get hacked, be adversely affected by disasters, or otherwise lose information stored on your computer systems? Here, in no particular order, are the 21 best ways to not secure your systems:
1. Don't pay attention to or even bother to understand what you're trying to protect.
2. Leave your databases, especially those containing credit card or other confidential information, unencrypted. And be sure to store them on publicly accessible servers.
3. Don't patch your software or update your virus signatures, and never, ever run vulnerability assessments to detect newly discovered software flaws and system misconfigurations. It's just too time-consuming.
4. When an employee quits or is let go, leave his network log-ins and e-mail accounts enabled. You never know when he might want to check in on things.
5. Don't create any security policies that document how you're safeguarding your information to protect your organization and clients from information disasters and legal liabilities.
6. If you do happen to have a security policy, never refer to it, enforce it, update it or do what it says.
7. Completely outsource your information security initiatives. There's no need for anyone inside your organization to worry about such matters.
8. By all means, don't take an inventory of your information systems or document your network.
9. Apply the principle of greatest privilege. Give all users the greatest amount of access to your information systems. Everyone should have access to everything -- it's only fair, right?
10. Rely solely on technology. Firewalls, encryption and antivirus software are all you need to protect your information.
11. Run your business without disaster recovery and business continuity plans. After all, you can think clearly and make critical decisions under pressure, right?
12. Don't monitor your systems. They'll be fine running by themselves, and if anything major happens with the integrity or availability of your information, you'll be notified automatically, won't you?
13. Don't back up your data, but if you must, don't test your backups.
|
|
Print this Story |
|
Send Us Feedback |
|
E-mail this Story |
|
Digg this Story |
|
Slashdot this Story |
|
|
|
|
|
|
|
|
All Zones Application Performance Zone Business Continuity Zone Data Center Management Zone Enterprise-Class Security Zone The File Data Management Zone Grid Computing on Windows Zone Security Management Zone ITIL Best Practices Zone The SAS Zone Storage Virtualization Zone Business Intelligence and Analytics Zone |
|
|
| ||||||||
| ||||||||
| ||||||||
|


Security Management ZoneSecurity management is the process of developing a comprehensive data protection plan. It takes into account all potential threats, the existing network environment, the future needs of the organization, and lays out a multi-tiered blueprint to integrate the security technology needed to combat these threats. CDW can help keep your network and data secure. Visit the CDW Security Management Zone now See All Zones
|
Fired up about IT? Join Sharkbait and share your true tales of IT. SharkBait is the place for you to sound off about everything IT the good, the bad, and the rest of the weird stuff you deal with every day.New baits |

"Security Directions" virtual trade show2008's Code-Red Security Issues for Protecting the EnterpriseWebcasts, white papers, demos, and more. Presented in a unique 3-d environment. Enter our show right now! Click here to enter
|

In SecuritySecurity's important, and risk must be addressed, right? Sure, but watch for four signs your policies go a bit overboard. Click here to read the latest column by Jon Espenschied |
| About Us Advertise Contacts Editorial Calendar Help Desk Jobs at IDG Privacy Policy Reprints Site Map |
|
CIO The Industry Standard |