TLS 1.2

• To keep your communication with CheckMarket secure, we will drop support for TLS 1.0 and 1.1 for all integrations as from July 1 2018, in response to security concerns around these protocols.
  
  We’re sticklers for API backwards-compatibility and make potentially breaking changes only when absolutely necessary. Our users’ security is paramount, so deprecating these outdated technologies is one of those rare cases.
  TLS 1.0 and 1.1 ensure that your communications stay private. In order to do this, they generate a series of random bytes used to encrypt your connection. TLS 1.0 provides two ways of doing this (CBC and RC4), but several vulnerabilities have been discovered in both of them (including BEAST and the RC4 biases). If you kept using old versions of TLS, someone could theoretically sniff your connection. With this change, we are following best practices in the industry: PCI council has announced June 30, 2018 as End of Life date for TLS 1.0
  
  As a result, we are moving towards TLS 1.2, which has few known attacks and is subject to more rigorous security design than its predecessors.
  

• What this means for you

  The upgrade process will be seamless for most users. At the application layer, TLS 1.2 behave identically to their older versions. You won’t need to change your code, but might need to upgrade your operating system or packages.
  
  Validate if your API connection is TLS 1.2 compliant. In your current application, you can perform a request to our new endpoint https://api-tls12.checkmarket.com/default.json.
  
  For a successfull connection, you will receive
  
  

  
  {
      "success": true
  }
              

  
  In this case, congratulations. You are already using TLS 1.2 and the most secure way of retrieving your data.
  
  If your connection fails, additional steps need to be taken before July 1st in order to use TLS 1.2.

• Update to TLS 1.2

  Depending on your environment, additional steps might be required. As shown below for cURL and .NET, these adaptations will be minor.
  
  

  • cURL

    The option --tlsv1.2 forces curl to use TLS version 1.2

  • C# .NET

    .NET framework 4.7 use the default as configured in your OS, lower versions can be forced to prioritize TLS 1.2 with ServicePointManager.SecurityProtocol = SecurityProtocolType.Tls12;