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.

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

in the IP header that are left unchanged by intermediate systems to hide a few, 28<br />

in the named approach, bits in otherwise legitimate IP packets. Similar approaches<br />

are conceivable for transport layer protocols, but we do not expect these to provide<br />

a significantly larger count of bits per packet.<br />

For IPv4 or TCP, the header length can be adjusted to allow adding additional<br />

options. In principle, a bot herder could use the extra space obtainable by adjusting<br />

the length field to increase the b<strong>and</strong>width of a steganographic approach. This<br />

highlights however an issue which also appears, though with a different nature,<br />

in the approach described in the previous paragraph. The use of additional options<br />

is very rare for both TCP <strong>and</strong> IPv4, i.e. while the attacker is free to choose<br />

an unsuspicious payload, using oversized headers may attract even more attention<br />

than simply transferring the steganographic payload in the application layer section<br />

of the packet. For the approaches that do not inflate the size of the header, the minuscule<br />

steganographic payload will require that a significant number of packets<br />

is transferred for any significant botnet protocol payload. Thus, differences in communication<br />

patterns may again be similarly or even more striking than without<br />

such an attempt to obfuscate the C 2 channel using these techniques.<br />

C. Use of cryptography<br />

Cryptographic protocols are designed to provide three core properties:<br />

• Confidentiality<br />

• Integrity<br />

• Authenticity<br />

Confidentiality ensures that messages cannot be read in transit. Integrity allows<br />

a peer to verify that messages have not been modified in transit <strong>and</strong> authenticity<br />

provides proof of identification or approval by a verified entity.<br />

The Storm botnet employed a custom encryption algorithm, its supposed<br />

successor, the Waledac botnet, the st<strong>and</strong>ardised AES algorithm but both implementations<br />

employed static keys [16]. When a static key is used, a network intrusion<br />

detection system may either decrypt an observed payload with the known<br />

key <strong>and</strong> then apply its pattern matching algorithm or sometimes it may even be<br />

enough to match on the encrypted message.<br />

Duqu could be considered an example for correct use of cryptography<br />

in that it can connect to its C 2 server through a legitimate HTTPS connection,<br />

however the C 2 server uses a frequently replaced self-signed certificate, rendering<br />

the connection subject to man-in-the-middle attacks. This appears to be<br />

acceptable from the malware author’s point of view since the actual payload<br />

is encrypted with a symmetric key stored in its binary, illustrated also by that<br />

a second method for establishing a C 2 channel exchanges the same data but<br />

using plain HTTP [17].

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

Saved successfully!

Ooh no, something went wrong!