Dark Reading is part of the Informa Tech Division of Informa PLC

This site is operated by a business or businesses owned by Informa PLC and all copyright resides with them.Informa PLC's registered office is 5 Howick Place, London SW1P 1WG. Registered in England and Wales. Number 8860726.

Perimeter

2/11/2010
03:48 AM
Gadi Evron
Gadi Evron
Commentary
Connect Directly
Twitter
LinkedIn
RSS
E-Mail
50%
50%

How Much Crypto You Really Need

Last month an international team of researchers announced they had managed to factor a 768-bit RSA key. This raises interesting questions about handling encryption and planning ahead in your security strategy.

Last month an international team of researchers announced they had managed to factor a 768-bit RSA key. This raises interesting questions about handling encryption and planning ahead in your security strategy.I am not a cryptographer and therefore not an authority on the RSA algorithm. However, I would like to discuss the strategic use of encryption and how that impacts our decision on choosing and implementing an encryption scheme.

In the introduction to their paper (PDF), the researchers wrote:

Because the first factorization of a 512-bit RSA modulus was reported only a decade ago (cf. [7]) it is not unreasonable to expect that 1024-bit RSA moduli can be factored well within the next decade by an academic effort such as ours or the one in [7]. Thus, it would be prudent to phase out usage of 1024-bit RSA within the next three to four years.
The researchers make it clear that this is not an immediate threat, and while the use of larger keys should be phased in, there are no immediate security ramifications.

When choosing an encryption algorithm, you must first ask yourself what your purpose is -- in other words, conduct a risk analysis. What do you want to protect? How important is it? How vulnerable is it? What is the threat? Who is the threat?

If your biggest risk is your neighbor, then you can feel relatively secure using off-the-shelf encryption without worrying about too many details.

However, even if you are not a nation-state with an opponent that will invest unlimited resources to get your information, there are three main questions you should ask:

1. How long into the future would I like this information to remain secret? Based on this answer you can consult with an industry analyst as to projected computer power changes in the coming years. Any foreseeable breakthroughs in the math that could reduce the time needed to break the encryption. Then based on two factors, make the call: How paranoid do you feel you need to be according to your risk assessment, judged against the functionality you require and implementation costs?

2. Does my opponent have the resources to deal with this encryption? To break modern encryption on a PC could take longer than the life of the universe. Don't be confused by this statement: Consider what else your opponent might be willing to do to get your information. Encryption makes us feel safer, but it does not equate security.

As an alternative, also consider that encryption is a secret, and you might want to use several encryption schemes so as to not make one too secure to work with; you won't be able to trust people who run your daily operations to use it.

3. Because the algorithm is rarely the weakest link in real-world attacks, have I taken care of the implementation? Most attacks against encryption systems are against the implementation rather than the algorithm -- be it the programming, which should be done and reviewed by experts, or the procedures by which the encryption is put to use.

Further, side-channel attacks ranging from the less likely, such as TEMPEST (electromagnetic emanations) to Trojan horses (which are a significant threat), and from stolen laptops to buying off an employee, must not be left to chance. These should all be considered and planned for. The algorithm alone does not make you safe.

Follow Gadi Evron on Twitter: http://twitter.com/gadievron.

Gadi Evron is an independent security strategist based in Israel. Special to Dark Reading. Gadi is CEO and founder of Cymmetria, a cyber deception startup and chairman of the Israeli CERT. Previously, he was vice president of cybersecurity strategy for Kaspersky Lab and led PwC's Cyber Security Center of Excellence, located in Israel. He is widely recognized for ... View Full Bio

 

Recommended Reading:

Comment  | 
Print  | 
More Insights
Comments
Threaded  |  Newest First  |  Oldest First
COVID-19: Latest Security News & Commentary
Dark Reading Staff 8/10/2020
Researcher Finds New Office Macro Attacks for MacOS
Curtis Franklin Jr., Senior Editor at Dark Reading,  8/7/2020
Exploiting Google Cloud Platform With Ease
Dark Reading Staff 8/6/2020
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Write a Caption, Win an Amazon Gift Card! Click Here
Latest Comment: It's a technique known as breaking out of the sandbox kids.
Current Issue
Special Report: Computing's New Normal, a Dark Reading Perspective
This special report examines how IT security organizations have adapted to the "new normal" of computing and what the long-term effects will be. Read it and get a unique set of perspectives on issues ranging from new threats & vulnerabilities as a result of remote working to how enterprise security strategy will be affected long term.
Flash Poll
The Changing Face of Threat Intelligence
The Changing Face of Threat Intelligence
This special report takes a look at how enterprises are using threat intelligence, as well as emerging best practices for integrating threat intel into security operations and incident response. Download it today!
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2020-24348
PUBLISHED: 2020-08-13
njs through 0.4.3, used in NGINX, has an out-of-bounds read in njs_json_stringify_iterator in njs_json.c.
CVE-2020-24349
PUBLISHED: 2020-08-13
njs through 0.4.3, used in NGINX, allows control-flow hijack in njs_value_property in njs_value.c. NOTE: the vendor considers the issue to be "fluff" in the NGINX use case because there is no remote attack surface.
CVE-2020-7360
PUBLISHED: 2020-08-13
An Uncontrolled Search Path Element (CWE-427) vulnerability in SmartControl version 4.3.15 and versions released before April 15, 2020 may allow an authenticated user to escalate privileges by placing a specially crafted DLL file in the search path. This issue was fixed in version 1.0.7, which was r...
CVE-2020-24342
PUBLISHED: 2020-08-13
Lua through 5.4.0 allows a stack redzone cross in luaO_pushvfstring because a protection mechanism wrongly calls luaD_callnoyield twice in a row.
CVE-2020-24343
PUBLISHED: 2020-08-13
Artifex MuJS through 1.0.7 has a use-after-free in jsrun.c because of unconditional marking in jsgc.c.