All TOSS local files and directories must have a valid owner.
Overview
| Finding ID | Version | Rule ID | IA Controls | Severity |
| V-253100 | TOSS-04-040580 | SV-253100r991589_rule | CCI-000366 | medium |
| Description | ||||
| Unowned files and directories may be unintentionally inherited if a user is assigned the same User Identifier "UID" as the UID of the un-owned files. | ||||
| STIG | Date | |||
| Tri-Lab Operating System Stack (TOSS) 4 Security Technical Implementation Guide | 2025-05-08 | |||
Related Frameworks
4 paths across 3 frameworks
Related Frameworks
NIST 800-531 mapping
CM-6
1.00
- DISA · 2 · disa_xccdf · related
- DISA · 2025-01-23 · disa_cci_list · equivalent
NIST 800-1712 mappings
3.4.1
1.00
- DISA · 2 · disa_xccdf · related
- DISA · 2025-01-23 · disa_cci_list · equivalent
- NIST · Rev 2 (Feb 2020, errata Jan 2021) · nist_800_171_app_d · equivalent
3.4.2
1.00
- DISA · 2 · disa_xccdf · related
- DISA · 2025-01-23 · disa_cci_list · equivalent
- NIST · Rev 2 (Feb 2020, errata Jan 2021) · nist_800_171_app_d · equivalent
CCI1 mapping
CCI-000366
1.00
- DISA · 2 · disa_xccdf · related
Details
Check Text (C-253100r991589_chk)
Verify all local files and directories on TOSS have a valid owner with the following command:
Note: The value after -fstype must be replaced with the filesystem type. XFS is used as an example.
$ sudo find / -fstype xfs -nouser
If any files on the system do not have an assigned owner, this is a finding.
Note: Command may produce error messages from the /proc and /sys directories.
Fix Text (F-56503r824971_fix)
Either remove all files and directories from the system that do not have a valid user, or assign a valid user to all unowned files and directories on TOSS with the "chown" command:
$ sudo chown <user> <file>