The output of the Guardium universal connector is forwarded to the Guardium sniffer on the collector, for policy and auditing enforcements. The Guardium universal connector identifies and parses the received events, and converts them to a standard Guardium format. The open architecture enables reuse of prebuilt filters and parsers, and creation of shared library for the Guardium community. For the data sources with pre-defined plug-ins, you configure Guardium to accept audit logs from the data source.įor data sources that do not have pre-defined plug-ins, you can customize the filtering and parsing components of audit trails and log formats. It supports pull and push modes, multi-protocols, on-premises, and cloud platforms. The Guardium universal connector supports many platforms and connectivity options. Guardium universal connector architectureĭata flow from input plugin to guardium sniffer The incoming events received by the universal connector can be configured to arrive either encrypted or as plain text.įigure 1. That includes: information and administrative system logs (e.g.: login logs, various data lake platform native plug-in related data), DDLs and DMLs, errors of varying subtypes, etc. The captured events embed messages of any type that is supported by the configured data source. You can easily develop plug-ins for other data sources and install them in Guardium. It includes support for various plug-in packages, requiring minimal configuration. The Guardium universal connector enables Guardium Data Protection and Guardium Insights to get data from potentially any data source's native activity logs without using S-TAPs.
0 Comments
Leave a Reply. |