DS9.2:: Difference between revisions
No edit summary |
No edit summary |
||
| (One intermediate revision by the same user not shown) | |||
| Line 1: | Line 1: | ||
'''DS 9.2 Identification and Maintenance of Configuration Items '''<br> | '''DS 9.2 Identification and Maintenance of Configuration Items '''<br> | ||
<br> | <br> | ||
'''Control Objective:'''<br> | '''Control Objective:''' | ||
<br> | |||
<br> | |||
Controls provide reasonable assurance that IT components, as they relate to security, processing and availability, are well protected, would prevent any unauthorized changes, and assist in the verification and recording of the current configuration | |||
<br> | <br> | ||
Put procedures in place to: | Put procedures in place to: | ||
| Line 12: | Line 15: | ||
<br> | <br> | ||
These procedures should provide proper authorization and logging of all actions on the configuration repository and be properly integrated with change management and problem management procedures. | These procedures should provide proper authorization and logging of all actions on the configuration repository and be properly integrated with change management and problem management procedures. | ||
<br> | |||
<br> | |||
'''Rationale —''' Configuration management includes procedures such that security, availability and processing integrity controls are set up in the system and maintained through its life cycle. Insufficient configuration controls can lead to security and availability exposures that may permit unauthorized access to systems and data and impact financial reporting | |||
<br> | <br> | ||
<br>'''Applicability:'''<br> | <br>'''Applicability:'''<br> | ||
<br> | <br> | ||
:: Sarbanes-Oxley | :: '''Sarbanes-Oxley''' | ||
:: HIPAA | :: HIPAA | ||
:: GLBA | :: GLBA | ||
| Line 25: | Line 31: | ||
:: User Defined | :: User Defined | ||
<br> | <br> | ||
'''Risk Association Control Activities:'''<br> | '''Risk Association Control Activities:''' | ||
<br> | |||
<br> | |||
[[Image:Key-control.jpg]]<br> | |||
::'''1. Risk: Insufficient configuration controls can lead to security and availability exposures that may permit unauthorized access to systems and data and impact financial reporting. .'''<br> | |||
:::a. [[SOX.2.0.32:|'''SOX.2.0.32''']] Periodic testing and assessment is performed to confirm that the software and network infrastructure is appropriately configured. <br> | |||
<br> | <br> | ||
'''Implementation Guide:'''<br> | '''Implementation Guide:'''<br> | ||
Latest revision as of 18:55, 25 June 2006
DS 9.2 Identification and Maintenance of Configuration Items
Control Objective:
Controls provide reasonable assurance that IT components, as they relate to security, processing and availability, are well protected, would prevent any unauthorized changes, and assist in the verification and recording of the current configuration
Put procedures in place to:
- 1. Identify configuration items and their attributes
- 2. Record new, modified and deleted configuration items
- 3. Identify and maintain the relationships among configuration items in the configuration repository
- 4. Update existing configuration items into the configuration repository
- 5. Prevent the inclusion of unauthorized software
These procedures should provide proper authorization and logging of all actions on the configuration repository and be properly integrated with change management and problem management procedures.
Rationale — Configuration management includes procedures such that security, availability and processing integrity controls are set up in the system and maintained through its life cycle. Insufficient configuration controls can lead to security and availability exposures that may permit unauthorized access to systems and data and impact financial reporting
Applicability:
- Sarbanes-Oxley
- HIPAA
- GLBA
- PCI
- FISMA
- NIST SP 800-66
- Ditscap
- Control Exception
- User Defined
Risk Association Control Activities:
- 1. Risk: Insufficient configuration controls can lead to security and availability exposures that may permit unauthorized access to systems and data and impact financial reporting. .
- a. SOX.2.0.32 Periodic testing and assessment is performed to confirm that the software and network infrastructure is appropriately configured.
- a. SOX.2.0.32 Periodic testing and assessment is performed to confirm that the software and network infrastructure is appropriately configured.
- 1. Risk: Insufficient configuration controls can lead to security and availability exposures that may permit unauthorized access to systems and data and impact financial reporting. .
Implementation Guide:
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:
