In this lab, we will learn how to integrate and configure VGS into a network and payments ecosystem in order to secure PII-sensitive and PCI-sensitive data and descope the network from the PII-sensitive and PCI-sensitive data while maintaining the ability to operate on the sensitive data.
For KYC/AML/ID Verification, the collection of PII from the end-user is necessary. VGS helps customers collect the PII-senstive data, secure the PII-sensitive data, and keep the PII-senstive data off of their networks.
When dealing with card-not-present, card issuing, and PCI, PCI rules require that the Primary Account Number (PAN) and card security code (CVC/CVV) be secured. VGS not only secures the PCI-sensitive data but also descopes networks completely from the PCI-sensitive data. By decoping from PCI-sensitive data, VGS helps companies simplify and accelerate their journey to PCI compliance.
This lab will walk partcipants through the following steps:
Let’s get started…
The examples and sample code provided in this workshop are intended to be consumed as instructional content. These will help you understand how various AWS services can be architected to build a solution while demonstrating best practices along the way. These examples are not intended for use in production environments.