Abstract: Adjustments to be made to a system for authenticating users may be made by performing the following operations: obtaining a stochastic model of the system, wherein the stochastic model includes two or more classes of requests; obtaining a set of preferences for handling authentication requests and a set of operational parameter values; determining, based at least in part on the stochastic model and the set of operational parameter values, that adjusting an authentication scheme will improve a probable degree to which the authentication system will meet the set of preferences; responsive to the determination that adjusting the authentication scheme will improve the probable degree to which the system for authenticating users will meet the set of preferences, adjusting the authentication scheme of the system for authenticating users; and performing an authentication of a user based on the adjusted authentication scheme.

Abstract: An example operation may include one or more of receiving one or more transaction requests to complete one or more transactions, recording the one or more transaction requests in a blockchain, requesting one or more transaction confirmations from an out-of-band device to confirm the one or more transactions, and committing the one or more confirmed transactions to the blockchain.

Abstract: Authenticated base digital document(s) are issued to client(s) by an issuing party, and aggregate digital document(s) are received. An aggregate digital document includes base digital document(s) and attachment(s). Authenticity of the aggregate digital document(s) is verified, resulting in authenticated aggregate digital document(s), which are stored and/or redistributed. Authentication challenge(s) are sent by a verifying party to a client requesting part or all of an aggregate digital document from the client be verified. The part or all of the aggregate digital document is received and authenticity and integrity are verified, resulting in an authenticated aggregate digital document. The client verifies authenticity of a base digital document and receives the authentication challenge(s) for an authenticated aggregate digital document and sends part or all of the authenticated aggregate digital document to the verifying party for verification by the verifying party.

Abstract: Authenticated base digital document(s) are issued to client(s) by an issuing party, and aggregate digital document(s) are received. An aggregate digital document includes base digital document(s) and attachment(s). Authenticity of the aggregate digital document(s) is verified, resulting in authenticated aggregate digital document(s), which are stored and/or redistributed. Authentication challenge(s) are sent by a verifying party to a client requesting part or all of an aggregate digital document from the client be verified. The part or all of the aggregate digital document is received and authenticity and integrity are verified, resulting in an authenticated aggregate digital document. The client verifies authenticity of a base digital document and receives the authentication challenge(s) for an authenticated aggregate digital document and sends part or all of the authenticated aggregate digital document to the verifying party for verification by the verifying party.

Abstract: Adjustments to be made to a system for authenticating users may be made by performing the following operations: obtaining a stochastic model of the system, wherein the stochastic model includes two or more classes of requests; obtaining a set of preferences for handling authentication requests and a set of operational parameter values; determining, based at least in part on the stochastic model and the set of operational parameter values, that adjusting an authentication scheme will improve a probable degree to which the authentication system will meet the set of preferences; responsive to the determination that adjusting the authentication scheme will improve the probable degree to which the system for authenticating users will meet the set of preferences, adjusting the authentication scheme of the system for authenticating users; and performing an authentication of a user based on the adjusted authentication scheme.

Abstract: Using a stochastic queuing model to determine adjustments to be made to authentication system operation. In light of operational parameter values and the stochastic queuing model, a determination is made that adjusting the value of a particular parameter for handling authentication requests is likely to improve some aspect of system performance, and the request handling parameter is adjusted accordingly.

Abstract: A certified checkpoint is provided for a ledger comprising a blockchain and a world state. The certified checkpoint enables a third party to recognize and verify that the ledger has integrity, a known starting state, and immutability properties starting at a specific point in time. Certification means that all of the validating peers reached consensus on the state of the ledger at that point in time. Thus, the certified checkpoint state represents an agreed-upon state, and that one or more subsequent operations on the ledger are relative to that agreed-upon state. Preferably, before a checkpoint is certified, it must be consistent, meaning that all validating peers have reached the same value for the checkpoint. Preferably, the checkpoint is a compression of the current blockchain world state into a compact representation (e.g., a hash) of the ledger that based on an agreed-upon consensus protocol is consistent across the (validating) peers.

Abstract: A certified checkpoint is provided for a ledger comprising a blockchain and a world state. The certified checkpoint enables a third party to recognize and verify that the ledger has integrity, a known starting state, and immutability properties starting at a specific point in time. Certification means that all of the validating peers reached consensus on the state of the ledger at that point in time. Thus, the certified checkpoint state represents an agreed-upon state, and that one or more subsequent operations on the ledger are relative to that agreed-upon state. Preferably, before a checkpoint is certified, it must be consistent, meaning that all validating peers have reached the same value for the checkpoint. Preferably, the checkpoint is a compression of the current blockchain world state into a compact representation (e.g., a hash) of the ledger that based on an agreed-upon consensus protocol is consistent across the (validating) peers. The approach also is extended to a permissionless blockchain.

Abstract: A certified checkpoint is provided for a ledger comprising a blockchain and a world state. The certified checkpoint enables a third party to recognize and verify that the ledger has integrity, a known starting state, and immutability properties starting at a specific point in time. Certification means that all of the validating peers reached consensus on the state of the ledger at that point in time. Thus, the certified checkpoint state represents an agreed-upon state, and that one or more subsequent operations on the ledger are relative to that agreed-upon state. Preferably, before a checkpoint is certified, it must be consistent, meaning that all validating peers have reached the same value for the checkpoint. Preferably, the checkpoint is a compression of the current blockchain world state into a compact representation (e.g., a hash) of the ledger that based on an agreed-upon consensus protocol is consistent across the (validating) peers. A technique to certify a blockchain checkpoint also is described.

