
Subscribe to
Computerworld
or
Other Security Stories
March 30, 2005 (Computerworld) -- It happens all too often that the first time a vulnerability becomes known is when a forensic investigation is under way to find out how a system was broken into, or when a virus that's already spreading is being analyzed.
Whether the vendors knew about the vulnerability a year ago or found out about it this morning, if the exploit code exists when the vulnerability is made public, it's a potential zero-day exploit that can threaten critical assets immediately.
Even after a patch has been created and advertised, there can be an extended period while the patch is tested and deployed on every system. During this time, systems are vulnerable to being exploited. Worse yet, most incidents of attack accelerate after an announcement or release of a patch.
A well-known example is the Slammer worm that targeted Microsoft SQL Servers. A hybrid worm that combined a distributed denial-of-service (DDoS) attack with the automated propagation techniques used by worms such as Code Red had targeted a known vulnerability in SQL Server systems. While signature-based systems are needed to provide overall protection, they aren't sufficient to stop unknown and zero-day exploits and application-level threats. To protect against emerging threats, organizations should consider using the following methods:
Enforce acceptable protocol and application usage
Many attacks target protocols such as HTTP, DNS and FTP. Certain programming errors, such as unchecked buffers, can be exploited by attackers to compromise or damage a system. These attacks exploit loose programming practices in applications and systems. Enforcing acceptable protocol behavior goes beyond checking requests for comments (RFC) and ensures that the data flowing through the network adheres to the policies of the applications running in your environment.
Most application attacks, by their very nature, contain malicious code that would cause the attack packet stream to violate acceptable protocol usage. Simply put, since it's clearly known whether a packet stream complies with acceptable application or protocol usage, any data stream that violates those protocols can be deemed malicious and thus be blocked.
Here's an example: The HTTP 1.0/1.1 protocol allows host names up to any length, so an RFC checker wouldn't bother checking this field.
|
|
Print this Story |
|
Send Us Feedback |
|
E-mail this Story |
|
Digg this Story |
|
Slashdot this Story |
|
|
|
|
|
|
|
|
All Zones Application Performance Zone Enterprise-Class Security Zone Enterprise Solutions Zone The File Data Management Zone Grid Computing on Windows Zone Security Management Zone ITIL Best Practices Zone The SAS Zone Storage Virtualization Zone The Data Center Management 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 SecurityThere's plenty of talk about how to behave during a Customs search of your computer and gear, but Jon Espenschied's got tips for securing your data (and privacy) before you reach the border. Click here to read the latest column by Jon Espenschied |
![]() |
Layered Security Solutions
Although basic network security issues have changed very little over the past decade, the
network security landscape has changed dramatically. Today's IT professionals still have the
primary responsibility of protecting the confidentiality of corporate information, preventing
unauthorized access, and defending the network against attacks. Security experts and analysts agree that a security solution comprised of multiple layers is the best defense against today's increasingly sophisticated attacks.Download this white paper
|
Universal Threat Management - Because Conventional UTM is Not Enough!
This white paper, written by Mark Bouchard of Missing Link Security Services, examines the challenges confronting today's enterprises with respect to managing threats on a network. It also discusses the need for "Universal Threat Management", which is a security solution approach for all physical locations within an enterprise that require threat protection.Download this white paper |
Selecting the Right Threat Management Solution
This short demo will guide you through key considerations for selecting a solution to manage threats on a network. Learn about the popularity of Unified Threat Management (UTM), and how it fits into an overall security solution. Explore critical elements of a network-wide solution for multisite and large network-size deployments and identify the four key features of a threat management solution.View this demo
|
| About Us Advertise Contacts Editorial Calendar Help Desk Jobs at IDG Privacy Policy Reprints Site Map |
|
CIO The Industry Standard |
