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.
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:
- Solaris Unix: etc/passwd
- AIX Unix: etc/passwd
- Linux Unix: etc/passwd
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
Status is acceptable.
Control Exception Commentary
Status is acceptable.
Remediation Plan
Remediation is not required at this time.
8. Risk: Insufficient security standards may allow unauthorized access to production systems and business data stores.
- a. SOX.4.2.1.8: UNIX passwords are required for each system ID. Password configuration is based on Corporate IT standards.
Testing Procedures
Obtain a copy of the configuration file enforcing the password parameters as defined by the corporate policy document: Technical Standard – Access Controls.
An example of this might be one of the following:
- Solaris Unix: etc/default/passwd
- AIX Unix: etc/security/user
- Linux Unix: etc/login.defs
Testing Frequency
Quarterly validation of all systems within scope.
Evidence Archive Location
Insert hyperlink or location of evidence archive.
Control Stewards Process Narrative
Passwords on all platforms adhere to the corporate policy document: Technical Standard – Access Controls.
The password complexity standards include the following:
- Password Length: 8 characters.
- Password Complexity: At least one each of alpha (a - z), numeric (0 - 9) and special characters (#, $ and @).
- Passwords may not be reused again for nine months.
- Password must be changed every thirteen weeks.
Control Steward – Pat Manager
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 at this time because the appropriate password parameters are automatically enforced and they meet or exceed corporate information technology password standards.
File:Greenlock.jpg
Continued ongoing random sample testing of all UNIX systems on a quarterly basis is advised.
Control Exception Commentary
Status acceptable. Control exceptions do not exist at this time.
Remediation Plan
Status acceptable. Remediation not required at this time.
9. Risk: Inappropriate administrative actions are executed without accountability measures.
- a. SOX.4.2.1.9: The UNIX operating system application has forensic auditing enabled to enable the monitoring of administrative access related events.
Testing Procedures
Obtain a copy of an automatic notification message produced by the system being tested to verify that the security administrators are being proactively notified of possible access violations.
An example might be a monitoring background process that sends an electronic message to the security administrative group automatically when root access occurs. The email message will provide a date, time, source, destination, and responsible entity to satisfy compliance requirements.
Testing Frequency
Semi- Annual validation of all systems within scope.
Evidence Archive Location
Insert hyperlink or location of evidence archive.
Control Stewards Process Narrative
Currently, no active notification of security violations occurs. If there is suspicion of activity, IT Security would work with the Systems Software group to access to security logs on each AIX host.
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 not effective at this time because automatic system alerts are not being generated to provide effective proactive security event alerts to the security administrators.
File:Redlock.jpg
Creating simple monitoring shell scripts or implementing a commercial solution is advised.
Control Exception Commentary
Status in not acceptable.
Remediation Plan
Implement a CRON driven shell script to monitor activity logs. Alert activity should be proactively forwarded to security administrators as these events occur ideally through electronic mail. The security administrator should investigate suspect activities and document any findings. This action report should be archived for compliance testing purposes.
10. Risk: Reactive security monitoring results in data compromise and financial loss or liability.
- a. SOX.4.2.1.10: UNIX administration team is notified when security violations occur.
Testing Procedures
Obtain a copy of an automatic notification message produced by the system being tested to verify that security violations are being proactively monitored and that security administrators are being proactively notified of possible security violations.
An example might be a monitoring background process that sends an electronic message to the security administrative group automatically when violations occur. The email message will provide a date, time, source, destination, and responsible entity to satisfy compliance requirements.
Testing Frequency
Quarterly validation of all systems within scope.
Evidence Archive Location
Insert hyperlink or location of evidence archive.
Control Stewards Process Narrative
Currently, no active notification of security violations occurs. If there is suspicion of activity, IT Security would work with the Systems Software group to access to security logs on each AIX host.
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 not effective at this time because automatic system alerts are not being generated to provide effective proactive security event alerts to the security administrators.
File:Redlock.jpg
Creating simple monitoring shell scripts or implementing a commercial solution is advised.
Control Exception Commentary
Status in not acceptable.
Remediation Plan
Implement a CRON driven shell script to monitor activity logs. Alert activity should be proactively forwarded to security administrators as these events occur ideally through electronic mail. The security administrator should investigate suspect activities and document any findings. This action report should be archived for compliance testing purposes.
11. Risk: Forensic evidence is not available to resolve malfunctions, compromises or other security compromising incidents.
- a. SOX.4.2.1.11: The UNIX administration team reviews security logs looking for security violations.
12. Risk: Unauthorized access is granted to business systems or data stores.
- a. SOX.4.2.1.12: UNIX access is granted through a service request.
13. Risk: Unauthorized access may occur resulting in business data compromise or destruction.
- a. SOX.4.2.1.13: Terminations are sent through the HR process. An Email is sent from HR with all terminations to the UNIX system administrators.
14. Risk: Insufficient security standards may allow unauthorized access to production systems and business data stores.
- a. SOX.4.2.1.14: UNIX password expiration is set to Corporate IT standards.
15. Risk: Security violations or data corruption may occur with no forensic evidence available to resolve the situation.
- a. SOX.4.2.1.15: UNIX rules and logging is applied to everyone equally including system administrators.
16. Risk: Unauthorized access (i.e. terminated employees) may occur.
- a. SOX.4.2.1.16: A semi-annual revalidation of UNIX administrator accounts are performed by security administration.
17. Risk: Unauthorized execution of privileged system commands may disrupt business processes, and corrupt critical business data stores.
- a. SOX.4.2.1.17: Root level access is password restricted. This password is know only by system the administrators.
18. Risk: Unauthorized users could elevate their access to privileged file systems.
- a. SOX.4.2.1.18: The /etc/default/login UMASK 027 parameter is enabled.
19. Risk: Unauthorized personnel gain access to the application through remote access.
- a. SOX.4.2.1.19: The /etc/default/login CONSOLE parameter is enabled.