Linux-UNIX: S-TAP configuration per database type

This section provides detailed instructions or example for configuring monitoring on various databases.

Linux-UNIX: Configuring Apache Cassandra and S-TAP for auditing interception
Configure Apache Cassandra and S-TAP to monitor encrypted traffic on Apache Cassandra. Monitoring includes authorization messages for login, normal SQLs, prepared statements, batch statements, bind variables, and bound values. This configuration does not require an inspection engine or K-TAP.
Linux-UNIX: Application server S-TAP configuration
Application Server S-TAP is a very easy way to identify application users for Java Application Server applications when built-in functionality is not available. It doesn't require any changes to existing applications which makes it a very attractive solution. Nevertheless some considerations need to be taken into account.
Linux-UNIX: CockroachDB inspection engine configuration
View a typical Cockroach database inspection engine cofiguration. Guardium supports unencrypted connections with a cockroach database. This configuration required K-TAP.
Linux-UNIX: Couchbase auditing configuration
Use a double proxy to capture couchbase traffic with real client IPs.
Linux-UNIX: Using SAP-HANA with encrypted connections
When SAP-HANA is configured with SSL/TLS encryption, S-TAP requires configuring two proxies using NGINX.
Linux-UNIX: Datastax Cassandra auditing configuration
Configure logging to a file appender for monitoring encrypted traffic on Datastax Cassandra. This supports the audits provided by the built-in audit logging, for example: queries, data manipulation language, data definition language, data control syntax, authentication. This configuration does not require an inspection engine or K-TAP.
Linux-UNIX: Db2 IE configuration
View a typical insepction engine configuration, and flows for enabling and disabling A-TAP, and opening the SSL console for an Db2 inspection engine.
Linux-UNIX: Elastic Search configuration
Encrypted Elastic Search is supported via SSL termination.
Linux-UNIX: Configuring Exit libraries
Exit libraries embed a Guardium library into the database, using the exit mechanism. The exit library, or module, communicates directly with the Guardium S-TAP to forward database traffic.
Linux-UNIX: Hadoop configuration
This topic introduces fundamental concepts and processes for monitoring Hadoop data with Guardium.
Linux-UNIX: MongoDB IE configuration
View a typical insepction engine configuration, and flows for enabling and disabling A-TAP, and opening the SSL console for a MongoDB inspection engine.
Linux-UNIX: Neo4J auditing configuration
Use a double proxy together with either K-TAP or PCAP to capture encrypted Neo4J traffic.
Linux-UNIX: Oracle Connection Manager configuration to monitor encrypted traffic
You can use the Oracle Connection Manager to monitor encrypted traffic, without A-TAP.
Linux-UNIX: Oracle IE configuration
View a typical configuration for an inspection engine on an Oracle database.
Linux-UNIX: Configuring S-TAP interception using Oracle Unified Audit
Use Oracle Unified Auditing (OUA) to capture user activities in Oracle database environments based on Oracle Unified Audit policies. All captured activities are stored in specific tables. Linux S-TAP x86_64 can dynamically load and use Oracle-provided libraries to connect to the configured Oracle services. The S-TAP can then pull data from the unified auditing tables, and send data to Guardium collectors.
Linux-UNIX: Redis configuration
Redis TCP protocol is supported by an S-TAP installed on a Redis server. If Redis is set up with SSL/TLS encryption, you need two proxies using HAProxy Load Balancer.

Parent topic: Linux-UNIX: S-TAP user's guide