{"id":1367,"date":"2016-05-13T14:50:21","date_gmt":"2016-05-13T13:50:21","guid":{"rendered":"https:\/\/www.retarus.com\/blog\/it\/the-ultimate-pci-checklist-are-you-up-to-date-with-changing-pci-regulations"},"modified":"2024-05-07T20:01:39","modified_gmt":"2024-05-07T18:01:39","slug":"the-ultimate-pci-checklist-are-you-up-to-date-with-changing-pci-regulations","status":"publish","type":"post","link":"https:\/\/www.retarus.com\/blog\/it\/the-ultimate-pci-checklist-are-you-up-to-date-with-changing-pci-regulations\/","title":{"rendered":"The Ultimate PCI Checklist: Are you up to-date with changing PCI regulations?"},"content":{"rendered":"

Did you know, PCI DSS Regulations are changing and are due to be in effect as early as June 30th, 2016? After uncovering numerous exploits into the technology, POODLE and Heartbleed for example, the PCI DSS council has dropped SSL (Secure Sockets Layer) from the list of strong cryptography approaches (i.e. encryption) back in early 2015. While initial timelines stated that companies had only a single year to get their security approach in order, revised timelines have extended this complete migration deadline to 2018. The exception is all processing and third party entities, which must provide TLS 1.1 or greater into their offerings by June 2016<\/a>. As PCI DSS 3.1 takes effect June 30, 2016, Technology Executives like Tim Brown of Dell<\/a>, argue that these compliance regulations provide the jumping off point for achieving a higher level of security across channels. But, with the initial deadline quickly approaching, what should organizations do to ensure continuing compliance with PCI and information security? Key points to consider for PCI compliance review:<\/strong> <\/p>\n