US20130185775A1 - Multi factor authentication - Google Patents
Multi factor authentication Download PDFInfo
- Publication number
- US20130185775A1 US20130185775A1 US13/751,420 US201313751420A US2013185775A1 US 20130185775 A1 US20130185775 A1 US 20130185775A1 US 201313751420 A US201313751420 A US 201313751420A US 2013185775 A1 US2013185775 A1 US 2013185775A1
- Authority
- US
- United States
- Prior art keywords
- user
- factor authentication
- authentication information
- network
- instance
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Abandoned
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L63/00—Network architectures or network communication protocols for network security
- H04L63/08—Network architectures or network communication protocols for network security for authentication of entities
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L63/00—Network architectures or network communication protocols for network security
- H04L63/08—Network architectures or network communication protocols for network security for authentication of entities
- H04L63/0869—Network architectures or network communication protocols for network security for authentication of entities for achieving mutual authentication
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L63/00—Network architectures or network communication protocols for network security
- H04L63/18—Network architectures or network communication protocols for network security using different networks or channels, e.g. using out of band channels
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L63/00—Network architectures or network communication protocols for network security
- H04L63/16—Implementing security features at a particular protocol layer
- H04L63/166—Implementing security features at a particular protocol layer at the transport layer
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L63/00—Network architectures or network communication protocols for network security
- H04L63/16—Implementing security features at a particular protocol layer
- H04L63/168—Implementing security features at a particular protocol layer above the transport layer
Definitions
- Internet access has become ubiquitous. In addition to traditional dial-up and Local Area Network-based network access, wireless access technologies including IEEE 802.11b and 802.11g (WiFi), WiMax, BluetoothTM, and others are being widely deployed. Many public locations, such as airports, bookstores, coffee shops, hotels, and restaurants have free or fee-based access to wireless Internet service. Some locations, such as hotel rooms, also offer internet access via Ethernet ports. In addition, businesses offer visiting professionals access to Internet service while they are on the premises.
- Such Internet access services typically are not secured at the datalink layer. It is often possible for network administrators, other users, or even criminals to capture and view network transmissions made on these networks.
- the “last mile”, or the few hops on the network that are closest to the end user, are often only lightly secured, if at all, and are particularly vulnerable to traffic snooping. Enhanced communication security would find utility.
- Authentication refers to a process by which a user makes his or her identity known to a system or application which the user is attempting to access, and occasionally, also the process by which the user verifies the identity of the system being accessed.
- a common authentication technique involves the use of a shared username and password combination. This style of authentication is vulnerable to a number of weaknesses. For example, passwords must be made long enough to be secure while being short enough to be memorable. Additionally, the loss of the password is sufficient to allow an attacker to gain access to the system by impersonating the user. Therefore, additional authentication techniques would find utility.
- FIG. 1 is a schematic illustration of a networked computing environment in accordance with an embodiment.
- FIG. 2 is a schematic illustration of a server in accordance with an embodiment.
- FIGS. 3-8 are flow diagrams of embodiments of methods for secure network computing.
- FIG. 9 is a schematic illustration of a networked computing environment in accordance with an embodiment.
- FIG. 10 is a flow diagram of embodiments of a method for multifactor authentication.
- FIG. 11 is a schematic illustration of and embodiment of a data file which may be used in a multifactor authentication.
- Described herein are exemplary systems and methods for secure network computing and multifactor authentication.
- the methods described herein may be embodied as logic instructions on a computer-readable medium. When executed on a processor, the logic instructions cause a general purpose computing device to be programmed as a special-purpose machine that implements the described methods.
- the processor when configured by the logic instructions to execute the methods recited herein, constitutes structure for performing the described methods.
- FIG. 1 is a schematic illustration of a networked computing environment in accordance with an embodiment.
- one or more client computing devices 110 a, 110 b, 110 c establish a communication connection with a point of presence (POP) server 130 , which in turn communicates with one or more target servers 140 , 142 , 144 via a network 120 .
- POP point of presence
- Target servers 140 , 142 , 144 provide access to one or more computing resources such, as, e.g., internet services, electronic mail services, data transfer services, and the like.
- Client computing devices 110 a, 110 b, 110 c may be any computer-based communication device, including a personal computer 110 a, a personal digital assistant (PDA) 110 b, or a terminal device 110 c.
- Client computing devices 110 a, 110 b, 110 c establish a communication with POP server 130 via a communication network, which may be the same network 120 or a separate communication network.
- the particular form of communication network is not important.
- Communication network may comprise one or more direct communication links (e.g., a dial-up connection) between respective remote access devices 110 a, 110 b, 110 c.
- the communication network may comprise a private data network such as, e.g., an X.25 network, a local area network (LAN), a wide area network (WAN), or a public network such as, e.g., the Internet.
- POP server 130 may be implemented by a general purpose computing device such as, e.g., a server, that executes logic instructions which cause the processor to execute various methods for performing secure network computing.
- FIG. 2 is a schematic illustration of an exemplary computer system 200 adapted to perform secure network computing.
- the computer system 200 includes a computer 208 and one or more accompanying input/output devices 206 including a display 202 having a screen 204 , a keyboard 210 , other I/O device(s) 212 , and a mouse 214 .
- the other device(s) 212 can include a touch screen, a voice-activated input device, a track ball, and any other device that allows the system 200 to receive input from a developer and/or a user.
- the computer 208 includes system hardware 220 and random access memory and/or read-only memory 230 .
- a file store 280 is communicatively connected to computer 208 .
- System hardware 220 includes a processor 222 and one or more input/output (I/O) ports 224 .
- File store 280 may be internal such as, e.g., one or more hard drives, or external such as, e.g., one or more external hard drives, network attached storage, or a separate storage network.
- Memory 230 includes an operating system 240 for managing operations of computer 208 .
- operating system 240 includes a hardware interface module 254 that provides an interface to system hardware 220 .
- operating system 240 includes one or more file systems 250 that managed files used in the operation of computer 208 and a process control subsystem 252 that manages processes executing on computer 208 .
- Operating system 240 further includes a system call interface module 242 that provides an interface between the operating system 240 and one or more application modules 262 and/or libraries 264 .
- one or more application modules 260 executing on computer 208 make calls to the system call interface module 242 to execute one or more commands on the computer's processor.
- the system call interface module 242 invokes the services of the file systems 250 to manage the files required by the command(s) and the process control subsystem 252 to manage the process required by the command(s).
- the file system 250 and the process control subsystem 252 invoke the services of the hardware interface module 254 to interface with the system hardware 220 .
- Operating system 240 may be embodied as a UNIX operating system or any derivative thereof (e.g., Linux, Solaris, etc.) or as a Windows® brand operating system.
- memory 230 includes one or more network interface modules 262 , 268 , one or more secure tunnel modules 264 , and one or more communication management modules 266 .
- Network interface modules may be implemented as web browsers such as, e.g., Internet Explorer, Netscape, Mozilla, or the like.
- Secure tunnel module 264 comprises logic instructions which, when executed by a processor, configure the processor to generate a secure communication tunnel between the POP server 130 and a client computing device such as, e.g., one or more of client computing devices 110 a, 110 b, 110 c.
- Communication management module 266 comprises logic instructions which, when executed by a process, configure the processor to manage communications between the POP server 130 and one or more client computing devices 110 a, 110 b, 110 c and between the POP server 130 and the one or more servers 140 , 142 , 144 .
- POP server 130 receives a service request from a client computing device such as, e.g., one or more of client computing devices 110 a, 110 b, 110 c, identifying one or more resources available on a server such as 140 , 142 , 144 .
- the service request may be embodied as a Uniform Resource Locator (URL) transmitted to POP server 130 from a browser executing on a client computing device.
- POP server 130 establishes a first communication link between the POP server 130 and the one or more resources available via a computing network identified in the service request.
- POP server 130 may launch an independent request for the resource request for the resource identified in the service request from the client computing device.
- POP server 130 may further establish a first, secure communication link between the POP server 130 and the client computing device 110 a, 110 b, 110 c, and connect a network interface module on the client computing device to the secure communication link.
- POP server 130 may further manage communication activity between the client computing device and the one or more resources available via a computing network at the POP server.
- managing communication activity may include passing information received from a server 140 , 142 , 144 in response to a resource request from the POP server 130 to a client computing device 110 a, 110 b, 110 c via a secure communication link.
- FIGS. 3-8 are flow diagrams of embodiments of methods for secure network computing.
- FIG. 3 is a flow diagram illustrating high-level operations executed by a computing device such as one of client computing devices 110 a, 110 b, 110 c in a method for secure network computing.
- a secure communication link is initialized between POP server 130 and the client computing device 110 a, 110 b, 110 c.
- the client computing device sends outbound data via the secure communication link and at operation 320 the client computing device receives inbound data via the secure communication link.
- FIG. 4 is a flow diagram illustrating operations in a method for initializing a secure communication link between POP server 130 and a client computing device 110 a, 110 b, 110 c.
- POP server 130 implements an application tunneling technology, referred to herein as an AppTunnel, to construct a secure communication tunnel between POP server 130 and a client computing device 110 a, 110 b, 110 c.
- AppTunnel application tunneling technology
- POP server 130 receives an address of one or more resources such as, e.g., a website or other resource available on network 120 .
- the address received may represent a URL received in a service request from a web browser executing on client computing device 110 a, 110 b, 110 c.
- POP server 130 transmits an ActiveX control comprising launch data to client computing device 110 a, 110 b, 110 c.
- the ActiveX control client may be replaced with a plug-in module compatible with other protocols such as, for example, the JAVA architecture or a CORBA architecture.
- the client computing device 110 a, 110 b, 110 c receives the ActiveX launch data from server 130 . If, at operation 425 the client computing device is not compatible with ActiveX technology, then control passes to operation 465 and a rewriter host module may be activated. This procedure is explained in greater detail below.
- control passes to operation 430 and the client computing device 110 a, 110 b, 110 c, activates an ActiveX control host page.
- the Active X control host page instructs the browser how to load the ActiveX control, where to retrieve it from (if it is not already locally cached), and with what parameters the control should be started.
- a similar host page may be used to embedding plug-ins into other browsers such as Mozilla, Netscape, etc. This information may be contained in an HTML ⁇ OBJECT> tag.
- the client computing device 110 a, 110 b, 110 c initiates the ActiveX control received from the server 130 .
- the ActiveX control causes the client computing device 110 a, 110 b, 110 c to launch a new incidence of a browser or other network interface software (operation 440 ). If additional ActiveX controls are necessary to enable the client computing device 110 a, 110 b, 110 c, then one or more additional ActiveX controls maybe transmitted between the server 130 and the client computing device 110 a, 110 b, 110 c.
- the client attaches a secure channel module to the browser.
- the secure channel module may be embodied as an AppTunnel client module.
- the AppTunnel secure channel module is described in detail in U.S. patent application Ser. No. 10/737,200, incorporated by reference here above. Portions of that description are excerpted in the following paragraphs.
- Application tunneling is a method for transporting data from a user's computer to a third party computer (a “proxy”).
- Application data may be intercepted as soon as it is sent (i.e., above layer 4 of the OSI model), before it is encapsulated by Internet protocols such as TCP, UDP, or IP. Data may then be transported across the network to the proxy.
- this application-level data is acquired differently (perhaps, for example, through the use of a virtual adapter). In all cases, it is application-level data (OSI layers 5-7, depending on the application and the protocol) that is tunneled via AppTunnels.
- AppTunnels is application tunneling technology that tunnels data from an application on a first computer to a second computer, perhaps over a secure tunnel, for further processing and proxying at that other computer.
- AppTunnels technology may be implemented in a Static form or in a Dynamic form. Static AppTunnels technology requires manual (or pre-configured) establishment of the application tunnels and listeners. By contrast, dynamic AppTunnels implements on-the-fly tunnel creation using hook mechanisms.
- Encryption and/or other security technologies may be applied to the tunnel to add security to the data being transported, although this is not strictly necessary.
- AppTunnels differs from existing tunneling technologies such as Generic Routing Encapsulation (GRE) in that it is designed to operate at the end user's computer, in such a way that the end user's applications do not have to be informed about the existence of the tunneling technology.
- GRE Generic Routing Encapsulation
- tunneling technologies such as GRE, on the other hand, are designed to be implemented in network elements such as routers.
- AppTunnels differs from host-based encryption technologies such as SSL in several ways.
- SSL technology must be directly supported by the application in order to be applied. AppTunnels, however, does not require application awareness in order to be applied.
- SSL is closely tied to a particular security and encryption architecture. AppTunnels may be used with or without security technologies, and imposes no requirements on the underlying security technologies. AppTunnels has been used in conjunction with the WTP security protocol and with SSL.
- a local listener is created and a tunnel is established between the first computer and the second computer.
- a local listener may be implemented as listening TCP, UDP, or other socket(s) bound to a local host address (e.g., 127.0.0.1) on a computer.
- the port number where applicable, may be determined by the tunneled application, and may be arbitrary in some protocols.
- Local listeners may be created either in response to instructions from dynamic AppTunnels hooks or by static configuration received in advance. It is also possible for a user to manually initiate the creation of a listener (and its associated tunnel).
- a data tunnel may be created between the AppTunnels client software and a compatible tunnel module on a server. In one embodiment, the tunnel may be implemented in accord with the WTP protocol described in U.S. patent application Ser. No. 10/737,200.
- the end user application can be directed to connect to the AppTunnel.
- the process for this varies per application.
- Dynamic AppTunnels no other action is necessary; data simply starts flowing from the application to the AppTunnels software, which in turn tunnels the data across the connection to the WTP concentrator.
- the application is tricked into connecting to the local listener instead of to the target server, as would otherwise naturally be the case.
- the DNS system is configured to return the localhost address (127.0.0.1, usually) to requests for the destination server's IP address. This is usually done by changing the locally-present “hosts” file that the computer's DNS system consults before returning an IP address. This hosts file is modified, with an entry being inserted for the name of the target server with the IP address of localhost.
- the AppTunnels client may be implemented as an executable component that is incorporated into and run by the user's web browser such as, e.g., an ActiveX control. For other browsers or other platforms, a Netscape Plugin may be used.
- AppTunnels implements a method of intercepting traffic in order to tunnel it is as follows: First, the computer's DNS resolution system is modified to re-route traffic for target network servers to the local computer. Next, the AppTunnels Client establishes itself as a server on the port that the application would expect to connect to. Once established, applications transparently connect to the Client on the local computer rather than to their natural target-network servers. No configuration or modification of the tunneled application is necessary.
- the AppTunnels method can be used to tunnel any user-mode data over a tunnel to the server 130 .
- This includes TCP and UDP on all platforms.
- Other protocols may be available for tunneling, depending on the platform.
- the AppTunnels architecture supports complex network protocols such as FTP, RPC, H.323, and other proprietary multi-connection protocols. It provides this support by inspection of protocol data at the server.
- a protocol may be termed ‘complex’ if it requires more than a simple client-to-server TCP connection.
- the client computing device 110 a, 110 b, 110 c receives a module called the AppTunnels Client, which attaches to the web browser.
- the AppTunnels client enables the web browser to access target network web pages by proxying requests through the AppTunnels client.
- the AppTunnels client forwards the requests to the server 130 , which retrieves the requested document and returns it to the AppTunnels client, which in turn returns it to the web browser.
- the client computing device 110 a, 110 b, 110 c first reads the proxy settings configuration from the user's web browser.
- the client computing device 110 a, 110 b, 110 c stores the proxy settings and configures the browser to use a proxy auto-configuration file.
- This file instructs the browser to request its new proxy settings from the AppTunnels client. The request is made and replied to, and the new settings cause all further requests for documents to be proxied through the AppTunnels client.
- the AppTunnels client then establishes a connection to server 130 and authenticates itself. After authentication, the AppTunnels client establishes itself as a server application and listens for incoming requests from the browser. As requests are received, they are forwarded to server 130 . Responses are read in from the server and are sent back to the waiting browser.
- the browser is monitored by Dynamic AppTunnels for any network communication attempts.
- these attempts may be monitored using function call hooks of the Microsoft Winsock library, but other hooks are possible, as are other monitoring architectures (such as, for example, Winsock Layered Service Providers).
- function call hooks of the Microsoft Winsock library but other hooks are possible, as are other monitoring architectures (such as, for example, Winsock Layered Service Providers).
- Winsock Layered Service Providers such as, for example, Winsock Layered Service Providers.
- Child processes created by the browser may be injected with the Dynamic AppTunnels monitoring code.
- Child process monitoring may be implemented using an API hook for all of the CreateProcess( ) family of functions.
- the Dynamic AppTunnels code receives it first, and ensures that the monitoring code is injected in the resulting new process.
- dynamic AppTunnels technology is implemented using API hooks.
- dynamic AppTunnels receives a request to start a tunneled process, it creates a new process using the CreateProcess( ) API call.
- a new process may be created as suspended, so that the process does not run after it is initially created.
- one or more imported functions are substituted, or hooked, such that they point to wrapper functions that are part of the Dynamic AppTunnels software.
- the hooked functions are of two classes: network functions and process management functions.
- the CreateProcess( ) function (and its relatives) may be hooked so that any child processes that are created can have the Dynamic AppTunnels monitoring code injected as well.
- This code is responsible for signaling the browser plugin that it should inject the rest of the hooks into the newly created process. Any child processes of that child are treated in the same way.
- the networking functions that are hooked are related to connection requests and to name resolution requests. In general, all functions that are called during initial connection setup are intercepted. Once hooked, these functions receive any connection requests, and use this information for two purposes. The first is to coordinate with the tunneling protocol on the AppTunnel server to create an additional AppTunnel between the client and the AppTunnel server, and to create a local listener that is attached to that tunnel. The second is to re-direct the requesting application to the local listening socket, so that connections are made it instead of to the original target server. This process allows network traffic generated by the client to be captured by the browser plug-in and tunneled.
- the plug-in may choose to examine the connection request information and make a decision at runtime as to whether the traffic should be tunneled or allowed to go straight out to the network as it otherwise would have. These decisions can be based on names (such as DNS or WINS names), network addresses, port numbers, or other identifying information. While this description has largely been written in the context of TCP sockets, it should be pointed out that other kinds of network traffic may be supported, including UDP and raw IP packets.
- the browser instantiated at the client computing device 110 a, 110 b, 110 c loads the requested resource, which may be displayed on a suitable user interface such as, e.g., a computer screen or the like.
- a suitable user interface such as, e.g., a computer screen or the like.
- subsequent data transfer operations between the client computing device 110 a, 110 b, 110 c and the server 130 are conveyed through the secure tunnel.
- the browser may be closed. Closing the browser also closes any dynamic AppTunnels constructed between the client computing device 110 a, 110 b, 110 c and the server 130 .
- FIG. 5 is a flow diagram illustrating operations in a method for implementing an AppTunnel on a client computing device 110 a, 110 b, 110 c.
- the ActiveX control transmitted from the server 130 to the client computing device operations of FIG. 5 may cause the client computing device to perform the operations illustrated in FIG. 5 .
- the AppTunnels plugin i.e., the ActiveX control
- receives a request to start an application For example, the plugin may receive a request to start an instance of a browser.
- AppTunnels can operate in either a static mode or in a dynamic mode. The difference is in the way the data is acquired for tunneling.
- Static AppTunnels uses a static local listening TCP/IP socket for each pre-configured service. If a user wants to use a web browser over a static AppTunnel, for example, there must be a configured application tunnel listening on TCP port 80 on the local host. Furthermore, the destination address for the AppTunnel must be specified.
- the DNS system of the client computing device is configured (usually using the computer's hosts file) to change the IP address of the server in question to point to the local host (usually 127.0.0.1), thereby fooling the application into making a local connection to the listening socket.
- creating a new process may involve a user clicking an HTML link on the web page in a browser executing on the client computing device.
- the ActiveX control then launches the new process and injects the Dynamic AppTunnels application monitoring code into the newly started process (operation 545 ).
- a new AppTunnel is created between the client computing device and the server 130 .
- the data received in the AppTunnel is removed and passed to the process (i.e., the web browser) for further processing and presentation to a user via a suitable interface such as, e.g., a display.
- Operations 560 - 565 may be repeated until, at operation 570 , there is no more data to tunnel, whereupon operations terminate.
- FIG. 6 is a flow diagram illustrating operations in a method for processing outbound traffic from a network interface module such as, for example, a web browser executing on a client computing device 110 a, 110 b, 110 c.
- the operations of FIG. 6 depict traffic processing for a browser that has an AppTunnel module attached to the browser.
- the web browser receives an address of a resource available on network 120 .
- the address may represent a Uniform Resource Locator (URL) of a resource available on network 120 .
- URL Uniform Resource Locator
- the browser initiates a service request for the resource.
- the service request is intercepted by the AppTunnel module.
- the AppTunnel client secures the request data and at operation 630 the AppTunnel client forwards the request to the POP server 130 .
- the secured request is received at the POP server 130 .
- the secure tunnel module 264 i.e., the AppTunnel server extracts the request data from the secure tunnel.
- the POP server forwards the service request to the address identified in the service request.
- the service request is received in a first network interface module 262 instantiated on POP server 130 , and POP server 130 instantiates a second network interface module 268 and launches a service request from the second network interface module.
- FIG. 7 is a flow diagram illustrating operations in a method for processing inbound traffic such as, for example, one or more resources returned from a service request.
- the data returned by the resource request is received at the POP server 130 .
- the data is received in the second network interface module 268 instantiated on the POP server 130 .
- the response data is secured.
- response data is operated on by the secure tunnel module 264 .
- the response data is placed in the secure tunnel to the client computing device 110 a, 110 b, 110 c via the first network interface module 262 .
- the client receives the response data transmitted to the client by the server.
- the data is removed from the secure tunnel established by AppTunnels.
- the AppTunnels client attached to the browser in the client computing device 110 a, 110 b, 110 c removes the received data from the tunnel and, at operation 735 , forwards the data to the web browser.
- the web browser may present the data on a user interface such as, e.g., a display, for viewing by the user.
- URL rewriting is a method of providing a reverse proxy server for use in secure remote access systems and other applications without the need for any locally installed code.
- Most web browsers can exchange traffic with web servers using a protocol known as secure HTTP, or HTTPS. However, most websites do not support HTTPS. To add security to every website the user requests, special HTTPS requests are made to a URL rewriter server instead of the target web server, using HTTPS to the rewriter.
- the rewriter then forwards the request to the target web server by proxy, using the expected destination protocol of the web server (typically HTTP). On return, the web data is returned over HTTPS to the client's browser.
- HTTP the expected destination protocol of the web server
- any other form of browser-based security, or no security whatsoever, could be used in the communications link to the rewriter.
- references to other web data will now cause the user's browser to make direct requests to the target server, rather than ask the rewriter server.
- references to other web content may be rewritten in the webpage so that they refer to the rewriter instead of to the target server to ensure that all web traffic is routed through the rewriter, and not via direct connections. Accordingly, any web references in the returned document are rewritten with references to the URL rewriter server.
- FIG. 8 is a flow diagram illustrating operations in a method for processing inbound traffic such as, for example, one or more resources returned from a service request.
- a rewriter host page on the client computing device 110 a, 110 b, 110 c launches a second web browser using instructions embedded in the HTML and JavaScript code that is a part of the page.
- the rewritten URL is written into the second browser.
- the second browser requests the specified resource using the rewritten URLs.
- the server 130 receives the service request from the client computing device 110 a, 110 b, 110 c.
- the server 130 un-rewrites the URL, and at operation 835 the server retrieves the requested resource from the server 140 , 142 , 144 hosting the resource on the network 120 .
- the server rewrites the embedded URLs in the retrieved resource, and at operation 845 the server returns the rewritten resource to the client.
- processing the requested resource may include presenting the resource on a suitable display. If at operation 855 there are more requests to be processed, then control passes back to operation 820 , and the browser requests the specified resource(s). By contrast, if at operation 855 there are no further resource requests, then the process terminates.
- FIGS. 3-8 enable a client device such as one or more of client computing devices 110 a, 110 b, 110 c to establish a secure “last mile” communication link, thereby enabling secure communication with resources hosted by one or more servers 140 , 142 , 144 in a network 120 .
- the systems and methods described herein are agnostic regarding the type of encryption applied (if any) to communication links between POP server 130 and servers 140 , 142 , 144 .
- a client computing device 110 a, 110 b, 110 c may download and install a permanent piece of client encryption module onto the end user's computer.
- the permanent client provides encryption services between the client computing device 110 a, 110 b, 110 c and the servers 140 , 142 , 144 .
- a permanent client encryption module With a permanent client encryption module, the end user does not have to navigate to the service provider's website in order to turn on secure surfing. Further, a client-based approach can support all Internet-based applications.
- an ActiveX control installs and initializes a virtual VPN Miniport, as described in U.S. patent application Ser. No. 10/737,200.
- the ActiveX control captures and processes any relevant traffic on the computer. In this way, end user traffic is directed into the secured tunnel described above.
- a virtual VPN Miniport can support non-TCP protocols, while maintaining the convenience of a web-based environment. It can also secure applications that have already been started. For example, if the end user were running an instant messaging client, that client's communications would be secured from the time of connection forward, without a need to re-launch the client. Installation of a VPN driver can be silent and automatic, and only needs to occur one time. From that point on, the ActiveX control activates the VPN driver and manages network routes to cause traffic to be directed into the VPN driver for encryption.
- Access to the POP server 130 may be provided by a number of methodologies. In one embodiment access to POP server 130 may be provided on a pay-for-service business model.
- POP server 130 may include a transaction processing module to process payment transactions, e.g., by a credit card or other payment mechanism. Charges may be levied on the basis of bandwidth consumed, or by a time parameter (i.e., minutes, hours, days, years, etc.).
- access to server 130 may be implemented on the basis of advertising revenue.
- pay-per-click advertising can be implemented, using randomly-selected advertisements
- pay-per-click advertising can be implemented, using information gained by inspecting the user's traffic during secure surfing to select targeted advertisements
- traditional Internet banner advertisements can be inserted, either randomly or based on inspection of the secured data. Advertisements can be inserted in the initial service provider web page, in the refreshed web page that hosts the ActiveX control, or even inline with the displayed web pages.
- Service levels may be differentiated by one or more facts such as, for example throughput (i.e., a performance aspect might be controlled), bandwidth (i.e., the total number of bytes transferred might be capped), data transfer (i.e., a transfer cap might be imposed per day, per month, or per year), or some combination thereof.
- throughput i.e., a performance aspect might be controlled
- bandwidth i.e., the total number of bytes transferred might be capped
- data transfer i.e., a transfer cap might be imposed per day, per month, or per year
- Other options include allowing only a limited amount of time to use the system or bandwidth in a tier or a certain amount of throughput for a certain amount of time, with decreased throughput after the elapse of that time, or restricting access to certain resources based on the service level.
- Last-mile encryption service may be provided to a user with no pre-existing account.
- the web-based interface can be used simply by entering the address of a website that is to be securely accessed.
- the user logs in anonymously using the supplied anonymous login method.
- Anonymous users may be granted a different tier of service, as described above.
- cookie-based, form-based, or IP address-based information may be used to correlate the anonymous user's browsing activities, for purposes including providing advanced service features (such as browsing history, enhanced status reporting, etc), selecting relevant advertising, or for other purposes.
- Users that desire temporary top-tier service may be given the option of paying electronically for a one-time use of the service without creating an account.
- Users that wish to use the service repeatedly may wish to create a user account.
- the user account could then be used to track browsing history, make more intelligent decisions about advertising content to be presented, or offer other value-added services.
- Users of the service would then be prompted to log in to the website (or to the downloaded client software) using the established authentication credentials.
- a cookie-based login persistence mechanism can be supported, allowing the user to go for a period of time without the need to log in.
- multifactor authentication techniques which may be used alone, or in combination with other security techniques described herein to provide secure access to resources in a computer network.
- Embodiments of multifactor authentication techniques will be described in the context of a computer network similar to the network described in with reference to FIG. 1 . It will be understood, however, that authentication techniques as described herein may be implemented in a wide variety of computer networks.
- FIG. 9 is a schematic illustration of a networked computing environment in accordance with an embodiment.
- one or more client computing devices 910 a, 910 b, 910 c, 910 d, 910 e establish a communication connection with an authentication server 930 , which in turn communicates with one or more target servers 940 , 942 , 944 via a network 920 .
- Target servers 940 , 942 , 944 provide access to one or more computing resources such, as, e.g., internet services, electronic mail services, data transfer services, and the like.
- Client computing devices 910 a, 910 b, 910 c, 910 d, 910 e may be any computer-based communication device, including a personal computer 910 a, a personal digital assistant (PDA) 910 b, a terminal device 910 c, a mobile telephone 910 d, or a land-line telephone 910 e.
- Client computing devices 910 a, 910 b, 910 c, 910 d, 910 e establish a communication with authentication server 930 via a communication network, which may be the same network 920 or a separate communication network. The particular form of communication network is not important.
- Communication network may comprise one or more direct communication links (e.g., a dial-up connection) between respective remote access devices 910 a, 910 b, 910 c, 910 d, 910 e.
- the communication network may comprise a private data network such as, e.g., an X.25 network, a local area network (LAN), a wide area network (WAN), or a public network such as, e.g., the Internet.
- Authentication server 930 may be embodied as a computing device, substantially as described in with reference to FIG. 2 , above.
- the computing device 200 and comprise one or more authentication modules 269 which may execute when as an application module and the memory 230 of the computing system 200 .
- the authentication module 269 and implemented logic instructions which, when executed by a processor such as the processor 222 , cause the authentication module 269 to implement multifactor authentication procedures to manage access to one or more resources of the computer network 920 , such as for example, resources provided by servers 940 , 942 , or 944 .
- the authentication server 930 implements a first authentication process in response to an authentication request from a client computing device such as one of client computing devices 910 a, 910 b, 910 c, 910 d, 910 e. If the first authentication process is successful, then the authentication server 930 originates a second authentication request to a client device such as one of client computing devices 910 a, 910 b, 910 c, 910 d, 910 e. In some embodiments, the authentication request from the client is transmitted through a first communication channel and the second authentication request originated by the authentication server 930 is transmitted using a second communication channel, different from the first communication channel.
- the authentication server 930 may process the response to the second authentication request and allow or deny access to a resource based on the response.
- the first communication channel and the second communication channel may be across separate communication networks.
- the first communication channel may be across the computer network, while the second communication channel may be across a telephone network.
- a first client initiates a primary authentication request for access to a resource provided by computer network 920 .
- the primary authentication request may include a username and password combination associated with a user and/or a device from which the primary authentication request is originated.
- the primary authentication request may be transmitted to the authentication server 930 to a first communication channel.
- the authentication server 930 receives the primary authentication request, and at operation 1020 the authentication server 930 processes the primary authentication request.
- the authentication server 930 performs a centralized authentication function which manages authentication to one or more resources and network 920 .
- authentication server 930 may maintain a data file comprising username and password combinations which may be associated with one or more resources of the computer network 920 .
- FIG. 11 is a schematic illustration of and embodiment of a data file which may be used in a multifactor authentication. Referring briefly to FIG. 11 , the illustrated data file 1100 includes a column for usernames, a column for passwords, and a column for approved resources. Usernames and passwords may be logically associated with the approved resource indicated in the table 1100 . A single username may be associated with multiple passwords for different approved resources.
- processing the primary authentication request may comprise searching the data file 1100 maintained by the authentication server for a username and password combination that corresponds to the username and password combination receipt in the primary authentication request.
- an operation 1025 the primary authentication request is unsuccessful, i.e., if there is no corresponding username and password combination in the data table 1100 , then the authentication server 930 denies the requester access to network resource(s). In some embodiments, the authentication server 930 may transmit an error message to the requester indicating that the username and password are invalid. Control that returns to operation 1015 and the authentication server 930 continues to monitor for another primary authentication request.
- the secondary authentication request is transmitted from the authentication server 930 to the user via a second communication channel, different from the first communication channel.
- the secondary authentication request is transmitted from the authentication server 930 to a second client in the user's possession.
- the user may initiate the primary authentication request from a computing device such as a desktop computer or laptop computer and the authentication server 930 may transmit the secondary authentication request by initiating a telephone call to a telephone registered to the user.
- a user may register, via a suitable user interface, a contact number to which the secondary authentication request may be transmitted from the authentication server 930 .
- the authentication server 930 may initiate a call to contact number indicated in the data table 1100 . It should be noted that a user may provide different contact numbers for different resources.
- the secondary authentication request is received at the second client.
- the secondary authentication request may comprise a voice message which makes a request for information to authenticate the user.
- the system may allow a user to prerecord a customized secondary authentication request in the user's own voice. For example, the user may record a message requesting a specific sequence of keystrokes or requesting the user to speak to a specific word or group of words. Having a user recorded message in the second authentication request helps to authenticate the system to the user, thereby eliminating or at least reducing the likelihood of a “man in the middle” attack on the system.
- a user may select one or more tokens to be presented with a secondary authentication requests.
- a token may include a predetermined word or character or numeric sequence selected by the user.
- the user response to the secondary authentication request initiated by the authentication server 930 may respond by pressing a predetermined sequence of keystrokes on a telephone keypad, or by pressing the pound key or the star key.
- the user may respond by speaking a predetermined word or series of words.
- the user need not provide an affirmative response; simply answering the telephone call may suffice as a response.
- the secondary authentication request initiated by the authentication server 930 may be implemented as a text message rather than a telephone call. Accordingly, the response to the secondary authentication request may also be implemented as a text message in which the user transmits a predetermined character or series of characters back to the authentication server 930 .
- the secondary authentication request may require a user to initiate a call back in order to authenticate the user.
- the secondary authentication request may transmit a text message or a voice call requesting the user to call back to the system to authenticate the user.
- a return phone number may be included with the secondary authentication request, while in other embodiments a user may be required to call a predetermined phone number. As described above, the user may be required to provide one or more codes in the secondary authentication response.
- the authentication server 930 receives the response to the secondary authentication request, and at operation 1055 the authentication server 930 processes the response.
- authentication server 930 maintains authentication codes which represent the anticipated response to the secondary authentication request in the data table 1100 .
- the response to the secondary authentication request received from the user may be compared with the authentication code stored in the data table 1100 in order to determine whether the user is authentic.
- the authentication server 930 may implement an error routine in response to a failed a secondary authentication request.
- the authentication routine may transmit an error message to the user via the first communication channel, the second communication channel, or both.
- the error message may instruct the user that authentication has failed and they provide the user with an opportunity to restart the authentication process.
- the operations depicted in FIG. 10 enable the network infrastructure depicted in FIG. 11 to implement a multifactor authentication process.
- the multifactor authentication process utilizes two separate network devices, i.e., a computing device and a telephone.
- the multifactor authentication process may utilize a single network device, i.e., a computing device, which executes two or more logical network devices.
- a user may initiate a primary authentication request from a first application executing on the computing device, and the second authentication request may be directed to a second application executing on the computing device.
- the second application may be an Internet Protocol (IP) telephony application.
- IP Internet Protocol
- the authentication server 930 may store in a memory module such as cache memory the results of a primary authentication request initiated by a user, alone or in combination with the results of a secondary authentication response provided by the user.
- the results may be stored in for a predetermined period of time or for a dynamic period of time.
- the authentication server 930 may require that subsequent primary authentication requests be initiated from the same network address in order to bypass the secondary authentication request.
- the authentication server 930 may detect the network address from which the primary authentication request is initiated and may store the network address in a memory module.
- the authentication server 930 may detect the network address from which the primary authentication request is initiated and may compare the network address with a list of approved network addresses stored in a memory module.
- the authentication server 930 may flag a user as a suspect for fraudulent access and may decline to initiate a secondary authentication request unless further conditions are met.
- the authentication server may flag a user as a suspect for fraudulent access and may decline to initiate a secondary authentication request unless further conditions are met. For example, a user may be required to reset passwords or to speak personally with an administrator.
- the authentication server 930 may provide a user interface that enables users to register one or more telephone numbers or contact addresses for the network device intended for use for the secondary authentication request.
- the user interface may further permit users to select one or more authentication codes or personal identification numbers (PINs) for both the primary authentication request and the secondary authentication response.
- PINs personal identification numbers
- Various alternate embodiments may be implemented. For example, n some situations it may not be possible to submit a user's primary authentication credentials to the authentication server without incurring unwanted side-effects. For example, logging into a web application using primary authentication credentials may cause the application to take actions such as creating a user session, logging a message, or the like that may be undesirable.
- a the authentication server may implement a pre-authentication process. After receiving the primary authentication credentials, the authentication system can attempt to pre-authenticate them using a different API interface, rather than pre-authenticating to the target server itself. For example, in a web application such as Microsoft's Outlook Web Access, the system may pre-authenticate the user by calling the Windows LogonUser( ) API, which checks the user's username and password against the Windows password database. Alternatively, in a Citrix environment, the system could pre-authenticate the user using the Citrix authentication APIs.
- the secondary authentication may be implemented as described before. Only if that is also successful are the user's credentials submitted to the application in question for final log-in. This becomes a three-phase login, but it has the benefit of allowing compatibility with applications that would not otherwise support the two-phase approach.
- the strength of the authentication process can be increased using voice-print technology during the confirmation call.
- the system asks the user to repeat a series of words. The user repeats the words, and the system makes a determination of whether the user is who he claims to be by evaluating the user's voice against a voice database, using voice matching algorithms.
- the primary authentication is something the user knows
- the secondary is something the user has (phone)
- the tertiary authentication is something the user is (his voice).
- This system can also be used for multi-person authentication. For example, in situations which require the approval of more than one to allow an action to complete, multiple secondary authentication calls can be placed. For example, in the case of a bank transfer requiring two people to agree to the transaction, the system may place multiple confirmation calls, one to every person authorized to approve the transaction. It could then play back details of the proposed transaction to each user (which can happen simultaneously), and if a minimum number of those users confirm the transaction, the system returns success. This system can scale to an arbitrarily large number of required confirmations.
- Coupled may mean that two or more elements are in direct physical or electrical contact. However, “coupled” may also mean that two or more elements may not be in direct contact with each other, but may still cooperate or interact with each other.
Landscapes
- Engineering & Computer Science (AREA)
- Computer Hardware Design (AREA)
- Computer Security & Cryptography (AREA)
- Computing Systems (AREA)
- General Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Data Exchanges In Wide-Area Networks (AREA)
Abstract
In one embodiment, a network element comprises one or more processors, and a memory module communicatively coupled to the processor. The memory module comprises logic instructions which, when executed by the processor, configure the processor to receive, via a first communication channel, a primary authentication request transmitted from a user from a first device, process the primary authentication request to determine whether the user is authorized to access one or more resources, in response to a determination that the user is authorized to access one or more resources, initiate, a secondary authentication request, and transmit the secondary authentication request from the network element to the user via a second communication channel, different from the first communication channel.
Description
- This application is a continuation application, and claims priority benefit with regard to all common subject matter, of U.S. patent application Ser. No. 11/862,173, filed Sep. 26, 2007, entitled “MULTI FACTOR AUTHENTICATION,” and which issued Jan. 29, 2013, as U.S. Pat. No. 8,365,258 (“the '258 Patent”). The '258 Patent is a non-provisional application, and claims priority benefit with regard to all common subject matter, of earlier-filed U.S. Provisional Patent Application No. 60/866,068, filed Nov. 16, 2006, entitled “MULTI-FACTOR AUTHENTICATION SYSTEM,” and 60/939,091, filed May 21, 2007, entitled “MULTI-FACTOR AUTHENTICATION SYSTEM.” The identified earlier-filed patent and provisional patent applications are hereby incorporated by reference in their entirety into the present application.
- Internet access has become ubiquitous. In addition to traditional dial-up and Local Area Network-based network access, wireless access technologies including IEEE 802.11b and 802.11g (WiFi), WiMax, Bluetooth™, and others are being widely deployed. Many public locations, such as airports, bookstores, coffee shops, hotels, and restaurants have free or fee-based access to wireless Internet service. Some locations, such as hotel rooms, also offer internet access via Ethernet ports. In addition, businesses offer visiting professionals access to Internet service while they are on the premises.
- Such Internet access services typically are not secured at the datalink layer. It is often possible for network administrators, other users, or even criminals to capture and view network transmissions made on these networks. The “last mile”, or the few hops on the network that are closest to the end user, are often only lightly secured, if at all, and are particularly vulnerable to traffic snooping. Enhanced communication security would find utility.
- In addition, authentication remains a persistent technical problem in the information technology industry. With the proliferation of untrusted applications and untrusted networks, and the increasing use of the Internet for business functions, the authentication issues have become prominent. Authentication refers to a process by which a user makes his or her identity known to a system or application which the user is attempting to access, and occasionally, also the process by which the user verifies the identity of the system being accessed. A common authentication technique involves the use of a shared username and password combination. This style of authentication is vulnerable to a number of weaknesses. For example, passwords must be made long enough to be secure while being short enough to be memorable. Additionally, the loss of the password is sufficient to allow an attacker to gain access to the system by impersonating the user. Therefore, additional authentication techniques would find utility.
- The detailed description is provided with reference to the accompanying figures. In the figures, the left-most digit(s) of a reference number identifies the figure in which the reference number first appears. The use of the same reference numbers in different figures indicates similar or identical items.
-
FIG. 1 is a schematic illustration of a networked computing environment in accordance with an embodiment. -
FIG. 2 is a schematic illustration of a server in accordance with an embodiment. -
FIGS. 3-8 are flow diagrams of embodiments of methods for secure network computing. -
FIG. 9 is a schematic illustration of a networked computing environment in accordance with an embodiment. -
FIG. 10 is a flow diagram of embodiments of a method for multifactor authentication. -
FIG. 11 is a schematic illustration of and embodiment of a data file which may be used in a multifactor authentication. - Described herein are exemplary systems and methods for secure network computing and multifactor authentication. The methods described herein may be embodied as logic instructions on a computer-readable medium. When executed on a processor, the logic instructions cause a general purpose computing device to be programmed as a special-purpose machine that implements the described methods. The processor, when configured by the logic instructions to execute the methods recited herein, constitutes structure for performing the described methods.
- In the following description, numerous specific details are set forth in order to provide a thorough understanding of various embodiments. However, various embodiments of the invention may be practiced without the specific details. In other instances, well-known methods, procedures, components, and circuits have not been described in detail so as not to obscure the particular embodiments of the invention.
-
FIG. 1 is a schematic illustration of a networked computing environment in accordance with an embodiment. In the exemplary architecture depicted inFIG. 1 , one or moreclient computing devices server 130, which in turn communicates with one ormore target servers network 120.Target servers -
Client computing devices personal computer 110 a, a personal digital assistant (PDA) 110 b, or aterminal device 110 c.Client computing devices POP server 130 via a communication network, which may be thesame network 120 or a separate communication network. The particular form of communication network is not important. Communication network may comprise one or more direct communication links (e.g., a dial-up connection) between respectiveremote access devices - In one embodiment,
POP server 130 may be implemented by a general purpose computing device such as, e.g., a server, that executes logic instructions which cause the processor to execute various methods for performing secure network computing.FIG. 2 is a schematic illustration of anexemplary computer system 200 adapted to perform secure network computing. Thecomputer system 200 includes acomputer 208 and one or more accompanying input/output devices 206 including adisplay 202 having ascreen 204, akeyboard 210, other I/O device(s) 212, and amouse 214. The other device(s) 212 can include a touch screen, a voice-activated input device, a track ball, and any other device that allows thesystem 200 to receive input from a developer and/or a user. Thecomputer 208 includessystem hardware 220 and random access memory and/or read-only memory 230. Afile store 280 is communicatively connected tocomputer 208.System hardware 220 includes aprocessor 222 and one or more input/output (I/O)ports 224.File store 280 may be internal such as, e.g., one or more hard drives, or external such as, e.g., one or more external hard drives, network attached storage, or a separate storage network. -
Memory 230 includes anoperating system 240 for managing operations ofcomputer 208. In one embodiment,operating system 240 includes ahardware interface module 254 that provides an interface tosystem hardware 220. In addition,operating system 240 includes one ormore file systems 250 that managed files used in the operation ofcomputer 208 and aprocess control subsystem 252 that manages processes executing oncomputer 208.Operating system 240 further includes a systemcall interface module 242 that provides an interface between theoperating system 240 and one ormore application modules 262 and/orlibraries 264. - In operation, one or
more application modules 260 executing oncomputer 208 make calls to the systemcall interface module 242 to execute one or more commands on the computer's processor. The systemcall interface module 242 invokes the services of thefile systems 250 to manage the files required by the command(s) and theprocess control subsystem 252 to manage the process required by the command(s). Thefile system 250 and theprocess control subsystem 252, in turn, invoke the services of thehardware interface module 254 to interface with thesystem hardware 220. - The particular embodiment of
operating system 240 is not critical to the subject matter described herein.Operating system 240 may be embodied as a UNIX operating system or any derivative thereof (e.g., Linux, Solaris, etc.) or as a Windows® brand operating system. - In one embodiment,
memory 230 includes one or morenetwork interface modules secure tunnel modules 264, and one or morecommunication management modules 266. Network interface modules may be implemented as web browsers such as, e.g., Internet Explorer, Netscape, Mozilla, or the like.Secure tunnel module 264 comprises logic instructions which, when executed by a processor, configure the processor to generate a secure communication tunnel between thePOP server 130 and a client computing device such as, e.g., one or more ofclient computing devices Communication management module 266 comprises logic instructions which, when executed by a process, configure the processor to manage communications between thePOP server 130 and one or moreclient computing devices POP server 130 and the one ormore servers - In embodiments,
POP server 130 receives a service request from a client computing device such as, e.g., one or more ofclient computing devices POP server 130 from a browser executing on a client computing device. In response to the service request,POP server 130 establishes a first communication link between thePOP server 130 and the one or more resources available via a computing network identified in the service request. In one embodiment,POP server 130 may launch an independent request for the resource request for the resource identified in the service request from the client computing device.POP server 130 may further establish a first, secure communication link between thePOP server 130 and theclient computing device -
POP server 130 may further manage communication activity between the client computing device and the one or more resources available via a computing network at the POP server. In one embodiment, managing communication activity may include passing information received from aserver POP server 130 to aclient computing device - Operations implemented by the
various modules client computing devices FIGS. 3-8 .FIGS. 3-8 are flow diagrams of embodiments of methods for secure network computing.FIG. 3 is a flow diagram illustrating high-level operations executed by a computing device such as one ofclient computing devices POP server 130 and theclient computing device operation 315 the client computing device sends outbound data via the secure communication link and atoperation 320 the client computing device receives inbound data via the secure communication link. If, atoperation 325 there are more outbound data requests, then control passes back tooperation 315. Similarly, if atoperation 330 there is more inbound data control passes back tooperation 320 and the inbound data is received. If there are no further data requests or inbound data remaining, then control passes tooperation 335 and the secure communication link may be terminated. Operations illustrated inFIG. 3 are explained in greater detail inFIGS. 4-8 . -
FIG. 4 is a flow diagram illustrating operations in a method for initializing a secure communication link betweenPOP server 130 and aclient computing device POP server 130 implements an application tunneling technology, referred to herein as an AppTunnel, to construct a secure communication tunnel betweenPOP server 130 and aclient computing device - Referring to
FIG. 4 , atoperation 410POP server 130 receives an address of one or more resources such as, e.g., a website or other resource available onnetwork 120. In one embodiment, the address received may represent a URL received in a service request from a web browser executing onclient computing device POP server 130 transmits an ActiveX control comprising launch data toclient computing device - At
operation 420 theclient computing device server 130. If, atoperation 425 the client computing device is not compatible with ActiveX technology, then control passes tooperation 465 and a rewriter host module may be activated. This procedure is explained in greater detail below. By contrast, if theclient computing device client computing device - At
operation 435 theclient computing device server 130. The ActiveX control causes theclient computing device client computing device server 130 and theclient computing device - At
operation 450 the client attaches a secure channel module to the browser. In one embodiment, the secure channel module may be embodied as an AppTunnel client module. The AppTunnel secure channel module is described in detail in U.S. patent application Ser. No. 10/737,200, incorporated by reference here above. Portions of that description are excerpted in the following paragraphs. - Application tunneling is a method for transporting data from a user's computer to a third party computer (a “proxy”). In one implementation, Application data may be intercepted as soon as it is sent (i.e., above layer 4 of the OSI model), before it is encapsulated by Internet protocols such as TCP, UDP, or IP. Data may then be transported across the network to the proxy. In other implementations, this application-level data is acquired differently (perhaps, for example, through the use of a virtual adapter). In all cases, it is application-level data (OSI layers 5-7, depending on the application and the protocol) that is tunneled via AppTunnels.
- AppTunnels is application tunneling technology that tunnels data from an application on a first computer to a second computer, perhaps over a secure tunnel, for further processing and proxying at that other computer. AppTunnels technology may be implemented in a Static form or in a Dynamic form. Static AppTunnels technology requires manual (or pre-configured) establishment of the application tunnels and listeners. By contrast, dynamic AppTunnels implements on-the-fly tunnel creation using hook mechanisms.
- Encryption and/or other security technologies may be applied to the tunnel to add security to the data being transported, although this is not strictly necessary.
- AppTunnels differs from existing tunneling technologies such as Generic Routing Encapsulation (GRE) in that it is designed to operate at the end user's computer, in such a way that the end user's applications do not have to be informed about the existence of the tunneling technology. By contrast, tunneling technologies such as GRE, on the other hand, are designed to be implemented in network elements such as routers.
- AppTunnels differs from host-based encryption technologies such as SSL in several ways. First, SSL technology must be directly supported by the application in order to be applied. AppTunnels, however, does not require application awareness in order to be applied. Furthermore, SSL is closely tied to a particular security and encryption architecture. AppTunnels may be used with or without security technologies, and imposes no requirements on the underlying security technologies. AppTunnels has been used in conjunction with the WTP security protocol and with SSL.
- To intercept the network traffic of an application a local listener is created and a tunnel is established between the first computer and the second computer. In one embodiment, a local listener may be implemented as listening TCP, UDP, or other socket(s) bound to a local host address (e.g., 127.0.0.1) on a computer. The port number, where applicable, may be determined by the tunneled application, and may be arbitrary in some protocols. Local listeners may be created either in response to instructions from dynamic AppTunnels hooks or by static configuration received in advance. It is also possible for a user to manually initiate the creation of a listener (and its associated tunnel). A data tunnel may be created between the AppTunnels client software and a compatible tunnel module on a server. In one embodiment, the tunnel may be implemented in accord with the WTP protocol described in U.S. patent application Ser. No. 10/737,200.
- Once an AppTunnel has been initialized, the end user application can be directed to connect to the AppTunnel. The process for this varies per application. In the case of Dynamic AppTunnels, no other action is necessary; data simply starts flowing from the application to the AppTunnels software, which in turn tunnels the data across the connection to the WTP concentrator.
- In the case of Static AppTunnels, one additional step is required. The application is tricked into connecting to the local listener instead of to the target server, as would otherwise naturally be the case. To trick the client, the DNS system is configured to return the localhost address (127.0.0.1, usually) to requests for the destination server's IP address. This is usually done by changing the locally-present “hosts” file that the computer's DNS system consults before returning an IP address. This hosts file is modified, with an entry being inserted for the name of the target server with the IP address of localhost. In one embodiment, the AppTunnels client may be implemented as an executable component that is incorporated into and run by the user's web browser such as, e.g., an ActiveX control. For other browsers or other platforms, a Netscape Plugin may be used.
- In one embodiment, AppTunnels implements a method of intercepting traffic in order to tunnel it is as follows: First, the computer's DNS resolution system is modified to re-route traffic for target network servers to the local computer. Next, the AppTunnels Client establishes itself as a server on the port that the application would expect to connect to. Once established, applications transparently connect to the Client on the local computer rather than to their natural target-network servers. No configuration or modification of the tunneled application is necessary.
- The AppTunnels method can be used to tunnel any user-mode data over a tunnel to the
server 130. This includes TCP and UDP on all platforms. Other protocols may be available for tunneling, depending on the platform. The AppTunnels architecture supports complex network protocols such as FTP, RPC, H.323, and other proprietary multi-connection protocols. It provides this support by inspection of protocol data at the server. A protocol may be termed ‘complex’ if it requires more than a simple client-to-server TCP connection. - In AppTunnels mode, the
client computing device server 130, which retrieves the requested document and returns it to the AppTunnels client, which in turn returns it to the web browser. - In brief, the
client computing device client computing device - The AppTunnels client then establishes a connection to
server 130 and authenticates itself. After authentication, the AppTunnels client establishes itself as a server application and listens for incoming requests from the browser. As requests are received, they are forwarded toserver 130. Responses are read in from the server and are sent back to the waiting browser. - The browser is monitored by Dynamic AppTunnels for any network communication attempts. In one embodiment, these attempts may be monitored using function call hooks of the Microsoft Winsock library, but other hooks are possible, as are other monitoring architectures (such as, for example, Winsock Layered Service Providers). When new network traffic is detected, it is intercepted by the Dynamic AppTunnels code for further processing.
- In one embodiment, child processes created by the browser may be injected with the Dynamic AppTunnels monitoring code. Thus, network traffic generated by child processes send will be encapsulated in the AppTunnel. Child process monitoring may be implemented using an API hook for all of the CreateProcess( ) family of functions. When a call to CreateProcess( ) is made, the Dynamic AppTunnels code receives it first, and ensures that the monitoring code is injected in the resulting new process.
- In one embodiment, dynamic AppTunnels technology is implemented using API hooks. When dynamic AppTunnels receives a request to start a tunneled process, it creates a new process using the CreateProcess( ) API call. A new process may be created as suspended, so that the process does not run after it is initially created. At this point, one or more imported functions are substituted, or hooked, such that they point to wrapper functions that are part of the Dynamic AppTunnels software. The hooked functions are of two classes: network functions and process management functions.
- In particular, the CreateProcess( ) function (and its relatives) may be hooked so that any child processes that are created can have the Dynamic AppTunnels monitoring code injected as well. This code is responsible for signaling the browser plugin that it should inject the rest of the hooks into the newly created process. Any child processes of that child are treated in the same way.
- The networking functions that are hooked are related to connection requests and to name resolution requests. In general, all functions that are called during initial connection setup are intercepted. Once hooked, these functions receive any connection requests, and use this information for two purposes. The first is to coordinate with the tunneling protocol on the AppTunnel server to create an additional AppTunnel between the client and the AppTunnel server, and to create a local listener that is attached to that tunnel. The second is to re-direct the requesting application to the local listening socket, so that connections are made it instead of to the original target server. This process allows network traffic generated by the client to be captured by the browser plug-in and tunneled.
- Alternatively, the plug-in may choose to examine the connection request information and make a decision at runtime as to whether the traffic should be tunneled or allowed to go straight out to the network as it otherwise would have. These decisions can be based on names (such as DNS or WINS names), network addresses, port numbers, or other identifying information. While this description has largely been written in the context of TCP sockets, it should be pointed out that other kinds of network traffic may be supported, including UDP and raw IP packets.
- Referring back to
FIG. 4 , atoperation 455 the browser instantiated at theclient computing device client computing device server 130 are conveyed through the secure tunnel. When the user of the client computing device is finished with the browsing session, the browser may be closed. Closing the browser also closes any dynamic AppTunnels constructed between theclient computing device server 130. -
FIG. 5 is a flow diagram illustrating operations in a method for implementing an AppTunnel on aclient computing device server 130 to the client computing device operations ofFIG. 5 may cause the client computing device to perform the operations illustrated inFIG. 5 . - Referring to
FIG. 5 , atoperation 510 one or more static listeners and AppTunnels are initialized on the client computing device. Atoperation 515 the AppTunnels plugin (i.e., the ActiveX control) receives a request to start an application. For example, the plugin may receive a request to start an instance of a browser. - At
operation 520 it is determined whether the device supports dynamic AppTunnels. As described above, AppTunnels can operate in either a static mode or in a dynamic mode. The difference is in the way the data is acquired for tunneling. Static AppTunnels uses a static local listening TCP/IP socket for each pre-configured service. If a user wants to use a web browser over a static AppTunnel, for example, there must be a configured application tunnel listening on TCP port 80 on the local host. Furthermore, the destination address for the AppTunnel must be specified. To cause the user's application to connect to the AppTunnels socket instead of trying to use Internet routes in the usual way, the DNS system of the client computing device is configured (usually using the computer's hosts file) to change the IP address of the server in question to point to the local host (usually 127.0.0.1), thereby fooling the application into making a local connection to the listening socket. - Thus, referring to
FIG. 5 , if atoperation 520 dynamic AppTunnels is not enabled, then control passes to operation 525 and the DNS system is configured, and at operation 530 a local listening socket is created. At operation 535 a new process is created. - By contrast, if at
operation 520 the device accommodates dynamic AppTunnels, then control passes tooperation 540 and a new process is created on the client computing device. In one embodiment creating a new process may involve a user clicking an HTML link on the web page in a browser executing on the client computing device. The ActiveX control then launches the new process and injects the Dynamic AppTunnels application monitoring code into the newly started process (operation 545). At operation 550 a new AppTunnel is created between the client computing device and theserver 130. - Following either
operation operation 560 and the application receives data in the listening socket generated by the AppTunnel. Atoperation 565 the data received in the AppTunnel is removed and passed to the process (i.e., the web browser) for further processing and presentation to a user via a suitable interface such as, e.g., a display. Operations 560-565 may be repeated until, atoperation 570, there is no more data to tunnel, whereupon operations terminate. -
FIG. 6 is a flow diagram illustrating operations in a method for processing outbound traffic from a network interface module such as, for example, a web browser executing on aclient computing device FIG. 6 depict traffic processing for a browser that has an AppTunnel module attached to the browser. Referring toFIG. 6 , atoperation 610 the web browser receives an address of a resource available onnetwork 120. In one embodiment, the address may represent a Uniform Resource Locator (URL) of a resource available onnetwork 120. Atoperation 615 the browser initiates a service request for the resource. Atoperation 620 the service request is intercepted by the AppTunnel module. Atoperation 625 the AppTunnel client secures the request data and atoperation 630 the AppTunnel client forwards the request to thePOP server 130. Atoperation 640 the secured request is received at thePOP server 130. Atoperation 645 the secure tunnel module 264 (i.e., the AppTunnel server) extracts the request data from the secure tunnel. - At
operation 650 the POP server forwards the service request to the address identified in the service request. In one embodiment, the service request is received in a firstnetwork interface module 262 instantiated onPOP server 130, andPOP server 130 instantiates a secondnetwork interface module 268 and launches a service request from the second network interface module. -
FIG. 7 is a flow diagram illustrating operations in a method for processing inbound traffic such as, for example, one or more resources returned from a service request. Referring briefly toFIG. 7 , atoperation 710 the data returned by the resource request is received at thePOP server 130. In one embodiment, the data is received in the secondnetwork interface module 268 instantiated on thePOP server 130. Atoperation 715 the response data is secured. In one embodiment, response data is operated on by thesecure tunnel module 264. Atoperation 720 the response data is placed in the secure tunnel to theclient computing device network interface module 262. - At operation 725 the client receives the response data transmitted to the client by the server. At
operation 730 the data is removed from the secure tunnel established by AppTunnels. In one embodiment, the AppTunnels client attached to the browser in theclient computing device operation 735, forwards the data to the web browser. The web browser may present the data on a user interface such as, e.g., a display, for viewing by the user. - Referring back to
FIG. 4 , if atoperation 425 the client computing device is not capable of executing a plugin such as, e.g., an ActiveX control, then control passes tooperation 465 and a URL rewriter technique is activated. URL rewriting is a method of providing a reverse proxy server for use in secure remote access systems and other applications without the need for any locally installed code. Most web browsers can exchange traffic with web servers using a protocol known as secure HTTP, or HTTPS. However, most websites do not support HTTPS. To add security to every website the user requests, special HTTPS requests are made to a URL rewriter server instead of the target web server, using HTTPS to the rewriter. The rewriter then forwards the request to the target web server by proxy, using the expected destination protocol of the web server (typically HTTP). On return, the web data is returned over HTTPS to the client's browser. It should be noted that any other form of browser-based security, or no security whatsoever, could be used in the communications link to the rewriter. - It should be noted that references to other web data will now cause the user's browser to make direct requests to the target server, rather than ask the rewriter server. Thus, references to other web content (hyperlinks, images, java applets, and so on) may be rewritten in the webpage so that they refer to the rewriter instead of to the target server to ensure that all web traffic is routed through the rewriter, and not via direct connections. Accordingly, any web references in the returned document are rewritten with references to the URL rewriter server.
-
FIG. 8 is a flow diagram illustrating operations in a method for processing inbound traffic such as, for example, one or more resources returned from a service request. Referring briefly toFIG. 8 at operation 810 a rewriter host page on theclient computing device operation 815 the rewritten URL is written into the second browser. Atoperation 820 the second browser requests the specified resource using the rewritten URLs. - At
operation 825 theserver 130 receives the service request from theclient computing device operation 830 theserver 130 un-rewrites the URL, and atoperation 835 the server retrieves the requested resource from theserver network 120. Atoperation 840 the server rewrites the embedded URLs in the retrieved resource, and atoperation 845 the server returns the rewritten resource to the client. - At
operation 850 theclient computing device operation 855 there are more requests to be processed, then control passes back tooperation 820, and the browser requests the specified resource(s). By contrast, if atoperation 855 there are no further resource requests, then the process terminates. - Thus, the operations described in
FIGS. 3-8 enable a client device such as one or more ofclient computing devices more servers network 120. The systems and methods described herein are agnostic regarding the type of encryption applied (if any) to communication links betweenPOP server 130 andservers - The systems described above are browser-based systems. In alternate embodiments, a
client computing device client computing device servers - In another embodiment, an ActiveX control installs and initializes a virtual VPN Miniport, as described in U.S. patent application Ser. No. 10/737,200. The ActiveX control captures and processes any relevant traffic on the computer. In this way, end user traffic is directed into the secured tunnel described above.
- A virtual VPN Miniport can support non-TCP protocols, while maintaining the convenience of a web-based environment. It can also secure applications that have already been started. For example, if the end user were running an instant messaging client, that client's communications would be secured from the time of connection forward, without a need to re-launch the client. Installation of a VPN driver can be silent and automatic, and only needs to occur one time. From that point on, the ActiveX control activates the VPN driver and manages network routes to cause traffic to be directed into the VPN driver for encryption.
- Access to the
POP server 130 may be provided by a number of methodologies. In one embodiment access toPOP server 130 may be provided on a pay-for-service business model. In this embodiment,POP server 130 may include a transaction processing module to process payment transactions, e.g., by a credit card or other payment mechanism. Charges may be levied on the basis of bandwidth consumed, or by a time parameter (i.e., minutes, hours, days, years, etc.). - In alternate embodiments access to
server 130 may be implemented on the basis of advertising revenue. For example, pay-per-click advertising can be implemented, using randomly-selected advertisements, pay-per-click advertising can be implemented, using information gained by inspecting the user's traffic during secure surfing to select targeted advertisements, or traditional Internet banner advertisements can be inserted, either randomly or based on inspection of the secured data. Advertisements can be inserted in the initial service provider web page, in the refreshed web page that hosts the ActiveX control, or even inline with the displayed web pages. - Multiple levels of service may be defined. For example, low-quality service might be provided free of charge, while high-quality service might be provided for a fee. Service levels may be differentiated by one or more facts such as, for example throughput (i.e., a performance aspect might be controlled), bandwidth (i.e., the total number of bytes transferred might be capped), data transfer (i.e., a transfer cap might be imposed per day, per month, or per year), or some combination thereof. Other options include allowing only a limited amount of time to use the system or bandwidth in a tier or a certain amount of throughput for a certain amount of time, with decreased throughput after the elapse of that time, or restricting access to certain resources based on the service level.
- Last-mile encryption service may be provided to a user with no pre-existing account. The web-based interface can be used simply by entering the address of a website that is to be securely accessed. In the installed client case, the user logs in anonymously using the supplied anonymous login method. Anonymous users may be granted a different tier of service, as described above.
- In an anonymous user case, cookie-based, form-based, or IP address-based information may be used to correlate the anonymous user's browsing activities, for purposes including providing advanced service features (such as browsing history, enhanced status reporting, etc), selecting relevant advertising, or for other purposes.
- Users that desire temporary top-tier service may be given the option of paying electronically for a one-time use of the service without creating an account.
- Users that wish to use the service repeatedly may wish to create a user account. The user account could then be used to track browsing history, make more intelligent decisions about advertising content to be presented, or offer other value-added services. Users of the service would then be prompted to log in to the website (or to the downloaded client software) using the established authentication credentials. Optionally, a cookie-based login persistence mechanism can be supported, allowing the user to go for a period of time without the need to log in.
- As described above, authentication remains a technical challenge in the information technology sector. Described herein are multifactor authentication techniques which may be used alone, or in combination with other security techniques described herein to provide secure access to resources in a computer network. Embodiments of multifactor authentication techniques will be described in the context of a computer network similar to the network described in with reference to
FIG. 1 . It will be understood, however, that authentication techniques as described herein may be implemented in a wide variety of computer networks. -
FIG. 9 is a schematic illustration of a networked computing environment in accordance with an embodiment. In the exemplary architecture depicted inFIG. 9 , one or moreclient computing devices authentication server 930, which in turn communicates with one ormore target servers network 920.Target servers -
Client computing devices personal computer 910 a, a personal digital assistant (PDA) 910 b, aterminal device 910 c, amobile telephone 910 d, or a land-line telephone 910 e.Client computing devices authentication server 930 via a communication network, which may be thesame network 920 or a separate communication network. The particular form of communication network is not important. Communication network may comprise one or more direct communication links (e.g., a dial-up connection) between respectiveremote access devices -
Authentication server 930 may be embodied as a computing device, substantially as described in with reference toFIG. 2 , above. Referring briefly toFIG. 2 , thecomputing device 200 and comprise one ormore authentication modules 269 which may execute when as an application module and thememory 230 of thecomputing system 200. In some embodiments, theauthentication module 269 and implemented logic instructions which, when executed by a processor such as theprocessor 222, cause theauthentication module 269 to implement multifactor authentication procedures to manage access to one or more resources of thecomputer network 920, such as for example, resources provided byservers - In some embodiments, the
authentication server 930 implements a first authentication process in response to an authentication request from a client computing device such as one ofclient computing devices authentication server 930 originates a second authentication request to a client device such as one ofclient computing devices authentication server 930 is transmitted using a second communication channel, different from the first communication channel. Theauthentication server 930 may process the response to the second authentication request and allow or deny access to a resource based on the response. In some embodiments the first communication channel and the second communication channel may be across separate communication networks. For example, the first communication channel may be across the computer network, while the second communication channel may be across a telephone network. - One embodiment of multifactor authentication will be explained with reference to
FIG. 10 , which is a flow diagram of embodiments of a method for multifactor authentication. Referring toFIG. 10 , at operation 1010 a first client initiates a primary authentication request for access to a resource provided bycomputer network 920. In some embodiments, the primary authentication request may include a username and password combination associated with a user and/or a device from which the primary authentication request is originated. The primary authentication request may be transmitted to theauthentication server 930 to a first communication channel. -
Operation 1015 theauthentication server 930 receives the primary authentication request, and atoperation 1020 theauthentication server 930 processes the primary authentication request. In some embodiments, theauthentication server 930 performs a centralized authentication function which manages authentication to one or more resources andnetwork 920. For example,authentication server 930 may maintain a data file comprising username and password combinations which may be associated with one or more resources of thecomputer network 920.FIG. 11 is a schematic illustration of and embodiment of a data file which may be used in a multifactor authentication. Referring briefly toFIG. 11 , the illustrateddata file 1100 includes a column for usernames, a column for passwords, and a column for approved resources. Usernames and passwords may be logically associated with the approved resource indicated in the table 1100. A single username may be associated with multiple passwords for different approved resources. In one embodiment, processing the primary authentication request may comprise searching the data file 1100 maintained by the authentication server for a username and password combination that corresponds to the username and password combination receipt in the primary authentication request. - If, an
operation 1025, the primary authentication request is unsuccessful, i.e., if there is no corresponding username and password combination in the data table 1100, then theauthentication server 930 denies the requester access to network resource(s). In some embodiments, theauthentication server 930 may transmit an error message to the requester indicating that the username and password are invalid. Control that returns tooperation 1015 and theauthentication server 930 continues to monitor for another primary authentication request. - By contrast, if that
operation 1025 primary authentication request is successful, i.e., if there is a corresponding username and password combination in the data table 1100, then control passes tooperation 1035 and theauthentication server 930 initiates a secondary authentication request. The secondary authentication request is transmitted from theauthentication server 930 to the user via a second communication channel, different from the first communication channel. In some embodiments, the secondary authentication request is transmitted from theauthentication server 930 to a second client in the user's possession. For example, the user may initiate the primary authentication request from a computing device such as a desktop computer or laptop computer and theauthentication server 930 may transmit the secondary authentication request by initiating a telephone call to a telephone registered to the user. Referring briefly again toFIG. 11 , a user may register, via a suitable user interface, a contact number to which the secondary authentication request may be transmitted from theauthentication server 930. In response to a successful primary authentication request, theauthentication server 930 may initiate a call to contact number indicated in the data table 1100. It should be noted that a user may provide different contact numbers for different resources. - At
operation 1040 the secondary authentication request is received at the second client. The secondary authentication request may comprise a voice message which makes a request for information to authenticate the user. In some embodiments, the system may allow a user to prerecord a customized secondary authentication request in the user's own voice. For example, the user may record a message requesting a specific sequence of keystrokes or requesting the user to speak to a specific word or group of words. Having a user recorded message in the second authentication request helps to authenticate the system to the user, thereby eliminating or at least reducing the likelihood of a “man in the middle” attack on the system. In alternate embodiments, rather than using a prerecorded message in the user's voice, a user may select one or more tokens to be presented with a secondary authentication requests. For example, a token may include a predetermined word or character or numeric sequence selected by the user. - At
operation 1045 the user response to the secondary authentication request initiated by theauthentication server 930. For example, in some embodiments the user may respond by pressing a predetermined sequence of keystrokes on a telephone keypad, or by pressing the pound key or the star key. In alternate embodiments the user may respond by speaking a predetermined word or series of words. In alternate embodiments the user need not provide an affirmative response; simply answering the telephone call may suffice as a response. - In some embodiments, the secondary authentication request initiated by the
authentication server 930 may be implemented as a text message rather than a telephone call. Accordingly, the response to the secondary authentication request may also be implemented as a text message in which the user transmits a predetermined character or series of characters back to theauthentication server 930. - In alternate embodiments, the secondary authentication request may require a user to initiate a call back in order to authenticate the user. For example, the secondary authentication request may transmit a text message or a voice call requesting the user to call back to the system to authenticate the user. In some embodiments, a return phone number may be included with the secondary authentication request, while in other embodiments a user may be required to call a predetermined phone number. As described above, the user may be required to provide one or more codes in the secondary authentication response.
- At
operation 1050 theauthentication server 930 receives the response to the secondary authentication request, and atoperation 1055 theauthentication server 930 processes the response. In some embodiments,authentication server 930 maintains authentication codes which represent the anticipated response to the secondary authentication request in the data table 1100. The response to the secondary authentication request received from the user may be compared with the authentication code stored in the data table 1100 in order to determine whether the user is authentic. - If, at
operation 1060, the response to the secondary authentication request fails to successfully authenticate the user then access to network resources is denied atoperation 1065 and control passes back tooperation 1015 in the authentication server monitors for additional incoming primary authentication requests. In some embodiments, theauthentication server 930 may implement an error routine in response to a failed a secondary authentication request. The authentication routine may transmit an error message to the user via the first communication channel, the second communication channel, or both. The error message may instruct the user that authentication has failed and they provide the user with an opportunity to restart the authentication process. - By contrast, is that
operation 1060 the response to the secondary authentication request successfully authenticates the user then control passes tooperation 1070 and the user is granted access to the network resource or resources associated with the username and password in the data table 1100. Control then passes back tooperation 1015 and theauthentication server 930 continues to monitor for additional primary authentication request. - Thus, the operations depicted in
FIG. 10 enable the network infrastructure depicted inFIG. 11 to implement a multifactor authentication process. In some embodiments described herein, the multifactor authentication process utilizes two separate network devices, i.e., a computing device and a telephone. In some embodiments, the multifactor authentication process may utilize a single network device, i.e., a computing device, which executes two or more logical network devices. For example, a user may initiate a primary authentication request from a first application executing on the computing device, and the second authentication request may be directed to a second application executing on the computing device. For example, the second application may be an Internet Protocol (IP) telephony application. - Various features may be added to the functionality of the basic authentication process described herein. In some embodiments, the
authentication server 930 may store in a memory module such as cache memory the results of a primary authentication request initiated by a user, alone or in combination with the results of a secondary authentication response provided by the user. The results may be stored in for a predetermined period of time or for a dynamic period of time. Thus, when a user has successfully authenticated himself or herself to the system additional authentication may not be required during the time period. Theauthentication server 930 may require that subsequent primary authentication requests be initiated from the same network address in order to bypass the secondary authentication request. Thus, in some embodiments theauthentication server 930 may detect the network address from which the primary authentication request is initiated and may store the network address in a memory module. - Further, there may be circumstances in which secondary authentication requests may not be necessary. For example, if a user is located on a trusted network in the secondary authentication request may be bypassed. Thus, in some embodiments of the
authentication server 930 may detect the network address from which the primary authentication request is initiated and may compare the network address with a list of approved network addresses stored in a memory module. - Still further, there may be circumstances in which the
authentication server 930 declines to initiate a secondary authentication requests. In some embodiments, in the event of a predetermined number of failures for a primary authentication request theauthentication server 930 may flag a user as a suspect for fraudulent access and may decline to initiate a secondary authentication request unless further conditions are met. In some embodiments, in the event multiple primary authentication requests are received from different network addresses within a predetermined period of time the authentication server may flag a user as a suspect for fraudulent access and may decline to initiate a secondary authentication request unless further conditions are met. For example, a user may be required to reset passwords or to speak personally with an administrator. - In some embodiments, the
authentication server 930 may provide a user interface that enables users to register one or more telephone numbers or contact addresses for the network device intended for use for the secondary authentication request. The user interface may further permit users to select one or more authentication codes or personal identification numbers (PINs) for both the primary authentication request and the secondary authentication response. - Various alternate embodiments may be implemented. For example, n some situations it may not be possible to submit a user's primary authentication credentials to the authentication server without incurring unwanted side-effects. For example, logging into a web application using primary authentication credentials may cause the application to take actions such as creating a user session, logging a message, or the like that may be undesirable.
- In such situations, a the authentication server may implement a pre-authentication process. After receiving the primary authentication credentials, the authentication system can attempt to pre-authenticate them using a different API interface, rather than pre-authenticating to the target server itself. For example, in a web application such as Microsoft's Outlook Web Access, the system may pre-authenticate the user by calling the Windows LogonUser( ) API, which checks the user's username and password against the Windows password database. Alternatively, in a Citrix environment, the system could pre-authenticate the user using the Citrix authentication APIs.
- If the pre-authentication step is successful, the secondary authentication may be implemented as described before. Only if that is also successful are the user's credentials submitted to the application in question for final log-in. This becomes a three-phase login, but it has the benefit of allowing compatibility with applications that would not otherwise support the two-phase approach.
- In addition, the strength of the authentication process can be increased using voice-print technology during the confirmation call. During the secondary authentication call, the system asks the user to repeat a series of words. The user repeats the words, and the system makes a determination of whether the user is who he claims to be by evaluating the user's voice against a voice database, using voice matching algorithms.
- Again, this makes the system three-factor: the primary authentication is something the user knows, the secondary is something the user has (phone), and the tertiary authentication is something the user is (his voice).
- This system can also be used for multi-person authentication. For example, in situations which require the approval of more than one to allow an action to complete, multiple secondary authentication calls can be placed. For example, in the case of a bank transfer requiring two people to agree to the transaction, the system may place multiple confirmation calls, one to every person authorized to approve the transaction. It could then play back details of the proposed transaction to each user (which can happen simultaneously), and if a minimum number of those users confirm the transaction, the system returns success. This system can scale to an arbitrarily large number of required confirmations.
- Reference in the specification to “one embodiment” or “an embodiment” means that a particular feature, structure, or characteristic described in connection with that embodiment may be included in at least an implementation. The appearances of the phrase “in one embodiment” in various places in the specification may or may not be all referring to the same embodiment.
- Also, in the description and claims, the terms “coupled” and “connected,” along with their derivatives, may be used. In some embodiments, “connected” may be used to indicate that two or more elements are in direct physical or electrical contact with each other. “Coupled” may mean that two or more elements are in direct physical or electrical contact. However, “coupled” may also mean that two or more elements may not be in direct contact with each other, but may still cooperate or interact with each other.
- Thus, although embodiments of the invention have been described in language specific to structural features and/or methodological acts, it is to be understood that claimed subject matter may not be limited to the specific features or acts described. Rather, the specific features and acts are disclosed as sample forms of implementing the claimed subject matter.
Claims (18)
1. A method of authenticating a user for accessing a resource, said method relying on multi-factor authentication of the user, the method comprising the steps of:
associating the user with a first factor authentication information;
associating the user with a second factor authentication information;
receiving information of a first instance of a first factor authentication step, said first factor authentication step comprising the user inputting a first user authentication information across a first communications network and matching the first user authentication information to the first factor authentication information;
upon receipt of the information of the first instance of the first factor authentication step, performing a first instance of a second factor authentication step, said second factor authentication step comprising—
placing a telephone call or sending a text message to the user across a second communications network at a pre-registered number associated with a telecommunications device of the user,
in response to placing said telephone call or sending said text message to the user, receiving a second user authentication information inputted by the user at the user's telecommunications device,
confirming that said second user authentication information provided by the user via the user's telecommunications device matches the second factor authentication information, and
upon confirming that the second user authentication information matches the second factor authentication information, identifying the user as being authorized to access the resource;
receiving information of the user performing a second instance of said first factor authentication step;
determining if the second instance of said first factor authentication step is within a predetermined period of time since the first instance of said second factor authentication step;
if the second instance of said first factor authentication step is outside the predetermined period of time, performing a second instance of said second factor authentication step for the user; and
if the second instance of said first factor authentication step is within the predetermined period of time, not performing the second instance of said second factor authentication step for the user.
2. The method as set forth in claim 1 , wherein the first communications network is selected from the group consisting of a private data network, a local area network, a wide area network, or a public network.
3. The method as set forth in claim 1 , wherein the first communications network is the Internet.
4. The method as set forth in claim 1 , wherein the input of said first user authentication information is immediately prior to the user accessing said resource.
5. The method as set forth in claim 1 , wherein the first factor authentication information comprises a username and password.
6. The method as set forth in claim 1 , wherein the second communications network is selected from the group consisting of a public switched telephone network and an Internet Protocol network.
7. A non-transitory computer-readable storage medium with an executable program stored thereon for directing operation of at least one computer to authenticate a user for accessing a resource, wherein the program instructs the at least one computer to perform the following steps:
associate the user with a first factor authentication information;
associate the user with a second factor authentication information;
receive information of a first instance of a first factor authentication step, said first factor authentication step comprising the user inputting a first user authentication information across a first communications network and match the first user authentication information to the first factor authentication information;
upon receipt of the information of the first instance of the first factor authentication step, perform a first instance of a second factor authentication step, said second factor authentication step comprising—
place a telephone call or send a text message to the user across a second communications network at a pre-registered number associated with a telecommunications device of the user,
in response to placing said telephone call or sending said text message to the user, receive a second user authentication information inputted by the user at the user's telecommunications device,
confirm that said second user authentication information provided by the user via the user's telecommunications device matches the second factor authentication information, and
upon confirming that the second user authentication information matches the second factor authentication information, identify the user as being authorized to access the resource;
receive information of the user performing a second instance of said first factor authentication step;
determine if the second instance of said first factor authentication step is within a predetermined period of time since the first instance of said second factor authentication step;
if the second instance of said first factor authentication step is outside the predetermined period of time, perform a second instance of said second factor authentication step for the user; and
if the second instance of said first factor authentication step is within the predetermined period of time, not perform the second instance of said second factor authentication step for the user.
8. The computer-readable storage medium as set forth in claim 7 , wherein the first communications network is selected from the group consisting of a private data network, a local area network, a wide area network, or a public network.
9. The computer-readable storage medium as set forth in claim 7 , wherein the first communications network is the Internet.
10. The computer-readable storage medium as set forth in claim 7 , wherein the input of said first user authentication information is immediately prior to the user accessing said resource.
11. The computer-readable storage medium as set forth in claim 7 , wherein the first factor authentication information comprises a username and password.
12. The computer-readable storage medium as set forth in claim 7 , wherein the second communications network is selected from the group consisting of a public switched telephone network and an Internet Protocol network.
13. A method of authenticating a user for accessing a resource, said method relying on multi-factor authentication of the user, the method comprising the steps of:
associating the user with a first factor authentication information;
associating the user with a second factor authentication information;
receiving information of a first instance of a first factor authentication step, said first factor authentication step comprising the user inputting a first user authentication information across a first communications network and matching the first user authentication information to the first factor authentication information; and
upon receipt of the information of the first instance of the first factor authentication step, performing a first instance of a second factor authentication step, said second factor authentication step comprising—
placing a first telephone call or sending a first text message to the user across a second communications network at a pre-registered number associated with a telecommunications device of the user,
in response to placing said first telephone call or sending said first text message to the user, receiving a second user authentication information inputted by the user at the user's telecommunications device,
confirming that said second user authentication information provided by the user via the user's telecommunications device matches the second factor authentication information,
if the second user authentication information matches the second factor authentication information, identifying the user as being authorized to access the resource, and
if the second user authentication information does not match the second factor authentication information, identifying the user as not being authorized to access the resource, and placing a second telephone call or sending a second text message to the user across the second communications network at the pre-registered number, wherein the second telephone call or the second text message includes information notifying the user that the second factor authentication step failed and that the user must initiate a second instance of said first factor and said second factor authentication steps.
14. The method as set forth in claim 13 , wherein the first communications network is selected from the group consisting of a private data network, a local area network, a wide area network, or a public network.
15. The method as set forth in claim 13 , wherein the first communications network is the Internet.
16. The method as set forth in claim 13 , wherein the input of said first user authentication information is immediately prior to the user accessing said resource.
17. The method as set forth in claim 13 , wherein the first factor authentication information comprises a username and password.
18. The method as set forth in claim 13 , wherein the second communications network is selected from the group consisting of a public switched telephone network and an Internet Protocol network.
Priority Applications (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US13/751,420 US20130185775A1 (en) | 2006-11-16 | 2013-01-28 | Multi factor authentication |
Applications Claiming Priority (4)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US86606806P | 2006-11-16 | 2006-11-16 | |
US93909107P | 2007-05-21 | 2007-05-21 | |
US11/862,173 US8365258B2 (en) | 2006-11-16 | 2007-09-26 | Multi factor authentication |
US13/751,420 US20130185775A1 (en) | 2006-11-16 | 2013-01-28 | Multi factor authentication |
Related Parent Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US11/862,173 Continuation US8365258B2 (en) | 2006-11-16 | 2007-09-26 | Multi factor authentication |
Publications (1)
Publication Number | Publication Date |
---|---|
US20130185775A1 true US20130185775A1 (en) | 2013-07-18 |
Family
ID=39418424
Family Applications (2)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US11/862,173 Expired - Fee Related US8365258B2 (en) | 2006-11-16 | 2007-09-26 | Multi factor authentication |
US13/751,420 Abandoned US20130185775A1 (en) | 2006-11-16 | 2013-01-28 | Multi factor authentication |
Family Applications Before (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US11/862,173 Expired - Fee Related US8365258B2 (en) | 2006-11-16 | 2007-09-26 | Multi factor authentication |
Country Status (1)
Country | Link |
---|---|
US (2) | US8365258B2 (en) |
Cited By (14)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20090144810A1 (en) * | 2007-12-03 | 2009-06-04 | Gilboy Christopher P | Method and apparatus for providing authentication |
WO2016032206A3 (en) * | 2014-08-29 | 2016-04-21 | Samsung Electronics Co., Ltd. | Authentication method and apparatus using biometric information and context information |
US10674009B1 (en) | 2013-11-07 | 2020-06-02 | Rightquestion, Llc | Validating automatic number identification data |
US10715543B2 (en) | 2016-11-30 | 2020-07-14 | Agari Data, Inc. | Detecting computer security risk based on previously observed communications |
US10805270B2 (en) | 2016-09-26 | 2020-10-13 | Agari Data, Inc. | Mitigating communication risk by verifying a sender of a message |
US10805314B2 (en) | 2017-05-19 | 2020-10-13 | Agari Data, Inc. | Using message context to evaluate security of requested data |
US10880322B1 (en) | 2016-09-26 | 2020-12-29 | Agari Data, Inc. | Automated tracking of interaction with a resource of a message |
US11019076B1 (en) | 2017-04-26 | 2021-05-25 | Agari Data, Inc. | Message security assessment using sender identity profiles |
US11044267B2 (en) | 2016-11-30 | 2021-06-22 | Agari Data, Inc. | Using a measure of influence of sender in determining a security risk associated with an electronic message |
US11051163B1 (en) | 2017-05-16 | 2021-06-29 | BlueOwl, LLC | Systems and methods for one-click two-factor authentication |
US11102244B1 (en) | 2017-06-07 | 2021-08-24 | Agari Data, Inc. | Automated intelligence gathering |
US11722513B2 (en) | 2016-11-30 | 2023-08-08 | Agari Data, Inc. | Using a measure of influence of sender in determining a security risk associated with an electronic message |
US11757914B1 (en) | 2017-06-07 | 2023-09-12 | Agari Data, Inc. | Automated responsive message to determine a security risk of a message sender |
US11936604B2 (en) | 2016-09-26 | 2024-03-19 | Agari Data, Inc. | Multi-level security analysis and intermediate delivery of an electronic message |
Families Citing this family (183)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20070255843A1 (en) * | 2006-04-28 | 2007-11-01 | Zubev Alexander I | Configuration of clients for multiple computer services |
US9762576B2 (en) * | 2006-11-16 | 2017-09-12 | Phonefactor, Inc. | Enhanced multi factor authentication |
US7921454B2 (en) * | 2007-10-22 | 2011-04-05 | International Business Machines Corporation | System and method for user password protection |
US20090125992A1 (en) * | 2007-11-09 | 2009-05-14 | Bo Larsson | System and method for establishing security credentials using sms |
US7930732B2 (en) * | 2008-02-22 | 2011-04-19 | Novell, Inc. | Techniques for secure transparent switching between modes of a virtual private network (VPN) |
US20100125635A1 (en) * | 2008-11-17 | 2010-05-20 | Vadim Axelrod | User authentication using alternative communication channels |
US20100132017A1 (en) * | 2008-11-21 | 2010-05-27 | Avaya, Inc. | Process for authenticating a user by certificate using an out-of band message exchange |
US8774864B2 (en) * | 2008-12-24 | 2014-07-08 | St-Ericsson Sa | Locking of communication device |
US8612768B2 (en) * | 2009-01-08 | 2013-12-17 | Microsoft Corporation | Unique account identification |
US9357384B2 (en) * | 2009-02-09 | 2016-05-31 | International Business Machines Corporation | System and method to support identity theft protection as part of a distributed service oriented ecosystem |
US9313196B2 (en) | 2009-11-06 | 2016-04-12 | Certified Cyber Solutions, Inc. | System and method for secure access of a remote system |
US20110162023A1 (en) * | 2009-12-30 | 2011-06-30 | Marcus Kellerman | Method and system for providing correlated advertisement for complete internet anywhere |
US8850196B2 (en) | 2010-03-29 | 2014-09-30 | Motorola Solutions, Inc. | Methods for authentication using near-field |
US9659164B2 (en) * | 2011-08-02 | 2017-05-23 | Qualcomm Incorporated | Method and apparatus for using a multi-factor password or a dynamic password for enhanced security on a device |
US20130055379A1 (en) * | 2011-08-23 | 2013-02-28 | Research In Motion Limited | System, device and method for authentication |
US9215225B2 (en) | 2013-03-29 | 2015-12-15 | Citrix Systems, Inc. | Mobile device locking with context |
US9280377B2 (en) | 2013-03-29 | 2016-03-08 | Citrix Systems, Inc. | Application with multiple operation modes |
US8881229B2 (en) | 2011-10-11 | 2014-11-04 | Citrix Systems, Inc. | Policy-based application management |
US20140053234A1 (en) | 2011-10-11 | 2014-02-20 | Citrix Systems, Inc. | Policy-Based Application Management |
US8869235B2 (en) | 2011-10-11 | 2014-10-21 | Citrix Systems, Inc. | Secure mobile browser for protecting enterprise data |
US20140032733A1 (en) | 2011-10-11 | 2014-01-30 | Citrix Systems, Inc. | Policy-Based Application Management |
CN103188221B (en) * | 2011-12-28 | 2018-01-30 | 腾讯科技(深圳)有限公司 | application program login method, device and mobile terminal |
US8613066B1 (en) * | 2011-12-30 | 2013-12-17 | Amazon Technologies, Inc. | Techniques for user authentication |
US9092427B2 (en) * | 2012-06-08 | 2015-07-28 | Lockheed Martin Corporation | Dynamic trust session |
CA2818439A1 (en) * | 2012-07-05 | 2014-01-05 | Cyber-Ark Software Ltd. | System and method for out-of-band application authentication |
US9015808B1 (en) * | 2012-07-11 | 2015-04-21 | Sprint Communications Company L.P. | Restricting mobile device services between an occurrence of an account change and acquisition of a security code |
KR101960062B1 (en) * | 2012-08-24 | 2019-03-19 | 삼성전자주식회사 | Content Sharing Method and Device Thereof |
US9424543B2 (en) | 2012-09-27 | 2016-08-23 | International Business Machines Corporation | Authenticating a response to a change request |
US8613070B1 (en) | 2012-10-12 | 2013-12-17 | Citrix Systems, Inc. | Single sign-on access in an orchestration framework for connected devices |
US9516022B2 (en) | 2012-10-14 | 2016-12-06 | Getgo, Inc. | Automated meeting room |
US20140109171A1 (en) * | 2012-10-15 | 2014-04-17 | Citrix Systems, Inc. | Providing Virtualized Private Network tunnels |
US20140109176A1 (en) | 2012-10-15 | 2014-04-17 | Citrix Systems, Inc. | Configuring and providing profiles that manage execution of mobile applications |
US8910239B2 (en) * | 2012-10-15 | 2014-12-09 | Citrix Systems, Inc. | Providing virtualized private network tunnels |
US9606774B2 (en) | 2012-10-16 | 2017-03-28 | Citrix Systems, Inc. | Wrapping an application with field-programmable business logic |
US9971585B2 (en) | 2012-10-16 | 2018-05-15 | Citrix Systems, Inc. | Wrapping unmanaged applications on a mobile device |
US20140108793A1 (en) | 2012-10-16 | 2014-04-17 | Citrix Systems, Inc. | Controlling mobile device access to secure data |
US9170800B2 (en) | 2012-10-16 | 2015-10-27 | Citrix Systems, Inc. | Application wrapping for application management framework |
US8806205B2 (en) | 2012-12-27 | 2014-08-12 | Motorola Solutions, Inc. | Apparatus for and method of multi-factor authentication among collaborating communication devices |
US8782766B1 (en) | 2012-12-27 | 2014-07-15 | Motorola Solutions, Inc. | Method and apparatus for single sign-on collaboration among mobile devices |
US9332431B2 (en) | 2012-12-27 | 2016-05-03 | Motorola Solutions, Inc. | Method of and system for authenticating and operating personal communication devices over public safety networks |
US8955081B2 (en) | 2012-12-27 | 2015-02-10 | Motorola Solutions, Inc. | Method and apparatus for single sign-on collaboraton among mobile devices |
US9648014B2 (en) * | 2013-03-15 | 2017-05-09 | Christopher Tobin | Methods and apparatus for non-contact radio frequency detection and automatic establishment of corresponding communication channel |
US9413736B2 (en) | 2013-03-29 | 2016-08-09 | Citrix Systems, Inc. | Providing an enterprise application store |
US9985850B2 (en) | 2013-03-29 | 2018-05-29 | Citrix Systems, Inc. | Providing mobile device management functionalities |
US20140297840A1 (en) | 2013-03-29 | 2014-10-02 | Citrix Systems, Inc. | Providing mobile device management functionalities |
US9355223B2 (en) | 2013-03-29 | 2016-05-31 | Citrix Systems, Inc. | Providing a managed browser |
US8813179B1 (en) | 2013-03-29 | 2014-08-19 | Citrix Systems, Inc. | Providing mobile device management functionalities |
US8849979B1 (en) | 2013-03-29 | 2014-09-30 | Citrix Systems, Inc. | Providing mobile device management functionalities |
US10284627B2 (en) | 2013-03-29 | 2019-05-07 | Citrix Systems, Inc. | Data management for an application with multiple operation modes |
US9137245B2 (en) * | 2013-04-26 | 2015-09-15 | Tencent Technology (Shenzhen) Company Limited | Login method, apparatus, and system |
NL2010733C2 (en) * | 2013-04-29 | 2014-10-30 | Baseline Automatisering B V | METHODS FOR AUTHENTICATION, SERVER, DEVICE AND DATA CARRIER. |
WO2015034384A1 (en) | 2013-09-04 | 2015-03-12 | Churyumov Anton Nikolaevich | Apparatus and method for authenticating a user via multiple user devices |
US9319419B2 (en) * | 2013-09-26 | 2016-04-19 | Wave Systems Corp. | Device identification scoring |
US9201840B2 (en) * | 2014-04-21 | 2015-12-01 | Iboss, Inc. | Generating proxy automatic configuration scripts |
CN105024986B (en) * | 2014-04-30 | 2019-09-17 | 腾讯科技(深圳)有限公司 | The methods, devices and systems that account number logs in |
US11736468B2 (en) * | 2015-03-16 | 2023-08-22 | Assa Abloy Ab | Enhanced authorization |
US10219154B1 (en) | 2015-08-18 | 2019-02-26 | Richard J. Hallock | Frictionless or near-frictionless 3 factor user authentication method and system by use of triad network |
CN106603461A (en) | 2015-10-14 | 2017-04-26 | 阿里巴巴集团控股有限公司 | Business authentication method, apparatus and system |
US10164973B1 (en) * | 2015-12-02 | 2018-12-25 | United Services Automobile Association (Usaa) | Public authentication systems and methods |
US11017376B1 (en) | 2015-12-28 | 2021-05-25 | Wells Fargo Bank, N.A. | Mobile device-based dual custody verification using micro-location |
US10356081B2 (en) * | 2016-01-29 | 2019-07-16 | Cable Television Laboratories, Inc. | Systems and methods for secure automated network attachment |
US11132425B1 (en) * | 2016-07-07 | 2021-09-28 | Wells Fargo Bank, N.A. | Systems and methods for location-binding authentication |
US10275590B2 (en) | 2016-09-27 | 2019-04-30 | Bank Of America Corporation | Distributed trust as secondary authentication mechanism |
US10547600B2 (en) | 2016-09-30 | 2020-01-28 | Palo Alto Networks, Inc. | Multifactor authentication as a network service |
US10225243B2 (en) | 2016-09-30 | 2019-03-05 | Palo Alto Networks, Inc. | Intercept-based multifactor authentication enrollment of clients as a network service |
US10701049B2 (en) | 2016-09-30 | 2020-06-30 | Palo Alto Networks, Inc. | Time-based network authentication challenges |
US10367784B2 (en) | 2016-09-30 | 2019-07-30 | Palo Alto Networks, Inc. | Detection of compromised credentials as a network service |
US10789386B2 (en) * | 2016-11-09 | 2020-09-29 | Reavire, Inc. | Dispatching identity information from secure hardware appliance |
EP3340560A1 (en) * | 2016-12-22 | 2018-06-27 | Mastercard International Incorporated | Mobile device user validation method and system |
US10860703B1 (en) * | 2017-08-17 | 2020-12-08 | Walgreen Co. | Online authentication and security management using device-based identification |
US11558365B1 (en) * | 2017-10-10 | 2023-01-17 | NortonLifeLock Inc. | Multi-second factor authentication |
US10911464B2 (en) | 2018-04-27 | 2021-02-02 | Oracle International Corporation | Framework for multi-level and multi-factor inline enrollment |
US10546444B2 (en) | 2018-06-21 | 2020-01-28 | Capital One Services, Llc | Systems and methods for secure read-only authentication |
US11050740B2 (en) | 2018-09-09 | 2021-06-29 | OneLogin, Inc. | Third party multi-factor authentication with push notifications |
SG11202101874SA (en) | 2018-10-02 | 2021-03-30 | Capital One Services Llc | Systems and methods for cryptographic authentication of contactless cards |
KR20210065961A (en) | 2018-10-02 | 2021-06-04 | 캐피탈 원 서비시즈, 엘엘씨 | System and method for cryptographic authentication of contactless card |
US10949520B2 (en) | 2018-10-02 | 2021-03-16 | Capital One Services, Llc | Systems and methods for cross coupling risk analytics and one-time-passcodes |
CA3115084A1 (en) | 2018-10-02 | 2020-04-09 | Capital One Services, Llc | Systems and methods for cryptographic authentication of contactless cards |
US10581611B1 (en) | 2018-10-02 | 2020-03-03 | Capital One Services, Llc | Systems and methods for cryptographic authentication of contactless cards |
AU2019351911A1 (en) | 2018-10-02 | 2021-02-25 | Capital One Services, Llc | Systems and methods for cryptographic authentication of contactless cards |
US10511443B1 (en) | 2018-10-02 | 2019-12-17 | Capital One Services, Llc | Systems and methods for cryptographic authentication of contactless cards |
WO2020072552A1 (en) | 2018-10-02 | 2020-04-09 | Capital One Services, Llc | Systems and methods for cryptographic authentication of contactless cards |
US10542036B1 (en) | 2018-10-02 | 2020-01-21 | Capital One Services, Llc | Systems and methods for signaling an attack on contactless cards |
KR20210065109A (en) | 2018-10-02 | 2021-06-03 | 캐피탈 원 서비시즈, 엘엘씨 | System and method for cryptographic authentication of contactless card |
US11210664B2 (en) | 2018-10-02 | 2021-12-28 | Capital One Services, Llc | Systems and methods for amplifying the strength of cryptographic algorithms |
US10748138B2 (en) | 2018-10-02 | 2020-08-18 | Capital One Services, Llc | Systems and methods for cryptographic authentication of contactless cards |
CA3115107A1 (en) | 2018-10-02 | 2020-04-09 | Capital One Services, Llc | Systems and methods for cryptographic authentication of contactless cards |
US10607214B1 (en) | 2018-10-02 | 2020-03-31 | Capital One Services, Llc | Systems and methods for cryptographic authentication of contactless cards |
WO2020072687A1 (en) | 2018-10-02 | 2020-04-09 | Capital One Services, Llc | Systems and methods for cryptographic authentication of contactless cards |
CA3115142A1 (en) | 2018-10-02 | 2020-04-09 | Capital One Services, Llc | Systems and methods for cryptographic authentication of contactless cards |
US10505738B1 (en) | 2018-10-02 | 2019-12-10 | Capital One Services, Llc | Systems and methods for cryptographic authentication of contactless cards |
JP2022502901A (en) | 2018-10-02 | 2022-01-11 | キャピタル・ワン・サービシーズ・リミテッド・ライアビリティ・カンパニーCapital One Services, LLC | Systems and methods for cryptographic authentication of non-contact cards |
US10783519B2 (en) | 2018-10-02 | 2020-09-22 | Capital One Services, Llc | Systems and methods for cryptographic authentication of contactless cards |
US10565587B1 (en) | 2018-10-02 | 2020-02-18 | Capital One Services, Llc | Systems and methods for cryptographic authentication of contactless cards |
US10554411B1 (en) | 2018-10-02 | 2020-02-04 | Capital One Services, Llc | Systems and methods for cryptographic authentication of contactless cards |
US10771254B2 (en) | 2018-10-02 | 2020-09-08 | Capital One Services, Llc | Systems and methods for email-based card activation |
US10582386B1 (en) | 2018-10-02 | 2020-03-03 | Capital One Services, Llc | Systems and methods for cryptographic authentication of contactless cards |
SG11202101171VA (en) | 2018-10-02 | 2021-03-30 | Capital One Services Llc | Systems and methods for cryptographic authentication of contactless cards |
US10771253B2 (en) | 2018-10-02 | 2020-09-08 | Capital One Services, Llc | Systems and methods for cryptographic authentication of contactless cards |
US10592710B1 (en) | 2018-10-02 | 2020-03-17 | Capital One Services, Llc | Systems and methods for cryptographic authentication of contactless cards |
US10909527B2 (en) | 2018-10-02 | 2021-02-02 | Capital One Services, Llc | Systems and methods for performing a reissue of a contactless card |
US10579998B1 (en) | 2018-10-02 | 2020-03-03 | Capital One Services, Llc | Systems and methods for cryptographic authentication of contactless cards |
US10489781B1 (en) | 2018-10-02 | 2019-11-26 | Capital One Services, Llc | Systems and methods for cryptographic authentication of contactless cards |
WO2020072583A1 (en) | 2018-10-02 | 2020-04-09 | Capital One Services, Llc | Systems and methods for establishing identity for order pick up |
US11139975B2 (en) | 2018-11-19 | 2021-10-05 | International Business Machines Corporation | Authentication in non-secure communication channels via secure out-of-bands channels |
US20200226581A1 (en) | 2019-01-11 | 2020-07-16 | Capital One Services, Llc | Systems and methods for touch screen interface interaction using a card overlay |
US10944743B2 (en) | 2019-01-22 | 2021-03-09 | Adp, Llc | Rich communication services security authentication system |
US11037136B2 (en) | 2019-01-24 | 2021-06-15 | Capital One Services, Llc | Tap to autofill card data |
US10467622B1 (en) | 2019-02-01 | 2019-11-05 | Capital One Services, Llc | Using on-demand applications to generate virtual numbers for a contactless card to securely autofill forms |
US10510074B1 (en) | 2019-02-01 | 2019-12-17 | Capital One Services, Llc | One-tap payment using a contactless card |
US11120453B2 (en) | 2019-02-01 | 2021-09-14 | Capital One Services, Llc | Tap card to securely generate card data to copy to clipboard |
US10425129B1 (en) | 2019-02-27 | 2019-09-24 | Capital One Services, Llc | Techniques to reduce power consumption in near field communication systems |
JP7234699B2 (en) * | 2019-03-05 | 2023-03-08 | ブラザー工業株式会社 | Application program and information processing device |
US10523708B1 (en) * | 2019-03-18 | 2019-12-31 | Capital One Services, Llc | System and method for second factor authentication of customer support calls |
US11082229B2 (en) | 2019-03-18 | 2021-08-03 | Capital One Services, Llc | System and method for pre-authentication of customer support calls |
GB2582326B (en) * | 2019-03-19 | 2023-05-31 | Securenvoy Ltd | A method of mutual authentication |
US10984416B2 (en) | 2019-03-20 | 2021-04-20 | Capital One Services, Llc | NFC mobile currency transfer |
US10535062B1 (en) | 2019-03-20 | 2020-01-14 | Capital One Services, Llc | Using a contactless card to securely share personal data stored in a blockchain |
US10643420B1 (en) | 2019-03-20 | 2020-05-05 | Capital One Services, Llc | Contextual tapping engine |
US10438437B1 (en) | 2019-03-20 | 2019-10-08 | Capital One Services, Llc | Tap to copy data to clipboard via NFC |
US10970712B2 (en) | 2019-03-21 | 2021-04-06 | Capital One Services, Llc | Delegated administration of permissions using a contactless card |
US11521262B2 (en) | 2019-05-28 | 2022-12-06 | Capital One Services, Llc | NFC enhanced augmented reality information overlays |
US10516447B1 (en) | 2019-06-17 | 2019-12-24 | Capital One Services, Llc | Dynamic power levels in NFC card communications |
US11694187B2 (en) | 2019-07-03 | 2023-07-04 | Capital One Services, Llc | Constraining transactional capabilities for contactless cards |
US10871958B1 (en) | 2019-07-03 | 2020-12-22 | Capital One Services, Llc | Techniques to perform applet programming |
US11392933B2 (en) | 2019-07-03 | 2022-07-19 | Capital One Services, Llc | Systems and methods for providing online and hybridcard interactions |
US12086852B2 (en) | 2019-07-08 | 2024-09-10 | Capital One Services, Llc | Authenticating voice transactions with payment card |
US10713649B1 (en) | 2019-07-09 | 2020-07-14 | Capital One Services, Llc | System and method enabling mobile near-field communication to update display on a payment card |
US10498401B1 (en) | 2019-07-15 | 2019-12-03 | Capital One Services, Llc | System and method for guiding card positioning using phone sensors |
US10885514B1 (en) | 2019-07-15 | 2021-01-05 | Capital One Services, Llc | System and method for using image data to trigger contactless card transactions |
US11182771B2 (en) | 2019-07-17 | 2021-11-23 | Capital One Services, Llc | System for value loading onto in-vehicle device |
US10733601B1 (en) | 2019-07-17 | 2020-08-04 | Capital One Services, Llc | Body area network facilitated authentication or payment authorization |
US10832271B1 (en) | 2019-07-17 | 2020-11-10 | Capital One Services, Llc | Verified reviews using a contactless card |
US11521213B2 (en) | 2019-07-18 | 2022-12-06 | Capital One Services, Llc | Continuous authentication for digital services based on contactless card positioning |
US10506426B1 (en) | 2019-07-19 | 2019-12-10 | Capital One Services, Llc | Techniques for call authentication |
US10541995B1 (en) | 2019-07-23 | 2020-01-21 | Capital One Services, Llc | First factor contactless card authentication system and method |
JP2023503795A (en) | 2019-10-02 | 2023-02-01 | キャピタル・ワン・サービシーズ・リミテッド・ライアビリティ・カンパニー | Client Device Authentication Using Contactless Legacy Magnetic Stripe Data |
US10733283B1 (en) | 2019-12-23 | 2020-08-04 | Capital One Services, Llc | Secure password generation and management using NFC and contactless smart cards |
US10657754B1 (en) | 2019-12-23 | 2020-05-19 | Capital One Services, Llc | Contactless card and personal identification system |
US11651361B2 (en) | 2019-12-23 | 2023-05-16 | Capital One Services, Llc | Secure authentication based on passport data stored in a contactless card |
US10862540B1 (en) | 2019-12-23 | 2020-12-08 | Capital One Services, Llc | Method for mapping NFC field strength and location on mobile devices |
US11113685B2 (en) | 2019-12-23 | 2021-09-07 | Capital One Services, Llc | Card issuing with restricted virtual numbers |
US10885410B1 (en) | 2019-12-23 | 2021-01-05 | Capital One Services, Llc | Generating barcodes utilizing cryptographic techniques |
US11615395B2 (en) | 2019-12-23 | 2023-03-28 | Capital One Services, Llc | Authentication for third party digital wallet provisioning |
US11200563B2 (en) | 2019-12-24 | 2021-12-14 | Capital One Services, Llc | Account registration using a contactless card |
US10853795B1 (en) | 2019-12-24 | 2020-12-01 | Capital One Services, Llc | Secure authentication based on identity data stored in a contactless card |
US10664941B1 (en) | 2019-12-24 | 2020-05-26 | Capital One Services, Llc | Steganographic image encoding of biometric template information on a card |
US10909544B1 (en) | 2019-12-26 | 2021-02-02 | Capital One Services, Llc | Accessing and utilizing multiple loyalty point accounts |
US10757574B1 (en) | 2019-12-26 | 2020-08-25 | Capital One Services, Llc | Multi-factor authentication providing a credential via a contactless card for secure messaging |
US11038688B1 (en) | 2019-12-30 | 2021-06-15 | Capital One Services, Llc | Techniques to control applets for contactless cards |
US11455620B2 (en) | 2019-12-31 | 2022-09-27 | Capital One Services, Llc | Tapping a contactless card to a computing device to provision a virtual number |
US10860914B1 (en) | 2019-12-31 | 2020-12-08 | Capital One Services, Llc | Contactless card and method of assembly |
US11210656B2 (en) | 2020-04-13 | 2021-12-28 | Capital One Services, Llc | Determining specific terms for contactless card activation |
US11823175B2 (en) | 2020-04-30 | 2023-11-21 | Capital One Services, Llc | Intelligent card unlock |
US10861006B1 (en) | 2020-04-30 | 2020-12-08 | Capital One Services, Llc | Systems and methods for data access control using a short-range transceiver |
US11222342B2 (en) | 2020-04-30 | 2022-01-11 | Capital One Services, Llc | Accurate images in graphical user interfaces to enable data transfer |
US10915888B1 (en) | 2020-04-30 | 2021-02-09 | Capital One Services, Llc | Contactless card with multiple rotating security keys |
US11030339B1 (en) | 2020-04-30 | 2021-06-08 | Capital One Services, Llc | Systems and methods for data access control of personal user data using a short-range transceiver |
US10963865B1 (en) | 2020-05-12 | 2021-03-30 | Capital One Services, Llc | Augmented reality card activation experience |
US11063979B1 (en) | 2020-05-18 | 2021-07-13 | Capital One Services, Llc | Enabling communications between applications in a mobile operating system |
US11100511B1 (en) | 2020-05-18 | 2021-08-24 | Capital One Services, Llc | Application-based point of sale system in mobile operating systems |
US11062098B1 (en) | 2020-08-11 | 2021-07-13 | Capital One Services, Llc | Augmented reality information display and interaction via NFC based authentication |
US11165586B1 (en) | 2020-10-30 | 2021-11-02 | Capital One Services, Llc | Call center web-based authentication using a contactless card |
US11482312B2 (en) | 2020-10-30 | 2022-10-25 | Capital One Services, Llc | Secure verification of medical status using a contactless card |
US11373169B2 (en) | 2020-11-03 | 2022-06-28 | Capital One Services, Llc | Web-based activation of contactless cards |
US11216799B1 (en) | 2021-01-04 | 2022-01-04 | Capital One Services, Llc | Secure generation of one-time passcodes using a contactless card |
US11682012B2 (en) | 2021-01-27 | 2023-06-20 | Capital One Services, Llc | Contactless delivery systems and methods |
US11687930B2 (en) | 2021-01-28 | 2023-06-27 | Capital One Services, Llc | Systems and methods for authentication of access tokens |
US11562358B2 (en) | 2021-01-28 | 2023-01-24 | Capital One Services, Llc | Systems and methods for near field contactless card communication and cryptographic authentication |
US11792001B2 (en) | 2021-01-28 | 2023-10-17 | Capital One Services, Llc | Systems and methods for secure reprovisioning |
US11438329B2 (en) | 2021-01-29 | 2022-09-06 | Capital One Services, Llc | Systems and methods for authenticated peer-to-peer data transfer using resource locators |
US11777933B2 (en) | 2021-02-03 | 2023-10-03 | Capital One Services, Llc | URL-based authentication for payment cards |
US11637826B2 (en) | 2021-02-24 | 2023-04-25 | Capital One Services, Llc | Establishing authentication persistence |
US11245438B1 (en) | 2021-03-26 | 2022-02-08 | Capital One Services, Llc | Network-enabled smart apparatus and systems and methods for activating and provisioning same |
US11961089B2 (en) | 2021-04-20 | 2024-04-16 | Capital One Services, Llc | On-demand applications to extend web services |
US11935035B2 (en) | 2021-04-20 | 2024-03-19 | Capital One Services, Llc | Techniques to utilize resource locators by a contactless card to perform a sequence of operations |
US11902442B2 (en) | 2021-04-22 | 2024-02-13 | Capital One Services, Llc | Secure management of accounts on display devices using a contactless card |
US11354555B1 (en) | 2021-05-04 | 2022-06-07 | Capital One Services, Llc | Methods, mediums, and systems for applying a display to a transaction card |
US12041172B2 (en) | 2021-06-25 | 2024-07-16 | Capital One Services, Llc | Cryptographic authentication to control access to storage devices |
US12061682B2 (en) | 2021-07-19 | 2024-08-13 | Capital One Services, Llc | System and method to perform digital authentication using multiple channels of communication |
US12062258B2 (en) | 2021-09-16 | 2024-08-13 | Capital One Services, Llc | Use of a payment card to unlock a lock |
US12069173B2 (en) | 2021-12-15 | 2024-08-20 | Capital One Services, Llc | Key recovery based on contactless card authentication |
CN114826745A (en) * | 2022-04-28 | 2022-07-29 | 成都安恒信息技术有限公司 | Method for realizing user authentication in transparent scene |
Citations (31)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5878143A (en) * | 1996-08-16 | 1999-03-02 | Net 1, Inc. | Secure transmission of sensitive information over a public/insecure communications medium |
US6012144A (en) * | 1996-10-08 | 2000-01-04 | Pickett; Thomas E. | Transaction security method and apparatus |
US20040078571A1 (en) * | 2000-12-27 | 2004-04-22 | Henry Haverinen | Authentication in data communication |
US6731731B1 (en) * | 1999-07-30 | 2004-05-04 | Comsquare Co., Ltd. | Authentication method, authentication system and recording medium |
US20040243832A1 (en) * | 2001-10-17 | 2004-12-02 | Saar Wilf | Verification of a person identifier received online |
US20060015743A1 (en) * | 2004-07-15 | 2006-01-19 | Anakam L.L.C. | System and method for blocking unauthorized network log in using stolen password |
US20060179304A1 (en) * | 2002-03-30 | 2006-08-10 | Min-Gyu Han | Instant log-in method for authentificating a user and settling bills by using two different communication channels and a system thereof |
US20060190980A1 (en) * | 2003-07-14 | 2006-08-24 | Sony Corporation | Information processing device, information processing method, and information processing program |
US20060204051A1 (en) * | 2005-03-10 | 2006-09-14 | Debix One, Inc. | Method and system for managing account information |
US7142840B1 (en) * | 2003-02-20 | 2006-11-28 | Sprint Spectrum L.P. | Method and system for multi-network authorization and authentication |
US20070027807A1 (en) * | 2005-07-29 | 2007-02-01 | Alexandre Bronstein | Protecting against fraud by impersonation |
US20070079135A1 (en) * | 2005-10-04 | 2007-04-05 | Forval Technology, Inc. | User authentication system and user authentication method |
US20070079136A1 (en) * | 2005-09-30 | 2007-04-05 | Sbc Knowledge Ventures, Lp | Methods and systems for using data processing systems in order to authenticate parties |
US20070107050A1 (en) * | 2005-11-07 | 2007-05-10 | Jexp, Inc. | Simple two-factor authentication |
US20070136573A1 (en) * | 2005-12-05 | 2007-06-14 | Joseph Steinberg | System and method of using two or more multi-factor authentication mechanisms to authenticate online parties |
US20070150946A1 (en) * | 2005-12-23 | 2007-06-28 | Nortel Networks Limited | Method and apparatus for providing remote access to an enterprise network |
US20070157298A1 (en) * | 2005-03-20 | 2007-07-05 | Timothy Dingwall | Method and system for providing user access to a secure application |
US20070199053A1 (en) * | 2006-02-13 | 2007-08-23 | Tricipher, Inc. | Flexible and adjustable authentication in cyberspace |
US20070203850A1 (en) * | 2006-02-15 | 2007-08-30 | Sapphire Mobile Systems, Inc. | Multifactor authentication system |
US20070250632A1 (en) * | 2005-05-11 | 2007-10-25 | Takashi Nomura | Processing Device, Method for Establishing Processing Device Communication Session, Program, and Recording Medium |
US20080010674A1 (en) * | 2006-07-05 | 2008-01-10 | Nortel Networks Limited | Method and apparatus for authenticating users of an emergency communication network |
US20080086767A1 (en) * | 2006-10-06 | 2008-04-10 | Rajandra Luxman Kulkarni | Multi-party, secure Multi-Channel Authentication |
US20080098464A1 (en) * | 2006-10-24 | 2008-04-24 | Authernative, Inc. | Two-channel challenge-response authentication method in random partial shared secret recognition system |
US20080115198A1 (en) * | 2006-10-31 | 2008-05-15 | Hsu Paul J | Multi-factor authentication transfer |
US20090013388A1 (en) * | 2002-05-31 | 2009-01-08 | Holvey R David | Method and system for protecting information on a computer system |
US20100235276A1 (en) * | 2009-03-10 | 2010-09-16 | Boku, Inc. | Systems and Methods to Process User Initiated Transactions |
US8014756B1 (en) * | 2007-02-28 | 2011-09-06 | Intuit Inc. | Mobile authorization service |
US8191161B2 (en) * | 2005-12-13 | 2012-05-29 | Microsoft Corporation | Wireless authentication |
US20120274444A1 (en) * | 2002-04-08 | 2012-11-01 | Silvio Micali | Physical access control |
US20120295580A1 (en) * | 2011-05-19 | 2012-11-22 | Boku, Inc. | Systems and Methods to Detect Fraudulent Payment Requests |
US20130347129A1 (en) * | 2004-07-15 | 2013-12-26 | Anakam, Inc. | System and Method for Second Factor Authentication Services |
Family Cites Families (33)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5153918A (en) | 1990-11-19 | 1992-10-06 | Vorec Corporation | Security system for data communications |
JPH10507053A (en) | 1995-05-24 | 1998-07-07 | ウォーカー・アセット・マネイジメント・リミテッド・パートナーシップ | 900th Billing and Collection System and Method for Online Computer Services |
US5617470A (en) * | 1995-06-02 | 1997-04-01 | Depasquale; George B. | Apparatus and method for preventing unauthorized access to a system |
US6298120B1 (en) | 1996-06-28 | 2001-10-02 | At&T Corp. | Intelligent processing for establishing communication over the internet |
US6868391B1 (en) | 1997-04-15 | 2005-03-15 | Telefonaktiebolaget Lm Ericsson (Publ) | Tele/datacommunications payment method and apparatus |
US6016476A (en) | 1997-08-11 | 2000-01-18 | International Business Machines Corporation | Portable information and transaction processing system and method utilizing biometric authorization and digital certificate security |
US5979875A (en) * | 1997-08-21 | 1999-11-09 | Yocum; David C. | Mechanical jack transmission |
US6157705A (en) | 1997-12-05 | 2000-12-05 | E*Trade Group, Inc. | Voice control of a server |
FI980427A (en) | 1998-02-25 | 1999-08-26 | Ericsson Telefon Ab L M | Procedure, arrangement and device for verification |
SE512440C2 (en) | 1998-05-27 | 2000-03-20 | Telia Ab | Method for secure telephony with mobility in a telephone and data communication system comprising an IP network |
US6604086B1 (en) | 1998-07-20 | 2003-08-05 | Usa Technologies, Inc. | Electronic commerce terminal connected to a vending machine operable as a telephone |
US6097800A (en) * | 1999-03-09 | 2000-08-01 | Lucent Technologies, Inc. | Network controlled telephone for the visually impaired |
FR2794917B1 (en) * | 1999-06-10 | 2001-08-31 | Cit Alcatel | METHOD FOR AUTHORIZING ACCESS TO A CELLULAR RADIOCOMMUNICATION NETWORK FROM A SIMPLIFIED TELEPHONE, RADIOCOMMUNICATION SYSTEM AND SIMPLIFIED TELEPHONE THEREOF |
US6934858B2 (en) | 1999-12-15 | 2005-08-23 | Authentify, Inc. | System and method of using the public switched telephone network in providing authentication or authorization for online transactions |
US7870599B2 (en) | 2000-09-05 | 2011-01-11 | Netlabs.Com, Inc. | Multichannel device utilizing a centralized out-of-band authentication system (COBAS) |
US6990472B2 (en) * | 2000-10-23 | 2006-01-24 | Starpound Corporation | Telecommunications initiated data fulfillment system |
US20020083012A1 (en) * | 2000-11-16 | 2002-06-27 | Steve Bush | Method and system for account management |
US20020138635A1 (en) * | 2001-03-26 | 2002-09-26 | Nec Usa, Inc. | Multi-ISP controlled access to IP networks, based on third-party operated untrusted access stations |
US6829467B2 (en) * | 2001-09-25 | 2004-12-07 | Toshiba Tec Kabushiki Kaisha | Apparatus for settling accounts and method of settling accounts |
US6693530B1 (en) * | 2001-10-16 | 2004-02-17 | At&T Corp. | Home security administration platform |
US20030115203A1 (en) * | 2001-12-19 | 2003-06-19 | Wendell Brown | Subscriber data page for augmenting a subscriber connection with another party |
US7461258B2 (en) | 2002-05-24 | 2008-12-02 | Authentify, Inc. | Use of public switched telephone network for capturing electronic signatures in on-line transactions |
US7383572B2 (en) | 2002-05-24 | 2008-06-03 | Authentify, Inc. | Use of public switched telephone network for authentication and authorization in on-line transactions |
US8539232B2 (en) * | 2002-06-26 | 2013-09-17 | Sony Corporation | Information terminal apparatus, information processing apparatus and information communication system |
CA2518055A1 (en) * | 2003-03-04 | 2004-09-16 | Gamelogic, Inc. | User authentication system and method |
US8171303B2 (en) | 2004-11-03 | 2012-05-01 | Astav, Inc. | Authenticating a login |
US9094194B2 (en) * | 2006-04-18 | 2015-07-28 | International Business Machines Corporation | Method and system for automating the recovery of a credential store when a user has forgotten their password using a temporary key pair created based on a new password provided by the user |
US20070250914A1 (en) * | 2006-04-19 | 2007-10-25 | Avaya Technology Llc | Method and system for resetting secure passwords |
KR100914548B1 (en) * | 2006-07-03 | 2009-09-02 | (주)씽크에이티 | The Preliminary Verification System which has a Authentication by Phone on the Internet Environment |
US20090235346A1 (en) * | 2007-07-19 | 2009-09-17 | Joseph Steinberg | System and method for augmented user and site authentication from mobile devices |
US20090302997A1 (en) | 2008-06-04 | 2009-12-10 | Alexandre Bronstein | Third-party access control |
JP2010224785A (en) * | 2009-03-23 | 2010-10-07 | Konica Minolta Business Technologies Inc | System and method for transferring data |
US20120221437A1 (en) * | 2011-02-24 | 2012-08-30 | Boku, Inc. | Systems and Methods to Automate Social Networking Activities |
-
2007
- 2007-09-26 US US11/862,173 patent/US8365258B2/en not_active Expired - Fee Related
-
2013
- 2013-01-28 US US13/751,420 patent/US20130185775A1/en not_active Abandoned
Patent Citations (31)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5878143A (en) * | 1996-08-16 | 1999-03-02 | Net 1, Inc. | Secure transmission of sensitive information over a public/insecure communications medium |
US6012144A (en) * | 1996-10-08 | 2000-01-04 | Pickett; Thomas E. | Transaction security method and apparatus |
US6731731B1 (en) * | 1999-07-30 | 2004-05-04 | Comsquare Co., Ltd. | Authentication method, authentication system and recording medium |
US20040078571A1 (en) * | 2000-12-27 | 2004-04-22 | Henry Haverinen | Authentication in data communication |
US20040243832A1 (en) * | 2001-10-17 | 2004-12-02 | Saar Wilf | Verification of a person identifier received online |
US20060179304A1 (en) * | 2002-03-30 | 2006-08-10 | Min-Gyu Han | Instant log-in method for authentificating a user and settling bills by using two different communication channels and a system thereof |
US20120274444A1 (en) * | 2002-04-08 | 2012-11-01 | Silvio Micali | Physical access control |
US20090013388A1 (en) * | 2002-05-31 | 2009-01-08 | Holvey R David | Method and system for protecting information on a computer system |
US7142840B1 (en) * | 2003-02-20 | 2006-11-28 | Sprint Spectrum L.P. | Method and system for multi-network authorization and authentication |
US20060190980A1 (en) * | 2003-07-14 | 2006-08-24 | Sony Corporation | Information processing device, information processing method, and information processing program |
US20060015743A1 (en) * | 2004-07-15 | 2006-01-19 | Anakam L.L.C. | System and method for blocking unauthorized network log in using stolen password |
US20130347129A1 (en) * | 2004-07-15 | 2013-12-26 | Anakam, Inc. | System and Method for Second Factor Authentication Services |
US20060204051A1 (en) * | 2005-03-10 | 2006-09-14 | Debix One, Inc. | Method and system for managing account information |
US20070157298A1 (en) * | 2005-03-20 | 2007-07-05 | Timothy Dingwall | Method and system for providing user access to a secure application |
US20070250632A1 (en) * | 2005-05-11 | 2007-10-25 | Takashi Nomura | Processing Device, Method for Establishing Processing Device Communication Session, Program, and Recording Medium |
US20070027807A1 (en) * | 2005-07-29 | 2007-02-01 | Alexandre Bronstein | Protecting against fraud by impersonation |
US20070079136A1 (en) * | 2005-09-30 | 2007-04-05 | Sbc Knowledge Ventures, Lp | Methods and systems for using data processing systems in order to authenticate parties |
US20070079135A1 (en) * | 2005-10-04 | 2007-04-05 | Forval Technology, Inc. | User authentication system and user authentication method |
US20070107050A1 (en) * | 2005-11-07 | 2007-05-10 | Jexp, Inc. | Simple two-factor authentication |
US20070136573A1 (en) * | 2005-12-05 | 2007-06-14 | Joseph Steinberg | System and method of using two or more multi-factor authentication mechanisms to authenticate online parties |
US8191161B2 (en) * | 2005-12-13 | 2012-05-29 | Microsoft Corporation | Wireless authentication |
US20070150946A1 (en) * | 2005-12-23 | 2007-06-28 | Nortel Networks Limited | Method and apparatus for providing remote access to an enterprise network |
US20070199053A1 (en) * | 2006-02-13 | 2007-08-23 | Tricipher, Inc. | Flexible and adjustable authentication in cyberspace |
US20070203850A1 (en) * | 2006-02-15 | 2007-08-30 | Sapphire Mobile Systems, Inc. | Multifactor authentication system |
US20080010674A1 (en) * | 2006-07-05 | 2008-01-10 | Nortel Networks Limited | Method and apparatus for authenticating users of an emergency communication network |
US20080086767A1 (en) * | 2006-10-06 | 2008-04-10 | Rajandra Luxman Kulkarni | Multi-party, secure Multi-Channel Authentication |
US20080098464A1 (en) * | 2006-10-24 | 2008-04-24 | Authernative, Inc. | Two-channel challenge-response authentication method in random partial shared secret recognition system |
US20080115198A1 (en) * | 2006-10-31 | 2008-05-15 | Hsu Paul J | Multi-factor authentication transfer |
US8014756B1 (en) * | 2007-02-28 | 2011-09-06 | Intuit Inc. | Mobile authorization service |
US20100235276A1 (en) * | 2009-03-10 | 2010-09-16 | Boku, Inc. | Systems and Methods to Process User Initiated Transactions |
US20120295580A1 (en) * | 2011-05-19 | 2012-11-22 | Boku, Inc. | Systems and Methods to Detect Fraudulent Payment Requests |
Cited By (30)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20090144810A1 (en) * | 2007-12-03 | 2009-06-04 | Gilboy Christopher P | Method and apparatus for providing authentication |
US8839386B2 (en) * | 2007-12-03 | 2014-09-16 | At&T Intellectual Property I, L.P. | Method and apparatus for providing authentication |
US20150007285A1 (en) * | 2007-12-03 | 2015-01-01 | At&T Intellectual Property I, L.P. | Method and apparatus for providing authentication |
US10755279B2 (en) | 2007-12-03 | 2020-08-25 | At&T Intellectual Property I, L.P. | Methods, systems and products for authentication |
US9380045B2 (en) * | 2007-12-03 | 2016-06-28 | At&T Intellectual Property I, L.P. | Method and apparatus for providing authentication |
US20160277402A1 (en) * | 2007-12-03 | 2016-09-22 | At&T Intellectual Property I, L.P. | Methods, Systems, and Products for Authentication |
US9712528B2 (en) * | 2007-12-03 | 2017-07-18 | At&T Intellectual Property I, L.P. | Methods, systems, and products for authentication |
US10694029B1 (en) | 2013-11-07 | 2020-06-23 | Rightquestion, Llc | Validating automatic number identification data |
US10674009B1 (en) | 2013-11-07 | 2020-06-02 | Rightquestion, Llc | Validating automatic number identification data |
US11856132B2 (en) | 2013-11-07 | 2023-12-26 | Rightquestion, Llc | Validating automatic number identification data |
US11005989B1 (en) | 2013-11-07 | 2021-05-11 | Rightquestion, Llc | Validating automatic number identification data |
US10609023B2 (en) | 2014-08-29 | 2020-03-31 | Samsung Electronics Co., Ltd | Authentication method and apparatus using biometric information and context information |
WO2016032206A3 (en) * | 2014-08-29 | 2016-04-21 | Samsung Electronics Co., Ltd. | Authentication method and apparatus using biometric information and context information |
US10880322B1 (en) | 2016-09-26 | 2020-12-29 | Agari Data, Inc. | Automated tracking of interaction with a resource of a message |
US11595354B2 (en) | 2016-09-26 | 2023-02-28 | Agari Data, Inc. | Mitigating communication risk by detecting similarity to a trusted message contact |
US10992645B2 (en) | 2016-09-26 | 2021-04-27 | Agari Data, Inc. | Mitigating communication risk by detecting similarity to a trusted message contact |
US10805270B2 (en) | 2016-09-26 | 2020-10-13 | Agari Data, Inc. | Mitigating communication risk by verifying a sender of a message |
US12074850B2 (en) | 2016-09-26 | 2024-08-27 | Agari Data, Inc. | Mitigating communication risk by verifying a sender of a message |
US11936604B2 (en) | 2016-09-26 | 2024-03-19 | Agari Data, Inc. | Multi-level security analysis and intermediate delivery of an electronic message |
US11044267B2 (en) | 2016-11-30 | 2021-06-22 | Agari Data, Inc. | Using a measure of influence of sender in determining a security risk associated with an electronic message |
US11722513B2 (en) | 2016-11-30 | 2023-08-08 | Agari Data, Inc. | Using a measure of influence of sender in determining a security risk associated with an electronic message |
US10715543B2 (en) | 2016-11-30 | 2020-07-14 | Agari Data, Inc. | Detecting computer security risk based on previously observed communications |
US11722497B2 (en) | 2017-04-26 | 2023-08-08 | Agari Data, Inc. | Message security assessment using sender identity profiles |
US11019076B1 (en) | 2017-04-26 | 2021-05-25 | Agari Data, Inc. | Message security assessment using sender identity profiles |
US11057374B1 (en) | 2017-05-16 | 2021-07-06 | BlueOwl, LLC | Systems and methods for one-click two-factor authentication |
US11051163B1 (en) | 2017-05-16 | 2021-06-29 | BlueOwl, LLC | Systems and methods for one-click two-factor authentication |
US11805119B1 (en) | 2017-05-16 | 2023-10-31 | BlueOwl, LLC | Systems and methods for one-click two-factor authentication |
US10805314B2 (en) | 2017-05-19 | 2020-10-13 | Agari Data, Inc. | Using message context to evaluate security of requested data |
US11102244B1 (en) | 2017-06-07 | 2021-08-24 | Agari Data, Inc. | Automated intelligence gathering |
US11757914B1 (en) | 2017-06-07 | 2023-09-12 | Agari Data, Inc. | Automated responsive message to determine a security risk of a message sender |
Also Published As
Publication number | Publication date |
---|---|
US8365258B2 (en) | 2013-01-29 |
US20080120711A1 (en) | 2008-05-22 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US8365258B2 (en) | Multi factor authentication | |
US10122715B2 (en) | Enhanced multi factor authentication | |
US8244875B2 (en) | Secure network computing | |
US9935788B2 (en) | Pluggable authentication and authorization | |
US8510811B2 (en) | Network transaction verification and authentication | |
EP3095225B1 (en) | Redirect to inspection proxy using single-sign-on bootstrapping | |
US9338007B1 (en) | Secure delegated authentication for applications | |
US7685631B1 (en) | Authentication of a server by a client to prevent fraudulent user interfaces | |
US8412156B2 (en) | Managing automatic log in to internet target resources | |
US20170063829A1 (en) | Systems and methods for location-based authentication | |
US20100107240A1 (en) | Network location determination for direct access networks | |
US20090328182A1 (en) | Enabling two-factor authentication for terminal services | |
CN112468481B (en) | Single-page and multi-page web application identity integrated authentication method based on CAS | |
KR20060126952A (en) | A persistent and reliable session securely traversing network components using an encapsulating protocol | |
KR20060047252A (en) | Account creation via a mobile device | |
US12015592B2 (en) | Zero trust approach to secure sensitive mobile applications and prevent distributed denial of service attacks | |
US10834074B2 (en) | Phishing attack prevention for OAuth applications | |
CA2912774C (en) | Providing single sign-on for wireless devices | |
CN115664761A (en) | Single sign-on method and device, electronic equipment and readable storage medium | |
EP3582469B1 (en) | Authentication using a mobile network operator system |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
AS | Assignment |
Owner name: PHONEFACTOR, INC., KANSAS Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:DISPENSA, STEPHEN T.;REEL/FRAME:029703/0556 Effective date: 20110805 |
|
STCB | Information on status: application discontinuation |
Free format text: ABANDONED -- FAILURE TO RESPOND TO AN OFFICE ACTION |