Commentary

George Hulme
 

Modeling IT Attacks

Every day IT managers have to contend with an ever-changing risk environment. That's where good risk modeling can help.

Every day IT managers have to contend with an ever-changing risk environment. That's where good risk modeling can help.Late Friday afternoon, EE Times ran a story about ongoing research at NIST and George Mason University that aims to create "attack graphs" designed to help measure the risk posture of an organization:

By analyzing and assigning probabilities to every path a hacker could use to penetrate a computer system, NIST hopes attack graphs will help IT managers identify weak points that need to be patched to safeguard valuable data.

More Security Insights

White Papers

More >>

Reports

More >>

Webcasts

More >>

Attack graphs, developed by NIST jointly with George Mason University, calculate the vulnerability of each path into a computer system using NIST's National Vulnerability Database (NVD). By assigning a probable risk to various computer network pathways, the researchers hope to secure computer systems from multistep attacks.

Here's how NIST described the technology in its announcement:

NIST researchers evaluate each route and assign it a risk based on how challenging it is to the hacker. The paths are determined using a technique called "attack graphs." A new analysis technique based on attack graphs was jointly developed by Singhal and research colleagues at George Mason University. A patent is pending on the technique.

This type of threat modeling can go a long way in helping security teams determine which patches they need to deploy first. For instance, by evaluating the vulnerabilities in a network through a scan, you could see that there are many low, medium, and high vulnerabilities scattered about. Fortunately, the low-risk vulnerabilities are on the perimeter, and the highly critical flaws are deep inside the corporate network on a number of servers.

The bad news is that the business managers and application owners don't want those servers patched for another three weeks, because it's so costly and risky to mess with them. What do you do now to mitigate those critical vulnerabilities?

Well, a close look at your attack graph (as NIST is calling it) reveals that by patching a few low-risk vulnerabilities on the perimeter, all risky external access to those at-risk servers has been closed. You can sleep now knowing that those servers are relatively safe until the business will let you apply patches.

Threat modeling like this certainly isn't new, and security vendors such as Skybox Security and RedSeal Systems have been providing modeling capabilities for some time.


Related Reading




Currently we allow the following HTML tags in comments:

Single tags

These tags can be used alone and don't need an ending tag.

<br> Defines a single line break

<hr> Defines a horizontal line

Matching tags

These require an ending tag - e.g. <i>italic text</i>

<a> Defines an anchor

<b> Defines bold text

<big> Defines big text

<blockquote> Defines a long quotation

<caption> Defines a table caption

<cite> Defines a citation

<code> Defines computer code text

<em> Defines emphasized text

<fieldset> Defines a border around elements in a form

<h1> This is heading 1

<h2> This is heading 2

<h3> This is heading 3

<h4> This is heading 4

<h5> This is heading 5

<h6> This is heading 6

<i> Defines italic text

<p> Defines a paragraph

<pre> Defines preformatted text

<q> Defines a short quotation

<samp> Defines sample computer code text

<small> Defines small text

<span> Defines a section in a document

<s> Defines strikethrough text

<strike> Defines strikethrough text

<strong> Defines strong text

<sub> Defines subscripted text

<sup> Defines superscripted text

<u> Defines underlined text

InformationWeek encourages readers to engage in spirited, healthy debate, including taking us to task. However, InformationWeek moderates all comments posted to our site, and reserves the right to modify or remove any content that it determines to be derogatory, offensive, inflammatory, vulgar, irrelevant/off-topic, racist or obvious marketing/SPAM. InformationWeek further reserves the right to disable the profile of any commenter participating in said activities.

Disqus Tips To upload an avatar photo, first complete your Disqus profile. | View the list of supported HTML tags you can use to style comments. | Please read our commenting policy.
T-Shirt Giveaway T-Shirt Giveaway: Each week we're selecting one great comment from our readers. The author of the comment will receive an InformaitonWeek Community t-shirt. So get posting!
Subscribe to RSS

Resource Links