Ulf Mattsson - Cos Cob CT, US Yigal Rozenberg - Wilton CT, US
International Classification:
G06F 21/60
US Classification:
726 9
Abstract:
Data can be protected in mobile and payment environments through various tokenization operations. A mobile device can tokenize communication data based on device information and session information associated with the mobile device. A payment terminal can tokenize payment information received at the payment terminal during a transaction based on transaction information associated with the transaction. Payment data tokenized first a first set of token tables and according to a first set of tokenization parameters by a first payment entity can be detokenized or re-tokenized with a second set of token tables and according to a second set of tokenization parameters. Payment information can be tokenized and sent to a mobile device as a token card based on one or more selected use rules, and a user can request a transaction based on the token card. The transaction can be authorized if the transaction satisfies the selected use rules.
- George Town, KY Yigal Rozenberg - Wilton CT, US Raul Ortega - Westport CT, US
International Classification:
G06F 17/30
US Classification:
707803
Abstract:
Financial regulations can require the storing of transaction date information when conducting financial transactions. To improve the security of storing such information, date information can be tokenized prior to storage. Client devices used in conducting and processing transactions can access date information rules and token tables for use in tokenizing date information. The client device can also require and use starting date when tokenizing date information. To tokenize the date information, a client device can convert the date information into an integer, for instance based on a number of days from a starting date, and can use the date integer as an input to one or more token tables. The token tables output a tokenized date integer, which can be converted into a tokenized date using a second starting date. The tokenized date can then be stored for subsequent access.
Yigal Rozenberg - Wilton CT, US Vichai Levy - Norwalk CT, US
Assignee:
Protegrity Corporation - George Town KY
International Classification:
G06Q 20/38
US Classification:
705 64, 705 39
Abstract:
Data can be protected in mobile and payment environments through various tokenization operations. A mobile device can tokenize communication data based on device information and session information associated with the mobile device. A payment terminal can tokenize payment information received at the payment terminal during a transaction based on transaction information associated with the transaction. Payment data tokenized first a first set of token tables and according to a first set of tokenization parameters by a first payment entity can be detokenized or re-tokenized with a second set of token tables and according to a second set of tokenization parameters. Payment information can be tokenized and sent to a mobile device as a token card based on one or more selected use rules, and a user can request a transaction based on the token card. The transaction can be authorized if the transaction satisfies the selected use rules.
Data can be protected in mobile and payment environments through various tokenization operations. A mobile device can tokenize communication data based on device information and session information associated with the mobile device. A payment terminal can tokenize payment information received at the payment terminal during a transaction based on transaction information associated with the transaction. Payment data tokenized first a first set of token tables and according to a first set of tokenization parameters by a first payment entity can be detokenized or re-tokenized with a second set of token tables and according to a second set of tokenization parameters. Payment information can be tokenized and sent to a mobile device as a token card based on one or more selected use rules, and a user can request a transaction based on the token card. The transaction can be authorized if the transaction satisfies the selected use rules.
Tokenization Of Payment Information In Mobile Environments
Ulf Mattsson - Cos Cob CT, US Yigal Rozenberg - Wilton CT, US
International Classification:
G06Q 20/40
US Classification:
705 44, 705 39
Abstract:
Data can be protected in mobile and payment environments through various tokenization operations. A mobile device can tokenize communication data based on device information and session information associated with the mobile device. A payment terminal can tokenize payment information received at the payment terminal during a transaction based on transaction information associated with the transaction. Payment data tokenized first a first set of token tables and according to a first set of tokenization parameters by a first payment entity can be detokenized or re-tokenized with a second set of token tables and according to a second set of tokenization parameters. Payment information can be tokenized and sent to a mobile device as a token card based on one or more selected use rules, and a user can request a transaction based on the token card. The transaction can be authorized if the transaction satisfies the selected use rules.
Multi-Tenant Data Protection In A Centralized Network Environment
- Grand Cayman, KY George Curran - Northport NY, US Raul Ortega - Westport CT, US Jan Boberg - Skelleftea, SE Rajnish Jain - Fairfield CT, US Yigal Rozenberg - Wilton CT, US
Data can be protected in a centralized tokenization environment. A security value is received by a central server from a client device. The central server accesses a token table corresponding to the client device and generates a reshuffled static token table from the accessed token table based on the received security value. When the client device subsequently provides data to be protected to the central server, the central server tokenizes the provided data using the reshuffled static token table and stores the tokenized data in a multi-tenant database. By reshuffling token tables using security values unique to client devices, the central server can protect and store data for each of multiple tenants such that if the data of one tenant is compromised, the data of each other tenant is not compromised.
A gateway device includes a network interface connected to data sources, and computer instructions, that when executed cause a processor to access data portions from the data sources. The processor accesses classification rules, which are configured to classify a data portion of the plurality of data portions as sensitive data in response to the data portion satisfying the rule. Each rule is associated with a significance factor representative of an accuracy of the classification rule. The processor applies each of the set of classification rules to a data portion to obtain an output of whether the data is sensitive data. The output are weighed by significance factors to produce a set of weighted outputs. The processor determines if the data portion is sensitive data by aggregating the set of weighted outputs, and presents the determination in a user interface. Security operations may also be performed on the data portion.
Multi-Tenant Data Protection In A Centralized Network Environment
- Grand Cayman, KY George Curran - Northport NY, US Raul Ortega - Westport CT, US Jan Boberg - Skelleftea, SE Rajnish Jain - Fairfield CT, US Yigal Rozenberg - Wilton CT, US
Data can be protected in a centralized tokenization environment. A security value is received by a central server from a client device. The central server accesses a token table corresponding to the client device and generates a reshuffled static token table from the accessed token table based on the received security value. When the client device subsequently provides data to be protected to the central server, the central server tokenizes the provided data using the reshuffled static token table and stores the tokenized data in a multi-tenant database. By reshuffling token tables using security values unique to client devices, the central server can protect and store data for each of multiple tenants such that if the data of one tenant is compromised, the data of each other tenant is not compromised.
Protegrity
Senior Vice President Technology
Protegrity
Vice President Software Engineering
Protegrity Jun 2005 - Feb 2012
Vp, Chief Architect
Kavado Jan 2000 - May 2005
Vice President R and D
Education:
Tel Aviv University
Skills:
Software Development Enterprise Software Saas Product Management Scalability Software Project Management Software Design Encryption Start Ups Security Cloud Computing Software Engineering Architecture Architectures C++ Integration Enterprise Architecture Agile Methodologies Pci Dss Databases Strategic Partnerships Pre Sales Linux Solution Selling Go To Market Strategy Sql System Architecture Professional Services Solution Architecture Software As A Service
Youtube
The Jewish Historical Museum Amsterdam: Prof....
Collections of Memories - Jewish Museums in a Changing Reality The Jew...
Duration:
1h 38m 47s
YUAR - (BaHalom)
... : Music and lyrics by Arina Popova Translation to Hebrew - Dan T...
Duration:
3m 39s
Au cur de la Rashi Shul avec le Rav Cham Zvi ...
la mmoire du Rav Cham Zvi Rozenberg zatsal, dcd en 2019, film entre 2...
Duration:
16m 1s
A Jewish Name in a Babylonian Toponym of 425 ...
A Jewish Name in a Babylonian Toponym of 425, a lecture given by Dr. Y...