FIELD

The present application relates to technically inventive, non-routine solutions that are necessarily rooted in computer technology and that produce concrete technical improvements. In particular, the present application relates to authentication based on network connection history.

BACKGROUND

As computer security becomes increasingly important, attempts at defeating such security are also becoming increasingly sophisticated. As such, certain traditional modes of ensuring security used alone are becoming increasingly insufficient for actually ensuring security. For instance, requiring a password for logging in to various user accounts does not provide a sufficient level of security anymore due to hacks of data centers storing such passwords as well as those passwords being intercepted during transmission when a user attempts to login. There are currently no adequate solutions to the foregoing computer-related, technological problem and, as recognized herein, there is a need for more dynamic and additional ways to perform electronic authentication.

SUMMARY

Accordingly, in one aspect a device includes at least one processor and storage accessible to the at least one processor. The storage includes instructions executable by the at least one processor to access a first network connection history for a second device different from the first device. The instructions are also executable to determine in a first instance whether to authenticate the second device based on the first network connection history and to authenticate the second device based on a determination to authenticate the second device.

The first network connection history may be accessed by being received via a network interface of the first device from the second device, and may include a Wi-Fi network connection history. Additionally or alternatively, the first network connection history may include a non-Wi-Fi network connection history such as a Bluetooth connection history, an automatic teller machine (ATM) connection history, a near-field communication (NFC) connection history, a virtual private network (VPN) connection history, and/or a wired ethernet connection history.

In some examples, the instructions may also be executable to determine in the first instance whether to authenticate the second device based on data in the first network connection history matching data in a second network connection history for the second device that was previously stored at a storage location accessible to the first device. The matching may include network connections indicated in the first network connection history matching network connections indicated in the second network connection history by order of connection and/or by timing of connection.

Also in some examples, the instructions may be executable to store the first network connection history, and may then be executable to access a third network connection history for the second device and determine in a second instance whether to authenticate the second device based on data in the third network connection history matching data in the stored first network connection history. In these examples, the matched data in the stored first network connection history may not be indicated in the second network connection history. Furthermore, the instructions may then be executable determine in the second instance whether to authenticate the second device based on data in the third network connection history matching the data in the stored first network connection history and based on data in the third network connection history matching data in the second network connection history.

Additionally, in some examples the instructions may be executable to, prior to the first instance, receive the second network connection history in a third instance, where the third instance pertains to authentication and involves authentication through at least two other methods not involving use of any network connection history.

In another aspect, a method includes accessing, at a first device, a first network connection history for a second device different from the first device. The method also includes determining in a first instance whether to authenticate the second device based on the first network connection history and, responsive to determining to authenticate the second device based on the first network connection history, authenticating the second device and permitting access to at least one resource.

In certain examples, the resource may include one or more of access to a Wi-Fi network, access to an email account, access to another account accessible over the Internet, access to a bank account, and/or access to an account indicating medical records.

Also, in some examples, the method may include appending a second network connection history received prior to the first instance with data in the first network connection history responsive to determining to authenticate the second device based on the first network connection history.

In another aspect, a computer readable storage medium (CRSM) that is not a transitory signal includes instructions executable by at least one processor to access, via a first device, a first network connection history associated with a second device different from the first device. The instructions are also executable to determine in a first instance whether to authenticate the second device based on the first network connection history and to authenticate the second device responsive to a determination to authenticate the second device based on the first network connection history.

The details of present principles, both as to their structure and operation, can best be understood in reference to the accompanying drawings, in which like reference numerals refer to like parts, and in which:

