DS12.2:: Difference between revisions
No edit summary |
No edit summary |
||
| Line 16: | Line 16: | ||
<br> | <br> | ||
'''Risk Association Control Activities:'''<br> | '''Risk Association Control Activities:'''<br> | ||
::''' | ::1. '''Risk: Third party service providers may not meet business, compliance and regulatory needs of the business inducing risk.'''<br> | ||
:::a. SOX.1.5: | :::a. [[SOX.1.5:|'''SOX.1.5''']] A designated individual is responsible for regular monitoring and reporting on the achievement of the third-party service-level performance criteria.<br> | ||
<br> | <br> | ||
::'''2. Risk: Security and business continuity risks are introduced by technical designs incompatible with enterprise standards.''' | ::'''2. Risk: Security and business continuity risks are introduced by technical designs incompatible with enterprise standards.''' | ||
:::a. SOX.1.15: | :::a. [[SOX.1.15:|'''SOX.1.15''']] The organizations SDLC policies and procedures consider the development and acquisition of new systems and major changes to existing systems.<br> | ||
<br> | <br> | ||
::'''3. Risk: Power failure will result in uncontrolled shutdown of business applications.'''<br> | ::'''3. Risk: Power failure will result in uncontrolled shutdown of business applications.'''<br> | ||
:::a. SOX.2.5.1: UPS and generators are periodically tested. | :::a. [[SOX.2.5.1:|'''SOX.2.5.1''']] UPS and generators are periodically tested. | ||
<br> | <br> | ||
::'''4. Risk: Critical Business Systems may be compromised as the result of catastrophic events resulting in the loss of critical data and applications systems.''' | ::'''4. Risk: Critical Business Systems may be compromised as the result of catastrophic events resulting in the loss of critical data and applications systems.''' | ||
:::a. SOX.2.5.5: Equipment is protected by environmental controls including fire prevention or detection systems, air conditioning, humidity controls, alternative power supplies, etc. | :::a. [[SOX.2.5.5:|'''SOX.2.5.5''']] Equipment is protected by environmental controls including fire prevention or detection systems, air conditioning, humidity controls, alternative power supplies, etc. | ||
<br> | <br> | ||
::'''5. Risk: Security incidents and incompliance with information security procedures may go overlooked and not addressed.''' | ::'''5. 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. | :::a. [[SOX.3.1.1:|'''SOX.3.1.1''']] Management should monitor security incidents and the extent of compliance with information security procedures. | ||
<br> | <br> | ||
'''Process Narrative'''<br> | '''Process Narrative'''<br> | ||
Latest revision as of 18:12, 21 June 2006
DS 12.2 Physical Security Measures
Control Objective:
Define and implement physical security measures in line with business requirements. Measures should include, but are not limited to, the layout of the security perimeter, security zones, location of critical equipment, and shipping and receiving areas. In particular, keep a low profile about the presence of critical IT operations. Responsibilities for monitoring and procedures for reporting and resolving physical security incidents need to be established.
Applicability:
- Sarbanes-Oxley
- HIPAA
- GLBA
- PCI
- FISMA
- NIST SP 800-66
- Ditscap
- Control Exception
- User Defined
Risk Association Control Activities:
- 1. Risk: Third party service providers may not meet business, compliance and regulatory needs of the business inducing risk.
- a. SOX.1.5 A designated individual is responsible for regular monitoring and reporting on the achievement of the third-party service-level performance criteria.
- a. SOX.1.5 A designated individual is responsible for regular monitoring and reporting on the achievement of the third-party service-level performance criteria.
- 1. Risk: Third party service providers may not meet business, compliance and regulatory needs of the business inducing risk.
- 2. Risk: Security and business continuity risks are introduced by technical designs incompatible with enterprise standards.
- a. SOX.1.15 The organizations SDLC policies and procedures consider the development and acquisition of new systems and major changes to existing systems.
- a. SOX.1.15 The organizations SDLC policies and procedures consider the development and acquisition of new systems and major changes to existing systems.
- 2. Risk: Security and business continuity risks are introduced by technical designs incompatible with enterprise standards.
- 3. Risk: Power failure will result in uncontrolled shutdown of business applications.
- a. SOX.2.5.1 UPS and generators are periodically tested.
- 3. Risk: Power failure will result in uncontrolled shutdown of business applications.
- 4. Risk: Critical Business Systems may be compromised as the result of catastrophic events resulting in the loss of critical data and applications systems.
- a. SOX.2.5.5 Equipment is protected by environmental controls including fire prevention or detection systems, air conditioning, humidity controls, alternative power supplies, etc.
- 4. Risk: Critical Business Systems may be compromised as the result of catastrophic events resulting in the loss of critical data and applications systems.
- 5. 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.
- 5. Risk: Security incidents and incompliance with information security procedures may go overlooked and not addressed.
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:
ISO 7.1 Secure areas
ISO 7.2 Equipment security
ISO 7.3 General controls
ISO 8.5 Network management
ISO 8.6 Media handling and security
ISO 4.1 Information security infrastructure
ISO 4.2 Security of third-party access
ISO 6.1 Security in job definition and resourcing
ISO 8.1 Operational procedures and responsibilities
ISO 9.3 User responsibilities
