fbpx

Authorize.net Disabling TLS 1.0 and 1.1

Authorize.net Disabling TLS 1.0 and 1.1

I’ve had lots of clients that have received an email from authorize stating that they were disabling TLS 1.0 and 1.1.

“As you may be aware, new PCI DSS requirements state that all payment systems must disable early TLS by 2018. Transport Layer Security (TLS), is a technology used to encrypt sensitive information sent via the Internet. TLS is the replacement for Secure Sockets Layer (SSL).

In preparation for this requirement, Authorize.Net plans to disable TLS 1.0 and TLS 1.1 on the following dates:”

If you want to make sure you are safe just visit SSL labs and run this test:

when the test completes scroll down until you see what versions of TLS is supported. You should see “yes” next to TLS 1.2. If not contact your certificate provider.

Here is also a little script to check it.

<?php

/*
The ‘S’ in “HTTPS” is the TLS protocol. When folks refer to the “TLS” they are referring to the most common of
modern protocols of encrypting data across the internet.
*/

// check the tls version
$ch = curl_init( “https://smartzweb.com” );
curl_setopt( $ch, CURLOPT_RETURNTRANSFER, true );
$data = curl_exec( $ch );
curl_close( $ch );
$json = json_decode( $data );

echo $json->tls_version;

require_once ‘sslLabsApi.php’;

//Return API response as JSON string
$api = new sslLabsApi();

//Set content-type header for JSON output
header(‘Content-Type: application/json’);

//get API information replace with your domain and ip
var_dump($api->fetchEndpointData(‘https://smartzweb.com’, ‘34.200.83.13’));