+1 613 254 5456
adjust font size Increase Font Size Reset Font Size Decrease Font Size

Elliptic is expanding its popular line of security protocol accelerators with the introduction of SPAcc-LTE, a highly efficient security processing engine for the rapidly developing 4th Generation mobile wireless Jan31 SPAcc-LTE1-300x224markets.

 

The International Telecommunication Unit (ITU) has recently selected LTE-Advanced and IEEE 802.16m as the technologies to deliver high bandwidth mobile broadband data for smartphones, tablet computers and other mobile wireless devices. The wireless broadband bandwidth is increasing at an incredible rate, jumping to 100 Mbps for mobile devices and an incredible 1 Gbps for fixed wireless devices. These high data rates must be achieved against a backdrop of increasing demands for enhanced privacy, greater energy efficiency and longer battery life.

 

The CLP-620 SPAcc-LTE is a high-performance cost- and power-efficient security engine that supports all confidentiality and integrity algorithms required for 3GPP/LTE/LTE-Advanced protocols. These algorithms are based on ciphers like AES, SNOW 3G, ZUC, and legacy ciphers such as Kasumi to support older networks. The security engine is targeted at high-performance base stations, handsets and femtocell applications.

 

“Elliptic strives to remain at the forefront with leading edge security IP solutions backed by acknowledged security experts” said Elliptic CTO Mike Borza. “CLP-620 is the first security IP on the market that supports all algorithms required for 4G wireless markets around the world, including the ZUC based algorithms which have been recently introduced to target wireless networks in key Asian markets”.


Elliptic Technologies is joining forces with Freescale Semiconductor – a leader in the design and manufacturing of embedded semiconductors, to showcase its Ellipsys Trust Framework ™ in tandem with Freescale’s QorIQ processor products to create trusted execution environments.

 

At the conference, Elliptic will demonstrate how Ellipsys Trust Framework (ETF) can be used to build and install trusted firmware on QorIQ based systems. Trusted execution environments enable a vast array of protections of systems and users, including tamper proof firmware installations and system provisioning for identification, secure manufacturing and secure field updates.


In the previous blog “The Many Flavors of AES – Part 1″ we gave a little background on the AES standard and its most used modes which are tied to specific applications. In the current blog we will dive deeper into the world of AES “modes”.

 

Some of the better known and widely used AES “modes” are: ECB/CBC/OFB/CFB/CTR/CCM/GCM/XTS.

 

A few words about ECB/CBC/OFB/CFB/CTR. These are approved modes of using a block cipher (like AES) and are covered in detail in NIST SP 800-38A (csrc.nist.gov/publications/nistpubs/800-38a/sp800-38a.pdf). A nice picture of ECB/CBC/OFB/CFB can be found on page 229 of the Handbook of Applied Cryptography. ECB or Electronic Code Book is the base use of AES. A pure block cipher application where each transaction involves putting in a 128, 192, or 256-bit key and a 128-bit block of data, and sending it through the AES cipher with a 128-bit of data coming out. Either a 128-bit block of plaintext [3] data goes in with a key and a 128-bit block of ciphertext comes out, or the reverse. Nothing is saved between blocks. This is nice, but in truth AES-ECB is not very useful (safe) because it is susceptible to cryptographic attacks; it essentially breaks down to a simple substitution cipher, where a given 128-bit block of plaintext is always encrypted to the same 128-bit block of ciphertext, and thus can be statistically analyzed.

 

The CBC/CFB/OFB modes address this problem with ECB by introducing feedback between blocks of data, which means an initial value (cryptographic nonce [4]) is introduced. Now there are three inputs to get encryption or decryption started on a message: key, initial value, and data block; and each subsequent block takes feedback of some part of the previous AES operation as part of its input: key, feedback value, and data block. Each of CBC/CFB/OFB apply different feedback, and are suited to different applications.

 

CTR mode starts the same way as CBC/CFB/OFB with an initial value, but there is no feedback! This is very useful because it means that the operation can be pipelined – particularly useful for hardware implementations or multiprocessor machines where blocks can be processed in parallel. The way this is accomplished is by selecting an initial value (nonce) for what is called the counter (hence CTR), and defining an algorithm for incrementing the counter (the simplest and most common algorithm is add one at each step). For each block of data to be processed, the current value of the counter (128-bit) is fed into an AES-ECB unit together with the key being used, and the output 128-bit block from this, which is usually the output data, is XOR’d [5] with the input data block. For the next time through, the updated counter value is used. Note there is no feedback from the output to the input, so pipelining is possible. Another nice thing about AES-CTR mode is that it uses the same operation for both encryption and decryption, thus making AES-CTR implementations smaller than other AES mode implementations.

 

AES-CCM stands for AES-CTR with AES-CBC MAC which sort of makes an acronym if you look at it long enough. It is an example of an integrated cipher and MAC, which as we’ve stated before usually happen together in sound cryptographic systems. AES-CTR mode is as described above, and is applied to data for encryption. The interesting thing about this compound mode is that the MAC is generated by a novel use of AES-CBC. Essentially AES-CCM pushes the message through the AES cipher twice: once in AES-CTR mode to output the plaintext or ciphertext, and a second time through in AES-CBC mode with the final output block being the MAC. There’s a little more interaction than that, but at this level, it’s a pretty good idea of what goes on. There are some other uses of AES in a MAC mode (like CBC above), for instance AES-f9, and AES-XCBC.

 

