Tag Archives: security

Como proteger seu novo iPhone em três passos simples

Com a chegada do Iphone 6 e do Iphone 6 Plus, a Symantec compartilha um blog post que apresenta três passos simples para garantir a segurança dos dispositivos e contas da Apple.

Life on Mars: How attackers took advantage of hope for alien existance in new Darkmoon campaign

Attackers sent fake NASA emails containing “proof” of alien life on Mars to spread Backdoor.Darkmoon.

??????????????????? Snifula ???????????????

      No Comments on ??????????????????? Snifula ???????????????

Snifula の亜種は、セキュリティ製品 PhishWall のインストールを推奨する画像が銀行の Web サイト上に表示されないよう妨害します。

The Future of SSL Encryption

      No Comments on The Future of SSL Encryption

Most of you reading this will immediately connect the acronym “RSA” with the encryption algorithm invented in 1977 by Rivest, Shamir and Adleman and which is still today the most-adopted in Public Key Infrastructure (PKI) systems, such as SSL. Through a mathematical process that remains ingenious even by modern standards its merits are strong, but the world changes very quickly in technology and the paint on the RSA algorithm is starting to crack. Some RSA key lengths have been successfully broken over the years, and RSA-1024 was deprecated by the industry for Public CA use before any hack could be proven, but it would only have been a matter of time.

Today’s regulations mandate a minimum of 2048 bits for keys in public SSL certificates, but since there is no randomization in the RSA process, the availability of greater computing power will eventually make attacks on longer key lengths feasible. This will not happen for the foreseeable future to 2048 bit keys, but takes us to the next concern.

ssl-blog.jpg

Our modern lives rely more and more on smaller devices, down to “smartwatches”, but we still expect our data to be kept secure by them as it would be on our traditional computers. Smaller devices pose two problems though. First, they have comparably low computing power, and second they are used in mobility, meaning they rely on batteries to work, making every minute of battery life truly important.

With the increasing key lengths required for the decryption of even common services secured by an SSL certificate, there comes an issue about the amount of time and power a small device will need to calculate its share of a certificate key. But help is at hand through Symantec, and has been available for several months now, in a publicly-available production environment. Meet Elliptic Curve Cryptography, a.k.a. ECC, a part of Symantec’s public SSL certificate offering.

ECC is a newer mathematical algorithm that came into widespread use in 2005, and which solves the two issues above by providing a better level of security through shorter key lengths: an ECC key of only 256 bits will provide a security level comparable to RSA with 3072 bit keys. ECC can further be coupled to other smart encryption technologies such as Diffie-Hellmann, and raise the security offered by ECC SSL certificates through a technique called Perfect Forward Secrecy (PFS), where the session keys are “exchanged” periodically and implicitly and therefore even a captured encrypted data stream will at best only be decipherable in part. Thus, the eavesdropper stands a minimal chance of guessing a quantity of key pairs that would make any sense out of the data in his possession.

Are you unsure about leaving your users on legacy systems in the dark at this point? ECC certificates can be configured to serve both ECC and RSA intermediates, guaranteeing that the certificate chain will still function correctly to anyone on Windows XP. Symantec is already using ECC roots so we are well-equipped for the future. And using ECC SSL will decrease your power bill, because the math needed in the process is calculated easily by modern processors since the functions are built in.

So, with Symantec’s SSL certificates you have access to the future of encryption today, allowing you to save on your server resources, providing higher security to your users, and a better (and faster) user experience especially when in mobility. At Symantec our prime mission is to keep ahead of the next big thing in digital security, so you can do what you do best: your business. Do get in touch; we’d love to hear from you.

?????????????????(CSRF,?CWE-352)????

      No Comments on ?????????????????(CSRF,?CWE-352)????
クロスサイトリクエストフォージェリ(CWE-352)

このブログではウェブサイトやその上で動作しているウェブアプリケーションの脆弱性について紹介すると共に注意喚起をする目的でまとめられています。
今回は代表的なWebアプリケーション脆弱性であるクロスサイトリクエストフォージェリについて解説をしています。

????????????(CWE-22)???

      No Comments on ????????????(CWE-22)???
ディレクトリトラバーサル(CWE-22)

このブログではウェブサイトやその上で動作しているウェブアプリケーションの脆弱性について紹介すると共に注意喚起をする目的でまとめられています。
今回は代表的なWebアプリケーション脆弱性であるディレクトリトラバーサルについて解説をしています。

