Security - RDS (Remote Development Services)
Configure remote development access and security settings
Overview
Remote Development Services (RDS) is a ColdFusion feature that gives development tools remote HTTP-based access to files and databases on your ColdFusion server. Adobe lists Dreamweaver, HomeSite+, ColdFusion Extensions for Eclipse, and the ColdFusion Report Builder as RDS clients (source: Use the ColdFusion administrator). Adobe recommends that you disable RDS for production servers. While useful for development, RDS provides significant server access and must be carefully controlled in production environments.
RDS Configuration Settings
Control whether RDS is enabled and configure authentication requirements.
Enable RDS Service
Staging: Disabled or restricted by IP
Development: Enabled with strong password
RDS Password
- Use password manager to generate and store complex password
- Never use the same password as the ColdFusion Administrator
- Rotate password regularly (every 90 days minimum)
- Never share RDS passwords via email or chat
- Change immediately if compromise suspected
RDS Authentication
Separate user name and password: Each developer signs in with an individual account created in the User Manager and granted RDS access
What RDS Provides Access To
Understanding the scope of access granted when RDS is enabled.
File System Access
- Capabilities
- Browse, read, edit, create, delete files
- Scope
- Full server file system (subject to OS permissions)
- Risk Level
- Critical
Allows complete file system manipulation including CFM templates, configuration files, and data.
Database Access
- Capabilities
- Query all configured datasources
- Scope
- Full database read/write access
- Risk Level
- Critical
Direct SQL execution against all configured databases with datasource privileges.
Debugging Access
- Capabilities
- Remote debugging sessions
- Scope
- Inspect variables, step through code
- Risk Level
- High
View application variables, session data, and execution flow in real-time. Adobe lists RDS as a prerequisite for the ColdFusion Builder extension's step debugger (source: Adobe: Debug applications).
Configuring RDS in Development Tools
IDE Connections
In any RDS client, enter the server host name, the port of the web server that serves ColdFusion, and the RDS credentials. Use HTTPS for connections over untrusted networks. Check your tool's own documentation for the exact menu path.
Security Best Practices
Production Environment
- Disable RDS completely - No exceptions for production
- Verify RDS is disabled in administrator before deployment
- Block
/CFIDE/main/ide.cfm(the RDS endpoint) at the web server; RDS has no dedicated port - Remove or restrict /CFIDE directory web access
- Include RDS disabled check in deployment checklist
- Monitor logs for any RDS connection attempts
Development Environment
- Enable RDS only on local development machines
- Use strong, unique passwords (16+ characters)
- Use separate user name and password RDS authentication, and never reuse the Administrator password
- Never expose the RDS endpoint to the internet
- Use VPN for remote RDS access if absolutely required
- Restrict access by IP address when possible
- Disable RDS when not actively developing
- Use HTTPS for all RDS connections
- Rotate RDS passwords quarterly
Alternatives to RDS
More secure with granular access control
Direct database connection with better security
CommandBox server for local development
RDS Network Exposure
Where RDS Is Reachable
/CFIDE/main/ide.cfm (see Adobe's JEE configuration guide) served on whatever port serves ColdFusion. Firewalling port 8500 only restricts the built-in web server (which also serves the Administrator and applications); it does not disable RDS behind IIS or Apache. Disable RDS in Security > RDS and block /CFIDE/main/ide.cfm at the web server.# Restrict the built-in web server port (which also carries RDS)
# This does not affect RDS served through IIS or Apache
# Allow only from specific IP (replace with your IP)
# Block built-in web server HTTP port from all
iptables -A INPUT -p tcp --dport 8500 -j DROP
# Allow from trusted IP only
iptables -I INPUT -p tcp -s 192.168.1.100 --dport 8500 -j ACCEPT
# Allow from local network (adjust subnet as needed)
iptables -I INPUT -p tcp -s 192.168.1.0/24 --dport 8500 -j ACCEPT
# Save rules
service iptables save# PowerShell commands for Windows Firewall
# Block built-in web server HTTP port (also carries RDS)
New-NetFirewallRule -DisplayName "Block RDS HTTP" `
-Direction Inbound -LocalPort 8500 -Protocol TCP -Action Block
# Allow RDS from specific IP
New-NetFirewallRule -DisplayName "Allow RDS from Dev IP" `
-Direction Inbound -LocalPort 8500 -Protocol TCP `
-Action Allow -RemoteAddress 192.168.1.100Common Issues & Solutions
Cannot Connect to RDS
- Verify RDS is enabled in ColdFusion Administrator
- Check ColdFusion service is running
- Confirm correct port number (8500 default)
- Verify the firewall allows the ColdFusion web port from your IP
- Test connectivity:
telnet server.com 8500 - Check RDS password is correct
- Review ColdFusion logs for authentication failures
RDS Authentication Failed
- Verify RDS password in CF Administrator (Security → RDS)
- Check whether RDS authentication uses a single password or separate user names, and use the matching credentials
- Check for special characters that may need escaping
- Reset RDS password in administrator and retry
- Clear IDE's saved RDS credentials and re-enter
RDS Security Audit Failed
- Disable RDS immediately on production servers
- Verify RDS disabled: check Security → RDS in administrator
- Block
/CFIDE/main/ide.cfmat the web server and restrict the built-in web server port (8500 by default) - Restrict /CFIDE directory access in web server config
- Review access logs for unauthorized RDS usage
- Document remediation for audit report
- Add RDS check to deployment verification checklist
Verifying RDS Status
Confirm on every production server that Enable RDS Service is unchecked under Security > RDS in the ColdFusion Administrator. As a second check, request /CFIDE/main/ide.cfm (the RDS endpoint) from outside your network and confirm the web server blocks it.