Ubuntu OS must generate audit records for successful/unsuccessful attempts to use the fdisk command.
Overview
| Finding ID | Version | Rule ID | IA Controls | Severity |
| V-275696 | RIIM-OS-654045 | SV-275696r1148138_rule | CCI-000172 | medium |
| Description | ||||
| Without generating audit records specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one. Audit records can be generated from various components within the information system (e.g., module or policy filter). | ||||
| STIG | Date | |||
| Riverbed NetIM OS Security Technical Implementation Guide | 2025-10-02 | |||
Details
Check Text (C-275696r1148138_chk)
Verify Ubuntu OS is configured to audit the execution of the partition management program "fdisk" by using the following command:
$ sudo auditctl -l | grep fdisk
-w /usr/sbin/fdisk -p x -k fdisk
If the command does not return a line, or the line is commented out, this is a finding.
Note: The "-k" value is arbitrary and can be different from the example output above.
Fix Text (F-79703r1148137_fix)
Configure Ubuntu OS to audit the execution of the partition management program "fdisk".
Add or modify the following line in the "/etc/audit/rules.d/stig.rules" file:
-w /usr/sbin/fdisk -p x -k fdisk
To reload the rules file, issue the following command:
$ sudo augenrules --load
Note: The "-k <keyname>" at the end of the line gives the rule a unique meaning to help during an audit investigation. The <keyname> does not need to match the example above.