Patent application number | Description | Published |
20150206144 | MULTI-LAYER TRANSACTION TRACKING - Embodiments for tracking multi-layer secured transactions include systems for receiving request for pre-authorization from a user and sending pre-authorization code to the user in response to the request. The systems for receive transaction data from the user that includes the pre-authorization code and match the received pre-authorization code and the sent pre-authorization code. The systems further send a post-verification code to the user and receive post-verification confirmation from the user. | 07-23-2015 |
20150206149 | MULTI-LAYER TRANSACTION TRACKING AND ENCRYPTION - Embodiments for tracking multi-layer secured transactions include systems for providing a dedicated secure transaction channel to a user and sending pre-authorization code to the user via the transaction channel. The systems allow the user to encrypt transaction data and receive the encrypted transaction data from the user via the transaction channel. The systems further unlock the encrypted data and match the sent pre-authorization code to the received pre-authorization code. The systems send a post verification notification to the user comprising the one or more transactions via the transaction channel and receive a post verification confirmation from user in response to the post verification notification. | 07-23-2015 |
20150302210 | SECURE DATA ACCESS - Embodiments for preventing data loss and allowing selective access data include systems and methods that determine that a file has been created or received; determine a fingerprint of the file, wherein the fingerprint is a record of the file for comparison to the file at a later time; determine at least one permitted use related to the file, wherein the permitted uses comprises a permitted user and a permitted action; determine that the file is being accessed by a user; determine whether the user is a permitted user of the file based on an identity of the user; compare the file to the associated fingerprint of the file when the user is a permitted user; determine the action being taken by the user when the file matches the associated fingerprint; and permit the action to occur when the action is a permitted action of the file. | 10-22-2015 |
20150302216 | SECURE ENDPOINT FILE EXPORT IN A BUSINESS ENVIRONMENT - Embodiments for preventing data loss in a business environment are provided. In some embodiments, a secure endpoint file export application assigns users to different classes having different permissions for accessing and writing data. In an embodiment, the system and method are configured to identify a plurality of users in a business environment; classify the plurality of users according to business needs; assign the users to one of at least two classes based on the classification; determine that the first user is permitted to access the data; transmit the secure file to a second user who is permitted to write the data in the secure file to removable media; write the data in the secure file to the removable media; and track a location of the removable media. | 10-22-2015 |
20150302220 | SECURE DATA CONTAINERS - Embodiments for providing secure data containers and allowing selective access to files stored in the containers include systems and methods that receive a request to create a container, wherein the container is a file system comprising access parameters that define one or more permitted actions and one or more permitted users for the container; determine duration parameters for the container, wherein the duration parameter comprise a time duration during which the container may be accessed; determine a fingerprint of the container, the fingerprint being a record of the container for comparison to the container at a later time; generate the container with the access parameters, duration parameters, and fingerprint; monitor the container for compliance with the access parameters, duration parameters, and fingerprint; and apply a consequence when the container is not in compliance with the access parameters, duration parameters, or fingerprint. | 10-22-2015 |
20150302221 | SECURE ACCESS TO PROGRAMMING DATA - Embodiments for preventing data loss and allowing selective data access are provided. In some embodiments, the system and method are configured to receive task protocols and registration requests; determine an allowed list based on the protocols or requests, the list comprising registered data and codes needed to execute a task; allow a user to establish a connection to a device to execute the task on the device; identify data being transferred to and from the device; compare the data being transferred and the allowable list; and determine that at least some of the data being transferred is allowable. | 10-22-2015 |
20150339408 | UNIVERSAL TRANSACTION REPOSITORY - Embodiments disclosed herein relate to systems, methods, and computer program products for providing an extensible input database and associated reference database. In some embodiments, the system and method provide an extensible input database and a graphical user interface for inputting data into the extensible input database; receive data from a user via the graphical user interface, the data comprising content for the extensible input database; generate a key for a reference database based on the content received from the user; populate the extensible input database with the content; and associate the content in the extensible input database with the key in the reference database. The extensible input database is flexible in receiving different types of data and reduces the number of databases needed in order to store different types of data. | 11-26-2015 |
20150348182 | PREPROVISION ONBOARDING PROCESS - Disclosed is a system for onboarding a new customer. The system for onboarding a new customer typically includes a processor, a memory, and a customer onboarding module stored in the memory. The system for onboarding a new customer is typically configured for: creating a first pre-provisioned account, the first pre-provisioned account including generic customer information and account access credentials; storing the first pre-provisioned account in an account database; initiating an onboarding session with a customer; selecting the first pre-provisioned account from the account database; receiving customer-specific information from the customer and replacing generic customer information in the first pre-provisioned account with the customer-specific information; providing the first pre-provisioned account's access credentials to the customer; testing the customer's access to the first pre-provisioned account; determining that the customer successfully accessed the first pre-provisioned account; and based on determining that the customer successfully accessed the first pre-provisioned account, terminating the onboarding session. | 12-03-2015 |