Security - Secure Profile

One-step security hardening for ColdFusion servers

Overview

ColdFusion Secure Profile is a single on/off option that changes a fixed set of server settings to more secure values. The simplest way to get it is to choose the Production Profile (Secure) server profile during installation. If a server was installed with another profile, you can still apply the Secure Profile settings later: the ColdFusion 2025 Lockdown Guide notes that since ColdFusion 11 the Secure Profile settings can be toggled from the ColdFusion Administrator under Security > Secure Profile. What you cannot change after installation is the server profile type itself (Development, Production, or Production Secure), per Adobe's server profiles documentation.

Secure Profile hardens session cookies, Administrator and RDS authentication, datasource SQL permissions, error handling, and a few network services. Disabling individual tags such as<cfexecute> and enabling Sandbox Security are not in Adobe's list of affected settings.

Important: Secure Profile changes can break existing applications (for example, code that uses internal ColdFusion Java classes or runs DDL through a datasource). Always test in a non-production environment first.

Installer Server Profiles

The installer offers three server profiles: Development, Production, and Production Profile (Secure). Adobe notes that once you install the server with a profile, you cannot change the profile later. The Secure Profile settings themselves can still be applied afterward from Security > Secure Profile in the Administrator.

Development

Use Case
Local development and testing

Supports all types of debugging, remote inspection, and directory listing. Never use on publicly accessible servers.

Production

Use Case
Production servers that you will harden manually

Only basic security settings are pre-configured. Adobe lists Secure Profile support only for the Production Profile (Secure).

Production Profile (Secure)

Use Case
Production servers that should start hardened

Enables Secure Profile and lets you enter the IP addresses allowed to reach the Administrator during install.

Settings Changed by Secure Profile

Adobe documents the following changes when Secure Profile is enabled (source: Administer ColdFusion security).

Documented Changes

Java ComponentsDisable access to internal ColdFusion Java components: enabled
CookiesCookie Timeout set to 1440 minutes; updating of ColdFusion internal cookies with CFML tags and functions disabled
Error PagesCustom Missing Template Handler, Site-wide Error Handler, and Request Queue Timeout pages
ServicesWebSocket Server, Flash Policy Server, and CFSTAT disabled; RDS disabled
Allowed SQLCREATE, DROP, ALTER, GRANT, REVOKE, and stored procedures disabled for datasources
AuthenticationSeparate user name and password for Administrator and RDS; concurrent Administrator login sessions disabled
Directory BrowsingDisabled on standalone installations that use the built-in web server
Already secure by default: UUID for cftoken, Global Script Protection, a 20 MB maximum POST size, and Robust Exception Information disabled are listed as Secure Profile values, but they match the normal defaults.
Deployment Checklist for Secure Profile
Secure Profile Deployment Checklist

PRE-DEPLOYMENT:
□ Backup current configuration (neo-*.xml files)
□ Document current security settings
□ Enable Secure Profile in a staging/test environment
□ Run full application test suite
□ Check for code using internal ColdFusion Java classes
□ Check for DDL or stored procedure calls through datasources
□ Confirm Administrator users have separate user names and passwords
□ Review application logs for errors

DEPLOYMENT:
□ Schedule during maintenance window
□ Notify stakeholders of deployment
□ Install with the Production Profile (Secure) server profile
□ Restart ColdFusion service (if required)
□ Verify the changed settings in the Administrator
□ Test critical application functions immediately

POST-DEPLOYMENT:
□ Monitor application logs for errors
□ Document the date Secure Profile was enabled
□ Update security documentation
□ Schedule regular security reviews

ROLLBACK PLAN:
□ Have configuration backup ready
□ Document rollback procedure
□ Test rollback in staging first

What Secure Profile Does Not Do

Additional Hardening Still Required

Not in Adobe's list of affected settings:
  • Restricting tags such as <cfexecute>, <cfregistry>, and <cfobject>
  • Enabling Sandbox Security
Restricting TagsSandbox Security can disable tags and functions per directory, but Adobe marks it deprecated in ColdFusion 2025. Review code that uses these tags.
Further StepsFollow the Adobe ColdFusion Lockdown Guide for web server, file system, and service account hardening

Common Issues & Solutions

Application Breaks After Enabling Secure Profile

Symptom: Features stop working after Secure Profile is enabled
Solutions:
  • Review ColdFusion exception logs for the failing operation
  • Code that creates internal ColdFusion Java objects (for example coldfusion.server.ServiceFactory) fails once internal component access is disabled. The shipped ColdFusion 2025 Update 14 configuration in Adobe's official Docker image stores this setting as disableServiceFactory (neo-runtime.xml; default false, true under Secure Profile per neo-secureprofile.xml).
  • Queries that run DDL or stored procedures fail when the datasource's Allowed SQL blocks them; re-enable only on the datasources that need it
  • WebSocket features stop when the WebSocket Server is disabled
  • Test in a staging environment before production

Administrator Login Changes

Symptom: Administrator or RDS logins behave differently after Secure Profile is enabled
Solutions:
  • Secure Profile switches to separate user name and password authentication
  • Only one Administrator login session is allowed at a time
  • Create named Administrator users under Security > User Manager

Compliance and Security Frameworks

Security Standards Alignment: Secure Profile helps meet requirements for:
  • PCI-DSS: Requirement 2.2 - Develop configuration standards for all system components
  • OWASP Top 10: Mitigates several categories including A05:2021 Security Misconfiguration
  • NIST Cybersecurity Framework: PR.AC-3 Remote access is managed
  • ISO 27001: A.12.6.1 Management of technical vulnerabilities
  • SOC 2: CC6.6 Logical and physical access controls
  • CIS Benchmarks: Application server hardening guidelines
Audit Evidence: Document when Secure Profile was enabled and any settings you changed back afterward. This documentation is often required during security audits and compliance assessments.

Related Resources

Security - Secure Profile | ColdFusion Administrator | CFGuide