# New CRA security update

**URL:** <https://www.protaxcommunity.com/t/new-cra-security-update/435>\
**Category:** Product Suggestions\
**Created:** [August 10, 2015, 7:08pm UTC](https://www.protaxcommunity.com/t/new-cra-security-update/435 "2015-08-10T19:08:38Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![james1](https://sea2.discourse-cdn.com/flex016/user_avatar/www.protaxcommunity.com/james1/32/47_2.png) [@james1](https://www.protaxcommunity.com/u/james1)\
**Post date:** [August 10, 2015, 7:08pm UTC](https://www.protaxcommunity.com/t/new-cra-security-update/435/1 "2015-08-10T19:08:38Z")

</div>

Since CRA is requiring the use of TLS 1.2, Taxcycle should consider implementing the ability to test the security protocol the user is using. Clicking the test button would send a request to the Taxcycle servers and respond if the right protocol is in use. There are a lot of tax preparers who are not that computer savy and this may save you a lot of support time if users are getting rejected filings

---

<div class="post-metadata">

**Author:** ![Andrew](https://sea2.discourse-cdn.com/flex016/user_avatar/www.protaxcommunity.com/andrew/32/17_2.png) [@Andrew](https://www.protaxcommunity.com/u/Andrew)\
**Post date:** [August 10, 2015, 7:48pm UTC](https://www.protaxcommunity.com/t/new-cra-security-update/435/2 "2015-08-10T19:48:12Z")

</div>

We’ll be taking more steps in up-coming releases to handle this change over. Adding some additional test functionality is a good idea. I’ll add a way to test what the current system supports.

On October 14, 2014 Microsoft issued a [security advisory update](https://technet.microsoft.com/en-us/library/security/2977292.aspx) that automatically enabled TLS 1.2 for Windows 7, Server 2008 and newer. Though this update has been made available, not everyone may have applied this yet.

I should note that we switched over to TLS 1.2 in the June version of TaxCycle (4.5.x).