PO6.4:: Difference between revisions
No edit summary |
No edit summary |
||
| Line 7: | Line 7: | ||
'''Applicability:'''<br> | '''Applicability:'''<br> | ||
<br> | <br> | ||
:: Sarbanes-Oxley | :: '''Sarbanes-Oxley''' | ||
:: HIPAA | :: HIPAA | ||
:: GLBA | :: GLBA | ||
| Line 18: | Line 18: | ||
<br> | <br> | ||
'''Risk Association Control Activities:'''<br> | '''Risk Association Control Activities:'''<br> | ||
<br> | |||
[[Image:Key-control.jpg]]<br> | |||
::'''2. Risk: Production processes and associated controls operate as intended and support financial reporting requirements.'''<br> | |||
:::a. [[SOX.2.7.1:|'''SOX.2.7.1''']] End-user computing policies and procedures concerning security, availability and processing integrity exist and are followed.<br> | |||
<br> | |||
[[Image:Key-control.jpg]]<br> | |||
::'''2. Risk: Production processes and associated controls operate as intended and support financial reporting requirements.'''<br> | |||
:::a. [[SOX.2.7.6:|'''SOX.2.7.6''']] End-user computing, including spreadsheets and other user-developed programs, are documented and regularly reviewed for processing integrity, including their ability to sort, summarize and report accurately.<br> | |||
<br> | <br> | ||
'''Implementation Guide:'''<br> | '''Implementation Guide:'''<br> | ||
| Line 63: | Line 71: | ||
'''Implementation guidance'''<br> | '''Implementation guidance'''<br> | ||
Insert guidance in this section if it helps to elaborate upon the subject matter. Examples of evidence that would help guide the end user is desirable.<br> | Insert guidance in this section if it helps to elaborate upon the subject matter. Examples of evidence that would help guide the end user is desirable.<br> | ||
--[[User:Mdpeters|Mdpeters]] 14:03, 23 June 2006 (EDT) | |||
Revision as of 18:03, 23 June 2006
PO 6.4 Policy Rollout
Control Objective:
Ensure that IT policies are rolled out to all relevant staff and enforced, so they are built into and are an integral part of enterprise operations. Rollout methods should address resource and awareness needs and implications.
Applicability:
- Sarbanes-Oxley
- HIPAA
- GLBA
- PCI
- FISMA
- NIST SP 800-66
- Ditscap
- Control Exception
- User Defined
Risk Association Control Activities:
- 2. Risk: Production processes and associated controls operate as intended and support financial reporting requirements.
- a. SOX.2.7.1 End-user computing policies and procedures concerning security, availability and processing integrity exist and are followed.
- a. SOX.2.7.1 End-user computing policies and procedures concerning security, availability and processing integrity exist and are followed.
- 2. Risk: Production processes and associated controls operate as intended and support financial reporting requirements.
- 2. Risk: Production processes and associated controls operate as intended and support financial reporting requirements.
- a. SOX.2.7.6 End-user computing, including spreadsheets and other user-developed programs, are documented and regularly reviewed for processing integrity, including their ability to sort, summarize and report accurately.
- a. SOX.2.7.6 End-user computing, including spreadsheets and other user-developed programs, are documented and regularly reviewed for processing integrity, including their ability to sort, summarize and report accurately.
- 2. Risk: Production processes and associated controls operate as intended and support financial reporting requirements.
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:
ITIL Security Management, Security Management Measures.
ITIL 4.2 Implement Security Management, Security Management Measures.
ITIL 4.3 Audit and evaluate.
ISO 17799 3.1 Information security policy.
ISO 17799 4.1 Information security infrastructure 6.1 Security in job definition and resourcing.
ISO 12.2 Reviews of security policy and technical compliance.
Implementation guidance
Insert guidance in this section if it helps to elaborate upon the subject matter. Examples of evidence that would help guide the end user is desirable.
--Mdpeters 14:03, 23 June 2006 (EDT)