Adding Proxy device generates a SCP path that is too long

Products

• CASB Gateway Advanced
• CASB Advanced Threat Protection
• CASB Audit
• CASB Gateway
• CASB Security Advanced
• CASB Security Advanced IAAS
• CASB Security Premium
• CASB Security Premium IAAS
• CASB Security Standard
• CASB Securlet IAAS
• CASB Securlet SAAS
• CASB Securlet SAAS With DLP-CDS

Issue/Introduction

When creating an SCP data source in CASB Audit the provided data path is to long to fit in the SWG/Secure Web Gateway/ProxySG field.

Cause

There is a limitation on some of the ProxySG versions where the UI text field of the "Upload Path" parameter has a 64 character limit. the Path has to be entered via the command line.

Resolution

The Path has to be entered via the command line.
Here are the proxy commands to be used after connecting via SSH to the proxy:

#(config)
#(config)access-log
#(config access-log)edit log <LogName>
#(config log main)scp-client primary ?
 encrypted-password           Encrypted password for SCP primary host
 host                         Primary SCP host name
 password                     Password for SCP primary host
 path                         Path for SCP primary host
 username                     Username for SCP primary host
#(config log main)edit log <log name> host upload.elastica.net 
#(config log main)edit log <log name> username <username>
#(config log main)edit log <log name> path <path>
#(config log main)edit log <log name> password <password>

Additional Information

Directions for configuring a SCP data source can be found at the link below.

Configure an SCP connection or SpanVA datasource in CloudSOC