Abstract: Leveraging secure tokenization, such as a Non-Fungible Token (NFT), for purposes of multifactor and/or elevated user authentication. In this regard, an authentication NFT is generated based at least on a user's authentication credentials. Subsequently, the authentication NFT is verified/validated via a private distributed trust computing network and stored, in a deactivated state, on a distributed ledger. Once the user is confronted with an elevated and/or multifactored authentication process, the user may initiates use of the authentication NFT by checking-out the authentication NFT from the distributed ledger and moving the authentication NFT from the deactivated state to an activated state, in which the user credentials are accessible to the user for purposes of authentication.

Abstract: Multifactor user authentication leveraging secure tokenization, such as a Non-Fungible Token (NFT) and multiple passkeys (e.g., bifurcated passkey). One or more authentication NFTs are generated that use some form of a user's authentication credentials as the seed input for the NFT encryption/hash algorithm(s). In addition, passkeys are distributed to and/or made accessible to multiple passkey holders. In response to an event that requests multifactor authentication of the user, a plurality passkeys are requested, received and verified. Each of the passkeys being requested and received from, or at the directive of, one of the multiple passkey holders. In response to verifying the plurality of passkeys, at least one of the authentication NFTs is accessed and the cryptographic hash algorithm(s) is implemented to decrypt the authentication NFT(s) and identify the one or more user credentials.

Abstract: Embodiments of the invention are directed to systems, methods, and computer program products for audiovisual conferencing. The system comprising video input and output devices, which allow a user to be viewed by and view other conference attendees and audio input and output devices that allow the user to be heard by and hear other conference attendees. Further, the system includes a noise mitigation to ensure that a user has privacy when attending a remote meeting in a public or semi-public place.

Abstract: Implementing artificial intelligence, specifically, machine learning techniques to identify malicious emails and, in response, identifying and conducting actions, including reporting the malicious emails to identified internal and/or external entities and preventing the malicious emails from being delivered to email client mailboxes. The machine learning techniques rely on malicious email patterns identified, at least, from previously identified malicious emails and data resulting from continuously crawling the Web and threat intelligence sources. Further, the email clients may be configured to include an add-on feature in which the user can provide a single input to report the email as being suspicious, which results in further analysis to determine whether the email is, in fact, a malicious email.

Abstract: Leveraging secure tokenization, such as a Non-Fungible Token (NFT), for purposes of multifactor and/or elevated user authentication. In this regard, an authentication NFT is generated based at least on a user's authentication credentials. Subsequently, the authentication NFT is verified/validated via a private distributed trust computing network and stored, in a deactivated state, on a distributed ledger. Once the user is confronted with an elevated and/or multifactored authentication process, the user may initiates use of the authentication NFT by checking-out the authentication NFT from the distributed ledger and moving the authentication NFT from the deactivated state to an activated state, in which the user credentials are accessible to the user for purposes of authentication.

Abstract: Systems and methods for digitally encrypting sensitive, self-executing, digital content are provided. A method may include storing the digital content in an encrypted digital vault and generating a first password and a second password which together may unlock the digital vault. The method may include storing the first password on a first encrypted distributed ledger and the second password on a second encrypted distributed ledger. The method may include automatically updating the passwords periodically and storing the updated passwords as new entries on the distributed ledgers. When a document from a predetermined list of documents is digitally scanned and authenticated, the method may include unlocking access to the first password on the first distributed ledger for the designated entity. When the digital vault is unlocked with the first and the second passwords, the digital content may self-execute.

Abstract: Systems and methods for providing a double-sided estate authentication via a distributed ledger are set forth herein. A method may include periodically generating, for display by a first physical token, a first random password. The generating may be in response to periodic receipt of a biometric signal from a first human. The method may also include periodically generating, for display by a second physical token, a second random password. The method further includes receiving and storing the first random password at a distributed ledger and receiving and storing the second random password at the distributed ledger. Following a cessation of the periodic receipt of the biometric signal, the first physical token may stop generating the first random password, and the second physical token may start generating the first random password. The first random password and the second random password together may form a dual-knowledge password.

Abstract: Systems and methods for digitally encrypting sensitive, self-executing, digital content are provided. A method may include storing the digital content in an encrypted digital vault and generating a first password and a second password which together may unlock the digital vault. The method may include storing the first password on a first encrypted distributed ledger and the second password on a second encrypted distributed ledger. The method may include automatically updating the passwords periodically and storing the updated passwords as new entries on the distributed ledgers. When a document from a predetermined list of documents is digitally scanned and authenticated, the method may include unlocking access to the first password on the first distributed ledger for the designated entity. When the digital vault is unlocked with the first and the second passwords, the digital content may self-execute.

Abstract: A blind authenticator performs an authentication procedure with two devices that provides the convenience offered by password storage but avoids storing the passwords themselves. Generally, the blind authenticator stores on the two devices portions of different code generation algorithms. These algorithms on the devices are incomplete—they may not execute properly on their own. During an authentication procedure, the blind authenticator communicates to the devices the remaining portions of these code generation algorithms so that the devices can execute their respective code generation algorithms. The devices then send the generated codes to the blind authenticator, which performs a code validation algorithm on the received codes to determine whether the codes are valid. The code validation algorithm is not sent to the devices, so the devices do not know what makes a code valid or invalid.

Abstract: A blind authenticator performs an authentication procedure with two devices that provides the convenience offered by password storage but avoids storing the passwords themselves. Generally, the blind authenticator stores on the two devices portions of different code generation algorithms. These algorithms on the devices are incomplete—they may not execute properly on their own. During an authentication procedure, the blind authenticator communicates to the devices the remaining portions of these code generation algorithms so that the devices can execute their respective code generation algorithms. The devices then send the generated codes to the blind authenticator, which performs a code validation algorithm on the received codes to determine whether the codes are valid. The code validation algorithm is not sent to the devices, so the devices do not know what makes a code valid or invalid.