Google’s SHA-1 Deprecation Plan for Chrome

      No Comments on Google’s SHA-1 Deprecation Plan for Chrome

The latest news in the SSL and web browser industries is Google’s plans to deprecate SHA-1 in a unique way on upcoming releases of Chrome starting with version 39. Considerably different from Microsoft’s plans that were announced in November 2013, Google plans on placing visual marks or placing a block within the browser; all based on the version of the browser, date of use and certificate’s expiration date.

Here is what you need to know first:

  1. SHA-1 is still safe to use but critics say its long-term ability to stand up to collision attacks is questionable.
  2. SHA-2 is the next hashing algorithm to be used.  If your end-entity or intermediate certificates are SHA-1, it might be a good idea to exchange them now.
  3. This issue faces all Certification Authorities, not just Symantec.
  4. All SHA-1 end-entity certificates and SHA-2 end-entity certificates chaining up to a SHA-1 intermediate are affected. SHA-1 root certificates are not affected by either Microsoft’s or Google’s SHA-1 deprecation plan.
  5. Google is using three terms that you may want to familiarize yourself with:
    1. secure, but with minor errors,
    2. neutral, lacking security, and
    3. affirmatively insecure.
  6. Symantec offers free replacements for affected Symantec SSL certificates.

What we expect to see with future Chrome releases:

Chrome 39 (Beta release: 26 September 2014, tentative production release: November 2014):

  1. Any SHA-1 SSL certificate, on a page, that expires on or after 1 January 2017 will be treated as “secure, but with minor errors”.  The lock within the address bar of the browser will have a yellow arrow over the lock as in this example provided by Google:

google-blog-1.png

 

Chrome 40 (Beta release: 7 November 2014, tentative production release: post-holiday season):

  1. Pages secured with a SHA-1 certificate expiring between 1 June 2016 and 31 December 2016 inclusive will experience the same treatment as described above.
  2. Additionally, pages secured with a SHA-1 certificate expiring after 1 January 2017 will be treated as “neutral, lacking security”.  The lock in the address bar will be replaced by a blank page icon as in this example provided by Google:

google-blog-2.png

 

Chrome 41 (Q1-Q2 2015):

  1. Sites secured with a SHA-1 certificate with validity dates terminating between 1 January 2016 and 31 December 2016 inclusive will be treated as “Secure, but with minor errors.”
  2. Sites secured with a SHA-1 certificate expiring on or after 1 January 2017 will be treated as “affirmatively insecure”.  The lock will have a red “X” over it with the letters “HTTPS” crossed out with a red font as in this example provided by Google.

google-blog-3.png

 

Here is a matrix to help you understand the dates:

 

Sample Expiration Dates

Chrome Version (Beta dates)

SHA-1

(Dec 31 2015)

 

SHA-1

(Jan 1 – May 31  2016)

SHA-1

(Jun 1 – Dec 31 2016)

SHA-1

(Jan 1 2017 and beyond )

Recommended:

SHA-2

Chrome 39

(Sept. 2014)

google-blog-4.png

google-blog-4.png

google-blog-4.png

google-blog-5.png

google-blog-4.png

Chrome 40

(Nov. 2014)

google-blog-4.png

google-blog-4.png

google-blog-5.png

google-blog-6.png

google-blog-4.png

Chrome 41

(Q1 2015)

google-blog-4.png

google-blog-5.png

google-blog-5.png

google-blog-7.png

google-blog-4.png

Moral of the story: Move to SHA-2, especially if your SSL certificate expires after December 2015.

 

What you need to do.

  1. Use our SSL Toolbox to see if your certificates are affected.  SHA-1 SSL certificates expiring before 2016 are NOT affected and can be replaced with a SHA-2 certificate at renewal time if you wish.
  2. If your Symantec certificates are affected you can replace them at no additional charge for a SHA-2 certificate, or a SHA-1 certificate with a validity that does not go past 2015.  Check with your vendor if they have a free replacement program like Symantec.
  3. Install your new certificates.
  4. Test your installation using the SSL Toolbox.
  5. Security Best Practice:  Revoke any certificates that were replaced in step #2.

For more in-depth information, instructions, and assistance please refer to our knowledge center article on this subject.  For a list of SHA-2 supported and unsupported applications review this list from the CA Security Council.

Read our SHA-2 webpage for the tools, steps to take, and a list of FAQs that can be generally applicable across all browsers.