A DevOps approach to PCI compliance

October 4, 2016

I recently sat down with  Here are some highlights from our talk.

1. What were your main challenges getting to PCI compliance at your company?

Bullard: The first was timeline, as we only had three to four months to achieve PCI compliance. We had to move quickly in order to close prospective customers who required security that maintains compliance. Budget constraints were another challenge. As a company, Distil is scaling quickly, so every dollar counts. That’s why Benji and I were the full team working on this project. Balancing our normal workloads with setting up PCI compliance was another challenge in and of itself, but it made it that much more rewarding in the end to see what we had accomplished.

Taylor: We were both also very new to this process, so it took some time to gain a thorough understanding of everything needed to start the effort. But in the end it felt great knowing we did it all on our own, without the help of anyone else who had prior experience going through compliance.

Read the Article

Previous Article
Security Orchestration and Automation: Closing the Gap in Incident Response
Security Orchestration and Automation: Closing the Gap in Incident Response

Companies in North America are poised to increase their reliance on security orchestration and automation f...

Next Article
Security Takes Shape at Market Cube
Security Takes Shape at Market Cube

Distil Networks, a bot detection and mitigation system helps Market Cube, an online market research company...