22.01.2015 Views

Military Communications and Information Technology: A Trusted ...

Military Communications and Information Technology: A Trusted ...

Military Communications and Information Technology: A Trusted ...

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

402 <strong>Military</strong> <strong>Communications</strong> <strong>and</strong> <strong>Information</strong> <strong>Technology</strong>...<br />

V. Network layer observation of future botnets<br />

In this section, we analyse the properties that will remain observable given<br />

the expected design of future botnets discussed in section IV. We start with describing<br />

the properties that remain directly observable in section V.A, followed by<br />

an analysis of how the behaviour of applications correlates with them. Finally, we<br />

motivate a granularity below traditional netflows as the base for further analysis<br />

<strong>and</strong> ultimately detection in section V.C.<br />

A. Observable features<br />

While OSI layer 2 is persistent in local networks only, i.e. its header does not<br />

contain any information written by the source of a layer 3 packet unless the point<br />

of observation is within the very same local network, we can learn the size of its<br />

payload <strong>and</strong> the observation time from it. The former will be equal to the size<br />

of the layer 3 packet transmitted by the source unless layer 3 fragmentation occurs.<br />

We suggest however to disregard this special case <strong>and</strong> treat fragments of a packet<br />

as if they were individual packets sent with the observed size.<br />

For the latter, i.e. the observation time, a simple relation to the timestamp t source<br />

at which an observed packet was transmitted by the source holds. With m denoting<br />

the mean time needed for traversing the links until reaching the observation point<br />

<strong>and</strong> j the jitter introduced by differences in network load <strong>and</strong> routes, we can characterise<br />

an observation timestamp t as:<br />

t = t source + m + j<br />

Thus, while we cannot determine t source exactly without knowing m <strong>and</strong> j, we<br />

can infer that the delay between two consecutive observations differs from the delay<br />

at the source only by the differences of the jitter applied to these observations. I.e.<br />

the smaller j in the equation given above, the better we can approximate that delay<br />

by observing the delay at our observation point.<br />

Based on the analysis provided in section IV, we assume that headers at layer 3<br />

<strong>and</strong> 4 will generally be genuine, but at least allow associating observed packets with<br />

a particular flow. Note that forged source addresses, where possible, may serve to<br />

complicate attribution but would not impede with gathering <strong>and</strong> attributing data<br />

for the destination system.<br />

Our analysis further suggests that while OSI layer 5 <strong>and</strong> up data may be available<br />

technically, it will not contain exploitable features due to the combination<br />

of proper encryption <strong>and</strong> tunnelling through legitimate protocols. Note that with<br />

what we would call “not proper encryption”, using payload signatures may still be<br />

possible, as pointed out in [5].

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

Saved successfully!

Ooh no, something went wrong!