# Patent

## Title
Method and apparatus for network security using a router based authentication system

## Abstract

A router based authentication system provides packet level authentication of incoming data packets and eliminates the risk of having data packets come in to the network whose source cannot be authenticated. In Router Based Authentication System (RBAS), a prior art router is adapted with an authentication function that works in conjunction with a security function in the client. Alternatively, a new router can be built that embeds an authentication function. The router based authentication function includes: (i) an ability to receive a telephone call and verify the caller by comparing with pre-stored caller id, (ii) generate a random alphanumeric code, deliver to the caller, and save in the system, (iii) reject all packets from the client that do not have a passkey embedded in the header of the packet. The security function in the client includes (i) display of an authentication screen that may display a telephone number to a border or internal router of a computer network of a business and enables entry of the passkey made up of the telephone number of the user and the alphanumeric code, and (ii) a function that encrypts the passkey and inserts the passkey in the header of each outgoing data packet to the business.

## Background
CROSS REFERENCE TO RELATED APPLICATIONS
This application claims priority on Provisional Application Ser. No. 60/507,871, entitled “Method and Apparatus for Network Security Using a Router Based Authentication System” filed on Oct. 1, 2003, by Tara Chand Singhal. The contents of the Provisional Application Ser. No. 60/507,871 are incorporated herein by reference.
This application also claims priority on U.S. patent application Ser. No. 10/217,287, entitled “Method And Apparatus For User Authentication Using A Cellular Telephone And A Transient Pass Code” filed on Aug. 12, 2002, by Tara Chand Singhal. The contents of the U.S. patent application Ser. No.10/217,287 are incorporated herein by reference.


FIELD OF THE INVENTION
The present invention is directed to a method and apparatus for network access security using a router based authentication system for authenticating incoming data packets to a data network.
BACKGROUND
A business's computer network servers are protected by a border router, which hosts a firewall. The firewall checks and filters each incoming data packet, based an access control list programmed in the firewall. The access control list identifies the source and destination computer Internet Protocol (IP) addresses as well as destination computer port addresses. The firewall rejects al packets based on the source computer IP address, destination computer IP address and the destination computer port address that are listed in the access control list.
The header of the incoming data packets contains the source computer IP address, the destination computer IP address, and the destination computer port. IP denotes a unique address of every computer on a network and the port denotes the connection to a specific application of the computer.
The identification of source of a packet is in the form of an IP address, and is created and can be changed or altered to be set to any value by the source computer. Therefore, the destination computer cannot truly know where the packet came from or which computer it originated from. This is how spurious and harm causing data packets are sent to a computer over which the destination computer has no control since it cannot really authenticate the source of the data packet.
Therefore, a border router/firewall functions by checking each packet and filtering out those packets that are not for approved destination ports and did not come from a source IP and are not for a given destination IP as specified in the access control list. There are other types of firewall that may be placed before an application server that check for unauthorized or spurious content that is specific to that application in the packet.
In addition to the protection using border router/firewall to filter out data packets as described above, prior art teaches that the source authentication for each computer session between a source and a destination computer is performed using a user id and password. However, password is considered a weak form of authentication by the Information Security Experts as this form of authentication can be easily compromised.
Since there is no certainty that the sender of these data packets is who it says it is, the prior art may allow entry of data packets into a network that are harmful to a destination computer.
The industry solution to this state of weakness in protecting a network from harm has been to build an Intrusion Detection System (IDS). The IDS is a software function that is deployed on a server inside the network and monitors or sniffs all data packets traveling in the network. The IDS, copies all data packets in the network and applies rule and signature based logic to detect threat scenarios and alert the system managers that an attack may be taking place.
In the IDS approach, the data packets that cause harm have already entered the network in spite of the border router/firewall and the user authentication with a password. The IDS is a complex approach and does not work all the time creating many false alarms. It is so complex, that many businesses have hired other businesses to send them all the data traffic to a remote facility and let them monitor the data packets, thus also creating an issue of confidentiality of data going to another business.
Many businesses use card/token based strong (two-factor) source authentication in current systems for network access security. In card/token-based systems of access security, each employee of a business is given a card and a card reader. At the time of log in, the employee uses the card and a personal number in conjunction with the card to as well as a password to authenticate to the business computer system. The card/token based access control system is costly, has operational security and logistical issues, and therefore, is not widely used by businesses. Therefore businesses are using only a one-factor (password) authentication for establishing security of a session.
In light of the above, it is an objective of the present invention to have an apparatus and methods for network access security that does not have the deficiencies of the prior art as described above.
SUMMARY
The present invention is directed to a method and apparatus for network access security using a router based authentication system that provides a two factor packet level authentication for all incoming data packets from a source computer before routing them to the destination computer.
The two factors refer to something you know and something you have, out of the three possible factors including something you are such as a biometrics. These three factors are used in information security industry for judging the strength or adequacy of authentication. Any two factors combined yield a strong authentication, whereas one factor only such as a password (something you know) is considered a week form of user authentication.
In this invention, referred to as Router Based Authentication System (RBAS), a prior art router is adapted with an authentication function that works in conjunction with a security function in the client. Alternatively, a new router can be built that embeds an authentication function as described in this invention. Such authentication routers can be placed strategically inside a business's computer network. For example, they can be placed as border routers and major routers between sections of the network connecting different business function of the business.
The security function in the client includes (i) display of an authentication screen that may display a telephone number to a border or internal router of a computer network of a business and enables entry of the passkey made up of the telephone number of the user and the alphanumeric code, and (ii) a function that encrypts the passkey and inserts the passkey in the header of each outgoing data packet to the business.
The router based authentication function includes: (i) an ability to receive a telephone call and verify the caller by comparing with pre-stored caller id, (ii) generate a random alphanumeric code, deliver to the caller, and save in the system, (iii) reject all packets from the client that do not have a passkey embedded in the header of the packet.
The network access security using router based authentication system of this invention serves the businesses by eliminating the risk of having data packets come in to the network whose source cannot be authenticated. Thus eliminate the risk of being a target for hackers.



