Inline deployment methods intercept and inspect traffic in real-time as it flows between a user and a cloud application. A forward proxy steers all user-initiated traffic (e.g., from a managed device) through the Netskope security cloud for inspection before it reaches its destination. A reverse proxy is placed in front of a specific cloud application, intercepting all traffic destined for that service, which is ideal for protecting applications from unmanaged devices. Both methods sit directly in the data path, providing the required inline visibility and control.

B. Use an API connector: This is an out-of-band method that connects to the cloud application's API to scan data at rest and analyze activity logs after events have occurred.

C. Use a log parser: This is an out-of-band method that ingests and analyzes logs from existing network devices (like firewalls) to provide visibility into past cloud activity.

1. Netskope Official Documentation: Netskope All-Mode Architecture Whitepaper. Section: "A Full Spectrum of Deployment Options

" Page 3. This document explicitly categorizes Forward Proxy and Reverse Proxy as "Inline deployment options" that "sit in the flow of traffic to provide real-time

granular policy controls." It lists API Introspection and Log Analysis as out-of-band options.

2. Netskope Official Documentation: Netskope for Sanctioned Apps Deployment Guide. Section: "Deployment Options

" Page 5. This guide details the primary deployment architectures

stating

"For real-time visibility and control of traffic between users and the cloud app

you can deploy Netskope as a forward or reverse proxy."

3. University Courseware: Carnegie Mellon University

INI Information Networking Institute

14-814: Mobile and IoT Security

Lecture 15: Cloud Security. Slide 28

"CASB Deployment Modes." The lecture material describes proxy-based modes (forward and reverse) as inline solutions that intercept traffic in real-time

contrasting them with the API-based mode

which operates out-of-band.