STIGViewer Support

The ColdFusion administrator must be using HTTPS to maintain the confidentiality and integrity of information during reception.

Overview

Finding IDVersionRule IDIA ControlsSeverity
V-279098APAS-CF-000910SV-279098r1172830_ruleCCI-002422medium
Description
Information can be either unintentionally or maliciously disclosed or modified during reception, including, for example, during aggregation, at protocol transformation points and during packing/unpacking. These unauthorized disclosures or modifications compromise the confidentiality or integrity of the information. ColdFusion must use approved encryption when receiving transmitted data by configuring the Tomcat Connector to use HTTPS.
STIGDate
Adobe ColdFusion Security Technical Implementation Guide2025-12-19

Related Frameworks

1 mapping across 4 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.

CRY-01Use of Cryptographic Controls
0.50
CRY-01.3Pre/Post Transmission Handling
0.50
DCH-10Media Use
0.50
NIST 800-530 mappings

No source states a mapping between these directly.

Also reachable in 2 hops (29) 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-17(2)Protection of Confidentiality and Integrity Using Encryption
1.00
AC-3Access Enforcement
1.00
AU-10(1)Association of Identities
1.00
AU-10(2)Validate Binding of Information Producer Identity
1.00
CM-6Configuration Settings
1.00
CM-7Least Functionality
1.00
IA-2(8)Access to Accounts — Replay Resistant
1.00
IA-2(9)Network Access to Non-privileged Accounts — Replay Resistant
1.00
IA-5(1)Password-based Authentication
1.00

+19 more (top 10 by confidence shown)

CCI1 mapping
NIST CSF 2.00 mappings

No source states a mapping between these directly.

Also reachable in 4 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.

Details

Check Text (C-279098r1172830_chk)

Verify HTTPS. 1. Locate the server.xml file for each ColdFusion instance located at: <ColdFusion_Installation_Directory>\cfusion\runtime\conf\ 2. Open the server.xml file in a text editor. 3. Locate all <Connector> elements configured with an HTTP protocol (e.g., protocol="org.apache.coyote.http11.Http11Protocol" or Http11NioProtocol). If any HTTP connector exists without SSLEnabled="true" and is not commented out (<!-- ... -->), this is a finding. If there is no active (uncommented) <Connector> configured with SSLEnabled="true", scheme="https", and secure="true", this is a finding.

Fix Text (F-83551r1172829_fix)

Configure ColdFusion to use HTTPS and disable unsecured HTTP access. 1. Locate the server.xml file for each ColdFusion instance located at: <ColdFusion_Installation_Directory>\cfusion\runtime\conf\ 2. Open the server.xml file in a text editor. 3. Locate all <Connector> elements using the HTTP protocol (e.g., protocol="org.apache.coyote.http11.Http11Protocol" or Http11NioProtocol) without the attribute SSLEnabled="true" 4. Either delete these unsecured <Connector> tags or comment them out using XML syntax: <!-- <Connector port="8500" protocol="org.apache.coyote.http11.Http11Protocol" ... /> --> 5. Locate a <Connector> tag that includes SSLEnabled="true" and is configured to support HTTPS communication. 6. If this tag is present but commented out, uncomment it by removing the <!-- and --> markers. 7. If a secure HTTPS connector does not exist, create a new <Connector> tag within the <Service> element of the server.xml file. It should include the following attributes: <Connector port="8443" protocol="org.apache.coyote.http11.Http11NioProtocol" maxThreads="150" SSLEnabled="true" scheme="https" secure="true" clientAuth="false" keystoreFile="/path/to/keystore" keystorePass="changeit"/> 8. Replace /path/to/keystore with the actual path to the keystore file. 9. Replace "changeit" with the actual password for the keystore. 10. Save the file and restart ColdFusion for the changes to take effect.