This topic has information about sending log messages collected by a Sumo Logic Source or Cloud-to-Cloud Connector on to Cloud SIEM to be transformed into Records.
Cloud SIEM must be enabled in your Sumo Logic account in order to send data from Sumo Logic to Cloud SIEM. If it isn’t, contact your Sumo Logic Technical Account Manager or Sales Engineer.
The process consists of configuring a source or collector to forward messages to Cloud SIEM, and ensuring that the forwarded messages are correctly tagged with the information Cloud SIEM needs in order to map messages fields to Record attributes. These are referred to as mapping hints, and include: Format, Vendor, Product, and an Event ID template.
The diagram below is a high level illustration of several alternative processing flows from a data source to a Sumo Logic collector or source, and on to Cloud SIEM.
You can only send log data that resides in the Continuous data tier to Cloud SIEM.
Cloud SIEM ingestion best practices
We recommend the following ingestion processes, starting with the most preferred:
Follow an ingestion guide. The Ingestion Guides section of this help site provides specific collection and ingestion recommendations for many common products and services. An ingestion guide describes the easiest way to get data from a particular product into Cloud SIEM. When you’re ready to start using Cloud SIEM to monitor a new product, if there’s a Cloud SIEM ingestion guide for it, we recommend using it.
Use a Cloud-to-Cloud (C2C) connector. If you don’t see an Ingestion Guide for your data source, check to see if there is a C2C connector. It’s an easy method, because if you configure your C2C source to send logs to Cloud SIEM, it automatically tags messages it sends to Cloud SIEM with fields that contain the mapping hints that Cloud SIEM requires.
Most C2C connectors have a Forward to SIEM option in the configuration UI. If a C2C connector lacks that option, you can achieve the same effect by assigning a field named
_siemforward, set to true, to the connector.
For information about what C2C sources are available, see Cloud-to-Cloud Integration Framework.
Use a Sumo Logic Source and parser. If there isn’t a C2C connector for your data source, your next best option is to use a Sumo Logic Source (running on an Installed Collector or a Hosted Collector, depending on the data source)—and a Sumo Logic parser, if we have one for the data source.
To check if there’s a parser for your data source, go to the Manage Data > Logs > Parsers page in the Sumo Logic UI. If there is a parser for your data source, but you find it doesn’t completely meet your needs–for instance if the parser doesn’t support the particular log format you use–consider customizing the parser with a local configuration. If that’s not practical, you can submit a request for a new parser by filing a ticket at https://support.sumologic.com.
When you forward logs to Cloud SIEM for parser processing, there are two bits of important configuration:
Configure the source to forward logs. To configure an HTTP source to send log messages to Cloud SIEM, click the SIEM Processing checkbox. You can configure other source types to send data to Cloud SIEM by assigning a field named
_siemforward, set to true, to the source. For example:
A field can also be assigned at the collector level, in which case sources on the collector inherit the field setting, unless the same field is defined with a different value at the source level.
Configure the source with the path to the appropriate parser, by assigning a field named
_parser, whose value is the path to parser, for example:
_parser=/Parsers/System/AWS/AWS Network Firewall
You can get the path to a parser on the Manage Data > Logs > Parsers page in Sumo Logic. Click the three-dot more options menu in the row for a parser, and select Copy Path.
Use a Sumo Logic Source and Cloud SIEM Ingest mapping. This is the least recommended method, as you have to manually configure the mapping hints in an ingestion mapping. For more information, see Configure a Sumo Logic Ingest Mapping.