Forcepoint DLP Protector Inspection API Integration Guide

Home
Inspection APIs
Inspection Request
The general structure of the inspection request is made of 4 parts: "context", "contentDescriptors", "source" and "destinations". All parts are mandatory. Each part is described separately.
Source object
The source part includes information on the source of the data. It is mainly used to describe the user that the data originated from. At least 1 source attribute is mandatory.

Introduction
Inspection APIs
- Inspection Request
  The general structure of the inspection request is made of 4 parts: "context", "contentDescriptors", "source" and "destinations". All parts are mandatory. Each part is described separately.
  - Parameters for the Inspection Request
  - Definition of the Inspection Request
  - Example of the Inspection Request
  - Context Object
    The context object contains details about the inspection request arriving at DPS like the unique id of the request, what agent sent it, on which channel, what cloud operation it represents etc...
  - Content Descriptor Object
  - Source object
    The source part includes information on the source of the data. It is mainly used to describe the user that the data originated from. At least 1 source attribute is mandatory.
    - Example of the Source Object
    - Definition of the Source Object
  - Destination Object
    The destination part is a list of destinations that the data was sent to. For most channels, this is a list containing a single object. Only the email channel supports multiple destinations.
- Inspection Response
  The inspection response will return to the agent as a single json.
Enumerators
CASB Request Sample
Web Multipart Inspection

Source object

The source part includes information on the source of the data. It is mainly used to describe the user that the data originated from. At least 1 source attribute is mandatory.

Example of the Source Object
Definition of the Source Object

Copyright © 2024 Forcepoint LLC