What Changed
Updated default API hostname configuration across Rubrik Security Cloud automation components for proper customer deployments.
Configuration Updates
- API hostname change: Updated from rubrik-tme-rdp.my.rubrik.com to rubrik-tme-customer.my.rubrik.com across all components
- Affected playbooks:
- RubrikAdvanceThreatHunt
- RubrikAnomalyIncidentResponse
- RubrikTurboThreatHunt
- RubrikUpdateAnomalyStatusViaIncident
- Custom connector: Updated RubrikCustomConnector default hostname parameter
Security Impact (Visibility & Fidelity)
Configuration alignment for proper Rubrik Security Cloud integration:
- Ensures playbooks connect to correct Rubrik API endpoints during deployment
- Prevents deployment failures due to incorrect hostname defaults
- Maintains automated incident response and threat hunting capabilities with proper API connectivity
Affected Files
Solutions/RubrikSecurityCloud/Playbooks/RubrikAdvanceThreatHunt/azuredeploy.json Solutions/RubrikSecurityCloud/Playbooks/RubrikAnomalyIncidentResponse/azuredeploy.json Solutions/RubrikSecurityCloud/Playbooks/RubrikTurboThreatHunt/azuredeploy.json Solutions/RubrikSecurityCloud/Playbooks/RubrikUpdateAnomalyStatusViaIncident/azuredeploy.json Solutions/RubrikSecurityCloud/Playbooks/RubrikCustomConnector/Rubrik_custom_conn.json (packaging artefacts: mainTemplate.json, 3.5.1.zip)