As 2017 comes to an end, the latest PCI DSS 3.2 requirements (coming into effect on Feb. 1, 2018) are on the minds of many Service Providers and Merchants. A natural question stemming from these changes is "What do I do if I fail my PCI assessment?" Let's take a look back to a blog written earlier this year that answers just that.
Remember when PCI DSS version 3.2 was released way back in April 2016? We counted our blessings that the new requirements truly raised the bar - especially for Service Providers - and gave us a considerable grace period to implement them. And as it goes, 2018 seemed so far away and implementing these changes didn’t seem so urgent. Well fast forward to today and all of a sudden January 31, 2018 doesn’t seem too distant in the future anymore.
Read More
In September 2016, a user identifying themselves as flokibot advertised some new malware for the Windows operating system named Floki Bot. The malware was based on ZeuS 1 but with a new and improved dropper. Available for a low price of only $1,000 USD, the malware has evolved rapidly since incorporating new antidetection features, it is also expected to implement TOR connectivity soon.
Read More
Are you a Service Provider or a Merchant?
This is an important question because merchants and service providers are accountable to different entities for their PCI DSS compliance. These entities are the people that will need to know about your (temporarily!) failed status and they will want regular communications from you starting now until you successfully complete your compliance assessment.
Read More