Najwa Aaraj, Vice President, Special Projects, DarkMatter
In the past, attacks came from a single user. Today, we have complex and coordinated attacks that target heads of state and world leaders. This can enable terrorism as well.
We need to worry about encryption, key management, and keeping data secure in all manners of transport.On one system, you can't just worry about the communication layer, but also the operating system and how you manage all of this.
First and foremost, we need secure protocols. We may need non-repudiation, anonymity, etc - need to link it all together. We need to make sure it's all there.
Of course, if the kernel and hardware have security issues, you'll be in big trouble. Need to worry about data at rest, real time integrity monitor, hardened cryptographic library, key management and hardened OS and kernel.
Encryption should be intractable by theoretical cryptanalysis, but it also needs to be implemented correctly.
Common side-channel attacks: power analysis, EM analysis and timing. For example, when you are generating keys power usage will look the same with every key. Most common targets are smart cards, smart phones and FPGA microcontrollers.
Counter measures are most often implemented at the algorithm level. For example, masking/blinding of randomness, constant time implementations and pre-computations and leak reduction techniques.
We additionally need protocol level countermeasures to reduce the amount of leakage to less than the minimum required for key recovery using SPA/DPA/EM-based leakage and to reduce interim states that could lead to leakage.
In the hardware level, you can choose NAND gates that don't leak information about power consumption.
You need to consider all of these factors, and additionally make sure you write your software securely as well!
In the past, attacks came from a single user. Today, we have complex and coordinated attacks that target heads of state and world leaders. This can enable terrorism as well.
We need to worry about encryption, key management, and keeping data secure in all manners of transport.On one system, you can't just worry about the communication layer, but also the operating system and how you manage all of this.
First and foremost, we need secure protocols. We may need non-repudiation, anonymity, etc - need to link it all together. We need to make sure it's all there.
Of course, if the kernel and hardware have security issues, you'll be in big trouble. Need to worry about data at rest, real time integrity monitor, hardened cryptographic library, key management and hardened OS and kernel.
Encryption should be intractable by theoretical cryptanalysis, but it also needs to be implemented correctly.
Common side-channel attacks: power analysis, EM analysis and timing. For example, when you are generating keys power usage will look the same with every key. Most common targets are smart cards, smart phones and FPGA microcontrollers.
Counter measures are most often implemented at the algorithm level. For example, masking/blinding of randomness, constant time implementations and pre-computations and leak reduction techniques.
We additionally need protocol level countermeasures to reduce the amount of leakage to less than the minimum required for key recovery using SPA/DPA/EM-based leakage and to reduce interim states that could lead to leakage.
In the hardware level, you can choose NAND gates that don't leak information about power consumption.
You need to consider all of these factors, and additionally make sure you write your software securely as well!
Posts
No comments:
Post a Comment