BRIEF DESCRIPTION OF THE DRAWINGS
The novel features of this invention, as well as the invention itself, both as to its structure and its operation, will be best understood from the accompanying drawings, taken in conjunction with the accompanying description, in which similar reference characters refer to similar parts. The drawings are:
FIG. 1A is a block diagram that illustrates a version of the current invention of a router based authentication system.
FIG. 1B is a comparison of other network access security technologies with the router based authentication system of the current invention.
FIG. 2A is a block diagram that illustrates the client security functions of the current invention.
FIG. 2B is a block diagram that illustrates router based authentication functions of the current invention.
FIG. 3A is a block diagram that illustrates the functions of an authentication router of the current invention.
FIG. 3B is a block diagram that illustrates a version of the border router based authentications system of the current invention.
FIG. 4 is a block diagram that illustrates placement of random passkey data in the packet header of the current invention.
FIG. 5 is a flow diagram that illustrates the operation of the router based authentication system.



DESCRIPTION
Introduction
Network access security technologies of prior art, perform session authentication using a user id and a password. Sometimes to make the session authentication additionally or more strong, a security token or a security card is used in addition to the password.
A Router Based Authentication System (RBAS) of the current invention, for network access security performs packet level authentication of the source of each data packet coming into a business's computer network. In addition this packet level authentication in the current invention is accomplished without the prior art card based access control systems that add additional cost, operational security, and logistics issues of stocking, distributing and maintaining the security tokens or security card and card readers.
RBAS uses and takes advantage of the existing public telephone network infrastructure and thus avoids the infrastructure cost of maintaining card dependent security systems of the prior art. In RBAS, the source authentication of incoming data packets to a border router of a computer network is performed via a two-factor authentication that leverages the public voice telephone using caller id features and a personal identification number (PIN).
Therefore, there are three main distinguishing features of RBAS compared to prior art user authentication. These are: (i) RBAS does a packet level authentication for every packet coming into a network from an authorized user, whereas in prior art a session authentication only is performed in the beginning of a session; (ii) RBAS does authentication at the border router, and can appropriately route the authenticated and non-authenticated data packets, whereas in prior art the authentication is done at the application server level; (iii) RBAS does two-factor authentication without the added cost and complexity of security tokens and biometrics as in prior art means of strong two-factor authentication.
With initial reference to FIG. 1A, the RBAS for network access security has, an authorized user 14 using a client 10 with a Client Security Software Function 18. The user 14 has a cellular telephone 12 with a telephone number 12A. There is an adapted border router 20 adapted with an interface to a telephone network 40, and authentication function 21. The adapted router 20 also includes a prior art router function 22. The client 10 communicates with the business server 30 via the border router 20 using the Internet 24. The adapted router 20 is capable of routing the packets to business network that may include business application server 30 which only authorized users 14 can access and open content server 31, which all unauthorized users can access.
With initial reference to also FIG. 2A, the authorized user 14 using the telephone 12 dials a telephone number assigned to the adapted border router 20 and receives an alphanumeric code 28. The user 14 uses security function 18 that uses a passkey 216 composed of the alphanumeric code 28 and the cell telephone number 12A, and a function 220 that embeds an encrypted version of the passkey 216 in the header of each packet to authenticate the packets to the border router 20.
In summary, an RBAS implementation has:
(A) A router adapted with an authentication system. The system is equipped with (i) an interactive voice response system, that verifies the caller by caller id and PIN and generates and voice delivers a random alphanumeric code to the user, (ii) a database that maintains the cell telephone numbers and PIN of authorized users, and (iii) a function that verifies each packet via a passkey in the header of each packet.
(B) A security software function that is present in the client of an authorized user that (i) displays an authentication screen with a telephone number of the adapted router, (ii) accepts the entry of the cell number plus the random alphanumeric as entry of a passkey, and (iii) encrypts the passkey and embeds the passkey in the option field of each packet header.
An added optional security feature lets the user pre-select the length of the session in minutes or have a default value that would enable the authentication functions 21 in the router 20 to disable packet traffic from this user at the expiry of the session time.
RBAS enables a robust and cost effective network access security solution compared to the current prevalent network security technologies. FIG. 1B shows a comparison of the RBAS network access security compared to the current security technologies of Firewall, Intrusion Detection Systems and the login using a password.
RBAS can be implemented in both the border routers (FIG. 1A) and the major internal to the business network routers (not shown). FIG. 1B comparison illustrates the RBAS has the potential to replace firewalls, password infrastructure and the IDS systems and their costs and still provide a comparable or better network access security. The comparison includes the features 50 such as function 51, security 52 and operational logistics 53 for the different access control technologies 60 of IDS 61, Firewall 62, Login 63 and the current invention RBAS 64.
The preferred embodiment uses cellular phones being used to call the adapted router 20. A home phone, a business phone, or any other phone may also be used provided the telephone number is pre-stored in the router 20. The current caller ID technology provided by the telephone companies uniquely identifies a cell phone owner, or a telephone caller and is used to primarily verify the caller to the router system in addition to a PIN as described later as part of verification function 242 with reference to FIG. 3A.
The RBAS security system of this invention serves the businesses by eliminating the risk of having data packets come in to the network whose source cannot be authenticated. Thus eliminate the risk of being a target for hackers.
As an additional security feature the passkey that is embedded in each packet may be encrypted or altered and the user can pre-select the length of the session in minutes. These features are described later with reference to FIG. 2A, 2B, 3A, 3B, and 4. These embodiments are described herein. The headings are provided for the convenience of the reader.
Authentication Router 280
With reference to FIG. 3A, an authentication router 280 includes router functions 22, authentication functions 21, input interface 332, capable of receiving incoming data packet traffic, output interface 334, capable of routing the data packets to other servers based on the destination IP and port addresses in the header of the data packet, a telephone interface 336 with a modem with the ability to receive a telephone call and dial out a telephone call, and a service interface 266.
The telephone interface 336 may be a T 1 line that can receive up to 24 analog voice calls, interfaces with a Dialogic, Brooktrout or some other similar brand line interface modem. The interface 336 may also be a Voice over IP(VoIP) interface via a VoIP gateway to receive telephone calls. These modems and VoIP Gateways are prior art technologies.
The service interface 266 is able to load data such as access control lists 252 for firewall function and storage memory 326 for authentication functions 21 into the authentication router 280. The service interface is also used to load programs such as authentication function 21 and router functions 22. The service interface may include another computer and is prior art.
The storage memory 326 of router 280 may be any high-speed conventional memory such as Flash or similar other memory that can retain data without power. Alternatively, it may also be disk-based storage memory. In general, the router 280 is a general-purpose digital computer that has been adapted to perform the functions of an authentication router as described here.
The router functions 22 include a prior art router function 208, that routs packets to interface 334 based on destination address, a prior art firewall function 250 that filters packets for routing based on access control lists 252. The access control lists provides rules regarding the routing of packets based on source and destination IP and port addresses. The router function 208 is also used to route packet traffic from the interface 334 to the interface 332.
The authentication functions 21 include an Interactive Voice Response (IVR) function 240 that can receive a call, get caller id, receive tone inputs, convert them into numbers, and output a voice response alphanumeric to the caller. The IVR technology is prior art and used by many businesses.
The verification function 242 includes means to verify the caller to the authentication router 280. There are three different means to identify the caller. One means is by caller id, another means is by entry of a personal identification number on the keypad of the telephone, and a third means is the IVR dialing out or calling back on a pre-stored caller id telephone number. These three different means can be combined in different ways to achieve what is called a two-factor identification or authentication of the caller. Some of them are described here:
Means A: Verify the caller (i) by comparing the incoming caller id with a pre-stored caller id in database 360 and (ii) by comparing an entry of a PIN to that pre-stored in database 360 for that caller ID. There may be more than one caller id pre-stored in the database 360, allowing the caller to call from a home phone, a cell phone, or a business phone.
Means B: Verify caller by a caller id, then disconnect and the caller hangs up. The IVR calls the caller back to the same caller id provided it is one of the caller ids pre-stored in the database 360.
Means C: Verify a caller, by caller id and entry of a PIN1 and then disconnect/hang up. The IVR then calls the caller back on a pre-stored caller id and receive entry of second PIN2, and then again verify by comparing with a pre-stored PIN2 in the database 360.
As described here PIN is a numerical personal identification number and is the preferred embodiment due to ease of entering a numerical number on the keypad of a telephone. It may also include other keys such as # and * etc.
The key function 244, generates a random alphanumeric key that is called Random Pass Key (RPK). The RPK may be numeric only or alphanumeric and may include any number of digits. The preferred embodiment includes a 4 to 6 digit alphanumeric. The RPK is voice delivered to the caller after the caller has been verified by any one of the means as described above as part of the verification function 242.
The packet authentication function 246, examines the header of each incoming data packet for the presence of optional data. If there is no optional data fields as explained later with reference to FIG. 4, then the packet is not from an authorized source and can be routed to an open content server 31, as illustrated in FIG. 1A. If the header of the packet contains the optional data fields as described in FIG. 4, then it may be assumed to be from an authorized user and the contents of the data fields in the form of signature composed of the caller id and the RPK needs to be verified with reference to database 360.
In the signature verification, the caller id is first decrypted, by whatever approach it was encrypted by the client security function 18. After the caller id is decrypted, then it is checked against the database 360 to find the corresponding RPK alphanumeric 28. Using the RPK in the database 360 as a key, the RPK in the packet is decrypted and the decrypted RPK is compared with RPK alphanumeric 28. If they match, then the data packet is routed to an authorized application server 30, as illustrated in FIG. 1A.
Other features as part of the authentication functions 21 may also be optionally provided. One such feature is where the session length of a session of user to the network is limited in time. For example, a variable in database 360, called session length 366 may be used where it specifies the length of the session, let us say in minutes. When the caller calls the telephone number of the router, in addition to entering a PIN of fixed length, the user may also enter extra digits that may serve to define the session length variable 366 in the database 360. Pursuant to this feature, the session is automatically terminated after the session length. A default value may be provided for session length 366, such as 30 minutes. After the expiry of time of session length, the session would be automatically terminated, the router 280 refuse to route any more packets with this RPK and the RPK is deleted from the database 360. The authorized then has to initiate a fresh authentication procedure requiring calling and getting a new RPK.
Another feature as part of the authentication functions 21 may also be to define in the database 360, what are the authentication privileges (not shown) of the user. For example, the user may be authorized to connect to some of the application servers and not others based on his role or function within an organization.
Adapted Router 20
The router based authentication system may also use an existing router that has been adapted with an authentication function. Such an adaptation of a router is described here. Referring to FIG. 3B, the adapted router 20 includes (i) a storage device 326, (ii) an operating system 302 stored in the storage device 326, (iii) authentication functions 21 and a conventional router functions 22 stored in the storage device 326, (iv) and a processor 330 connected to the storage device 326,
The processor 330 can include one or more conventional CPU's. The processor 330 can be capable of high volume processing and database searches.
The authentication system storage device 326 can, for example, include one or more magnetic disk drives, magnetic tape drives, optical storage units, CD-ROM drives and/or flash memory. The storage device 326 also contains an authentication database 360.
The adapted router 20 includes a telephone network interface 336 that allows the adapted router 20 to communicate with the user 14 via the cell phone 12. The adapted router 20 also includes a system network interfaces 332 that allows the authentication system 10 to communicate with the Internet 24 or another computer network. The adapted router 20 also includes a system network interface 334 that allows the router 20 to communicate with business network 30 (as shown in FIG. 1A).
With respect to FIG. 2B, the processor 330 is operative with the authentication functions 21 to perform a telephone interface function 200, caller verification function 202, random alphanumeric code generation function 204 and a packet authentication function 206. These are described later in the specification with reference to FIG. 2B.
Databases 360
With reference to FIG. 3B, the database 360 in the router 20 stores caller id 12A, PIN 364, random pass key (RPK) alphanumeric 28, session length 366 and connection status 368 as an on/off status.
The alphanumeric 28 are present for only those sessions for which the connection status is on. The alphanumeric 28 are for onetime use only and are deleted from the database at the expiry of the session or when the authorized user terminates the session. Thus requiring a new alphanumeric 28 for every session.
The database 360 may also store classifications of the users (not shown) and the specific application server they are allowed to access, permitting the router 20 to route user to only those application servers for which he/she has been authorized.
Client Security Function 18
With reference to FIG. 2A, the security software function 18 in the client 10 includes a display authentication screen function 212. When the function 18 is invoked it displays the authentication screen 214. The authentication screen 214 displays: (i) a legend 215 that includes a telephone number of the adapted router of the business and instructions to call the telephone number using the cell phone and receive a code 28, (ii) space for the entry of the passkey 216 that is created by entering the telephone number 12A and the alphanumeric code 28, (iii), a connection button 218, which when activated executes the function 220 that encrypts the passkey and embeds in each outgoing packet header to the business network. Further details of the function 220 are described later with reference to FIG. 4.
Authentication Functions 21
With reference to FIG. 2B, the router adapted with an authentication function 21 includes: (i) a telephone interface adapted with an Interactive Voice Response (IVR) System 200 with the ability to receive a telephone call and user interactions and respond with voice, (ii) a function 202 to verify the caller by comparing with pre-stored caller id and a PIN, (iii) a function 204 to generate a random alphanumeric code for voice delivery it to the caller and save in the system, (iv) a packet authentication function 206 that rejects packets from the client 10 that do not have the encrypted passkey embedded in option field of the header of the packet.
The telephone interface function 200 performs the tasks of (i) receiving a telephone call and extracting the caller id from it and user input of tone keys for entry of PIN and voice responding with an alphanumeric code 28.
The caller id verification function 202 performs the tasks of (i) verifying the caller id in the database 360 and (ii) verifying PIN 364 in the database 360.
The random function 204 performs the task of creating an alphanumeric code 28 that is randomly created by the random function 204 using a prior art random number generator and saving in the database 360 anchored by the caller id 12A. The alphanumeric code may be very simple. For example, they may be a four to six digit alphanumeric making them easy to receive and use by the user 14.
The packet authentication function 206 performs the task of separating those packets, which have the option data and those, which do not have option data. Those packets that that do not have the option data in the packet are routed to the open content server 31 by the router functions 22. The packets that have the option data, verifying the presence of optional data in the packet, extracting the passkey from the packet, decrypting the passkey and verifying the caller id and alphanumeric code in the data base 360. Those packets that are verified by the packet authentication function 206 are routed to an authorized business application server 30. The database 360 may also have information that categorizes the authorized users and allows each authorized user to be routed to different application servers depending upon the type of authorization.
The prior art router functions 22 perform the task of routing the packet based on the destination address in the packet header.
A system admin function (not shown) enables the task of administration personnel to enter the authorized user's 14 caller id 12A and PIN 364 to be entered in the database 360 and to delete those caller ids for which the authorization is revoked such as an employee leaving. As well as to enter business rules of how long a session can last with the authorized users by limiting the entry of session length value 366 or deciding a default maximum value.
Internet Standard for IP packet
With reference to FIG. 4, an Internet Protocol RFC 791 Internet Standard for IP data packets has a header part 112, an option data part 116 and a data part 114. The header part 112 has data fields such as: Ver., IHL, Type of service, Total length, Identification, Flags Fragment Offset, Time to Live protocol, header checksum, source address and destination address. The optional data part 116 has fields such as Option type, Length, and Option data.
This standard allows the optional data fields in the header, which have been used here for a packet level authentication. The embodiment described here uses two 32 bit additional words that are used for a encrypted called id and a alphanumeric passkey as described earlier. The caller id is a ten-digit number, and the if the RPK is 6 digit alphanumeric, these sixteen digits can be accommodated in 64 bits of the two optional data words in the header. Each digit takes 4 bits, hence 64 bits would accommodate 16 digits.
It is believed, that the default or the minimum length of the header 112 is five words. The field, “Total Length”0 in the header 112, defines the total number of the words in the packet. The router and the applications can figure out where the data 114 begins and where the different fields of the header 112 are. For the optional data, the header has fields of option type, option data length and then the options data itself. Hence, it is believed, using optional data as in this invention does not in any way affect the operation of the routers and application servers. Where these optional data are used, additional programming may be used to make use of them as described in this invention.
Passkey Encryption/Alteration Function 100
With reference to FIG. 4, an encryption/alteration function 100 modifies the passkey into an encrypted passkey 104. The security software function 18 in the client 10 embeds the encrypted passkey 104 in the option data 116 of each packet.
The altering function 100 takes the passkey composed of the caller id 12A and the alphanumeric code 28 and by using an altering and or an encryption algorithm creates the encrypted passkey 104.
The altering algorithm parameters may be derived form the alphanumeric code 28 themselves. There can be many types of alternations such as simple offsets and reverse digits etc. The specific alternation technique and its parameters may be the alphanumeric code itself. Alternatively, a traditional encryption algorithm such as a one-way hash algorithm common in the information security applications may be used.
As an illustration of the altering function 100, the altering (encryption) function takes the alphanumeric and alters it to be another alphanumeric. For example, if the alphanumeric is B347, then it can be altered by adding the 2nd digit of 3 to all the digits such that B becomes E, 3 becomes 6, 4 becomes 7 and 7 becomes 0, so that the altered alphanumeric becomes E670. The code that is embedded in the packet is E670. Further more the altering function takes the caller id and alters it to another number by subtracting each digit from 9. For example if the caller id is 310 787 1460, it becomes 689 212 8539. Thus, if the passkey is 310 787 1460 B347, the encrypted or altered passkey may then become 689 212 8539 E670. This approach or encryption scheme makes sure that the encrypted signature in the packet header does not reveal either the caller id or the alphanumeric 28. Any number of such schemes may be used for creating an encrypted passkey.
Furthermore, the encryption or altering of the alphanumeric 28 may be such that it is changing from packet to packet or from a set of packets to a set of packets, provided similar decrypting logic is used in the packet authentication function in the router 20. An example of such variable encryption would be to create a number series using the digits of random passkey alphanumeric 28 as the parameters of the series.
The packet authentication function 206 first decrypts the caller id, and then using the database 360 finds the original alphanumeric code 28 in the database 360 using the caller id as a search reference. Then the function 206 decrypts the alphanumeric code 28 to verify that it matches what is present in the database 360. This verifies that the packet originated from the authorized user 14.
The RBAS Operation
With reference to FIG. 5, the RBAS performs the following steps
At step 500, a user desiring data interface connection to business invokes a security software function in the client, which displays an authentication screen, displaying a telephone number and an entry field for passkey.
At step 502, the User calls the telephone number and enters PIN. Optionally, also enters a numeral that specifies in minutes the length of the session desired. The border router receives call from user, verifies caller id in database, and generates a random alphanumeric code and delivers it user and saves these in the border router database anchored by caller id.
At step 504, user enters in the authentication screen, passkey made up of caller id and just received random alphanumeric code and clicks CONNECT button.
At step 506, the CONNECT button click initiates a session to border router, having pre-stored the link URL, the security software function encrypts and embeds passkey in each data packet header options data fields sent to the border router.
At step 508, the packet authentication function decrypts the passkey in the option data in the header and verifies the option data in the packet against the authentication database fields of caller id and alphanumeric code. Then enables the routing function to rout packet to business data network server 30. The packets that do not have the option field may be routed to the open content server 31.
In summary, the router based authentication system (RBAS) that has an adapted router 20, or an authentication router 280, and the Client Software Security Function 18 enables an authorized user 14 to be continuously authenticated to a business network 30 by embedding each packet with a encrypted passkey that enables the adapted router 20 or the authentication router 280 to protect the business network 30 by rejecting packets from unauthorized users. The RBAS, at the same time allows all other users to access the business open content server 31. The RBAS provides network access security by:

    
    
        A two-factor authentication of the source of each packet from authorized users.
        Enabling routing packets from other users to open content server in the same system simultaneously.
        Additional security means of limiting each session in minutes to what the user can pre-specify for each individual session.
        Cost reduction in network security by eliminating one or more of the firewall, cards and password infrastructure.
    
    


