Hi everyone,

I'm trying to deploy External S-TAP on-premise using docker. I follow the guide and try to install but when i come to the docker step, i not able to pull the External S-TAP repo. Have anyone deploy the External S-TAP on-premise and share with me ?

Beside that, i have some confuse about this External S-TAP :
- In some document i see that to deploy External S-TAP on-premise, it require load balance for some purpose like backup, fail-over ... But can i deploy External S-TAP on-premise without load balance ? Just Guardium, DB and External S-TAP host, is this enough ?
- If only use External S-TAP, i cannot monitor the local activity on DB right ?

THanks,

------------------------------
Quang Le Nguyen Hong
------------------------------

Quang,

I do not have the External TAP in my environment so someone else may need to correct me, but this is my understanding:

The load balancer is to manage two or more external S-TAPs for a database. Because the External TAP sits between the user and the database as a proxy if the External TAP were to go offline it will bring the connection between the user and database offline as well.​ This adds an availability risk that the regular S-TAP does not have and is why having two load balanced E-TAPs is recommended (I do not believe that it is mandatory).

Second, External TAP is a network man-in-the-middle TAP acting as a proxy in order to capture database traffic. If you bypass the E-TAP and directly connect to the database then the E-TAP will not see the traffic.

------------------------------
Chase Walkup
------------------------------

Hi Chase,

Yes, i agree with you. I still need someone help the problem with docker. Thanks!

------------------------------
Quang Le Nguyen Hong
------------------------------

Original Message:
Sent: Tue February 04, 2020 09:46 AM
From: Chase Walkup
Subject: Deploy External S-TAP Onpremise

Quang,

I do not have the External TAP in my environment so someone else may need to correct me, but this is my understanding:

The load balancer is to manage two or more external S-TAPs for a database. Because the External TAP sits between the user and the database as a proxy if the External TAP were to go offline it will bring the connection between the user and database offline as well.​ This adds an availability risk that the regular S-TAP does not have and is why having two load balanced E-TAPs is recommended (I do not believe that it is mandatory).

Second, External TAP is a network man-in-the-middle TAP acting as a proxy in order to capture database traffic. If you bypass the E-TAP and directly connect to the database then the E-TAP will not see the traffic.

------------------------------
Chase Walkup
------------------------------