↳ GitHub sourceConnector

[Deprecated] Forcepoint CASB via AMA

Description

The Forcepoint CASB (Cloud Access Security Broker) Connector allows you to automatically export CASB logs and events into Microsoft Sentinel in real-time. This enriches visibility into user activities across locations and cloud applications, enables further correlation with data from Azure workloads and other feeds, and improves monitoring capability with Workbooks inside Microsoft Sentinel.
Declared status
1
Declared author / publisher
Forcepoint CASB

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.

Install and configure the Linux agent to collect your Common Event Format (CEF) Syslog messages and forward them to Microsoft Sentinel. > Notice that the data from all regions will be stored in the selected workspace
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. Forward Common Event Format (CEF) logs to Syslog agent
Set your security solution to send Syslog messages in CEF format to the proxy machine. Make sure you to send the logs to port 514 TCP on the machine's IP address.
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)
3. Forcepoint integration installation guide
To complete the installation of this Forcepoint product integration, follow the guide linked below. [Installation Guide >](https://frcpnt.com/casb-sentinel)

Source provenance

GitHub

Displayed values come from files in Azure/Azure-Sentinel. They describe the published template, not your workspace configuration.

Source identifier
ForcepointCasbAma
Additional source files 1Solutions/Forcepoint CASB/Data Connectors/template_Forcepoint CASBAMA.jsonsource ↗
GSTEP / CATALOG TRACKING

Added to catalog : 16 Sept 2026 · 05:49 UTC
Last change observed : 16 Sept 2026 · 05:49 UTC

GSTEP sync dates, separate from the source content’s publication dates.