Analytics
1/22/2013
01:47 AM
Dark Reading
Dark Reading
Quick Hits
50%
50%

How To Conduct An Effective IT Security Risk Assessment

Measuring risk is a key to justifying new security spending. Here's a road map for doing it

[Excerpted from "How to Conduct an Effective IT Security Risk Assessment," a new report posted this week on Dark Reading's Risk Management Tech Center.]

Many security and compliance projects begin with a simple idea: assess the organization's risk of vulnerabilities and breaches. Indeed, implementing an IT security risk assessment is absolutely critical to the overall security posture of your organization.

An effective security risk assessment can prevent breaches, reduce the impact of realized breaches, and keep your company's name from appearing in the spotlight for all the wrong reasons. Regular IT security risk assessments also enable organizations to build up a cache of historical data that can be used to effectively gauge and communicate monetary impact related to risks -- and, hopefully, convince upper management to take decisive action to reduce the organization's threat surface.

It's important to note that not every IT security risk assessment is alike -- or even remotely close. Indeed, there are many ways to perform IT security risk assessments, and the results may vary widely depending on the method used. It should also be noted that performing a risk assessment is a very small part of the overall risk management process.

There are basically three risk management components:

1. Evaluation and assessment, to identify assets and evaluate their properties and characteristics.

2. Risk assessment, to discover threats and vulnerabilities that pose risk to assets.

3. Risk mitigation, to address risk by transferring, eliminating or accepting it.

The presence of these three high-level processes is constant in all risk assessment methodologies, although what they are called may vary. Our primary focus in this report is to discuss the assessment itself, but we will also touch on key elements of risk evaluation and assessment, as well as risk mitigation.

Traditional risk assessment includes general IT-related issues such as accidental outages, hardware failures, and uptime. Security risk assessment, on the other hand, is just what it sounds like -- analysis of the issues relating directly to security threats. However, many organizations lump these two types of assessments together, applying more generic risk models in the more dynamic world of IT security. That's a problem.

In many cases, the data compiled about a given asset and its risk is created with great care, but is not updated in a timeframe that would enable security pros to address the changing threat landscape. This leads to Band-Aid-style fixes, such as hard reassessment intervals every one or two years. Ultimately, this will leave gaps in security for months at a time.

For a look at the steps required to perform an effective IT security risk assessment -- and some key tips for implementing them -- download the free report.

Have a comment on this story? Please click "Add a Comment" below. If you'd like to contact Dark Reading's editors directly, send us a message.

Comment  | 
Print  | 
More Insights
Register for Dark Reading Newsletters
White Papers
Cartoon
Current Issue
Dark Reading December Tech Digest
Experts weigh in on the pros and cons of end-user security training.
Flash Poll
Threat Intel Today
Threat Intel Today
The 397 respondents to our new survey buy into using intel to stay ahead of attackers: 85% say threat intelligence plays some role in their IT security strategies, and many of them subscribe to two or more third-party feeds; 10% leverage five or more.
Video
Slideshows
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2014-4807
Published: 2014-11-22
Sterling Order Management in IBM Sterling Selling and Fulfillment Suite 9.3.0 before FP8 allows remote authenticated users to cause a denial of service (CPU consumption) via a '\0' character.

CVE-2014-6183
Published: 2014-11-22
IBM Security Network Protection 5.1 before 5.1.0.0 FP13, 5.1.1 before 5.1.1.0 FP8, 5.1.2 before 5.1.2.0 FP9, 5.1.2.1 before FP5, 5.2 before 5.2.0.0 FP5, and 5.3 before 5.3.0.0 FP1 on XGS devices allows remote authenticated users to execute arbitrary commands via unspecified vectors.

CVE-2014-8626
Published: 2014-11-22
Stack-based buffer overflow in the date_from_ISO8601 function in ext/xmlrpc/libxmlrpc/xmlrpc.c in PHP before 5.2.7 allows remote attackers to cause a denial of service (application crash) or possibly execute arbitrary code by including a timezone field in a date, leading to improper XML-RPC encoding...

CVE-2014-8710
Published: 2014-11-22
The decompress_sigcomp_message function in epan/sigcomp-udvm.c in the SigComp UDVM dissector in Wireshark 1.10.x before 1.10.11 allows remote attackers to cause a denial of service (buffer over-read and application crash) via a crafted packet.

CVE-2014-8711
Published: 2014-11-22
Multiple integer overflows in epan/dissectors/packet-amqp.c in the AMQP dissector in Wireshark 1.10.x before 1.10.11 and 1.12.x before 1.12.2 allow remote attackers to cause a denial of service (application crash) via a crafted amqp_0_10 PDU in a packet.

Best of the Web
Dark Reading Radio
Archived Dark Reading Radio
Now that the holiday season is about to begin both online and in stores, will this be yet another season of nonstop gifting to cybercriminals?