View source for PCI-3.4

<blockquote style="background: #C8CDC7; padding: 1em; margin-left: 0.5em;">
<br>
::'''Render sensitive cardholder data unreadable anywhere it is stored, (including data on portable media, in logs, and data received from or stored by wireless networks) by using any of the following approaches:'''<br>
<br>
::* One-way hashes (hashed indexes) such as SHA-1
::* Truncation
::* Index tokens and PADs, with the PADs being securely stored
::* Strong cryptography, such as Triple-DES 128-bit or AES 256-bit with associated key management processes and procedures.
<br>
::The MINIMUM account information that needs to be rendered unreadable is the payment card account number.<br>
<br>
:::'''PCI-3.4 A:''' Obtain documentation about the cryptographic system used to protect stored data, including the vendor, type of cryptographic system, and the encryption algorithms. Verify that data is rendered unreadable using one of the following algorithms:
<br>
:::* One-way hashes (hashed indexes) such as SHA-1
:::* Truncation or masking
:::* Index tokens and PADs, with the PADs being securely stored
:::* Strong cryptography, such as Triple-DES 128-bit or AES 256-bit, with associated key management processes and procedures.
<br>
:::'''PCI-3.4 B:''' Examine several tables from each database server in the sample of database machines to verify the data is encrypted (i.e., not stored in plain text).
:::'''PCI-3.4 C:''' Examine a sample of removable media (e.g., backup tapes) to confirm that cardholder data is encrypted.
:::'''PCI-3.4 D:''' Examine a sample of audit logs to confirm that cardholder data is sanitized or removed from the logs.
:::'''PCI-3.4 E:''' Verify that any cardholder data received from wireless networks is encrypted wherever stored.
<br>
</blockquote>
<br>
'''Testing Procedures'''
<blockquote style="background: white; border: 1px solid black; padding: 1em;">
Insert testing guidance here.
</blockquote>
'''Testing Frequency'''
<blockquote style="background: white; border: 1px solid black; padding: 1em;">
Describe testing frequency here.
<br>
</blockquote>

'''Evidence Archive Location'''
<blockquote style="background: white; border: 1px solid black; padding: 1em;">
Insert hyperlink or location of evidence archive.
<br>
</blockquote>

'''Control Stewards Process Narrative'''
<blockquote style="background: white; border: 1px solid black; padding: 1em;">
<p><font color=#008000>Provide control steward commentary indicating the formal methodology in place.</font></p>

<br>
'''Control Steward – Jon Doe'''
<br>
</blockquote>

'''Process Illustration'''
<blockquote style="background: white; border: 1px solid black; padding: 1em;">
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.
<br>
</blockquote>

'''Control Status and Auditors Commentary'''
<blockquote style="background: white; border: 1px solid black; padding: 1em;">
<p><font color=#008000>The control is effective.</font></p>
<br>
[[Image:greenlock.jpg]]<br>
<br>
Status is acceptable.
<br>
</blockquote>

'''Control Exception Commentary'''
<blockquote style="background: white; border: 1px solid black; padding: 1em;">
Status is acceptable.
<br>
</blockquote>

'''Remediation Plan'''
<blockquote style="background: white; border: 1px solid black; padding: 1em;">
Remediation is not required at this time.
<br>
</blockquote>
<br>

--[[User:Mdpeters|Mdpeters]] 10:08, 28 February 2007 (EST)