Welcome to the cyber. Very demystifying P C. I. D. S s compliance course.
This module will focus on the gold to the PC idea says, and the requirements associated with them.
This video introduces you to requirements 3.633 dot seven.
We'll talk about some of the requirements associated with protecting cardholder data.
The learning objective of this video is to explore how to satisfy requirements around protecting cardholder data and ways you can satisfy the PC idea says Requirement 3.623 dot seven
Requirement three is around. The protections you as a merchant need to have in place when dealing with credit card data.
Mechanisms such as encryption, truncation, masking and hashing should be leveraged to protect credit cards from an intruder.
You should also only store and maintain this data if it is absolutely necessary.
The 36 group is around all of the documentation and implementations of key management processes and procedures for cryptographic keys used for encryption of cardholder data.
Auditor will be looking for how you were addressing 3.6 that one. The generation of strong encryption keys
36 to secure cryptographic key, the distribution
and 363 Secure cryptographic key storage
generation, distribution and storage are all key components of a secure cryptographic infrastructure, and all need to have great care associated with it.
A lapse in any of these areas could lead to the collapse off all the security of all encryption mechanisms.
That auditor will be looking to observe all of the procedures and methods to ascertain if there any *** in the armor
encryption keys have a defined time period.
The key should expire after a set period of time. Because the Brazilians have a key may weaken over time.
Requirement 364 mandates that a merchant must have in place processes to handle key changes for keys that have expired.
PC I does not mandate any specific process, so an auditor will just be looking to see that you have something specifically defined and if you are following it.
Similarly, the 364365 looks to see that you have a process for replacing keys that need to be replaced for reasons other than expiration.
If a key has been weakened due to some new disclosure or suspected of being compromised
or if simply an employee leaves that had knowledge of a sensitive key component.
Then the merchant needs that have in place a process to replace or retire the keys.
Requirement 365 acknowledges that there may be instances where manual clear, clear text cryptographic key management operations have to be used.
In these instances, no one person may have full control of the key.
Operations must be managed using split knowledge where two or more people have a portion of the key, and they must all come together to form the whole key
or dual control can be used where it requires at least two people to perform any key management operation.
Well, Kermit 367 is for the prevention of unauthorized substitution of cryptographic keys.
The encryption solution you're using should not allow for or accept substitution of keys coming from unauthorized or unexpected sources.
If an attacker is ableto force your system to take keys from arbitrary source,
the encryption solution is un effective.
An auditor will be looking to interview personnel and verify that key management procedures specify processes to prevent unauthorized substitution of keys.
The 368 requirement should be a simple one.
The auditor will look to see if you're as emergent. Have to find who the key custodians are.
The auditor will then ask cryptographic key custodians to formally acknowledge that they understand and accept their key custodian responsibilities.
And finally, for requirement, three U. S. A. Merchant must ensure that security policies and operational procedures for protecting stored cardholder data are documented
in use and known to all affected. Parties.
In summary, would discuss all of the mandates associated with PC high requirements to be 0.6237
requirement. Three. Make sure that you are putting in place controls to protect your customers. Credit and debit card Information from Disclosure
36 Focuses on encryption about 37 Make sure you have a policy in place when dealing with cardholder data.
Now for a quick quiz.
cryptographic keys only need to be replaced when they expire.
If a key has been weakened due to some new disclosure or suspected of being compromised, it needs to be replaced.
Orphan employee leaves that had knowledge of the sensitive key components. The key should be replaced.
Split knowledge or dual control. It's necessary for
re vocation of keys,
clear text. Key management
and instances where manual clear text cryptographic key management operations have to be used. No one person may have full control of the key.