Patent classifications
H04L63/0442
ENCRYPTED GROUP COMMUNICATION METHOD
Embodiments herein include, for example, a method, comprising: generating a shared symmetric key to begin a communication session among a group of users by a first user; distributing, by the first user, the generated shared symmetric key to each user in the group of users; communicating within the communication session among a group of users, where each user encrypts a message to the group of users to be distributed through the communication session using the generated shared symmetric key, and each user decrypts a message received from the communication session using the generated shared symmetric key.
System and method of cryptographically signing web applications
Embodiments disclosed herein provide a method that includes receiving, at a client-side web browser, a minimal bootstrap payload from an application server; storing, by a client-side processor, the minimal bootstrap payload in a client-side local cache, where the locally cached minimal bootstrap payload is executed by the client-side processor before executing an application from the application server; the minimal bootstrap payload includes at least one public key and at least one Uniform Resource Location (URL) address of an application code payload.
SYSTEMS AND METHODS FOR CONTROLLED ACCESS TO BLOCKCHAIN DATA
Methods and systems for managing and/or processing a blockchain to maintain data security for confidential and/or personal data are provided. According to certain aspects, the disclosed data security techniques may enable access sharing functionality utilizing the blockchain. For example, access sharing may be utilized to file documents, share policy information, and/or comply with an audit. The data security techniques disclosed herein also enable the use of smart contracts to transfer funds associated with payment obligations and/or other forms of blockchain based payments, comply with anti-money laundering requirements, report industry data, validate interest payments and/or maintain agent sales data. Data security may be achieved through the use of public key/private key encryption techniques.
SYSTEMS, APPARATUS AND METHODS FOR IDENTIFYING AND SECURELY STORING DISTINGUISHING CHARACTERISTICS IN A DISTRIBUTED LEDGER WITHIN A DISTRIBUTED LEDGER-BASED NETWORK BASED ON FUNGIBLE AND NON-FUNGIBLE TOKENS
In some embodiments, a method includes storing data associated with fungible assets in a distributed ledger database. The method includes dividing fungible tokens into a first set of groups of fungible tokens based on the data and sending, via the distributed ledger-based network and based on an asymmetric cryptography key pair, each group of fungible tokens from the first set of groups of fungible tokens to a communication device from the first set of communication devices to cause the second plurality of communication devices to send, to a designated recipient communication device, non-fungible tokens for each group of fungible tokens from the second set of groups of fungible tokens. The first set of groups of fungible tokens is divided into a second set of groups of fungible tokens and received at a second set of communication devices.
Systems and methods encrypting messages using multiple certificates
This disclosure includes techniques for using multiple cryptographic certificates for a secure connection. One embodiment is a method including: receiving by a client N public encryption keys over a network from a server, wherein N is an integer greater than 1; generating N session keys in response to receiving the N public encryption keys; encrypting each of the N session keys with a respective one of the N public encryption keys; subsequent to encrypting each of the N session keys, sending the N session keys encrypted over the network to the server; encrypting, with a first one of the N session keys, a first portion of a payload associated with a first message; encrypting, with a second one of the N session keys, a second portion of the payload associated with the first message; and sending the first message, comprising the payload encrypted, to the server from the client.
Electronic device for secure communications with an automobile
A mobile device securely communicates with an electronic device within an automobile. The mobile device transmits encrypted spatial state information and the electronic device provides commands to the automobile in response. Spatial state information may include location, motion, or the like. Commands to the automobile may include door unlock commands, remote start commands, horn honk commands, or the like.
SECURE VERIFICATION OF MEDICAL STATUS USING A CONTACTLESS CARD
Systems, methods, articles of manufacture, and computer-readable media for verification of medical status using a contactless card. An application may receive a request specifying a subject and a medical condition. The application may receive a cryptogram from a contactless card. The application may receive a decryption result from a server and determine that the server decrypted the cryptogram. The application may receive, from the contactless card, a medical attestation, a digital signature of the medical attestation, and a public key of the digital signature. The application may decrypt the digital signature based on the public key of the digital signature and verify the medical attestation based on the decrypted digital signature. The application may determine, based on the verification of the medical attestation, that the subject is immune to the medical condition. The application may output a result that the subject is immune to the medical condition.
Data communication target control with contact tokens
Communication circuitry associates a data source with a source Identifier (ID) and a cryptographic key and associates a data target with a target ID, contact token, contact condition, and contact information. The communication circuitry receives and decrypts the encrypted source ID, the encrypted target ID, and the encrypted contact token with the cryptographic key, and in response, authenticates the source ID, authenticates the target ID, and validates the contact token. When the authentication and validation are successful, the communication circuitry selects a portion of the contact information based on the contact condition, encrypts the selected contact information, and transfers the encrypted selected contact information to the data source. The data source uses the selected contact information and the contact token to transfer data to the data target. The data target uses the contact token to validate the data source.
Service-to-service strong authentication
A request is received from a computing device for substitute data, with access to the substitute data being contingent upon successful multi-factor authentication of the first service. Signature data based on the request is generated using a first key of public-private key pair. Credential proof and the signature is provided to a second service, which verifies the credential proof as a first factor of the multi-factor authentication and verifies, using a second key, the signature as a second factor of the multi-factor authentication. The substitute data is obtained as a result of authentication by the second service. The computing device is caused, by providing the substitute data to the computing device, to input the substitute data into the interface in place of data associated with the first entity.
RECORDS ACCESS AND MANAGEMENT
Systems and methods for providing a healthcare provider with an electronic medical record of a patient, a recommendation, or an alert relating to the patient, based on an analysis of the patient's health data. Multiple electronic repositories may store the patient's health data as disaggregated health data. The patient's health data may be organized in a Healthcare Identity Graph providing a comprehensive medical history of the user. A device of the patient may access and analyze the patient's health data in response to detecting an event. The device can generate outputs or trigger actions based on the analysis of the patient's health data, and record the outputs or actions in the patient's Healthcare Identity Graph. Authentication and verification of the outputs or actions are stored at a Healthcare Liability Graph.