Elliptical curve ciphers use much shorter key lengths than the RSA keys that we have traditionally used. We understand elliptical curve keys with short key lengths provide similar strength as RSA keys with much longer length.
The reduction in CPU time to work with the larger keys is optimal due to the reduction in CPU usage and the subsequent reduction in power.
RSA public key algorithms are not considered legacy as of yet. It is likely that they will be in the next several years. In practice RSA key pairs are becoming less efficient each year as computing power increases. Elliptic curve cryptography is a newer alternative to public key cryptography. Elliptic curves are very efficient and offer the same level of security over much shorter prime fields and therefore the performance of ECC is significantly better than RSA public key cryptography. ECC is considered Next Generation Encryption by the US National Security Agency.
In ASA OS 9.4(1), released March 22, 2015, the ASA started supporting several new cipher suites.
In ASA OS 9.3(2), released December 18, 2014, the ASA started supporting Transport Layer Security version 1.2.
In ASA OS 9.0(1), released on October 29, 2012, the ASA started supporting using ECDSA key pairs for generating certificates.
AnyConnect v4.x is required, Apex or Plus license.
Both 9.4(1) and 9.3(2) require Next Generation ASA. They will not run on older ASA models like the ASA 5505, 5510, 5520 or 5540.
Assure you do not have anyconnect-essentials configured under webvpn. AnyConnect Essentials license does not support these ciphers and isn't in use when the Apex or Plus AnyConnect 4 license is installed.
Understanding Cipher Suites
You can view all the ssl cipher suites that the ASA supports by typing
show ssl ciphers
Each cipher suite has several parts. These are a key exchange and establishment algorithm, a bulk encryption algorithm, a message authentication code algorithm and a pseudorandom function.
Let’s look at this cipher suite as an example.
In the cipher suite listed above
The key exchange algorithm is ECDHE-ECDSA.
The bulk encryption algorithm is AES256-GCM.
The message authentication code is SHA384.
ECDHE is an asymmetric algorithm used for key establishment.
ECDSA is an asymmetric algorithm used for digital signatures.
AES256-GCM is a symmetric block or bulk cipher used to protect the ‘data’.
SHA384 is a hash function used to assure the data’s integrity by the receiving party.
The ASA supports lots of other cipher suites and we will not discuss those here.
There are several things we need to do here
We need to create an ECDSA key pair on the ASA.
We need to create an CSR and submit that to a 3rd party certificate provider
Install the certificate we receive from the 3rd party provider.
Configure the ASA to only support elliptic curve ciphers.
Step 1 & 2.
Creating a SHA-2 CSR using ECDHA
See this other document I wrote for this procedure.
Install the Identity Certificate and Intermediate Certificate you receive from the 3rd party provider.
Authenticate the CA
crypto ca authenticate my-trustpoint.lab-asa.xxxx.com
Install the Identity Certificate
crypto ca import my-trustpoint.lab-asa.xxxx.com
I chose to only support TLSv1.2. I did this because all modern OS’s and browsers support TLSv1.2. I also chose to only support elliptical curve cipher suites. All modern OS’s and browsers support elliptic curve ciphers. If you need to provide support to Windows XP or Mac OS X 10.5 or earlier you cannot exclusively use elliptic curve ciphers.
Force the minimum version of TLS to be 1.2
ssl server-version tlsv1.2
Force TLSv1.2 to only support elliptical curve sipher suites
The built in windows supplicant has no issues blocking access to unauthenticated networks however I can not get NAM to do the same! Users will not be able to add or modify networks in the NAM client so i have set up the only profile to be an authenti...
We are in the process of certification testing with ISE 3566 2.6 equipment.But the above fails. The detail information of the log is shown below.5434 Endpoint conducted several failed authentications of the same scenarioWhen I searc...
I am wondering if anyone has come across the following scenario and if so what was your fix:In some areas of our environment we run NAM on our Win10 workstations to utilize eap-chaining. The machines use ActivClient as the middleware. We have ...
Hi All, I'm configuring remote access on an ASA5505 and have it a popular stumbling block. The Remote access VPN has connected but I cannot access internal resources or the internet. weirdly I can ping the external interface. It's a full tunnel VPN.&...
Both RSA and AD are setup as external identities. RSA is also using AD as identity store. So effectively all accounts are present in both ext. ID stores. What I’m trying is to set my policy so that when I use an account that ends “_a” it requires to use R...