ISC CPA Practice Questions: Requirements of the PCI DSS

ISC 2 Requirements of the PCI DSS

Share This...

In this video, we walk through 6 ISC practice questions on requirements of the PCI DSS. These questions are from ISC content area 2 on the AICPA CPA exam blueprints: Security, Confidentiality and Privacy.

The best way to use this video is to pause each time we get to a new question in the video, and then make your own attempt at the question before watching us go through it.

Also be sure to watch one of our free webinars on the 6 “key ingredients” to an extremely effective & efficient CPA study process here…

Click here to watch the video on YouTube…

Requirements of the PCI DSS

The Payment Card Industry Data Security Standard (PCI DSS) is a set of security standards for any company that accepts, processes, stores, or transmits credit card information. It’s made up of 12 requirements organized under six control objectives. Each objective covers a different part of keeping card data safe, from how the network is set up to how the organization manages security as a whole.

Secure Network and Systems

The first objective is Build and Maintain a Secure Network and Systems, and it covers two requirements. Requirement 1 is to install and maintain network security controls. These controls, such as firewalls, decide what traffic can move between networks, and they keep untrusted networks like the internet separate from the company’s internal systems. Requirement 2 is to apply secure configurations to all system components. Systems should be set up securely before they’re put into use. That includes changing the default passwords that come from the manufacturer, since those are published and widely known, and turning off features and services that aren’t needed.

Protecting Account Data

The second objective is Protect Account Data, and it covers two requirements. Requirement 3 is to protect stored account data. Card data kept in a database or file should be encrypted, or masked so that only part of the number is shown, such as the last four digits. A company should also keep only the data it needs, for only as long as it needs it. Requirement 4 is to protect cardholder data with strong cryptography during transmission over open, public networks. When card details are sent over the internet, for example from a checkout page to a payment processor, they must be encrypted so they can’t be read if someone intercepts them. Both requirements use encryption, and the difference is whether the data is sitting in storage or moving across a network.

Vulnerability Management

The third objective is Maintain a Vulnerability Management Program, and it covers two requirements. Requirement 5 is to protect all systems and networks from malicious software. Malware includes viruses, ransomware, and programs that steal data, and anti-malware protection has to stay running and up to date to be effective. Requirement 6 is to develop and maintain secure systems and software. Software a company builds itself should be written securely. Software from vendors should be updated when the vendor releases a security patch, because once a flaw is public, attackers know about it too.

Access Control

The fourth objective is Implement Strong Access Control Measures, and it covers three requirements. Requirement 7 is to restrict access to system components and cardholder data by business need to know. Access is based on job duties, so a marketing employee whose work doesn’t involve payments shouldn’t be able to see card data. Requirement 8 is to identify users and authenticate access to system components. Each person gets a unique user ID so that activity can be traced to a specific individual, and multi-factor authentication confirms they are who they claim to be. Requirement 9 is to restrict physical access to cardholder data, using locks, badges, and escorts for visitors to protect servers, payment terminals, backup media, and paper records.

Monitoring and Testing

The fifth objective is Regularly Monitor and Test Networks, and it covers two requirements. Requirement 10 is to log and monitor all access to system components and cardholder data. Systems record who accessed what and when, and those logs are protected from tampering and reviewed regularly. Without logs, a company can’t detect a breach as it happens or piece together what happened afterward. Requirement 11 is to test security of systems and networks regularly, through vulnerability scans, penetration testing, and intrusion detection, so that weaknesses are found before an attacker finds them.

Information Security Policy

The sixth objective is Maintain an Information Security Policy, and it covers one requirement. Requirement 12 is to support information security with organizational policies and programs. This includes a written security policy approved by management that applies to all personnel. It also includes an incident response plan that’s in place before a breach ever happens, and security awareness training so every employee knows their responsibilities. This requirement is what holds the other eleven together across the organization.

Other Posts You'll Like...

Want to Pass as Fast as Possible?

(and avoid failing sections?)

Watch one of our free "Study Hacks" trainings for a free walkthrough of the SuperfastCPA study methods that have helped so many candidates pass their sections faster and avoid failing scores...