Account access security using a distributed ledger and/or a distributed file system
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.
1. A method, comprising:
obtaining, by a system 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 types of 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; and
determining, by the system, one or more account security scores based on providing the account access information as input to the smart contract.
2. The method of claim 1 , wherein the distributed ledger is implemented by a tamper-resistant data structure.
3. The method of claim 1 , further comprising:
providing the account access information to one or more nodes in a network.
4. The method of claim 1 , further comprising:
storing, by the system, the account access information as part of the distributed ledger.
5. The method of claim 1 , further comprising:
causing an encrypted identifier of the user to be stored as a record of the distributed ledger.
6. The method of claim 1 , wherein determining the one or more account security scores comprises:
determining the one or more account security scores based on using a machine learning model.
7. The method of claim 1 , further comprising:
performing an audit of records stored as part of the distributed ledger based on the one or more account security scores.
8. A system, 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 types of 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; and
determine one or more account security scores based on providing the account access information as input to the smart contract.
9. The system of claim 8 , wherein the distributed ledger is implemented by a tamper-resistant data structure.
10. The system of claim 8 , wherein the one or more processors are further configured to:
provide the account access information to one or more nodes in a network.
11. The system of claim 8 , wherein the one or more processors are further configured to:
store the account access information as part of the distributed ledger.
12. The system of claim 8 , wherein the one or more processors are further configured to:
cause an encrypted identifier of the user to be stored as a record of the distributed ledger.
13. The system of claim 8 , wherein the one or more processors, to determine the one or more account security scores, are configured to:
determine the one or more account security scores based on using a machine learning model.
14. The system of claim 8 , wherein the one or more processors are further configured to:
perform an audit of records stored as part of the distributed ledger based on the one or more account security scores.
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 system, cause the system 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 types of 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; and
determine one or more account security scores based on providing the account access information as input to the smart contract.
16. The non-transitory computer-readable medium of claim 15 , wherein the distributed ledger is implemented by a tamper-resistant data structure.
17. The non-transitory computer-readable medium of claim 15 , wherein the one or more instructions further cause the system to:
provide the account access information to one or more nodes in a network.
18. The non-transitory computer-readable medium of claim 15 , wherein the one or more instructions further cause the system to:
store the account access information as part of the distributed ledger.
19. The non-transitory computer-readable medium of claim 15 , wherein the one or more instructions further cause the system to:
cause an encrypted identifier of the user to be stored as a record of the distributed ledger.
20. The non-transitory computer-readable medium of claim 15 , wherein the one or more instructions further cause the system to:
perform an audit of records stored as part of the distributed ledger based on the one or more account security scores.