Description
Forcepoint Cloud Security Gateway is a converged cloud security service that provides visibility, control, and threat protection for users and data, wherever they are. For more information visit: https://www.forcepoint.com/product/cloud-security-gateway
- Declared status
- 1
- Declared author / publisher
- Forcepoint
Declared sources
Metadata from the source file. No dependencies inferred from KQL.
Data types
Declared permissions
read and write permissions are required.
Workspace
Workspace
read permissions to shared keys for the workspace are required. [See the documentation to learn more about workspace keys](https://docs.microsoft.com/azure/azure-monitor/platform/agent-windows#obtain-workspace-id-and-key).
Keys
Workspace
To collect data from non-Azure VMs, they must have Azure Arc installed and enabled. [Learn more](https://docs.microsoft.com/azure/azure-monitor/agents/azure-monitor-agent-install?tabs=ARMAgentPowerShell,PowerShellWindows,PowerShellWindowsArc,CLIWindows,CLIWindowsArc)
Common Event Format (CEF) via AMA and Syslog via AMA data connectors must be installed [Learn more](https://learn.microsoft.com/azure/sentinel/connect-cef-ama#open-the-connector-page-and-create-the-dcr)
Connector instructions
Content published in the repository. Refer to the original file for all parameters.
1. Kindly follow the steps to configure the data connector
Step A. Configure the Common Event Format (CEF) via AMA data connector
_Note:- CEF logs are collected only from Linux Agents_
1. Navigate to Microsoft Sentinel workspace ---> configuration ---> Data connector blade .
2. Search for 'Common Event Format (CEF) via AMA' data connector and open it.
3. Check If there is no existing DCR configured to collect required facility of logs, Create a new DCR (Data Collection Rule)
_Note:- It is recommended to install minimum 1.27 version of AMA agent [Learn more](https://learn.microsoft.com/azure/azure-monitor/agents/azure-monitor-agent-manage?tabs=azure-portal ) and ensure there is no duplicate DCR as it can cause log duplicacy_
4. Run the command provided in the CEF via AMA data connector page to configure the CEF collector on the machine.
Step B. Implementation options
The integration is made available with two implementations options.
1. Docker Implementation
Leverages docker images where the integration component is already installed with all necessary dependencies.
Follow the instructions provided in the Integration Guide linked below.
[Integration Guide >](https://frcpnt.com/csg-sentinel)
2. Traditional Implementation
Requires the manual deployment of the integration component inside a clean Linux machine.
Follow the instructions provided in the Integration Guide linked below.
[Integration Guide >](https://frcpnt.com/csg-sentinel)
Step C. Validate connection
Follow the instructions to validate your connectivity:
Open Log Analytics to check if the logs are received using the CommonSecurityLog schema.
It may take about 20 minutes until the connection streams data to your workspace.
If the logs are not received, run the following connectivity validation script:
1. Make sure that you have Python on your machine using the following command: python -version
2. You must have elevated permissions (sudo) on your machine
Run the following command to validate your connectivity:
2. Secure your machine
Make sure to configure the machine's security according to your organization's security policy
[Learn more >](https://aka.ms/SecureCEF).
Source provenance
GitHubDisplayed values come from files in Azure/Azure-Sentinel. They describe the published template, not your workspace configuration.
- Commit
629d1d3↗- Source identifier
ForcepointCSGAma
Additional source files 1
Solutions/Forcepoint CSG/Data Connectors/template_ForcepointCloudSecurityGatewayAMA.jsonsource ↗GSTEP / CATALOG TRACKING
Added to catalog : 16 Sept 2026 · 05:49 UTC
Last change observed : 16 Sept 2026 · 05:49 UTC