3.5 Requirement 3 Part 1
Join over 3 million cybersecurity professionals advancing their career
Sign up with
Required fields are marked with an *
Already have an account? Sign In »
welcome to the side. Very D mystifying PC idea says compliance Course.
This module will focus on the goals of the P C I D. Assess and the requirements associated with them.
This video introduces you to a requirement 3.1 through 3.5.
We will talk about some of the requirements associated with protecting cardholder data.
The learning objective of this video is that explore how to satisfy requirements around protecting cardholder data and ways you can satisfy the P. C. I. D. S s requirement 3.133 dot by
requirement three is around the protections us A. Merchant need to have in place when dealing with card data.
Mechanisms such as encryption, truncation, masking and hashing should be leveraged to protect cards from an intruder.
You should also only store and maintain this data if it is absolutely necessary.
Which leads us to requirement 31
Onley. Keep this data if it is necessary and maintain on lee the minimum data needed.
You should also have in place policies and procedures around the retention in the disposal of cardholder data.
Requirement 31 states that the merchant must limit data storage amount and retention time to that which is required for legal, regulatory and or business requirements.
You should implement specific retention requirements for cardholder data and established processes for secure deletion of data When it's no longer needed.
As a merchant, you must continually conduct a quarterly process for identifying and securely deleting stored cardholder data that exceeds to find retention.
This quarterly process can be either automatic or manual.
An auditor will come in to examine all of the policies around these requirements and confirmed that the relevant personnel are all trained on the policy and execute procedures to align with them.
The requirement, Group 32 states that you are not to store sensitive authentication data after authorization.
It doesn't matter if it's encrypted or hashed.
Requirement three dot to 3.0.1 mandates that the merchant does not store the full contents of credit card track.
The track is a magnetic strip on the back of a card or the chip that's embedded in the card.
An auditor may expect logs and databases to ascertain what card information is being maintained after a car has been authorized.
Now, requirement 3 to 2 mandates that we do not store the card verification code or value after authorization.
The card verification value code, or what could be called the Cvv cvb to see VC TO or C I. D is the 3 to 4 digit number that is printed on the card and use for card, not present transactions.
Encrypting or hashing these values and then storing them still about violates this requirement.
There shouldn't be any reason for merchants to maintain this information after processing a payment.
It should not be stored because if a cardholder data is compromised,
then the attacker would be able to make payments remotely.
The code is not needed for card on file or recurring transactions.
Merchants and service providers should contact their acquirer or the payment brands directly, as applicable
for guidance on how to process recurring or card on file transactions without requiring the transmission or storage of prohibited data.
Requirement 32.3 is in the same name
As a merchant, you cannot store any data that facilitates the authorization of transactions.
The merchant is not to store the personal identification number, pen
or encrypted pin block after authorization.
Encryption or hashing does not satisfy this requirement.
Requirement 33 is one that most of us have been exposed to
whatever. You set up auto pay on a website and you go back to it. You'll only see let Fast. Four digits of the card that you have entered is displayed
even on the merchants back in systems it should be office skated to the majority of the staff.
This is centered around the mandate that merchants must mass the primary account number Information as one display.
The 1st 6 in the last four digits are the maximum number of digits that can be displayed
As a merchant, you must demonstrate the need for specified personnel with a legitimate business. Need can see. This can see more than the first sticks or last four digits of the pan.
The auditor will look to see that this is documented somewhere.
Requirement 34 mandates that merchant surrender the primary account numbers unreadable anywhere where it's stored,
so this includes any backup media logs, USB drives or anywhere else.
This could be done via one way. Hash is based on strong cryptography, truncation, index tokens and pads.
A common question is, what about Pan and Memory
PC? I does not require that this requirement be applied to pan and memory,
but it does require that controls be put in place to ensure that memory maintains a non persistent state.
So, for example, if swap files or temporary folders are used, it needs to be purged or have correspondent controls that match PC I requirements applied to it.
Requirement 341 states that if a merchant is using disc encryption,
logical access must be managed separately. An independent of the native operating systems authentication and access control mechanisms
so you can't use local user account databases or general network log in credentials.
Basically, the authentication credentials that can decrypt the disc need to be separate from the credentials that log into the system.
This makes it so that Attackers need to compromise two sets of credentials to access data
as a note. Using whole disk encryption makes it difficult to meet PC I. Requirement 3.4
Because once you've brooded the system and mounted the drive, there's a transparent data encryption that it's accessible to the end user.
Many disc encryption solutions intercept the operating system, read, write operations and carry out the appropriate cryptographic transformation without any special action by the user other than supplying the use the password or pass for eighth upon system startup.
If you're using whole disk encryption to meet requirement 3.4 dot one, be prepared to have a conversation with your assessor about the controls. Your music.
The requirement Group 35 is all around the documentation and procedures put in place to protect keys usedto secure stored cardholder data against disclosure and misuse.
As a merchant, you need to make sure you haven't the infrastructure in place to maintain the security of your cryptographic keys.
The 351 requirement is mandated for his service providers only.
They need to maintain a documented description of the cryptographic architecture that includes the details of all algorithms, protocols and keys use for the protection of cardholder data, including key strength, an expiry date,
description of the key usage for each key
inventory of any hardware, security modules and other secure cryptographic devices used for key management
for crime. It 352 is an easy one.
Always limit access to everything to the fewest number is possible.
The same is true for cryptographic keys.
Restrict access to cryptographic keys to the fewest number of custodians necessary
again, the auditor will look to see how you've defined this group and maintained access.
The 353 requirement is to store secret and private keys used to encrypt and decrypt cardholder data and one or more of the following forms at all times.
It should be encrypted with a key encrypting key
that is at least a strong is a data and data encrypting key and that is stored separately from the data encrypting key
within a secure cryptographic device such as, AH hardware, security module or Pts approved point of interaction device.
And as atleast two full key length components are key shares in accordance with industry accepted method,
merchants need to protect your keys from unauthorized access and prevent them from getting the information contained in the keys, even if they happen to, even if they do happen to obtain them.
Basically, the keys that are used to decrypt your data need tohave. Strong security controls apply to them and are never in clear text.
The 354 requirement is just simply store your keys in its few locations as possible.
As your keys proliferate throughout the environment, the security of them is inversely impacted
most only have the number of house keys that they need necessary for the people to get in and perhaps the spare key.
The same type of thinking should be applied to your crypto keys.
In summary, we discuss all of the mandates associated with PC I requirements. 31 through 35
we went through some of the protections that have to be in place for protecting cardholder data
and F for quick quiz.
True or false.
After authorization, merchants may contain CVB data to facilitate recurring payments.
Merchants air not to maintain cvv or pens after authorization.
The challenge for full disk encryption is a access to encryption technology.
Be boldness cannot be really encrypted.
See separation from user, password and decryption, password
and D. The encryption is not strong enough.
The authentication credentials that can decrypt the disc need to be separate from the credentials that log into the system.
This makes it so the Attackers need to compromise two sets of credentials to access data.
Most full disk encryption solution leveraged the native user and password
3.6 Requirement 3 Part 2
3.7 Requirement 4
3.8 Requirement 5
3.9 Requirement 6
3.10 Requirement 7