STIGViewer Support

ColdFusion must produce log records containing information to establish what type of events occurred.

Overview

Finding IDVersionRule IDIA ControlsSeverity
V-279034APAS-CF-000070SV-279034r1171436_ruleCCI-000130low
Description
Without sufficient logging of events, including information about what type of event occurred, it is difficult to detect, understand, or respond to suspicious or unauthorized activity within the ColdFusion application server. Comprehensive event logging is essential to support auditing, troubleshooting, and forensic analysis. ColdFusion must generate log records that capture key attributes of events, such as event type, source, outcome, and affected components. This information enables security personnel to determine the nature of an event, assess its impact, and trace it back to a user or process. Failure to produce detailed and complete logs can result in missed detection of security incidents, hinder incident response efforts, and reduce overall situational awareness. Satisfies: SRG-APP-000095-AS-000056, SRG-APP-000096-AS-000059, SRG-APP-000097-AS-000060, SRG-APP-000098-AS-000061, SRG-APP-000099-AS-000062, SRG-APP-000100-AS-000063, SRG-APP-000101-AS-000072
STIGDate
Adobe ColdFusion Security Technical Implementation Guide2025-12-19

Related Frameworks

1 mapping across 5 frameworks
SCF0 mappings

No source states a mapping between these directly.

Also reachable in 3 hops (3) 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.

MON-01Continuous Monitoring
1.00
MON-01.4System Generated Alerts
1.00
MON-03Content of Event Logs
1.00
NIST 800-530 mappings

No source states a mapping between these directly.

Also reachable in 2 hops (45) 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-16Security and Privacy Attributes
1.00
AC-17(1)Monitoring and Control
1.00
AC-17(10)Authenticate Remote Commands
1.00
AC-2(1)Automated System Account Management
1.00
AC-2(4)Automated Audit Actions
1.00
AC-3Access Enforcement
1.00
AC-3(3)Mandatory Access Control
1.00
AC-4Information Flow Enforcement
1.00
AC-6(9)Log Use of Privileged Functions
1.00
AU-10Non-repudiation
1.00

+35 more (top 10 by confidence shown)

NIST 800-1710 mappings

No source states a mapping between these directly.

Also reachable in 3 hops (2) 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.

3.3.1
1.00
3.3.2
1.00
CCI1 mapping
NIST CSF 2.00 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.

Who does this work

6 NICE work roles and 5 EC-Council certifications.

This is an inference across published mappings, not a single claim by anyone. This check maps to a control, which maps to a Cybersecurity Framework outcome, which NIST assigns to the work roles below. EC-Council separately maps its certifications to those same roles.

A certification prepares someone for a role. It is not evidence that a holder is qualified, and neither NIST nor EC-Council has stated that any certification here addresses this check.

Work-role assignments published by NIST (NICE Framework Components 2.2.0 and the CSF 2.0 OLIR crosswalk). Certification mappings published by EC-Council.

Details

Check Text (C-279034r1171436_chk)

Verify neo-logging.xml Log Pattern configuration. 1. Open the neo-logging.xml file located at: <ColdFusion_Installation_Directory>\lib\neo-logging.xml 2. Examine the <var name='pattern'/> element. Review the value assigned to this element. Verify the log pattern configuration. 3. Confirm the value is: <string>"%p","%t",%d{"MM/dd/yy","HH:mm:ss"},"%a","%m%z"%n</string> OR Ensure the following pattern definition is included: - The pattern includes the %d (date/time) pattern definition with the appropriate format (MM/dd/yy and HH:mm:ss). - The pattern includes the %m (message) pattern. If the neo-logging.xml file is missing or cannot be located, this is a finding. If the <var name='pattern'/> element does not contain the exact required pattern, this is a finding. If the pattern does not include the %d token with the required date/time format, this is a finding. If the pattern does not include the %m (message) token, this is a finding.

Fix Text (F-83487r1171271_fix)

1. Locate the neo-logging.xml file for ColdFusion: <ColdFusion_Installation_Directory>\lib\neo-logging.xml 2. After creating a backup of this file, edit it and locate the <var name='pattern'/> element. 3. Set the value of this element to include all pertinent fields, for example: <string>"%p","%t",%d{"MM/dd/yy","HH:mm:ss"},"%a","%m%z"%n</string>