AES-GCM stands for Galois Counter Mode AES. For the mathematically inclined, Galois Fields are Finite Fields i.e. fields with a finite number of members. Field properties allow operations that are very useful cryptographically. For the rest of us, AES-GCM was developed to answer the need for VERY high throughput MAC’s for VERY high data rate applications such as 10/40/100 Gbps Ethernet. The older hashes such as SHA are not very scalable to these sorts of data rates. AES-CTR mode as explained above is scalable as it is can be pipelined in hardware. In AES-GCM the MAC’s are produced using special structures called Galois Field Multipliers and as you can guess, they are multipliers that use Galois Field operations to produce their results. The key thing is that they are scalable, and can be selected to match the throughput requirement of the data. AES-GCM is used in IPsec, 1619.1 (tape encryption), MACsec (Ethernet port security) to mention a few, and these are typically multi-Gbps applications.

 

As seen above, AES shows its versatility, and the list of protocols that use some modes of AES continues to grow. This makes the AES-based solution selection process that much harder.

 

To be continued …

 

[3]Plaintext is unencrypted data. Ciphertext is encrypted data. Plaintext is encrypted to
   form ciphertext, or ciphertext is decrypted to recover plaintext.
[4]Nonce n[ot to be used more than]once as a mnemonic. This is a random piece of data used
   to seed a cryptographic operation.
[5]XOR is a logic operation where two like inputs produce a true output when the inputs
   differ. In binary, inputs of (1,1) or (0,0) produce an output of 0, while inputs of
   (1,0) or (0,1) produce an output of 1. Bit-wise XOR is very efficient in most systems.

You’ve been sent on a mission to get some “AES encryption”, and after a quick look you find a multitude of expressions that contain AES. You may have found out that the acronym “AES” stands for Advanced Encryption Standard. You realize that it’s going to take more than a few minutes to find what you need. In fact, AES isn’t nearly enough information on the shopping list. This needs to be done hand-in-hand with more information about what’s available and what trade-off’s you can make, so you can hone in on the best solution for you.

 

First a little background. The American National Institute of Standards and Technology (NIST) www.nist.gov had a big contest to identify a successor to the venerable Data Encryption Standard (DES), which attracted candidate ciphers from around the world. The contest ended and a modified form of the cipher Rijndael was selected, and branded AES on November 26, 2001. AES was standardized as FIPS-197 (www.nist.gov/itl/upload/fips-197.pdf). FIPS is the American Federal Information Processing Standards. NIST also has a standard for the going-out-of-use DES, called FIPS 140-2.

 

AES candidates were scored on a variety of attributes including security and efficiency of mapping and throughput in hardware and software. The hardware and software part was important because many older ciphers don’t map efficiently into dedicated hardware or even modern general purpose processors. DES is a 56-bit symmetric key [1] block cipher that operates on 64-bit blocks. 3DES is a variant on DES that uses three different 56-bit keys sequentially to create a more secure version of DES. For cryptographically sound ciphers, longer keys (more bits) means tougher to crack by exhaustive attacks, which means more secure. AES is a block cipher which operates on 128-bit blocks of data and supports 128, 192, or 256-bit keys depending on the desired level of security, and the available computational horsepower. Longer keys means more work to encrypt/decrypt. More secure is better, but it comes at a price. In the case of AES, using 128/192/256-bit keys means encryption and decryption involves 10/12/14 rounds of data operations using the key and the block of data. More rounds means more work and more time.

 

AES has been well received and wildly successful. There are a large numbers of modes of AES used in a number of different applications, and that’s where things start to get a little more confusing. Part of selection is knowing what you need, and knowing what you need is about application. For instance, one application space that is quite active now and has a checkered cryptographic past is Wi-Fi. The Wi-Fi security standard IEEE 802.11i-2004 makes use of AES in a couple of modes. Other well-known application spaces that use AES as part of their security protocol include IPsec (AES-CBC and AES-GCM), SSL/TLS (AES-CBC), Disk Encryption (XTS-AES), MACsec (AES-GCM), LTE-Advanced (AES-CTR, AES-CMAC), and so on. Encryption and security are NOT synonyms and the proliferation of application modes of AES is a product of both fertile imaginations and serious threat assessments and security perimeter planning in these spaces. To list some of the better known and widely used AES “modes”: ECB/CBC/OFB/CFB/CTR/CCM/GCM/XTS.

 

To be continued …

 

[1] Symmetric key (private key) ciphers use the same key for
encryption and decryption. This differs from asymmetric (public key)

It has been announced at an international hacker conference recently that hackers have taken control over the Sony PlayStation 3. The vulnerability was found in the random number generator which is used to create private keys for the system. Apparently the random number generator does not create random numbers at all… The “random” numbers are actually a constant number… This is a significant flaw because hackers can take complete control of the console. All retail PS3 systems may have this vulnerability.

More on this story.


The IEEE Standards Board announced a few months ago its approval of the P1619.2 draft standard for wide-block encryption and block storage devices. This standard will be published officially as IEEE Std 1619.2-2010.

 

The latest Standards Watch Issue 9 just released by Elliptic Technologies is devoted entirely to this new standard for storage encryption, and it includes a review of the standard’s applications space as well as a comparison against 1619 -  the narrow-block encryption standard for disk drives and similar devices.


Featured Products

A proven HDCP-based content protection solution that provides robust security inside Trusted Execution Environments (TEEs) and enforces the protection of sensitive information to ensure that it is stored, processed and accessed only by authorized applications.The solution integrates seamlessly within frameworks such as ARM TrustZone™, where the critical security components are embedded in a trusted and secure OS environment. The non-critical components are executed by the rich OS, such as Android.
tower CLP-630: Multi-Packet Manager Security Engine
A highly programmable and unique Security Protocol Accelerator specifically designed to efficiently process data for high capacity wireless and network applications. The engine is perfectly suited for applications that deal with multiple active connections and significant traffic load on different contexts, such as 4G LTE-Advanced wireless cellular base stations and femtocells.