PCI Business-as-Usual Security—Best Practice or Requirement?
Blog Article Published: 10/08/2014
By Christine Drake, Senior Product Marketing Manager, Venafi When attending the 2014 PCI Community Meetings in Orlando in early September, the PCI SSC kicked off the conference with a presentation by Jake Marcinko, Standards Manager, on Business-as-Usual (BAU) compliance practices. The PCI DSS v3, released in November 2013, emphasizes that security controls implemented for compliance should be part of an organization’s business-as-usual security strategy, enabling organizations to maintain compliance on an ongoing basis. Compliance is not meant to be a single point in time that is achieved annually to pass an audit. Instead, compliance is meant to be an ongoing state, ensuring sustained security within the Cardholder Data Environment (CDE). Security should be maintained as part of the normal day-to-day routines and not as a periodic compliance project. To highlight the lack of business-as-usual security processes, Jake referenced the Verizon 2014 PCI Compliance Report, saying that almost no organization achieved compliance without requiring remediation following the assessment and there is dismally low continued compliance—only 1 out of 10 passed all 12 of the PCI DSS requirements in their 2013 assessments. But this was up from only 7.5% in 2012. Four elements of ongoing, business-as-usual security processes were outlined:
- Monitor security control operations
- Detect and respond to security control failures
- Understand how changes in the organization affect security controls
- Conduct periodic security control assessments, and identify and respond to vulnerabilities
Share this content on your favorite social network today!