PCI-3.1: Difference between revisions
Jump to navigation
Jump to search
(New page: <blockquote style="background: #C8CDC7; padding: 1em; margin-left: 0.5em;"> <br> ::'''From the sample of (insert number and or description of sample) system components, verify that non-con...) |
No edit summary |
||
| Line 1: | Line 1: | ||
<blockquote style="background: #C8CDC7; padding: 1em; margin-left: 0.5em;"> | <blockquote style="background: #C8CDC7; padding: 1em; margin-left: 0.5em;"> | ||
<br> | <br> | ||
::''' | ::'''Keep cardholder information storage to a minimum. Develop a data retention and disposal policy. Limit your storage amount and retention time to that which is required for business, legal, and/or regulatory purposes, as documented in the data retention policy.'''<br> | ||
<br> | <br> | ||
:::'''PCI-3.1:''' Obtain the company policies and procedures for data retention and disposal, and observe that these policies and procedures include:<br> | :::'''PCI-3.1:''' Obtain the company policies and procedures for data retention and disposal, and observe that these policies and procedures include:<br> | ||
| Line 8: | Line 8: | ||
:::* Disposal of data when no longer needed for legal, regulatory, or business reasons, including disposal of cardholder data. | :::* Disposal of data when no longer needed for legal, regulatory, or business reasons, including disposal of cardholder data. | ||
:::* Coverage for all storage of cardholder data, including database servers, mainframes, transfer directories, and bulk data copy directories used to transfer data between servers, and directories used to normalize data between server transfers. | :::* Coverage for all storage of cardholder data, including database servers, mainframes, transfer directories, and bulk data copy directories used to transfer data between servers, and directories used to normalize data between server transfers. | ||
:::* A programmatic (automatic) process to remove, at least on a quarterly basis, stored cardholder data that exceeds business retention requirements. Alternatively, performance of an audit, at least on a quarterly basis, to verify that stored cardholder data does not exceed business retention requirements. | :::* A programmatic (automatic) process to remove, at least on a quarterly basis, stored cardholder data that exceeds business retention requirements. Alternatively, performance of an audit, at least on a quarterly basis, to verify that stored cardholder data does not exceed business retention requirements. | ||
<br> | <br> | ||
</blockquote> | </blockquote> | ||
| Line 66: | Line 66: | ||
<br> | <br> | ||
--[[User:Mdpeters|Mdpeters]] 09: | --[[User:Mdpeters|Mdpeters]] 09:46, 28 February 2007 (EST) | ||
Latest revision as of 14:46, 28 February 2007
- Keep cardholder information storage to a minimum. Develop a data retention and disposal policy. Limit your storage amount and retention time to that which is required for business, legal, and/or regulatory purposes, as documented in the data retention policy.
- PCI-3.1: Obtain the company policies and procedures for data retention and disposal, and observe that these policies and procedures include:
- Legal, regulatory, and business requirements for data retention, including specific requirements for retention of cardholder data (e.g., cardholder data needs to be held for X period for Y business reasons).
- Disposal of data when no longer needed for legal, regulatory, or business reasons, including disposal of cardholder data.
- Coverage for all storage of cardholder data, including database servers, mainframes, transfer directories, and bulk data copy directories used to transfer data between servers, and directories used to normalize data between server transfers.
- A programmatic (automatic) process to remove, at least on a quarterly basis, stored cardholder data that exceeds business retention requirements. Alternatively, performance of an audit, at least on a quarterly basis, to verify that stored cardholder data does not exceed business retention requirements.
Testing Procedures
Insert testing guidance here.
Testing Frequency
Describe testing frequency here.
Evidence Archive Location
Insert hyperlink or location of evidence archive.
Control Stewards Process Narrative
Provide control steward commentary indicating the formal methodology in place.
Control Steward – Jon Doe
Process Illustration
Replace this test by inserting a process diagram, flowchart or other visual representation to illustrate the process narrative as necessary. Include a brief description of the process illustration.
Control Status and Auditors Commentary
The control is effective.
File:Greenlock.jpg
Status is acceptable.
Control Exception Commentary
Status is acceptable.
Remediation Plan
Remediation is not required at this time.
--Mdpeters 09:46, 28 February 2007 (EST)