Next Generation API Data Protection: Performance & Response Time

Next Generation API Data Protection operates out-of-band, connecting directly to cloud application APIs to scan files and enforce policies. Processing times depend on several variables, the most significant being API rate limiting imposed by the cloud service provider (such as Microsoft 365, Google Workspace, or Salesforce).

Standard Performance Expectations

Average response time: Under normal operating conditions, Next Generation API Data Protection detects a file, scans it, and applies the appropriate policy action within 2 to 3 minutes.
Real-time vs. Out-of-band: Unlike inline proxies (which process data in real-time), Next Generation API Data Protection operates in out-of-band because it relies on cloud provider event notifications and polling intervals.

Factors Causing Processing Delays

If you experience a delay in policy enforcement, it is usually caused by one of the following:

Provider throttling: If your cloud tenant experiences a sudden traffic spike or a high volume of concurrent file activity, the cloud provider may temporarily throttle API requests from Next Generation API Data Protection.
Back-off and retry mechanisms: When throttling occurs, Next Generation API Data Protection backs off and retries the request after a short cooldown period.
High-volume events: Bulk data migrations or large-scale file-sharing events can temporarily increase processing queues, causing an expected delay in policy enforcement.

Next Generation API Data Protection performance is directly tied to the health and responsiveness of the target cloud application’s API infrastructure.

Standard Performance Expectations

Average response time: Under normal operating conditions, Next Generation API Data Protection detects a file, scans it, and applies the appropriate policy action within 2 to 3 minutes.
Real-time vs. Out-of-band: Unlike inline proxies (which process data in real-time), Next Generation API Data Protection operates in out-of-band because it relies on cloud provider event notifications and polling intervals.

Factors Causing Processing Delays

If you experience a delay in policy enforcement, it is usually caused by one of the following:

Provider throttling: If your cloud tenant experiences a sudden traffic spike or a high volume of concurrent file activity, the cloud provider may temporarily throttle API requests from Next Generation API Data Protection.
Back-off and retry mechanisms: When throttling occurs, Next Generation API Data Protection backs off and retries the request after a short cooldown period.
High-volume events: Bulk data migrations or large-scale file-sharing events can temporarily increase processing queues, causing an expected delay in policy enforcement.

Next Generation API Data Protection performance is directly tied to the health and responsiveness of the target cloud application’s API infrastructure.