[Deprecated] Pulse Connect Secure connector for Microsoft Sentinel
Important
Log collection from many appliances and devices is now supported by the Common Event Format (CEF) via AMA, Syslog via AMA, or Custom Logs via AMA data connector in Microsoft Sentinel. For more information, see Find your Microsoft Sentinel data connector.
The Pulse Connect Secure connector allows you to easily connect your Pulse Connect Secure logs with Microsoft Sentinel, to view dashboards, create custom alerts, and improve investigations. Integrating Pulse Connect Secure with Microsoft Sentinel provides more insight into your organization's network and improves your security operation capabilities.
This is autogenerated content. For changes, contact the solution provider.
Connector attributes
| Connector attribute | Description |
|---|---|
| Log Analytics table(s) | Syslog (PulseConnectSecure) |
| Data collection rules support | Workspace transform DCR |
| Supported by | Microsoft Corporation |
Query samples
Top 10 Failed Logins by User
PulseConnectSecure
| where vpn_message startswith 'Login failed'
| summarize count() by vpn_user
| top 10 by count_
Top 10 Failed Logins by IP Address
PulseConnectSecure
| where vpn_message startswith 'Login failed'
| summarize count() by client_ip
| top 10 by count_
Prerequisites
To integrate with [Deprecated] Pulse Connect Secure make sure you have:
- Pulse Connect Secure: must be configured to export logs via Syslog
Vendor installation instructions
Note
This data connector depends on a parser based on a Kusto Function to work as expected which is deployed as part of the solution. To view the function code in Log Analytics, open Log Analytics/Microsoft Sentinel Logs blade, click Functions and search for the alias Pulse Connect Secure and load the function code or click here, on the second line of the query, enter the hostname(s) of your Pulse Connect Secure device(s) and any other unique identifiers for the logstream. The function usually takes 10-15 minutes to activate after solution installation/update.
- Install and onboard the agent for Linux
Typically, you should install the agent on a different computer from the one on which the logs are generated.
Syslog logs are collected only from Linux agents.
- Configure the logs to be collected
Configure the facilities you want to collect and their severities.
Under workspace advanced settings Configuration, select Data and then Syslog.
Select Apply below configuration to my machines and select the facilities and severities.
Click Save.
Configure and connect the Pulse Connect Secure
Follow the instructions to enable syslog streaming of Pulse Connect Secure logs. Use the IP address or hostname for the Linux device with the Linux agent installed as the Destination IP address.
Next steps
For more information, go to the related solution in the Azure Marketplace.