While it’s one of the areas that IT and security departments find challenging, documentation (and compliant evidence) is what makes for a happy and satisfied PCI Qualified Security Assessor (QSA), and, more importantly, a successful PCI compliance audit! Successful compliance programmes invariably depend on the accurate and consistent recording of events and the adherence to well-defined policies and procedures.
These documents ensure all staff are aware of their obligations, as well as defining the necessary actions to ensure a secure and compliant environment is achieved. With a number of PCI requirements, certain documents will need to be reviewed periodically or the instructions contained therein carried out at specific intervals.
If the actions in question (i.e. firewall rule reviews / external vulnerability scans) are not performed as instructed, the entire compliance initiative may be jeopardised. Organisations are well-advised to analyse their documentation and evidentiary requirements and summarise these centrally, where the content and resulting actions can be tracked.
Security policies and procedures are not a new concept and, coupled with the multitude of security standards that have been developed over the past few decades, there’s no need to start from scratch and be overly creative.
As long as the documents are clear, concise, deliver the intended message, are customised to the environment in question and elicit the necessary behaviour, the document set will achieve the desired outcome. It is essential that you ensure all PCI control statements which require explicit documentation are included in the relevant documents. This will save you both time and resources when addressing this necessary, albeit challenging, task.
The list of documents and evidence artefacts that act as the baseline for achieving compliance with the PCI DSS is very extensive.
Not all documents will be obligatory for all organisations, however, a significant number will need to have been implemented in order for a successful outcome to be achieved. If these documents, procedures and activities geared towards producing the necessary evidence are in place, you are well on the way to attaining compliance. To illustrate the type of documents and evidence (by no means exhaustive!) you will typically need to develop and implement, here is starter for ten!:
Documents
- Network device management policy
- Wireless scanning procedure (rogue access points)
- Remote access policy (staff/vendor)
- Device configuration standards
- Visitor policy
- Operational security procedures
Evidence
- Network diagrams
- Dataflow diagrams
- Incident response test
- Role-based access matrix
- Vulnerability scans
- Risk register
- Third party contracts (soft copy)
If your organisation has received a request for a SOC 2 report and is looking to meet all the necessary requirements, URM can offer you informed guidance and practical support.
URM can help you achieve ISO 27001 certification
URM can provide a range of ISO 27002:2022 transition services including conducting a gap analysis, supporting you with risk assessment and treatment activities as well as delivering a 2-day transition training course.
After the recent changes to PCI DSS v4.0 we're examining factors behind the greater utilisation of MFA, and what the key changes are in requirements.
There’s no getting away from the fact that preparing for a PCI DSS ROC can be a bit of a trial....
URM’s blog dissects the new PCI DSS requirements around targeted risk analysis, what they involve, and how the 2 types of TRA in the Standard differ.