DS9.3:: Difference between revisions
No edit summary |
No edit summary |
||
| Line 4: | Line 4: | ||
<br> | <br> | ||
Review and verify on a regular basis, using, where necessary, appropriate tools, the status of configuration items to confirm the integrity of the current and historical configuration data and to compare against the actual situation. Review periodically against the policy for software usage the existence of any personal or unlicensed software or any software instances in excess of current license agreements. Errors and deviations should be reported, acted on and corrected. | Review and verify on a regular basis, using, where necessary, appropriate tools, the status of configuration items to confirm the integrity of the current and historical configuration data and to compare against the actual situation. Review periodically against the policy for software usage the existence of any personal or unlicensed software or any software instances in excess of current license agreements. Errors and deviations should be reported, acted on and corrected. | ||
<br>'''Applicability:'''<br> | <br><br>'''Applicability:'''<br> | ||
<br> | <br> | ||
:: Sarbanes-Oxley | :: Sarbanes-Oxley | ||
Revision as of 17:30, 5 May 2006
DS 9.3 Configuration Integrity Review
Control Objective:
Review and verify on a regular basis, using, where necessary, appropriate tools, the status of configuration items to confirm the integrity of the current and historical configuration data and to compare against the actual situation. Review periodically against the policy for software usage the existence of any personal or unlicensed software or any software instances in excess of current license agreements. Errors and deviations should be reported, acted on and corrected.
Applicability:
- Sarbanes-Oxley
- HIPAA
- GLBA
- PCI
- FISMA
- NIST SP 800-66
- Ditscap
- Control Exception
- User Defined
Risk Association Control Activities:
- 1. Risk: Security incidents and incompliance with information security procedures may go overlooked and not addressed.
- a. SOX.3.1.1: Management should monitor security incidents and the extent of compliance with information security procedures.
- 1. Risk: Security incidents and incompliance with information security procedures may go overlooked and not addressed.
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:
