forcepoint/dlp
| Vendor | Forcepoint LLC |
| Author | CrowdStrike |
| Version | 1.1.0 |
| Minimum LogScale Version | 1.82.0 |
Correlate Forcepoint DLP data with endpoint or SSO data to identify insider threats or identity theft more quickly. LogScale offers improved storage of sensitive data access logs for compliance reasons (the native default is 60 days).
The parser included in this package supports two types of logs in CEF format, single events and reports, which are a set of events that are grouped together because they may indicate a specific breach, e.g. downloading files from a server.
The parser normalizes data to a common schema based on CrowdStrike Parsing Standard (CPS) 1.0. This schema allows you to search the data without knowing the data specifically, and just knowing the common schema instead. It also allows you to combine the data more easily with other data sources which conform to the same schema.
Breaking Changes
This update includes parser changes, which means that data ingested after upgrade will not be backwards compatible with logs ingested with the previous version.
Updating to version 1.0.0 or newer will therefore result in issues with existing queries in for example dashboards or alerts created prior to this version.
See CrowdStrike Parsing Standard (CPS) 1.0 for more details on the new parser schema.
Follow the CPS Migration to update your queries to use the fields and tags that are available in data parsed with version 1.0.0.
Installing the Package in LogScale
Find the repository where you want to send the events, or Creating a Repository or View.
Navigate to your repository in the LogScale interface, click Settings and then on the left.
Click and install the LogScale package for (i.e. forcepoint/dlp).
When the package has finished installing, click on the left still under the .
In the right panel, click to create a new token. Give the token an appropriate name (e.g. the name of the Event Hub it will collect logs from), and assign the parser forcepoint-dlp.
Before leaving this page, view the ingest token and copy it to your clipboard — to save it temporarily elsewhere.
Now that you have a repository set up in LogScale along with an ingest token you're ready to send logs to LogScale.
Configurations and Sending the Logs to LogScale
Follow the instructions provide here here to save the logs as syslogs which can then be shipped using the LogScale Collector, see Sources & Examples.
Verify Data is Arriving in LogScale
Once you have completed the above steps the data should be arriving in your LogScale repository.
You can verify this by doing a simple search for
#Vendor = "forcepoint" |
#event.module="dlp" to see the events.
Package Contents Explained
This package parses incoming data, and normalizing the data as part of that parsing. The parser normalizes the data to CrowdStrike Parsing Standard (CPS) 1.0 schema based on OpenTelemetry standards, while still preserving the original data.
If you want to search using the original field names and values, you can access those in the fields whose names are prefixed with the word Vendor. Fields which are not prefixed with Vendor are standard fields which are either based on the schema (e.g. source.ip) or on LogScale conventions (e.g. @rawstring).
The fields which the parser currently maps the data to, are chosen based on what seems the most relevant, and will potentially be expanded in the future. But the parser won't necessarily normalize every field that has potential to be normalized.