|
|
| Line 63: |
Line 63: |
| Remediation is not required at this time. | | Remediation is not required at this time. |
| <br> | | <br> |
| </blockquote>
| |
|
| |
|
| |
| <blockquote style="background: #C8CDC7; padding: 1em; margin-left: 0.5em;">
| |
| '''8. Risk: Insufficient security standards may allow unauthorized access to production systems and business data stores.'''<br>
| |
| :a. SOX.4.2.1.8: UNIX passwords are required for each system ID. Password configuration is based on Corporate IT standards.<br>
| |
| </blockquote>
| |
|
| |
| '''Testing Procedures'''
| |
| <blockquote style="background: white; border: 1px solid black; padding: 1em;">
| |
| Obtain a copy of the configuration file enforcing the password parameters as defined by the corporate policy document: '''Technical Standard – Access Controls.'''<br>
| |
|
| |
| An example of this might be one of the following:<br>
| |
|
| |
| *Solaris Unix: etc/default/passwd<br>
| |
| *AIX Unix: etc/security/user<br>
| |
| *Linux Unix: etc/login.defs<br>
| |
|
| |
| <br>
| |
| </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;">
| |
| <p><font color=#008000>Passwords on all platforms adhere to the corporate policy document: '''Technical Standard – Access Controls.'''</font></p><br>
| |
|
| |
| The password complexity standards include the following:<br>
| |
|
| |
| *Password Length: 8 characters.<br>
| |
|
| |
| *Password Complexity: At least one each of alpha (a - z), numeric (0 - 9) and special characters (#, $ and @).<br>
| |
|
| |
| *Passwords may not be reused again for nine months.<br>
| |
|
| |
| *Password must be changed every thirteen weeks.<br>
| |
|
| |
| '''Control Steward – Pat Manager'''
| |
| <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;">
| |
| <p><font color=#008000>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.</font></p>
| |
| <br>
| |
| [[Image:greenlock.jpg]]<br>
| |
| <br>
| |
| Continued ongoing random sample testing of all UNIX systems on a quarterly basis is advised.
| |
| <br>
| |
| </blockquote>
| |
|
| |
| '''Control Exception Commentary'''
| |
| <blockquote style="background: white; border: 1px solid black; padding: 1em;">
| |
| Status acceptable. Control exceptions do not exist at this time.
| |
| <br>
| |
| </blockquote>
| |
|
| |
| '''Remediation Plan'''
| |
| <blockquote style="background: white; border: 1px solid black; padding: 1em;">
| |
| Status acceptable. Remediation not required at this time.
| |
| <br>
| |
| </blockquote>
| |
|
| |
|
| |
| <blockquote style="background: #C8CDC7; padding: 1em; margin-left: 0.5em;">
| |
| '''9. Risk: Inappropriate administrative actions are executed without accountability measures.'''<br>
| |
| :a. SOX.4.2.1.9: The UNIX operating system application has forensic auditing enabled to enable the monitoring of administrative access related events.<br>
| |
| </blockquote>
| |
|
| |
| '''Testing Procedures'''
| |
| <blockquote style="background: white; border: 1px solid black; padding: 1em;">
| |
| 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.<br>
| |
|
| |
| 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.<br>
| |
| <br>
| |
| </blockquote>
| |
|
| |
| '''Testing Frequency'''
| |
| <blockquote style="background: white; border: 1px solid black; padding: 1em;">
| |
| Semi- Annual 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;">
| |
| <p><font color=#FF0000>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.</font></p>
| |
|
| |
| <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;">
| |
| <p><font color=#FF0000>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.</font></p>
| |
| <br>
| |
| [[Image:redlock.jpg]]<br>
| |
| <br>
| |
| Creating simple monitoring shell scripts or implementing a commercial solution is advised.
| |
| <br>
| |
| </blockquote>
| |
|
| |
| '''Control Exception Commentary'''
| |
| <blockquote style="background: white; border: 1px solid black; padding: 1em;">
| |
| Status in not acceptable.
| |
| <br>
| |
| </blockquote>
| |
|
| |
| '''Remediation Plan'''
| |
| <blockquote style="background: white; border: 1px solid black; padding: 1em;">
| |
| 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.
| |
|
| |
| <br>
| |
| </blockquote>
| |
|
| |
|
| |
| <blockquote style="background: #C8CDC7; padding: 1em; margin-left: 0.5em;">
| |
| '''10. Risk: Reactive security monitoring results in data compromise and financial loss or liability.'''<br>
| |
| :a. SOX.4.2.1.10: UNIX administration team is notified when security violations occur.<br>
| |
| </blockquote>
| |
|
| |
| '''Testing Procedures'''
| |
| <blockquote style="background: white; border: 1px solid black; padding: 1em;">
| |
| 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.<br>
| |
|
| |
| 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.<br>
| |
| <br>
| |
| </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;">
| |
| <p><font color=#FF0000>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.</font></p>
| |
|
| |
| <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;">
| |
| <p><font color=#FF0000>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.</font></p>
| |
| <br>
| |
| [[Image:redlock.jpg]]<br>
| |
| <br>
| |
| Creating simple monitoring shell scripts or implementing a commercial solution is advised.
| |
| <br>
| |
| </blockquote>
| |
|
| |
| '''Control Exception Commentary'''
| |
| <blockquote style="background: white; border: 1px solid black; padding: 1em;">
| |
| Status in not acceptable.
| |
| <br>
| |
| </blockquote>
| |
|
| |
| '''Remediation Plan'''
| |
| <blockquote style="background: white; border: 1px solid black; padding: 1em;">
| |
| 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.
| |
|
| |
| <br>
| |
| </blockquote>
| |
|
| |
|
| |
| <blockquote style="background: #C8CDC7; padding: 1em; margin-left: 0.5em;">
| |
| '''11. Risk: Forensic evidence is not available to resolve malfunctions, compromises or other security compromising incidents.'''<br>
| |
| :a. SOX.4.2.1.11: The UNIX administration team reviews security logs looking for security violations.<br>
| |
| </blockquote>
| |
|
| |
|
| |
| <blockquote style="background: #C8CDC7; padding: 1em; margin-left: 0.5em;">
| |
| '''12. Risk: Unauthorized access is granted to business systems or data stores.'''<br>
| |
| :a. SOX.4.2.1.12: UNIX access is granted through a service request.<br>
| |
| </blockquote>
| |
|
| |
|
| |
| <blockquote style="background: #C8CDC7; padding: 1em; margin-left: 0.5em;">
| |
| '''13. Risk: Unauthorized access may occur resulting in business data compromise or destruction.'''<br>
| |
| :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.<br>
| |
| </blockquote>
| |
|
| |
|
| |
| <blockquote style="background: #C8CDC7; padding: 1em; margin-left: 0.5em;">
| |
| '''14. Risk: Insufficient security standards may allow unauthorized access to production systems and business data stores.'''<br>
| |
| :a. SOX.4.2.1.14: UNIX password expiration is set to Corporate IT standards.<br>
| |
| </blockquote>
| |
|
| |
|
| |
| <blockquote style="background: #C8CDC7; padding: 1em; margin-left: 0.5em;">
| |
| '''15. Risk: Security violations or data corruption may occur with no forensic evidence available to resolve the situation.'''<br>
| |
| :a. SOX.4.2.1.15: UNIX rules and logging is applied to everyone equally including system administrators.<br>
| |
| </blockquote>
| |
|
| |
|
| |
| <blockquote style="background: #C8CDC7; padding: 1em; margin-left: 0.5em;">
| |
| '''16. Risk: Unauthorized access (i.e. terminated employees) may occur.'''<br>
| |
| :a. SOX.4.2.1.16: A semi-annual revalidation of UNIX administrator accounts are performed by security administration.<br>
| |
| </blockquote>
| |
|
| |
|
| |
| <blockquote style="background: #C8CDC7; padding: 1em; margin-left: 0.5em;">
| |
| '''17. Risk: Unauthorized execution of privileged system commands may disrupt business processes, and corrupt critical business data stores.'''<br>
| |
| :a. SOX.4.2.1.17: Root level access is password restricted. This password is know only by system the administrators.<br>
| |
| </blockquote>
| |
|
| |
|
| |
| <blockquote style="background: #C8CDC7; padding: 1em; margin-left: 0.5em;">
| |
| '''18. Risk: Unauthorized users could elevate their access to privileged file systems.'''<br>
| |
| :a. SOX.4.2.1.18: The /etc/default/login UMASK 027 parameter is enabled.<br>
| |
| </blockquote>
| |
|
| |
|
| |
| <blockquote style="background: #C8CDC7; padding: 1em; margin-left: 0.5em;">
| |
| '''19. Risk: Unauthorized personnel gain access to the application through remote access.'''<br>
| |
| :a. SOX.4.2.1.19: The /etc/default/login CONSOLE parameter is enabled.<br>
| |
| </blockquote> | | </blockquote> |
