Details

Without auditing, individual system accesses cannot be tracked, and malicious activity cannot be detected and traced back to an individual account.

Solution

The Audit Configuration profile is required. All audit flags must be enabled in a single command.

This action applies to the global zone only. Determine the zone that you are currently securing.

# zonename

If the command output is ‘global’, this action applies.

For Solaris 11, 11.1, 11.2, and 11.3:
# pfexec auditconfig -setflags cusa,-ps,fd,-fa,fm

For Solaris 11.4 or newer:
# pfexec auditconfig -setflags cusa,-fa,-ex,-ps,fd,fm

Enable the audit policy to collect command line arguments.

# pfexec auditconfig -setpolicy +argv

These changes will not affect users that are currently logged in.

Supportive Information

The following resource is also helpful.

• https://dl.dod.cyber.mil/wp-content/uploads/stigs/zip/U_SOL_11_x86_V2R6_STIG.ziphttps://dl.dod.cyber.mil/wp-content/uploads/stigs/zip/U_SOL_11_x86_V2R6_STIG.zip

This security hardening control applies to the following category of controls within NIST 800-53: Configuration Management.This control applies to the following type of system Unix.

References

• 800-53|CM-6b.
• CAT|III
• CCI|CCI-000366
• Rule-ID|SV-216033r603268_rule
• STIG-ID|SOL-11.1-010340
• STIG-Legacy|SV-60701
• STIG-Legacy|V-47825
• Vuln-ID|V-216033

Source

• Tenable.com/audits