AI3.2:: Difference between revisions
No edit summary |
No edit summary |
||
| Line 30: | Line 30: | ||
:::'''7. Risk: Unidentifiable users may compromise critical business processes and data.'''<br> | :::'''7. Risk: Unidentifiable users may compromise critical business processes and data.'''<br> | ||
::::a. SOX.4.2.1.7: The UNIX system will not allow identical administrator IDs.<br> | ::::a. SOX.4.2.1.7: The UNIX system will not allow identical administrator IDs.<br> | ||
'''Testing Procedures''' | '''Testing Procedures''' | ||
<blockquote style="background: white; border: 1px solid black; padding: 1em;"> | <blockquote style="background: white; border: 1px solid black; padding: 1em;"> | ||
Obtain a copy of the user control file from the system and verify that there are no duplicate system accounts.<br> | Obtain a copy of the user control file from the system and verify that there are no duplicate system accounts.<br> | ||
| Line 37: | Line 37: | ||
<br> | <br> | ||
</blockquote> | </blockquote> | ||
'''Testing Frequency''' | |||
<blockquote style="background: white; border: 1px solid black; padding: 1em;"> | |||
Quarterly validation of all systems within scope. | |||
<br> | |||
</blockquote> | |||
'''Evidence Archive Location''' | |||
<blockquote style="background: white; border: 1px solid black; padding: 1em;"> | |||
Insert hyperlink or location of evidence archive. | |||
<br> | |||
</blockquote> | |||
'''Control Stewards Process Narrative''' | |||
<blockquote style="background: white; border: 1px solid black; padding: 1em;"> | |||
The AIX operating system prevents the addition of duplicate Ids. Furthermore, the regular review of administrator IDs listed above serves as a backstop for this control.<br> | |||
'''Control Steward – Steve Somebody''' | |||
<br> | |||
</blockquote> | |||
'''Process Illustration''' | |||
<blockquote style="background: white; border: 1px solid black; padding: 1em;"> | |||
Replace this test by inserting a process diagram, flowchart or other visual representation to illustrate the process narrative as necessary. Include a brief description of the process illustration. | |||
<br> | |||
</blockquote> | |||
'''Control Status and Auditors Commentary''' | |||
<blockquote style="background: white; border: 1px solid black; padding: 1em;"> | |||
The control is effective. It is technically impossible to establish identical user accounts on a UNIX operating system.<br> | |||
<br> | |||
[[Image:greenlock.jpg]] | |||
<br> | |||
</blockquote> | |||
'''Control Exception Commentary''' | |||
<blockquote style="background: white; border: 1px solid black; padding: 1em;"> | |||
Status is acceptable. | |||
<br> | |||
</blockquote> | |||
'''Remediation Plan''' | |||
<blockquote style="background: white; border: 1px solid black; padding: 1em;"> | |||
Remediation is not required at this time. | |||
<br> | |||
</blockquote> | |||
:::'''3.2.2.2: WINDOWS'''<br> | :::'''3.2.2.2: WINDOWS'''<br> | ||
:::'''3.2.2.3: MAINFRAME'''<br> | :::'''3.2.2.3: MAINFRAME'''<br> | ||
:::'''3.2.2.4: AS/400'''<br> | :::'''3.2.2.4: AS/400'''<br> | ||
Revision as of 14:51, 2 May 2006
AI 3.2 Infrastructure Resource Protection and Availability
Control Objective:
Implement internal control, security and audit ability measures during configuration, integration and maintenance of hardware and infrastructural software to protect resources and ensure availability and integrity. Responsibilities for using sensitive infrastructure components should be clearly defined and understood by those who develop and integrate infrastructure components. Their use should be monitored and evaluated.
Applicability:
- Sarbanes-Oxley
- HIPAA
- GLBA
- PCI
- FISMA
- NIST SP 800-66
- Ditscap
- Control Exception
- User Defined
Risk Association Control Activities:
- 3.2.1: Infrastructure
- 3.2.1.1: Routers
- 3.2.1.2: Firewalls
- 3.2.1.3: VPN
- 3.2.1.4: Managed Switches
- 3.2.1.5: Intrusion Detection or Prevention System
- 3.2.1.1: Routers
- 3.2.1: Infrastructure
- 3.2.2: Operating Systems
- 3.2.2.1: UNIX
- 7. Risk: Unidentifiable users may compromise critical business processes and data.
- a. SOX.4.2.1.7: The UNIX system will not allow identical administrator IDs.
- a. SOX.4.2.1.7: The UNIX system will not allow identical administrator IDs.
- 3.2.2: Operating Systems
Testing Procedures
Obtain a copy of the user control file from the system and verify that there are no duplicate system accounts.
An example of this might be one of the following:
Testing Frequency
Quarterly validation of all systems within scope.
Evidence Archive Location
Insert hyperlink or location of evidence archive.
Control Stewards Process Narrative
The AIX operating system prevents the addition of duplicate Ids. Furthermore, the regular review of administrator IDs listed above serves as a backstop for this control.
Control Steward – Steve Somebody
Process Illustration
Replace this test by inserting a process diagram, flowchart or other visual representation to illustrate the process narrative as necessary. Include a brief description of the process illustration.
Control Status and Auditors Commentary
The control is effective. It is technically impossible to establish identical user accounts on a UNIX operating system.
File:Greenlock.jpg
Control Exception Commentary
Status is acceptable.
Remediation Plan
Remediation is not required at this time.
- 3.2.2.2: WINDOWS
- 3.2.2.3: MAINFRAME
- 3.2.2.4: AS/400
- 3.2.2.2: WINDOWS