This site uses cookies essential to its operation, for analytics, and for personalized content and ads. By continuing to browse this site, you acknowledge the use of cookies. Privacy statement
To meet your organization's legal compliance requirements and operational needs, you can forward
firewall logs stored in Strata Logging Service to external destinations. For
example, you can forward logs using syslog to a SIEM for long term storage, SOC, or
internal audit obligations, and forward email notifications for critical events to an
email address. You can forward logs to the following SIEMs:
Exabeam
Google Chronicle
Microsoft Sentinel
Splunk HTTP Event Collector (HEC)
When forwarding logs, Strata Logging Service
ensures accuracy by using unique identifiers and preserving long values, which are
important for identifying log records.
If you use a third-party log streaming
solution as an intermediary to forward logs from Strata Logging Service, the
volume of received logs can vary depending on the log processing mechanism used by the
third-party solution, including how the solution handles long identifiers. Strata Logging Service is tested and calibrated against the specific endpoints
listed above. Therefore, we can't guarantee support for logs processed through
unsupported intermediate streaming solutions. We recommend directly connecting to a
supported endpoint or verifying compatibility when using an intermediary
aggregator.
Strata Logging Service can forward logs in multiple formats: CSV, LEEF, CEF, JSON, or PARQUET.
For each instance of Strata Logging Service, you can forward logs to up to 200
syslog destinations. Use the following table to find more information about supported
log formats.
The Strata Logging Service ensures secure communication with log receivers through
the following mechanisms:
TLS 1.2 Encryption: All communications are encrypted using TLS 1.2, ensuring
data security during transmission.
Java 8 default cipher suites: The
service uses the default Java 8 cipher suites, including support for GCM
ciphers.
Certificate Validation: To establish a secure connection, the Strata Logging Service requires that the log receiver provides a valid
certificate.
Trusted Certification: The receiver's certificate must be signed by a
trusted root CA or a private CA.
Chain of Trust: The receiver must present all certificates in the chain
of trust to successfully complete the TLS handshake and establish the
connection.