Thus the RBAS technology of this invention enables the RBAS to jointly perform the function of access control, user authentication, firewall, and intrusion detection at the perimeter of the network. By incorporating the RBAS in the routers internal to the network, the RBAS protects different segments of the network from unauthorized uses in other segments of he network.
While the particular method and apparatus as illustrated herein and disclosed in detail is fully capable of obtaining the objective and providing the advantages herein before stated, it is to be understood that it is merely illustrative of the presently preferred embodiments of the invention and that no limitations are intended to the details of construction or design herein shown other than as described in the appended claims.

## Claims

1. A router based authentication system that authenticates the source of the data packets, comprising:
a. a subsystem integrated with a router with means (i) to receive a telephone call from a user desiring access to a computer network, (ii) to verify the user by a caller id with a pre-stored database of caller ids in an authentication database, (iii) to generate a random alphanumeric and save it in the authentication database, and (iv) to voice deliver the alphanumeric to the user;
b. a security function in a user client, capable of receiving data entry of a passkey, the passkey comprising of the caller id and the alphanumeric, and the security function having a means to encrypt the passkey and embed in the header of each outgoing data packet from the client to the router;
c. a packet authentication function in the router that decrypts the passkey in the packet header and verifies that the alphanumeric matches with the database entry in the authentication database.

