Network security linkage
An approach for establishing and managing network security linkages is disclosed. The linkages may be used to facilitate management of accounts, goals, or resources of one or more entities, or to provide an integrated view of the circumstances of, for example, family members or other interrelated persons. A person receiving assistance with the management of one or more accounts need not disclose authentication credentials to persons helping manage the accounts, enhancing security. Members may view members and access accounts administered by separate computing systems without needing credentials for each member, account, and/or computing system. The multiple accounts (which may be held at multiple institutions) need not be accessed individually by each member of the network security linkage, saving time and computing resources of users.
1. A service provider computing system comprising one or more processors, the service provider computing system configured to:
identify, based on analysis of one or more audio files captured using at least one of a first user device of a first user or a second user device of a second user, a verbal trigger to form an authentication circle between the first user and the second user;
associate a first login credential with the first user such that the first login credential grants the first user access to a dashboard, and associate a second login credential with the second user such that the second login credential grants the second user access to the dashboard;
in response to verifying that a first entered credential submitted via a login screen of the dashboard corresponds to the first login credential, enable (i) selection of a third-party account of the first user that is secured by a third-party computing system such that successful login with the third-party computing system is required to access the third-party account, and (ii) selection of account permissions defining account functionality to be granted, through access to the dashboard, to users in the authentication circle;
receive, via the dashboard, a first input selecting to link the third-party account to the authentication circle, and a second input identifying a permission level restricting account functionality to be granted to the second user through the dashboard;
in response to the first and second inputs, link the third-party account of the first user to the authentication circle by:
transmitting, to the third-party computing system, a request to link the third-party account to the authentication circle; and
receiving, from the third-party computing system in response to the request, a security access token generated by the third-party computing system to grant the service provider computing system access to the third-party account;
transmit, to the third-party computing system, a first application programming interface (API) account access request with the security access token;
receive account data from the third-party computing system in response to the first API account access request;
present the account data to the first user via the dashboard;
in response to verifying a second entered credential received via the login screen of the dashboard corresponds to the second login credential, identify, in the dashboard, the first user, the second user, and the third-party account; and
present, via the dashboard, to the second user, the account data as restricted by the permission level, wherein the dashboard provides access to the third-party account through the dashboard using the first login credential and the second login credential without requiring users to directly connect to and authenticate with the third-party computing system, thereby enabling access by multiple users with different credentials to the third-party account at different permission levels via the dashboard of the service provider computing system.
2. The system of claim 1 , wherein the verbal trigger comprises a word or phrase indicating a desire of one user to share account access with another user without sharing login credentials.
3. The system of claim 1 , further configured to, in response to identifying the verbal trigger, transmit to the first user device a first request for authorization to establish the authentication circle.
4. The system of claim 3 , further configured to, in response to receiving authorization from the first user, transmit to the second user device a second request for authorization to establish the authentication circle.
5. The system of claim 1 , further configured to transmit, to the third-party computing system, a second API account access request with the security access token and receive account data from the third-party computing system in response to the second API account access request prior to presenting the account data to the second user via the dashboard.
6. The system of claim 1 , wherein the third-party account is a first account, and wherein the system is further configured to link a second account of the first user or the second user to the authentication circle.
7. The system of claim 6 , further configured to generate the dashboard so as to provide the first and second users access to the first and second accounts via the first and second login credentials, respectively.
8. The system of claim 6 , wherein the dashboard is configured to enable a transaction involving both the first and second accounts.
9. The system of claim 1 , wherein the authentication circle defines a first role for the first user and a second role for the second user, wherein the dashboard is configured to provide users with the first role a first set of functionalities and provide users with the second role a second set of functionalities.
10. The system of claim 1 , wherein each user of the authentication circle is assigned a different permission level, and wherein the dashboard is configured to provide each user of the authentication circle with different account details based on the different permission level.
11. The system of claim 1 , further configured to receive, from at least one of the first user device or the second user device, one or more audio files with sounds captured using at least one of a first audio sensor of the first user device or a second audio sensor of the second user device, respectively, wherein sounds in the one or more audio files are analyzed to identify the verbal trigger.
12. The system of claim 11 , further configured to:
detect a sound signature indicative of an event involving at least one of the first and second users, the sound signature having been captured using at least one of the first audio sensor of the first user device or the second audio sensor of the second user device; and
generate, responsive to detecting the sound signature, a prompt in the dashboard to propose adding at least one of a second account or a third user to the authentication circle.
13. The system of claim 11 , wherein the second account is administered by the service provider computing system.
14. The system of claim 11 , wherein each of the first account and the second account is administered by a different third-party computing system other than the service provider computing system.
15. A computer-implemented method comprising:
identify, based on analysis of one or more audio files captured using at least one of a first user device of a first user or a second user device of a second user, a verbal trigger to form an authentication circle between the first user and the second user;
associating a first login credential with the first user such that the first login credential grants the first user access to a dashboard, and associating a second login credential with the second user such that the second login credential grants the second user access to the dashboard;
in response to verifying that a first entered credential submitted via a login screen of the dashboard corresponds to the first login credential, enabling (i) selection of a third-party account of the first user that is secured by a third-party computing system such that successful login with the third-party computing system is required to access the third-party account, and (ii) selection of account permissions defining account functionality to be granted, through access to the dashboard, to users in the authentication circle;
receiving, via the dashboard, a first input selecting to link the third-party account to the authentication circle, and a second input identifying a permission level restricting account functionality to be granted to the second user through the dashboard;
in response to the first and second inputs, link the third-party account of the first user to the authentication circle by:
transmitting, to the third-party computing system, a request to link the third-party account to the authentication circle; and
receiving, from the third-party computing system in response to the request, a security access token generated by the third-party computing system to grant the service provider computing system access to the third-party account;
transmitting, to the third-party computing system, a first API account access request with the security access token;
receiving account data from the third-party computing system in response to the first API account access request;
presenting the account data to the first user in the dashboard via the dashboard;
in response to verifying a second entered credential received via the login screen of the dashboard corresponds to the second login credential, identifying, in the dashboard, the first user, the second user, and the third-party account;
presenting, via the dashboard, to the second user, the account data as restricted by the permission level, wherein the dashboard provides access to the third-party account through the dashboard using the first login credential and the second login credential without requiring users to directly connect to and authenticate with the third-party computing system, thereby enabling access by multiple users with different credentials to the third-party account at different permission levels via the dashboard.
16. The computer-implemented method of claim 15 , wherein the verbal trigger comprises a word or phrase indicating that a desire to share account access without sharing login credentials.
17. The computer-implemented method of claim 15 , further comprising, in response to identifying the verbal trigger, transmitting to the first user device a first request for authorization to establish the authentication circle, and transmitting to the second user device a second request for authorization to establish the authentication circle.
18. The computer-implemented method of claim 15 , wherein the third-party account is a first account, and wherein the method further comprises linking a second account of the first user or the second user to the authentication circle, and generating the dashboard so as to provide the first and second users access to the first and second accounts via the first and second login credentials, respectively.
19. The computer-implemented method of claim 15 , wherein the dashboard is configured to enable a transaction involving both the first and second accounts.
20. The computer-implemented method of claim 15 , further comprising:
detecting a sound signature indicative of an event involving at least one of the first and second users, the sound signature having been captured using at least one of a first audio sensor of the first user device or a second audio sensor of the second user device; and
generating, responsive to detecting the sound signature, a prompt in the dashboard to propose adding at least one of a second account or a third user to the authentication circle.