PCI DSS workstation/user requirements

Are there any specific PCI requirements for workstations or user profiles in thin client environments?
LVL 3
pma111Asked:
Who is Participating?
 
CoccoBillConnect With a Mentor Commented:
Well, as the intro part of the standard states, all of the requirements apply to all system components, including workstations and user profiles, within the cardholder data environment plus any connected systems. System hardening, patch management, change management, AV, IDS, FIM, user access control, logging and monitoring, vulnerability scans and penetration testing, ALL apply to them, just as with any servers and network active devices.

Also, a compensating control is something that you can use if there is a business or technical reason why you cannot implement the exact control mandated by the standard. However, the compensating control must take the overall security level of the environment to the same or higher level than the original control would, and you need to write up a document detailing why and how it was done for each of them, and they need to be separately approved by your issuer, not the QSA. The standard is absolutely a list of MUSTs in all but very few cases.
0
 
Rich RumbleConnect With a Mentor Security SamuraiCommented:
Only for VPN really, the rest isn't specific to machines or host, but the controls around the data:
https://www.pcisecuritystandards.org/documents/pci_dss_v2.pdf
Mostly about how CC data is accessed/transmitted/stored. It's not a list of MUST's in most cases, compensating controls can be used instead of or in lieu of certain "requirements".
-rich
0
 
pma111Author Commented:
CoccoBill - what would a PCI DSS audit of user profiles include? I.e what neesd configuring on user profiles to ensure PCI compliance? And "user access control" - could you provide some examples?

Thanks man
0
Improve Your Query Performance Tuning

In this FREE six-day email course, you'll learn from Janis Griffin, Database Performance Evangelist. She'll teach 12 steps that you can use to optimize your queries as much as possible and see measurable results in your work. Get started today!

 
CoccoBillCommented:
I suggest you get the standard and see the requirements yourself, the standard is available at https://www.pcisecuritystandards.org/security_standards/documents.php (PCI DSS v2.0).

User access control is covered by requirements 7 and 8, which describe how user access must be granted, what kind of privileges can be given, authentication methods, password policies etc. Also take a look at requirement 2.2, which states you need to have a configuration standard for all system components. In practice this means all devices must be hardened according to an industry-accepted hardening guide, I would recommend the Center for Internet Security benchmarks: http://benchmarks.cisecurity.org/en-us/?route=downloads.benchmarks. they will detail each and every operating system level setting and how to configure them.

But in essence, your environment (your determined PCI scope) has to fulfill all applicable requirements in the standard in order to be compliant. Is your organization a service provider or a merchant, has your PCI scope been determined and what is your validation level (self-assessment questionnaire or on-site audit required)?
0
 
pma111Author Commented:
We dont store PCI data in our network, however we do take phone payments via phone using internal phone system - and access an externally hosted app that collects such data from machines within our LAN
0
 
pma111Author Commented:
Are the benchmarks tools or just documents?

Do you have to be a member?
0
 
Rich RumbleSecurity SamuraiCommented:
No membership, if your not storing the data, then the PCI burden is on your external vendor, phone payments in this scenario are not subject to pci.
-rich
0
 
CoccoBillCommented:
So I'll assume you're a merchant (you own the payment card transactions that your process) and you don't process hundreds of thousands of transactions a year, so you are not required to have an annual on-site audit.

I would look into the following options:

1. See if you can outsource the processing of payment data and make sure your environment never sees a single PAN. Cheapest and easiest option by far. :)
2. Contact your issuing bank to see if they have a specific policy for applicable requirements for your organization. The issuer determines your validation level and can agree to somewhat looser set of requirements under certain conditions.
3. If neither 1. nor 2. work out, your issuer will anyway determine which SAQ is applicable to you (https://www.pcisecuritystandards.org/merchants/self_assessment_form.php). There are 4 different ones, all with a different subset of the requirements for varying environments. Find out which one you need to fill and see the requirements that apply to you (well they still all apply, but only those will be validated).

The CIS benchmarks as pdf documents are free but require registration, the XCCDF format benchmarks are members only (non-free).
0
 
CoccoBillCommented:
> No membership, if your not storing the data, then the PCI burden is on your external vendor, phone payments in this scenario are not subject to pci.

Not true, unless the issuer determines this is the case. By default all requirements apply to all parts of the environment that "store, process or transmit" cardholder data, even one PAN is enough. They get the PAN from the customer over the phone and type it in using their thin clients to the external payment application, the physical premises where the thin clients are, the thin clients, the network are all in-scope by default.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.