2. The authentication system as in claim 1, the security function comprising:
a screen display of, (i) a telephone number of the subsystem, (ii) data entry fields for entry of a passkey comprised of the caller id and the alphanumeric, and (iii) a connect button that activates a function that encrypts the passkey and embeds in each of the outgoing data packets from the user client to the computer network.

3. The authentication system as in claim 1, the security function comprising:
a means to encrypt the caller id with an encryption scheme that is different than the encryption scheme for the alphanumeric, enabling the packet authentication function to decrypt the caller id and find the alphanumeric in the authentication database.

4. The authentication system as in claim 3, the encryption scheme comprising:
using an altering function that inputs a plurality of digits of the alphanumeric and that alters the alphanumeric to another alphanumeric having the same format and attributes as the original alphanumeric.

5. The authentication system as in claim 1, the security function comprising:
means that embed the passkey within option data fields of a header of each Internet Protocol packet.

6. The authentication system as in claim 1, comprising:
the pre-stored caller ids in the authentication database are only cellular telephone numbers that are associated with authorized users of the computer network.

7. The authentication system as in claim 1, further comprising:
the means to verify the user includes a means to verify by caller id and a personal identification number in the authentication database.

8. The authentication system as in claim 1, further comprising:
the authentication database pre-storing user privileges and routing data packets in accordance with these privileges.

