DS11.2:: Difference between revisions

From HORSE - Holistic Operational Readiness Security Evaluation.
Jump to navigation Jump to search
No edit summary
No edit summary
 
(One intermediate revision by the same user not shown)
Line 5: Line 5:
<br>
<br>
<br>
<br>
Define and implement procedures for data storage and archival, so data remain accessible and usable. The procedures should consider retrieval requirements, cost-effectiveness, continued integrity and security requirements. Establish storage and retention arrangements to satisfy legal, regulatory and business requirements for documents, data, archives, programs, reports and messages (incoming and outgoing) as well as the data (keys, certificates) used for their encryption and authentication.  
Define and implement procedures for data storage and archival, so data remain accessible and usable. The procedures should consider retrieval requirements, cost-effectiveness, continued integrity and security requirements. Establish storage and retention arrangements to satisfy legal, regulatory and business requirements for documents, data, archives, programs, reports and messages (incoming and outgoing) as well as the data (keys, certificates) used for their [[Encryption | encryption]] and authentication.  
<br>
<br>
<br>
<br>
Line 33: Line 33:
<br>
<br>
::'''3. Risk: Lost data could significantly impact financial reporting.'''
::'''3. Risk: Lost data could significantly impact financial reporting.'''
:::a. [[SOX.2.7.11:|'''SOX.2.7.11''']] Retention periods and storage terms are defined for documents, data, programs, reports and messages (incoming and outgoing), as well as the data (keys, certificates) used for their encryption and authentication.
:::a. [[SOX.2.7.11:|'''SOX.2.7.11''']] Retention periods and storage terms are defined for documents, data, programs, reports and messages (incoming and outgoing), as well as the data (keys, certificates) used for their [[Encryption | encryption]] and authentication.
<br>
<br>
<br>
<br>
Line 52: Line 52:
* PCI.3.3: Mask account numbers when displayed (the first six and last four digits are the maximum number of digits to be displayed).<br>
* PCI.3.3: Mask account numbers when displayed (the first six and last four digits are the maximum number of digits to be displayed).<br>
<br>
<br>
* PCI.3.4: Render sensitive cardholder data unreadable anywhere it is stored (including data on portable media, backup media, in logs, and data received from or stored by wireless networks) by using any of the following approaches: 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>
* PCI.3.4: Render sensitive cardholder data unreadable anywhere it is stored (including data on portable media, backup media, in logs, and data received from or stored by wireless networks) by using any of the following approaches: 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 | Advanced Encryption Standard]] (AES) 256-bit with associated key management processes and procedures.<br>
<br>
<br>
* PCI-4.1.1 For wireless networks transmitting cardholder data, encrypt the transmissions by using Wi-Fi Protected Access (WPA) technology if WPA capable, or VPN or SSL at 128-bit. Never rely exclusively on WEP to protect confidentiality and access to a wireless LAN. Use one of the above methodologies in conjunction with WEP at 128 bit, and rotate shared WEP keys quarterly and whenever there are personnel changes.<br>
* PCI-4.1.1 For wireless networks transmitting cardholder data, encrypt the transmissions by using Wi-Fi Protected Access (WPA) technology if WPA capable, or VPN or SSL at 128-bit. Never rely exclusively on WEP to protect confidentiality and access to a wireless LAN. Use one of the above methodologies in conjunction with WEP at 128 bit, and rotate shared WEP keys quarterly and whenever there are personnel changes.<br>

Latest revision as of 11:49, 28 March 2008

DS 11.2 Storage and Retention Arrangements

Control Objective: Controls provide reasonable assurance that data recorded, processed and reported remain complete, accurate and valid throughout the update and storage process.

Define and implement procedures for data storage and archival, so data remain accessible and usable. The procedures should consider retrieval requirements, cost-effectiveness, continued integrity and security requirements. Establish storage and retention arrangements to satisfy legal, regulatory and business requirements for documents, data, archives, programs, reports and messages (incoming and outgoing) as well as the data (keys, certificates) used for their encryption and authentication.

Rationale — Managing data include the controls and procedures used to support information integrity, including its completeness, accuracy, authorization and validity. Controls are designed to support initiating, recording, processing and reporting financial information. Deficiencies in this area could significantly impact financial reporting. For instance, without appropriate authorization controls over the initiation of transactions, resulting financial information may not be reliable.

Applicability:

Sarbanes-Oxley
HIPAA
GLBA
PCI
FISMA
NIST SP 800-66
Ditscap
Control Exception
User Defined


Risk Association Control Activities:

1. Risk: Lost data could significantly impact financial reporting.
a. SOX.2.7.9 Policies and procedures exist for the distribution and retention of data and reporting output.



2. Risk: Lost data could significantly impact financial reporting.
a. SOX.2.7.10 Management protects sensitive information— logically and physically, in storage and during transmission—against unauthorized access or modification.



3. Risk: Lost data could significantly impact financial reporting.
a. SOX.2.7.11 Retention periods and storage terms are defined for documents, data, programs, reports and messages (incoming and outgoing), as well as the data (keys, certificates) used for their encryption and authentication.




4. Risk: Lost data could significantly impact financial reporting.
a. SOX.2.7.12 Management has implemented a strategy for cyclical backup of data and programs.




5. Risk: Lost data could significantly impact financial reporting.
a. SOX.2.7.13 The restoration of backup media is periodically tested.


6. Risk: Lost data could significantly impact financial reporting.
a. SOX.2.7.14 Changes to data structures are authorized, made in accordance with design specifications and implemented in a timely manner.



  • PCI.3.3: Mask account numbers when displayed (the first six and last four digits are the maximum number of digits to be displayed).


  • PCI.3.4: Render sensitive cardholder data unreadable anywhere it is stored (including data on portable media, backup media, in logs, and data received from or stored by wireless networks) by using any of the following approaches: 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 Advanced Encryption Standard (AES) 256-bit with associated key management processes and procedures.


  • PCI-4.1.1 For wireless networks transmitting cardholder data, encrypt the transmissions by using Wi-Fi Protected Access (WPA) technology if WPA capable, or VPN or SSL at 128-bit. Never rely exclusively on WEP to protect confidentiality and access to a wireless LAN. Use one of the above methodologies in conjunction with WEP at 128 bit, and rotate shared WEP keys quarterly and whenever there are personnel changes.


Process Narrative
Insert a description of the process narration that is applicable to the existing control statement this narrative refers to.

Process Illustration
Insert a process diagram, flowchart or other visual representation here to illustrate the process narrative.

File:Someimage.jpg

Control Commentary
Insert a description of the control that is applicable to the existing control statement this commentary refers to.

Control Exception Commentary
Insert a description of the control exception that is applicable to the existing control statement this commentary refers to.

Evidence Archive Location
Insert Evidence Description Here.

Control Status and Auditors Commentary
Describe the condition of the applicable control and its effectiveness. Set the color icon to a redlock.jpg, yellowlock.jpg or greenlock.jpg.

File:Redlock.jpg

Remediation Plan
Insert remediation plan, applicability, or any information that indicates what needs to be done.

Supplemental Information: