21.03.2013 Views

Quantitatively Assessing and Visualising Industrial System Attack Surfaces

Quantitatively Assessing and Visualising Industrial System Attack Surfaces

Quantitatively Assessing and Visualising Industrial System Attack Surfaces

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

CHAPTER 5. CONCLUSION 49<br />

5.3 Criticality is dependent on context<br />

When examining this data, a natural question is ‘how many of these data points are really<br />

critical?’ This is an important but difficult question.<br />

Clearly, not all of them are critical to national systems, <strong>and</strong> some of them may even be<br />

demo systems with a legitimate reason to be Internet facing. However, some of these<br />

systems may be critical to a nation or at the very least the business that operates them.<br />

While it is difficult to quantitatively answer the question posed, we do not wish to avoid<br />

it.<br />

So in return we ask for refinement in the definition of criticality. Are we interested in<br />

the global economy, or a nation state, or a business critical operation? We might very<br />

well discover that a global economy means that a critical system to one nation resides<br />

in another nation. For example, 80% of Irel<strong>and</strong>’s natural gas is supplied by the UK<br />

wholesale market, <strong>and</strong> comes to Bord Gáis<br />

Éireann from three sub sea pipelines across<br />

the Irish sea. Thus the pressure pumps in Scotl<strong>and</strong> <strong>and</strong> Wales could be considered critical<br />

infrastructure to Irel<strong>and</strong>’s gas supply.<br />

We also point out that criticality can have temporal variance. In the example above, if<br />

Irel<strong>and</strong> has enough gas stored to ride-out shortages induced by temporary loss of those<br />

sub sea pipelines, then their criticality is reduced for short duration outages.<br />

To truly tackle this well-intentioned but poorly framed question, we must shift from a<br />

quantitative approach to a qualitative one. Analysis must be done on the data presented<br />

in the hope that it answers the question for a particular data point <strong>and</strong> in a particular<br />

context. This involves investigating each individual point hoping that clues from whois<br />

queries, hostnames, geolocation, logos on webservers, <strong>and</strong> other semi-reliable information<br />

can allow us to derive at least the company name of the asset owner. Then it is down to<br />

a querent to determine in conjunction with the owning organisation the criticality with<br />

respect to a given context.<br />

Criticality is a combination of dependency, process context, <strong>and</strong> risk. Additionally, there<br />

is no convenient tag for criticality. Only the users of a system have a notional concept of<br />

the utility of a system. Even then, they may not know that the system itself depends on<br />

services such as DNS for its daily functionality. Thus while we do not wish to dodge the<br />

question, we must admit we cannot with any confidence answer it for every single data<br />

point in this data set.<br />

Only further investigation can determine the answer for each data point on a case by case<br />

basis, with respect to the context or interests of a particular organisation.

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!