9. The authentication system as in claim 1, further comprising:
the subsystem having means that provides a programmable time limit for each alphanumeric in the authentication database and deletes the alphanumeric after the expiry of the time limit.

10. The authentication system as in claim 9, further comprising:
the subsystem having means that provides for the time limit to be selected by the user after caller id verification.

11. A computer network router comprising:
a. an authentication subsystem integrated with the router;
b. the authentication subsystem having means (i) to receive a telephone call from an authorized user, (ii) to verify the user by a caller id and a personal identification number, (iii) to voice respond with a randomly generated alphanumeric; and
c. a packet authentication function that verifies each data packet of communication from a user client for the presence of a passkey in the packet header decrypting the passkey, the decrypted passkey comprising the caller id and the alphanumeric, before processing and routing the data packet.

12. The router as in claim 11, the authentication subsystem further comprising:
an authentication database having fields for the caller id, the personal identification number, the alphanumeric, and a session time limit.

13. The router as in claim 12, further comprising:
the packet authentication function using the caller id verifies the alphanumeric in the authentication database.

14. The router as in claim 12, the authentication subsystem further comprising:
a means that enables the user to select a session time limit and means to delete the alphanumeric after the expiry of the session time limit.

15. The authentication system as in claim 12, further comprising:
the authentication database pre-storing user privileges and routing data packets in accordance with these privileges.

