Lightboard Lessons: Secure Data Tokenization
Companies that are subject to security audits, such as PCI DSS, could benefit from a solution that takes sensitive information and moves it from their web servers to the enterprise edge or ingress po...
Published Aug 03, 2016
Version 1.0ltwagnon
Ret. Employee
Joined May 15, 2019
ltwagnon
Ret. Employee
Joined May 15, 2019
Mats_Nyström
Sep 15, 2016Nimbostratus
Hi John!
Thanks for your answer!
I was refering to the Intercept_CC iRule that does the extraction and the sideband connection to the encryptor. I still think it needs send and recv. But on the other hand I might be wrong!
(Adding some lines of code to make it more understandable)
Build simple GET request to encrypt credit card number
set tokenizationRequest "GET /tokenize?data=$ccNum HTTP/1.1\r\nUserAgent: AlmostCurl!\r\nHost: ${static::HostString}\r\nAccept: */*\r\n\
r\n"
Connect to encryptor virtual server
set TokenServer [connect -protocol TCP -myaddr $static::myaddr -timeout
100 -idle 5 -status connect_status $static::TokenizationVirtualServer]
Adding "send and recv" that I think is missing in whitepaper
set send_info [send -timeout 3000 -status send_status $TokenServer $tokenizationRequest]
Not a very robust recv, needs adjustments...
set recv_data [recv -timeout 3000 $TokenServer]
set Token [findstr $recv_data "" 7 ""]
set TokenizedData "$FirstPartOfInboundRequest$Token$SecondPartOfInbound
Request"