OpenControls Logo

STIG Viewer

STIGViewer Support

The Photon operating system must reveal error messages only to authorized users.

Overview

Finding IDVersionRule IDIA ControlsSeverity
V-258832PHTN-40-000074SV-258832r958566_ruleCCI-001314medium
Description
Only authorized personnel should be aware of errors and the details of the errors. Error messages are an indicator of an organization's operational state or can identify the operating system or platform. Additionally, Personally Identifiable Information (PII) and operational information must not be revealed through error messages to unauthorized personnel or their designated representatives.
STIGDate
VMware vSphere 8.0 vCenter Appliance Photon OS 4.0 Security Technical Implementation Guide2026-06-02

Related Frameworks

1 mapping across 3 frameworks
SCF0 mappings

No source states a mapping between these directly.

Also reachable in 3 hops (1) derived by us, not asserted by any source

Each of these is a route we composed by chaining published mappings. No publisher states a relationship between the two endpoints.

TDA-19Error Handling
1.00
NIST 800-530 mappings

No source states a mapping between these directly.

Also reachable in 2 hops (12) derived by us, not asserted by any source

Each of these is a route we composed by chaining published mappings. No publisher states a relationship between the two endpoints.

AC-17(1)Monitoring and Control
1.00
AC-3Access Enforcement
1.00
AC-6(10)Prohibit Non-privileged Users from Executing Privileged Functions
1.00
AC-6(9)Log Use of Privileged Functions
1.00
AU-10Non-repudiation
1.00
AU-12Audit Record Generation
1.00
AU-14(1)System Start-up
1.00
AU-9Protection of Audit Information
1.00
AU-9(1)Hardware Write-once Media
1.00
AU-9(3)Cryptographic Protection
1.00

+2 more (top 10 by confidence shown)

CCI1 mapping
CCI-001314
1.00

Details

Check Text (C-258832r958566_chk)

If another package is used to offload logs, such as syslog-ng, and is properly configured, this is not applicable. At the command line, run the following command to verify rsyslog generates log files that are not world readable: # grep '^\$umask' /etc/rsyslog.conf Example result: $umask 0037 If "$umask" is not set to "0037" or more restrictive, this is a finding.

Fix Text (F-62481r933556_fix)

Navigate to and open: /etc/rsyslog.conf Add or update the following line: $umask 0037 At the command line, run the following command: # systemctl restart rsyslog.service