16. A method for a router based authentication system that authenticates the source of the data packets, comprising the steps of:
a. adapting a router with an authentication subsystem enabling the router receiving a telephone call from a user desiring access to a computer network, (ii) verifying the user by a caller id with a pre-stored database of caller ids in an authentication database, (iii) generating a random alphanumeric and saving it in the authentication database, and (iv) voice delivering the alphanumeric to the user;
b. receiving into a security function in a user client, data entry of a passkey, the passkey comprising of the caller id and the alphanumeric, and encrypting the passkey and embedding in the header of each outgoing data packet from the client to the router;
c. receiving data packets in the router, by a packet authentication function decrypting the passkey in the packet header and verifying that the alphanumeric match with database entry in the authentication database.

17. The method for router based authentication as in claim 16, further comprising the steps of:
a. invoking the client security function, displaying a screen with (i) a telephone number of the authentication subsystem, (ii) data entry fields for entry of a passkey comprised of the caller id and the alphanumeric, and (iii) a connect button that activates an altering function that encrypts the passkey and embeds in each of the outgoing data packets to the computer network;
b. entering the passkey, and activating the connect button.

18. The method for router based authentication as in claim 16, further comprising the steps of:
encrypting the passkey by inputting a plurality of digits of the alphanumeric to an altering function that alters the alphanumeric to another alphanumeric having the same format and attributes as the original alphanumeric.

19. The method for router based authentication as in claim 16, further comprising the steps of:
pre-storing user privileges in the authentication database and routing data packets in accordance with these privileges.

20. The method for router based authentication as in claim 16, further comprising the steps of:
selecting a session time limit for saving in the authentication database and deleting the alphanumeric after expiry of the session time limit.