Defeating PCI DSS v4.0 using SABSA Architecture

The change to the new version 4.0 of the PCI DSS has mainly formalised the way that the 12 different Requirements are formatted and makes the Standard feel more complete and well thought out than it has ever felt before. Think of a patchy blanket which is now rearranged into a quilt.

I believe that with the assistance of the SABSA Architecture, we* can go further and make the Standard easier to tackle, implement and manage. And also easier to assess and improve.

I have discussed and brainstormed this in different architecture forums and it has generated some debate. However, it seems that over-all there is benefit to be gained by using Enterprise Architecture to conquer PCI DSS.

This is not a niche talk that will appeal to my friends in dark blue suits, I will explain my thinking and how this doesn't just apply to PCI DSS but can be used for other Compliance driven frameworks and can use Enterprise Architecture that is not just SABSA.

As usual, I will attempt to use every ounce of my sense of humour, my light-hearted presentation skills and unique presenting method to keep the audience awake through something that can be rather dry and boring but is important.

We being the GRC people who never seem to get invited to the cool parties.