Some embodiments of the present disclosure disclose methods and systems for assessing the data risk management capabilities of data processors that receive second-party data as part of an engagement to provide support services. In some embodiments, the transfer of the second-party data to the data processors can be monitored to identify file transfers including unauthorized personally identifiable information (PII) attributes. In some embodiments, the database of the data processor may be scanned to locate any residual second-party data that should be removed after the data processor's engagement to provide the support services have expired.

Broadly speaking, embodiments of the present techniques provide methods and systems to enable a user to securely share user information with a third party. The user information is based on a user data item, but the user data item itself is kept secret and not shared with the third party. The present techniques generate a digital attestation or verifiable credential containing the user information to Receiving an attestation request for a fact be shared.

Embodiments relate to file-based sharing of content through a content distribution network. A request is received from a source to disseminate content to a target consumer. The request does not include target consumer URL information. Based upon the request, content metadata stored in a database with content data, is referenced to generate a file including metadata comprising a portion of the content metadata. The file does not include the content data. The file is exported to the source. The source delivers the file to the target consumer through a communication channel (e.g., shared folder, email) located outside of the distribution network. The file is imported from the target consumer. The metadata of the file is processed to examine its integrity. The metadata may comprise a key for reference during this process. Upon confirming integrity of the file, the content data and the content metadata are distributed to the target consumer.

There is provided a computer implemented method for secure management of data generated in an Electronic Health Record (EHR) during an episode of care, for a user, wherein the EHR is being maintained in a medical database (140) comprised within a Healthcare Service Provider (HSP) server (130), the computer implemented method comprising the steps of sending an identification hash corresponding to the user to an Application Program Interface (API) server (150) from a first client device (110a); extracting the data from the HSP server (130) and de-identifying the data to obtain de-identified data at the API server (150); generating a record hash at the API server (150); transmitting the identification hash, the record hash and the de-identified data from the API server (150) to a core server (160); receiving the identification hash, the record hash and the de-identified data at the core server (160) and transmitting the identification hash, the record hash and the de-identified data from the core server (160) to a repository database (170) to generate a record identification; transmitting the de-identified data, the record hash and the record identification from the repository database (170) to the first client device (110a), via the core server (160); generating a data hash by hashing the de-identified data and a plurality of attributes corresponding to the de-identified data; generating at the core server (160) a register package based on the data hash, the identification hash and the record hash; storing the register package, from the core server (160), on to a blockchain (180) to generate a transaction identification; transmitting the data hash and the transaction identification from the core server (160) to the repository database (170); and transmitting the transaction identification and the data hash from the repository database (170) to the first client device (110a), via the core server (160).

This invention relates generally to distributed ledger technology (including blockchain related technologies), particularly a method and corresponding system for providing a blockchain transaction comprising a redeem script for an output that comprises: i) a plurality of public keys, each associated with a corresponding private key, wherein each public key is uniquely associated with a potential state of at least one data source; and ii) logic arranged to provide a result based on: A) a determination of which of the plurality of associated private key(s) is/are used to sign the unlocking script, so as to provide an interim result: and B) a comparison of a parameter supplied via the unlocking script against the interim result, and further attempting to spend the transaction output more than once, each attempt supplying a different parameter.

A wireless communications system is provided that runs on a mobile device and includes a computer system run on at least one platform on which a plurality of different lottery transactions for different jurisdictions are supported and run from the at least one platform. A decentralized and distributed digital ledger is used to record transactions for the lottery transactions, where each of a lottery transaction can include a lottery element. At least one computer readable storage medium stores computer executable instructions that, when executed by the at least one network processor in the workflow server residing in the mobile communications network, implement components including: a workflow module comprising sets of workflow instructions for processing different types of lottery game packets from a plurality of different jurisdictions; and a deep packet inspection module for inspecting a received lottery game packet and providing information about the lottery game packet to the workflow module.

An information computer system is provided for securely releasing time-sensitive information to recipients via a blockchain. A submitter submits a document to the system and a blockchain transaction is generated and submitted to the blockchain based on the document (e.g., the document is included as part of the blockchain transaction). An editor may edit the document and an approver may approve the document for release to the recipients. Each modification and/or approval of the document is recorded as a separate transaction on the blockchain where each of the submitter, editor, approver, and recipients interact with the blockchain with corresponding unique digital identifiers—such as private keys.

Replication of a filesystem or a mount point or share may replicate all data that it consists of irrespective of where the data is stored. Replication protects data irrespective of location. One method is to replicate the filesystem namespace as is while skipping the data outside of the appliance/machine so that replication cost and time are reasonable. The data outside of the machine, like cloud/tape data is protected differently. One example method includes a data protection operation configured to replication a namespace associated with multiple data tiers. During replication, data from one of the tiers is skipped while all of the namespace metadata is replicated. The recovery restores the namespace metadata and the data that was replicated from the other tier. This may be performed in connection with cyber security, for example when replicating multi-tier data to a vault.

A system for providing access is configured to receive an application access request from an application for authorization to access and a sensitive data access request from the application for authorization to access a document that includes sensitive data. The system is further configured to determine to authorize access to the application in response to the application access request; to determine the user authentication device in response to the sensitive data access request; to provide a secondary request for authorization to access sensitive data to the user authentication device in response to the sensitive data access request, receive a secondary request response from the user authentication device to the secondary request; and to provide the secondary request response to the application enabling access to the sensitive data, where the document is encrypted for delivery to the application for the user using a blinding secret and an identity private key.

Systems, methods, and apparatuses for storing verified identification information in a distributed database and for verifying entities to requestors are provided herein. Identity information relating to an entity is verified by a generally recognized identity provider (GRIP). Once verified, the GRIP populates a distributed database with an entry corresponding to the verified identity information. The distributed database is publically accessible such that identity requestors can see the entries in the distributed database. In some arrangements, the distributed database is write-protected such that only an authorized GRIP can modify the distributed database. An entity can provide information to a requestor to verify an identity attribute of the entity to the requestor. The requestor uses information provided by the entity to retrieve verified entity identification information from the distributed database and to confirm that the identity attribute was verified by an authorized GRIP.