Abstract: Systems and methods for protecting a data item include, upon initiation of transfer of the data item from a server to a client device, determining a sensitivity score and a current protection, level of the data item. A policy is applied to determine an appropriate protection for the data item based upon the sensitivity score and the current protection level. A protected data item is provided to the client device by applying the appropriate protection to the data item.

Abstract: Dynamic multi-factor authentication challenge selection is provided. A risk associated with an operation that requires authentication of a user of a client device is determined. A plurality of authentication methods is identified. Each respective authentication method associated with a level of security offsetting the risk and a computing cost associated with a respective authentication method. One or more authentication methods are selected from the plurality of authentication methods according to the risk and to minimize the computing cost associated with authenticating the operation.

Abstract: Authenticating a user is provided. A decryption key corresponding to an authentication account of the user of a client device and authentication credential data obtained from the user of the client device is received during authentication. Encrypted authentication credential data corresponding to the user is decrypted using the received decryption key corresponding to the authentication account of the user. The decrypted authentication credential data is compared with the received authentication credential data to authenticate the user of the client device.

Abstract: Authenticating a user is provided. A decryption key corresponding to an authentication account of the user of a client device and authentication credential data obtained from the user of the client device is received during authentication. Encrypted authentication credential data corresponding to the user is decrypted using the received decryption key corresponding to the authentication account of the user. The decrypted authentication credential data is compared with the received authentication credential data to authenticate the user of the client device.

Abstract: An example operation may include one or more of receiving one or more transaction requests to complete one or more transactions, recording the one or more transaction requests in a blockchain, requesting one or more transaction confirmations from an out-of-band device to confirm the one or more transactions, and committing the one or more confirmed transactions to the blockchain.

Abstract: Authenticating a user is provided. A decryption key corresponding to an authentication account of the user of a client device and authentication credential data obtained from the user of the client device is received during authentication. Encrypted authentication credential data corresponding to the user is decrypted using the received decryption key corresponding to the authentication account of the user. The decrypted authentication credential data is compared with the received authentication credential data to authenticate the user of the client device.

Abstract: Dynamic risk communication associated with a computer device may include automatically detecting one or more security risk factors for the computer device based on current context information associated with the computer device. Whether an attempt is being made via the computer device to manipulate the one or more risk factors in an attempt to reduce a security level of a computer-implemented authentication procedure may be determined. Responsive to determining that the attempt is being made to manipulate the one or more risk factors, a new challenge for additional identification may be communicated for presentation on a user interface device of the computer device while suppressing one or more security risk factors from being presented on the user interface device. Responsive to determining that an attempt is not being made to manipulate the one or more risk factors, the new challenge and one or more security risk factors may be communicated.

Abstract: A blockchain may include various transactions which are identified and which require processing. The order of processing such transactions may be optimized by examining content of the transactions. One example method of operation may comprise one or more of receiving an ordered set of proposed transactions intended for inclusion in a blockchain block, creating a lattice structure containing the proposed transactions for the blockchain block, the lattice structure comprising a top and a bottom and a plurality of nodes representing the proposed transactions, determining an order of execution of the proposed transactions for the blockchain block via the lattice structure, and processing the proposed transactions in the lattice structure in parallel based on a configuration of the lattice structure.

Abstract: A certified checkpoint is provided for a ledger comprising a blockchain and a world state. The certified checkpoint enables a third party to recognize and verify that the ledger has integrity, a known starting state, and immutability properties starting at a specific point in time. Certification means that all of the validating peers reached consensus on the state of the ledger at that point in time. Thus, the certified checkpoint state represents an agreed-upon state, and that one or more subsequent operations on the ledger are relative to that agreed-upon state. Preferably, before a checkpoint is certified, it must be consistent, meaning that all validating peers have reached the same value for the checkpoint. Preferably, the checkpoint is a compression of the current blockchain world state into a compact representation (e.g., a hash) of the ledger that based on an agreed-upon consensus protocol is consistent across the (validating) peers. The approach also is extended to a permissionless blockchain.

Abstract: A certified checkpoint is provided for a ledger comprising a blockchain and a world state. The certified checkpoint enables a third party to recognize and verify that the ledger has integrity, a known starting state, and immutability properties starting at a specific point in time. Certification means that all of the validating peers reached consensus on the state of the ledger at that point in time. Thus, the certified checkpoint state represents an agreed-upon state, and that one or more subsequent operations on the ledger are relative to that agreed-upon state. Preferably, before a checkpoint is certified, it must be consistent, meaning that all validating peers have reached the same value for the checkpoint. Preferably, the checkpoint is a compression of the current blockchain world state into a compact representation (e.g., a hash) of the ledger that based on an agreed-upon consensus protocol is consistent across the (validating) peers.

Abstract: A certified checkpoint is provided for a ledger comprising a blockchain and a world state. The certified checkpoint enables a third party to recognize and verify that the ledger has integrity, a known starting state, and immutability properties starting at a specific point in time. Certification means that all of the validating peers reached consensus on the state of the ledger at that point in time. Thus, the certified checkpoint state represents an agreed-upon state, and that one or more subsequent operations on the ledger are relative to that agreed-upon state. Preferably, before a checkpoint is certified, it must be consistent, meaning that all validating peers have reached the same value for the checkpoint. Preferably, the checkpoint is a compression of the current blockchain world state into a compact representation (e.g., a hash) of the ledger that based on an agreed-upon consensus protocol is consistent across the (validating) peers. A technique to certify a blockchain checkpoint also is described.