HTTPS Proxies
VGS HTTPS Proxy sits in front of your backend and filters sensitive data out of incoming requests. By configuring the filtering rules (aka routes) via the VGS Dashboard, you ensure that sensitive data never hits your systems. Instead of storing the sensitive data, you store VGS-provided aliases.
When the time comes to use the data — for example to charge a credit card via a payment processor — the data is again passed through the VGS HTTPS Proxy on its way to a payment gateway or other 3rd party, and VGS substitutes the aliased data in transit with the original value.
Configuring the HTTPS Proxy
VGS HTTPS Proxy processes big variety of data types and 3rd party processors, check Operations Examples for detailed examples.
To make sure your sensitive data is fully secured use one of VGS Collect solutions for web and mobile apps.
Essential steps to integrate with VGS HTTPS Proxy are described in our Getting Started Guide.
Inbound and Outbound Routes Definition
The difference between the inbound and outbound routes is that Inbound Routes utilize a reverse proxy, and can therefore be accessed by third parties (such as a website or app), and the Outbound Routes utilize an HTTPS forward proxy, which sits between your server and third parties. Both tools can be used in conjunction for accepting and sending requests using a secure data infrastructure.
Integration Examples
Last updated