Distributed authorization of identities in a dynamic connected environment
US-2019289013-A1 · Sep 19, 2019 · US
US11601437B2 · US · B2
| Field | Value |
|---|---|
| Publication number | US-11601437-B2 |
| Application number | US-202117301469-A |
| Country | US |
| Kind code | B2 |
| Filing date | Apr 5, 2021 |
| Priority date | Jan 29, 2020 |
| Publication date | Mar 7, 2023 |
| Grant date | Mar 7, 2023 |
A practical reading order for non-experts. Skip the full description unless you need deep technical detail.
What the patent document calls the invention.
A short plain-language summary of the technical disclosure.
Who owns or filed the patent and who is credited as inventor.
Filing, priority, publication, and grant dates set the timeline.
The legal scope of protection — read this for what is actually claimed.
Technology tags used to group this patent with similar filings.
Prior art links and similar publications in this corpus.
Official abstract text for this publication.
A node of a network receives account access information (AAI) for an account that a user has with a system. The node causes a first record to be added to a distributed ledger that is used for managing access to the account, wherein the first record includes the AAI or an encrypted storage identifier that identifies a storage location for the AAI. The node determines a likelihood that the account is being accessed by the user based on the AAI and/or historical AAI for one or more accounts, that include the account, that are used to access the system. The node causes a second record that includes a value representing the likelihood to be added to the distributed ledger. The node causes one or more other nodes of the network to be alerted that the first record and the second record have been added to the distributed ledger.
Opening claim text (preview).
What is claimed is: 1. A method, comprising: obtaining, by a node of a network and based on user preferences information associated with an account that a user has with an organization, a smart contract that specifies permissible types of account access information that the user has consented to having monitored, wherein the user preferences information is added to a distributed ledger that is used for managing access to the account, and wherein the user preferences information specifies two or more of: which account access information of the user is permitted to be monitored, when the account access information of the user is permitted to be monitored, or how the account access information of the user is permitted to be monitored; receiving, by the node of the network, account access information; and causing, by the node of the network, a record to be added to the distributed ledger that is used for managing access to the account. 2. The method of claim 1 , wherein the account access information is associated with encrypted identifiers. 3. The method of claim 1 , wherein the account access information includes one or more of: attempted login information, login configuration information, or user behavior metadata. 4. The method of claim 1 , further comprising: providing the account access information to one or more other nodes in the network. 5. The method of claim 1 , further comprising: using the smart contract that is stored by the distributed ledger to determine an account security score. 6. The method of claim 1 , wherein the distributed ledger is implemented by a blockchain. 7. The method of claim 1 , further comprising: causing the smart contract to be stored as another record in the distributed ledger. 8. A node, comprising: one or more memories; and one or more processors, coupled to the one or more memories, configured to: obtain, based on user preferences information associated with an account that a user has with an organization, a smart contract that specifies permissible types of account access information that the user has consented to having monitored, wherein the user preferences information is added to a distributed ledger that is used for managing access to the account, and wherein the user preferences information specifies two or more of: which account access information of the user is permitted to be monitored, when the account access information of the user is permitted to be monitored, or how the account access information of the user is permitted to be monitored; receive account access information; and cause a record to be added to the distributed ledger that is used for managing access to the account. 9. The node of claim 8 , wherein the account access information is associated with encrypted identifiers. 10. The node of claim 8 , wherein the account access information includes one or more of: attempted login information, login configuration information, or user behavior metadata. 11. The node of claim 8 , wherein the one or more processors are further configured to: provide the account access information to one or more other nodes. 12. The node of claim 8 , wherein the one or more processors are further configured to: use the smart contract that is stored by the distributed ledger to determine an account security score. 13. The node of claim 8 , wherein the distributed ledger is implemented by a blockchain. 14. The node of claim 8 , wherein the one or more processors are further configured to: cause the smart contract to be stored as another record in the distributed ledger. 15. A non-transitory computer-readable medium storing a set of instructions, the set of instructions comprising: one or more instructions that, when executed by one or more processors of a node, cause the node to: obtain, based on user preferences information associated with an account that a user has with an organization, a smart contract that specifies permissible types of account access information that the user has consented to having monitored, wherein the user preferences information is added to a distributed ledger that is used for managing access to the account, and wherein the user preferences information specifies two or more of: which account access information of the user is permitted to be monitored, when the account access information of the user is permitted to be monitored, or how the account access information of the user is permitted to be monitored; receive account access information; and cause a record to be added to the distributed ledger that is used for managing access to the account. 16. The non-transitory computer-readable medium of claim 15 , wherein the account access information is associated with encrypted identifiers. 17. The non-transitory computer-readable medium of claim 15 , wherein the one or more instructions further cause the node to: attempt login information, login configuration information, or user behavior metadata. 18. The non-transitory computer-readable medium of claim 15 , wherein the one or more instructions further cause the node to: provide the account access information to one or more other nodes. 19. The non-transitory computer-readable medium of claim 15 , wherein the one or more instructions further cause the node to: use the smart contract that is stored by the distributed ledger to determine an account security score. 20. The non-transitory computer-readable medium of claim 15 , wherein the distributed ledger is implemented by a blockchain.
by observing the pattern of computer usage, e.g. typical user behaviour · CPC title
Access control lists [ACL] · CPC title
Databases characterised by their database models, e.g. relational or object models · CPC title
using passwords (cryptographic mechanisms or cryptographic arrangements for entity authentication using a predetermined code H04L9/3226) · CPC title
Machine learning · CPC title
Related publications grouped by family.
Answers are generated from the same data shown on this page.