Network and data security
- Last Updated: November 19, 2026
- 3 minute read
- Documentation
Progress Data Platform protects your data in transit and at rest. This topic describes how Data Platform secures connections and stored credentials, the network access that it requires, and the request limits that apply to your account. For information about how users and applications authenticate, see Authentication.
This topic covers the following:
- Secure connections to Data Platform
- Zones and data location
- Connections to your data sources
- Protection of data source credentials
- Request limits
- Network requirements
Secure connections to Data Platform
All connections to Data Platform use HTTPS. This includes the Data Platform interface in your browser, requests to the Data Platform API, connections from the command-line interface, and connections from AI agent clients through the Model Context Protocol (MCP).
Data Platform authenticates every request and rejects requests that do not include a valid identity. See Authentication.
Conversations with agents, such as the Platform Assistant, use secure WebSocket connections. Each connection is authorized with a short-lived token that is valid only for that connection.
Zones and data location
Your account's projects and data are stored in a zone, which is the region where the data is hosted. Requests for a zone's data go to a host name that is specific to that zone. When you switch zones in Data Platform, the service sends your requests to the host for the selected zone.
To work with data in a specific zone through the API, the command-line interface, or an MCP client, use the host for that zone.
For information about switching zones, see Sign in.
Connections to your data sources
When a pipeline runs or when you test a connection, Data Platform connects to the data source from the Data Platform service. Your browser does not connect to the data source. For more information on how Data Platform connects to each type of data source, see Data source options.
Notes:
- MarkLogic data sources do not support SSL connections. Connect only to MarkLogic app servers that are reachable over a trusted network.
- Grant the credentials that you use for a data source only the access that Data Platform needs, such as read-only access to the bucket, container, table, or database to import.
Protection of data source credentials
Data Platform protects the credentials that you enter for data sources, such as passwords, access keys, tokens, and service account keys:
- Encrypted at rest: Credentials are encrypted when you save the data source. Each account has its own encryption key, which is held in a key management service.
- Decrypted only when needed: Credentials are decrypted only immediately before Data Platform connects to the data source.
- Hidden in the interface: After you save a data source, its credentials are hidden. When you edit a data source, leave a credential field unchanged to keep its saved value.
- Shared with control: Data sources belong to the account. Only users who have access to a data source can view or use it. See Share a data source and Manage platform access.
Request limits
To protect the service, Data Platform limits the number of requests that each user and each account can make per minute. When a limit is exceeded, Data Platform rejects the request with HTTP status 429 Too Many Requests and a Retry-After header that specifies the number of seconds to wait before you retry.
When you automate work with the API, handle 429 responses by waiting for the time in the Retry-After header before you retry.
Network requirements
To use Data Platform, make sure that your network allows the following:
- Outbound HTTPS from users and applications to Data Platform: Allow HTTPS connections to the Data Platform host names for your zones, and to the Progress account service used for sign-in.
- WebSocket connections: Allow secure WebSocket connections to Data Platform. If your organization uses a proxy, make sure that it supports WebSocket upgrades. Agent conversations do not work without them.
- Inbound connections from Data Platform to your data sources: For databases, MarkLogic servers, and storage services that are not publicly reachable, allow connections from Data Platform to the host and port of the data source.
For a list of outbound and inbound IP addresses to allow, see Public IP addresses.
Note: If a connection test fails, confirm that the data source accepts connections from Data Platform, and then review the data source settings. See Test a connection for more information.