SYSTEM, METHOD AND APPARATUS FOR AUTHENTICATING AND PROTECTING AN IP USER-END DEVICE

[0001] This patent application is a continuation-in-part patent application of U.S. patent application Ser. No. 12/028,781 filed on Feb. 8, 2008 and entitled “System, Method and Apparatus for Two Factor Authentication in VoIP Networks,” which is a non-provisional application of U.S. provisional patent application 60/888,765 filed on Feb. 8, 2007 and entitled “System, Method and Apparatus for Two Factor Authentication in VoIP Networks,” which is hereby incorporated by reference in its entirety.

[0002] The present invention relates generally to the field of telecommunications and, more particularly, to a system, method and apparatus for authenticating and protecting an Internet Protocol (IP) user-end device.

[0003] The combination of device and user authentication is called “Two Factor” authentication. Enterprises already have this mechanism in place for remote users connecting through computers. RSA SecurID® or similar mechanism is the de facto way of enabling “two factor” authentication. Two Factor authentication requires a user to key in a special pass phrase or key that is displayed on a Secure Token. This token is typically issued by the company and is carried by the employee all the time. The token is linked back to token authentication server in the company. When the employee wants to login to corporate services, he/she must supply the pass phrase or key, which changes periodically, to ensure that only the employee is requesting the service. The supplied input data is validated against the authentication server and if the match occurs, the employee is granted the service. RSA tokens and RSA server are widely deployed two factor authentication mechanisms in corporations.

[0004] This above-mentioned technique works well for computer terminals as there are client applications built to accept the two factor authentication. There is, however, no client or user interface to allow two factor authentication on Internet Protocol (IP) user-end devices. Unlike traditional phones that are always tied to a physical wire connected to PBX/Switch, the new breed of IP user-end devices are IP enabled and thus provide portability and mobility. For example, an employee can carry an IP user-end device from his work and plug it into Ethernet connector at home and can access an entity's network. This flexibility enables businesses or other entities to deploy these phones to tele-workers, road warriors, consultants, partners and other. On the other hand, it makes these entities vulnerable to theft, attacks, and abuse.

[0005] Computers connected to an IP network are open to many forms of attacks and threats, such as DoS/DDoS floods, fuzzing/malformed messages, reconnaissance attacks, spoofing attacks, MIM attacks, stealth call attacks, rogue media, anomalous behavior, and/or SPAM. Similarly, IP user-end devices are vulnerable to these same types of attacks and threats. As a result, there is a need for a system, method and apparatus for authenticating and protecting an IP user-end device.

[0006] The present invention when applied in conjunction with deeper security threat mitigation creates a highly secure telephony that can be provided anywhere outside the corporation. As a result, entities can realize business continuity and the benefits of pervasive communications. The two factor authentication must be carried out in a secure channel between the IP user-end device and the entity as the IP user-end device is typically connected to the Internet. In addition, the voice conversation must be encrypted for privacy. With new IP user-end device terminals and soft phones this is typically achieved through encrypted transport. The present invention leverages the same control messages and voice prompts used for setting up calls to the phone to provide two factor authentication. Thus, an out-of-band channel is necessary to complete two factor authentication. Moreover, the present invention protects the IP user-end device by screening incoming IP traffic and detecting attacks or threat involving the IP user-end device.

[0007] The present invention provides a method for authenticating and protecting an Internet Protocol (IP) user-end device by providing a client-based security software resident on the IP user-end device, authenticating the IP user-end device using the client-based security software and a network security node communicably coupled to the IP user-end device, authenticating a user of the IP user-end device whenever a trigger condition occurs using an in-band channel between the client-based security software and the network security node, and protecting the IP user-end device by: (a) screening incoming IP traffic to the IP user-end device using the client-based security software, and (b) detecting an attack or a threat involving the IP user-end device using the network security node. Note that this process can be implemented using a computer readable medium executed by the processors wherein the steps are executed by one or more code segments.

[0008] In addition, the present invention provides an apparatus for authenticating and protecting an IP user-end device that includes a communications interface, a memory, and a processor communicably coupled to the communications interface and the memory. The processor is configured to run a client-based security software resident on the IP user-end device. The client-based security software and a network security node communicably coupled to the IP user-end device: (a) authenticate the IP user-end device, and (b) authenticate a user of the IP user-end device whenever a trigger condition occurs using an in-band channel between the client-based security software and the network security node. The client-based security software protects the IP user-end device by screening incoming IP traffic to the IP user-end device. The network security node protects the IP user-end device by detecting an attack or a threat involving the IP user-end device.

[0009] The present invention also provides a system that includes one or more IP user-end devices, a network security node, and an IP network communicably coupling the one or more IP user-end devices to the network security node. Each IP end-user device includes a first communications interface, a first memory, and a first processor communicably coupled to the first communications interface and the first memory wherein the first processor is configured to run a client-based security software resident on the IP user-end device. The network security node includes a second communications interface, a second memory, and a second processor communicably coupled to the second communications interface and the second memory. The client-based security software and the network security node: (a) authenticate the IP user-end device, and (b) authenticate a user of the IP user-end device whenever a trigger condition occurs using an in-band channel between the client-based security software and the network security node. The client-based security software protects the IP user-end device by screening incoming IP traffic to the IP user-end device. The network security node protects the IP user-end device by detecting an attack or a threat involving the IP user-end device.

[0010] The present invention is described in detail below with reference to the accompanying drawings.

[0023] While the making and using of various embodiments of the present invention are discussed in detail below, it should be appreciated that the present invention provides many applicable inventive concepts that can be embodied in a wide variety of specific contexts. The specific embodiments discussed herein are merely illustrative of specific ways to make and use the invention and do not delimit the scope of the invention. The discussion herein relates primarily to Voice over Internet Protocol (IP) technology (VoIP), but it will be understood that the concepts of the present invention are applicable to any Voice over IP application, or Unified Communication (UC) application such as Video calls, Presence, Instant Messaging, or any communication application that runs over IP.

[0024] The present invention when applied in conjunction with deeper security threat mitigation creates a highly secure telephony that can be provided anywhere outside the corporation. As a result, entities can realize business continuity and the benefits of pervasive communications. The two factor authentication must be carried out in a secure channel between the IP user-end device and the entity as the IP user-end device is typically connected to the Internet. In addition, the voice conversation must be encrypted for privacy. With new IP user-end device terminals and soft phones this is typically achieved through encrypted transport. The present invention leverages the same control messages and voice prompts used for setting up calls to the phone to provide two factor authentication. Thus, an out-of-band channel is necessary to complete two factor authentication. Moreover, the present invention protects the IP user-end device by screening incoming IP traffic and detecting attacks or threat involving the IP user-end device.

[0025] Now referring to FIGS. 1A and 1B, two network configurations in accordance with the present invention are illustrated. FIG. 1A represents the present invention in Internet Protocol Communication Security (IPCS) demilitarized zone (DMZ) mode 100. FIG. 1B represents the present invention in an IPCS in a tunnel mode 150. In either case, the present invention provides infrastructure and endpoint protection. The two factor authentication for remote users must be provided in the DMZ of enterprise. The security server 102 in the DMZ must be able to handle near-end and far-end firewall issues. The secrurity server 102 must: (a) provide authentication connectivity to the authentication server (not shown) (e.g., SecurID® server or other suitable authentication server); (b) terminate and inspect signaling and media; and (c) be a secure box. The security server (IPCS) 102 is communicably coupled to various IP user-end devices 104 and call servers 106 via an Intranet 108 or other IP-based communications network (internal, private or secure). Note that the security server 102 in FIG. 1B is communicably coupled to another security server 152, which is communicably coupled to the call servers 106, to establish a secure tunnel through the Intranet 108.

[0026] The security server 102 can be communicably coupled to various external IP user-end devices 110 via the Internet 112 or other IP-based communications network (external, less-secure or public). In addition, the security server 102 is protected by an internal firewall 114 and an external firewall 116. Similarly, external IP user-end devices 110 are protected by a firewall 118. The security server 102 includes a communications interface, a memory, and a processor communicably coupled to the communications interface and the memory. The processor is configured to perform the authentication processes described below. The IP user-end device 110 can be a dual mode phone, a wireless phone, a soft phone, a web phone, a personal data assistant or other IP-based telecommunications device that does not run a client-based authentication application during the authentication process described herein. Note that IP Private Branch Exchange (PBX) systems are not built to address the above requirements.

[0027] Referring now to FIG. 2, a flow chart illustrating a two factor authentication process 200 in accordance with one embodiment of the present invention is shown. The authentication process 200 begins in block 202. If the IP user-end device 110 is authorized, as determined in decision block 204, and a trigger condition occurs, as determined in decision block 206, the security server 102 initiates a call to the IP user-end device 110 in block 208. A “white list” or other type of commonly used device authentication can be used to authenticate the IP user-end device. The trigger condition can be a time-based condition, an event-based condition or a combination thereof. The time-based condition can be a requirement to authenticate the IP user-end device daily, weekly, bi-weekly, monthly, quarterly, yearly or some other specified time. The event-based condition can be receiving a registration request from the IP user-end device, a switch-over to standby, a challenge from an authentication manager, a request for a specified service, or a request for access to a specified device. If, however, the IP user-end device 110 is not authorized, as determined in decision block 204, or the trigger condition is not met, as determined in decision block 206, the process ends in block 216.

[0028] After the call is initiated, the secure server 102 sends a request for the user's passcode to the IP user-end device 110 in block 210. The request for the passcode may include one or more display prompts, one or more voice prompts or a combination thereof. The passcode can be a personal identification code, a token code, a physical key, an electronic key, a biometric identifier, a magnetic signature, an electronic signature, one or more numbers, one or more symbols, one or more alphabet characters, one or more keystrokes, or a combination thereof. If the passcode is valid, as determined in decision block 212, the call is terminated in block 214 and the process ends in block 216. If, however, the passcode is not valid, the security server 102 sends a message to the IP user-end device 110 that will disable the IP user-end device 110 in block 218. Thereafter, the call is terminated in block 214 and the process ends in block 216. After the authentication process 200 is successfully completed, the IP user-end device 110 will be allowed to access resources or connect to devices protected by the security server 102. Note that this process can be implemented using a computer readable medium executed by the secure server 102 wherein the steps are executed by one or more code segments.

[0029] Now referring to FIG. 3, a flow chart illustrating a two factor authentication process 300 in accordance with another embodiment of the present invention is shown. The authentication process 300 begins in block 302. If the IP user-end device 110 is not authorized, as determined in decision block 304, a security incidence is generated in block 306 and the process ends in block 308. A “white list” or other type of commonly used device authentication can be used to authenticate the IP user-end device. If, however, the IP user-end device 110 is authorized, but a trigger condition does not occur (or is not satisfied), as determined in decision block 310, the process ends in block 308. The trigger condition can be a time-based condition, an event-based condition or a combination thereof. The time-based condition can be a requirement to authenticate the IP user-end device daily, weekly, bi-weekly, monthly, quarterly, yearly or some other specified time. The event-based condition can be receiving a registration request from the IP user-end device, a switch-over to standby, a challenge from an authentication manager, a request for a specified service, or a request for access to a specified device If, however, the trigger condition is satisfied, the security server 102 initiates a call to the IP user-end device 110 in block 312.

[0030] After the call is initiated, the secure server 102 sends a request for the user's passcode to the IP user-end device 110 in block 314. The request for the passcode may include one or more display prompts, one or more voice prompts or a combination thereof. The passcode can be a personal identification code, a token code, a physical key, an electronic key, a biometric identifier, a magnetic signature, an electronic signature, one or more numbers, one or more symbols, one or more alphabet characters, one or more keystrokes, or a combination thereof. If the call is not answered, as determined in decision block 316, and request retries are allowed, as determined in decision block 318, the process waits in block 320 and a new request is sent in block 314. If, however, retries are not allowed, the call is terminated in block 324 and the process ends in block 308. If, however, the call is answered, as determined in decision block 316, and the passcode is valid, as determined in decision block 322, the call is terminated in block 324 and the process ends in block 308. If, however, the passcode is not valid, and the maximum number of attempts to enter the passcode have not been exceeded, as determined in decision block 326, the user may try to enter the correct passcode. If, however, the maximum number of attempts has been made, the security server 102 sends a message to the IP user-end device 110 that will disable the IP user-end device 110 in block 328, the user is notified that the IP user-end device 110 has been disabled in block 330. The notification may include one or more display messages, audio messages, voice mail messages, electronic mail messages, text messages, or a combination thereof. Thereafter, a security incidence is generated in block 332, the call is terminated in block 324 and the process ends in block 308. After the authentication process 300 is successfully completed, the IP user-end device 110 will be allowed to access resources or connect to devices protected by the security server 102.

[0031] The security server 102 can block any messages from the IP user-end device 110 until the IP user-end device 110 and the user are authenticated. In addition, the security server 102 can initiate another call to the IP user-end device 110 and send another request for a passcode to the IP user-end device 110 after the IP user-end device 110 has been disabled for a specified period of time. The security server 102 can delay registration of the IP user-end device 110 with a call manager until the IP user-end device 110 and the user are authenticated. Moreover, the IP user-end device 110 can be enabled after the IP user-end device 110 has been disabled by using a “clearing” process executed by the user, a technician, a security person, a supervisor or a combination thereof. Note that this process can be implemented using a computer readable medium executed by the secure server 102 wherein the steps are executed by one or more code segments.

[0032] Referring now to FIG. 4, a RSA SecurID® authentication network 400 in accordance with one embodiment of the present invention is illustrated. The system 400 includes a security server (IPCS) 102 communicably coupled to one or more protected resources, devices or phones 402 and an authentication server 404. The security server 102 is also communicably coupled to an IP user-end device 110. The user of the IP user-end device 110 has a RSA SecurID® 406 that provides a PIN+Token Number or RSA SecurID® with pinpad 408 that provides a Pass Code. The communication protocol used between the IP user-end device 110 and the security server 102 is SIP/Skinny over TLS and SRTP. The communication protocol used between the security server 102 and the protected phones 402 is SIP/Skinny over TCP. The communication protocol used between the security server 102 and the authentication server 404 (RSA Authentication Manager+RSA Radius Server) is PAP over RADIUS, EAP-GTC over RADIUS and/or EAP-POTP over RADIUS. The security server 102 can request authentication of the received passcode from the authentication server 404.

[0033] The present invention can implement any of the following pre-authentication rules:

• • [0034] 1. Perform following operations for devices in the white list. Any requests from devices not in white list, they are blocked and a security incidence is generated.
  • [0035] 2. Do not allow any messages from phone to Intranet before authentication completes.
  • [0036] 3. Serve default configuration file using Trivial File Transfer Protocol (TFTP). If the local copy is not available, use a default file that is preconfigured.
  • [0037] 4. When phone sends Registration Request, accept it and send the success response without any interaction with CCM network. (Register phone with some default values).
  • [0038] 5. Ring the phone and request for SecurID® key using Display Prompt. If the user doesn't pickup the phone, then authentication should be done whenever user goes off-hook. The ring should stop after timeout 3 mins, but display and light can remain on, and when phone goes offhook the IPCS will request for passcode.
  • [0039] 6. In the event Display prompt is not feasible with the protocol, IPCS shall request for the key using voice prompt.
  • [0040] 7. Allow configurable number of consecutive failed-attempts to authenticate before locking the phone down.
  • [0041] 8. If the phone is locked down, play the Lock down prompt. It should be both a display prompt and some tone. Audio is also possible.
  • [0042] 9. Generate an incidence when the phone is locked down.
  • [0043] 10. Use configurable timer to challenge the user to re-authenticate after locking down.
  • [0044] 11. When the timer expires prompt for re-authentication only if the user goes off-hook. Request for secureid key using Display Prompt in the following cases:
    • [0045] i. When the timer expires, ring the phone and display “Please go offhook to complete registration” don't request SecurID® passcode yet.
    • [0046] ii. Whenever the user goes off-hook. Now IPCS can request SecurID® passcode.
  • [0047] 12. If the SecurID® server rejects/challenges authentication request, IPCS shall use the prompt from “Reply-Message” attribute in the message. If prompt is too big to display a compressed format maybe used.
  • [0048] 13. Lockdown clearing process: IPCS allows the ability to clear the lock down using “out-of-band” mechanism.
  • [0049] 14. IPCS EMS will provide ability for help desk to login and clear the lock down.
  • [0050] 15. In addition, IPCS will provide “Self-service” capability by providing Web Service using SOAP/XML to offer this capability and integrate with Enterprise Employee portal.
  • [0051] 16. IPCS will display the portal URI on the phone when the user is locked down and procedure to clear it.

[0052] In addition, the following post-authentication rules can be used:

• • [0053] 17. Once Authentication completes the phone will have same capabilities as it would have without IPCS.
  • [0054] 18. The Re-Authentication of the phone will either be Time Based or Event based or both.
  • [0055] 19. If it is Time based, Admin must specify either daily, weekly, bi-weekly or monthly.
  • [0056] 20. If it is Event based Admin can select one or more events such as Phone sending Re-Registration Request, Call Manager switch-over to standby.

[0057] A RADIUS PAP RSA SecurID® Example flow is as follows:

[0058] Display Prompts on phone

[0059] To continue Phone Registration you must enter your PIN and Passcode.

[0060] 1. sending Access-Request . . .

[0061] 1. received Access-Challenge

[0062] You must select a new PIN. Do you want the system to generate your new PIN? (y/n) [n]

[0063] y

[0064] 2. sending Access-Request . . .

[0065] 2. received Access-Challenge

[0066] Enter a new PIN between 4 and 8 digits:

[0067] 1234

[0068] 3. sending Access-Request . . .

[0069] 3. received Access-Challenge

[0070] Re-enter new PIN to confirm:

[0071] 1234

[0072] 4. sending Access-Request . . .

[0073] 4. received Access-Challenge

[0074] PIN accepted. Wait for the tokencode to change, then enter a new PASSCODE:

[0075] 1234169199

[0076] 5. sending Access-Request . . .

[0077] 5. received Access-Accept

[0078] OK Registration Complete

[0079] BackGround RADIUS Messages

1. Code: Access-Request
Identifier: 182
Authentic: 1234567890123456
Attributes:
User-Name = “mikem”
Service-Type = Framed-User
NAS-IP-Address = 203.63.154.1
NAS-Port = 1234
Called-Station-Id = “123456789”
Calling-Station-Id = “987654321”
NAS-Port-Type = Async
User-Password=
	“<200><185>1<153><153>o4<199><142><10><9><160><216>}x<153>”
1. Code: Access-Challenge
Identifier: 182
Authentic: <143>R9<132>X<242><21><184>E<135>?#<9><189><11><228>
Attributes:
State = “SECURID=884099926”
Reply-Message = “You must select a new PIN. Do you want the
	system to generate your new PIN? (y/n) [n] ”
2. Code: Access-Request
Identifier: 202
Authentic: 1234567890123456
Attributes:
User-Name = “mikem”
Service-Type = Framed-User
NAS-IP-Address = 203.63.154.1
NAS-Port = 1234
Called-Station-Id = “123456789”
Calling-Station-Id = “987654321”
NAS-Port-Type = Async
User-Password=
	“<151><139>_<173><175>\<4><246><188>8<9><160><216>}x<153>”
State = “SECURID=884099926”
2. Code: Access-Challenge
Identifier: 202
Authentic:
	<156><131><25>j<212><154><153><193><201><152>WY?<208><164>d
Attributes:
State = “SECURID=884099926”
Reply-Message = “Enter a new PIN between 4 and 8 digits:”
3. Code: Access-Request
Identifier: 207
Authentic: 1234567890123456
Attributes:
User-Name = “mikem”
Service-Type = Framed-User
NAS-IP-Address = 203.63.154.1
NAS-Port = 1234
Called-Station-Id = “123456789”
Calling-Station-Id = “987654321”
NAS-Port-Type = Async
User-Password=
	“<200><185>1<153><175>\<4><246><188>8<9><160><216>}x<153>”
State = “SECURID=884099926”
3. Code: Access-Challenge
Identifier: 207
Authentic: <151><214>G<132>6S<134>ed<197>k<199>nK6<186>
Attributes:
State = “SECURID=884099926”
Reply-Message = “Re-enter new PIN to confirm: ”
4. Code: Access-Request
Identifier: 208
Authentic: 1234567890123456
Attributes:
User-Name = “mikem”
Service-Type = Framed-User
NAS-IP-Address = 203.63.154.1
NAS-Port = 1234
Called-Station-Id = “123456789”
Calling-Station-Id = “987654321”
NAS-Port-Type = Async
User-Password=
	“<200><185>1<153><175>\<4><246><188>8<9><160><216>}x<153>”
State = “SECURID=884099926”
4. Code: Access-Challenge
Identifier: 208
Authentic: <192><189><30>D<150><211><140>&$Gdz<252><135>S<250>
Attributes:
State = “SECURID=884099926”
Reply-Message = “PIN accepted. Wait for the tokencode to change,
	then enter a new PASSCODE: ”
5. Code: Access-Request
Identifier: 220
Authentic: 1234567890123456
Attributes:
User-Name = “mikem”
Service-Type = Framed-User
NAS-IP-Address = 203.63.154.1
NAS-Port = 1234
Called-Station-Id = “123456789”
Calling-Station-Id = “987654321”
NAS-Port-Type = Async
User-Password=
	“<200><185>1<153><158>o0<193><140><8><9><160><216>}x<153>”
State = “SECURID=884099926”
5. Code: Access-Accept
Identifier: 220
Authentic: <246>>′jM<173>s<17><214><217><220><219>[<243>D<220>
Attributes:

[0080] Now referring to FIG. 5, a call flow diagram 500 in accordance with another embodiment of the present invention is illustrated. The solution is described using the SKINNY protocol, but it can also apply to other protocols that are used to setup VoIP (Voice over IP) calls.

[0081] Referring now to FIG. 6, a screen shot of a virtual IP configuration table in accordance with one embodiment of the present invention is illustrated. For example, the following rules can be used:

• • [0082] 21. IPCS will use VIP table to configure TFTP proxy rules.
  • [0083] 22. The internal firewall should have a rule to allow TFTP port 69 to CCM from EIPCS (not necessary in tunnel mode).
  • [0084] 23. IPCS will request file from random ports (50001, 50002, . . . ) to CCM port 69.
  • [0085] 24. The CCM will send files from random port (51001, 51002, . . . ) to corresponding IPCS ports (50001, 50002, . . . ).
  • [0086] 25. The external firewall should have a rule to allow TFTP port (69) to VIP address on IPCS.
  • [0087] 26. The phone will request file from random ports (52001, 52002, . . . ) to IPCS port 69.
  • [0088] 27. The IPCS will send file from “fixed port” 69 to corresponding phone ports (52001, 52002, . . . ).
    • [0089] a. This way we can get around the far end firewall.
    • [0090] b. IPCS needs to keep context on IP address, port basis.
  • [0091] 28. The phones will be configured with alternate TFTP server in CCM such that they can transparently move in and out of the Enterprise without changing any configuration.

[0092] TFTP XML Rewriting

XML TAG	Original IP	Rewrite IP
<callManagerGroup>	10.10.100.10	192.168.10.30
	<members>
	<members>
	<callManager>
	<processNodeName>
<callManagerGroup>	10.10.100.11	192.168.10.31
	<members>
	<members>
	<callManager>
	<processNodeName>

	...
	<callManagerGroup>
	<members>
	<member priority=”0”>
	<callManager>
	<ports>
	<analogAccessPort>2002</analogAccessPort>
	<digitalAccessPort>2001</digitalAccessPort>
	<ethernetPhonePort>2000</ethernetPhonePort>
	<mgcpPorts>
	<listen>2427</listen>
	<keepAlive>2428</keepAlive>
	</mgcpPorts>
	</ports>
	<processNodeName>10.10.100.10</processNodeName>
	</callManager>
	</member>
	<member priority=”1”>
	<callManager>
	<ports>
	<analogAccessPort>2002</analogAccessPort>
	<digitalAccessPort>2001</digitalAccessPort>
	<ethernetPhonePort>2000</ethernetPhonePort>
	<mgcpPorts>
	<listen>2427</listen>
	<keepAlive>2428</keepAlive>
	</mgcpPorts>
	</ports>
	<processNodeName>10.10.100.11</processNodeName>
	</callManager>
	</member>
	</members>
	</callManagerGroup>
	...

• • [0093] 29. IPCS will parse and modify the XML for the SEP<MAC>.cnf.xml in accordance with the TFTP rewriting configuration
  • [0094] 30. The xml tags, current value and rewrite value will be configured.

[0095] Phone Behavior Analysis

[0096] Whenever Skinny Reset w DEVICE RESET message

• • [0097] Is received from call manager
  • [0098] Phone sends Un register message
  • [0099] CCM sends Un register ack message
  • [0100] CCM sends TCP reset
  • [0101] Phone requests config file
  • [0102] Phone receives config file
  • [0103] Phone Registers

[0104] Whenever Skinny Reset w DEVICE_RESTART message

• • [0105] Is received from call manager
  • [0106] Phone sends Un register message
  • [0107] CCM sends Un register ack message
  • [0108] CCM sends TCP reset
  • [0109] Phone Registers
  • [0110] Phone requests config file
  • [0111] Phone receives config file

[0112] When **#** on phone

• • [0113] Phone sends Un register message
  • [0114] CCM sends Un register ack message
  • [0115] CCM sends TCP reset
  • [0116] Phone requests config file
  • [0117] Phone receives config file
  • [0118] Phone Registers

[0119] When power cycle phone

• • [0120] Phone requests config file
  • [0121] Phone receives config file
  • [0122] Phone Registers
  • [0123] Phone requests config file again
  • [0124] Phone receives config file again

[0125] Ethernet connect disconnect

• • [0126] Phone Registers
  • [0127] Phone requests config file
  • [0128] Phone receives config file.

[0129] Now referring to FIG. 7, a state machine diagram 700 in accordance with one embodiment of the present invention is illustrated.

Events−>States	X requests config file	CCM serves file same	CCM serves file different
X File Unknown	Action: Serve local file	Not Possible	Not Possible
Entry: −	Request file from CCM
	Next State: X File Requested
X File Requested	Action: Serve local file	Action: None	Action: Send Skinny Reset
Entry: −	Next State: Same	Next State: X File Unknown	(DEVICE_RESTART)
			Next State: X File Unknown

[0130] An IPCS TFTP Message Sequence is as follows:

• • [0131] 31. Whenever phone requests file, IPCS will serve locally available file and IPCS will also request the same file from CCM.
  • [0132] 32. Always on receiving the file from CCM. IPCS will check if the contents of file have changed from the current version on IPCS and then update the local file.
  • [0133] 33. If the file obtained has been modified IPCS will send skinny reset with “DEVICE_RESTART” to phone to force it to update file.
  • [0134] a. To identify the phone IPCS will rely on Device name in the file name SEP<MAC>.cnf.xml.
  • [0135] b. To identify the phone in case of other files IPCS will rely on connection from same public IP, this will not handle the case of NAT.
  • [0136] 34. If the file obtained is same as the local copy on IPCS, IPCS will do nothing.

[0137] Referring now to FIG. 8, a network 800 configuration in accordance with another embodiment of the present invention is shown. The client-based security software 802 (e.g., Sipera UC-Sec Client application or plug-in) is installed on the IP user-end device 804 (e.g., a dual mode phone, a wireless phone 804a, a soft phone, a web phone, a personal data assistant, a computer 804b, or other IP-based telecommunications device). The network security node 806 (e.g., Sipera UC-Sec network node) is deployed in the core network 808 where it communicates with the client-based security software 802 on the IP user-end device 804 via an access network 810 and/or an open IP network 812. The network security node 806 is deployed in the DMZ of the associated Call Server 816 and Media Gateway 818 and will service any remote IP user-end device 804 that has the client-based security software 802 and is connecting to that DMZ. The Call Server 816 and Media Gateway 818 communicate with other devices or services within the core network 808 (e.g., Directory Services 818, Authentication, Authorization and Accounting (AAA) 820, Applications 822, etc.). All VoIP calls for the IP user-end device 804 operating remotely to the Enterprise will go through the network security node 806 deployed in the DMZ. A separate network security node (not shown) can also be deployed (upon customer need and request) inside the Enterprise to serve internal VoIP devices that have the client-based security software 802. The network security node 806 also communicates with the Back-office Network Operation Center 824 (e.g., Sipera Central EMS) in the operation network 826 via an out-of-band network 828. The operation network 826 typically also includes DHCP 830, SNMP 832, Syslog 834 and Chrg 836. The client-based security software 802 can apply to mobile phone devices with a Smart card, a Flex-SIM card, and user PC devices that have VoIP Soft-client. The client-based security software 802 does not apply to VoIP Hard phones 838.

[0138] Now referring to FIG. 9, a block diagram of a system 900 for authenticating and protecting an IP user-end device 804 in accordance with another embodiment of the present invention is shown. The system 900 includes one or more IP user-end devices 804 communicably coupled to a network security node 806 via an IP network 812. The network security node 806 is communicably coupled to a call server 814 and a media gateway 816 via a core network 808, and a security management center (EMS) 824 via an out-of-bound network 828. Each IP end-user device 804 includes a first communications interface 902, a first memory 904, and a first processor 906 communicably coupled to the first communications interface 902 and the first memory 904 wherein the first processor 906 is configured to run a client-based security software 802 resident on the IP user-end device 804. The IP user-end device 804 can be a dual mode phone, a wireless phone, a soft phone, a web phone, a personal data assistant, a computer, or other IP-based telecommunications device.

[0139] The IP user-end device 804 runs an IP-based application comprising a Voice over IP (VoIP) application, an Instant Messaging (IM) application, a Short Message Service (SMS) application, a video application, a presence application, or a Unified Communication (UC) application.

[0140] The network security node 806 includes a second communications interface 908, a second memory 910, and a second processor 912 communicably coupled to the second communications interface 908 and the second memory 910 wherein the second processor 912 is configured to run a network node security software 914 resident on the network security node 806. Other devices may be communicably coupled to the network security node 806, such as an authentication server or a call manager. The client-based security software 802 and the network security node 806: (a) authenticate the IP user-end device 804, and (b) authenticate a user of the IP user-end device 804 whenever a trigger condition occurs using an in-band channel between the client-based security software 802 and the network security node 806. The client-based security software 802 protects the IP user-end device 804 by screening incoming IP traffic to the IP user-end device 804. The network security node 806 protects the IP user-end device 804 by detecting an attack or a threat involving the IP user-end device 804. Various methods for authenticating and protecting the IP user-end device will be described in more detail with respect to FIGS. 10 and 11.

[0141] Referring now to FIG. 10, a flow chart 1000 of a method for authenticating and protecting an IP user-end device 804 in accordance with another embodiment of the present invention is shown. A client-based security software 802 resident on the IP user-end device 804 is provided in block 1002. The IP user-end device 804 is authenticated using the client-based security software 802 and a network security node 806 communicably coupled to the IP user-end device 804 in block 1004. The IP user-end device 804 can be authenticated using a smart card, a SIM card, a Flexi-SIM card, a security certificate stored on the smart card or the SIM card or on the UP user-end device, one or more control messages, one or more voice prompts, a “white-list”, or a combination thereof. If a trigger condition occurs, as determined in decision block 1006, a user of the IP user-end device 804 is authenticated using an in-band channel between the client-based security software 802 and the network security node 806 in block 1008. The trigger condition can be a time-based condition, an event-based condition or a combination thereof.

[0142] The time-based condition can be a requirement to authenticate the user of the IP user-end device daily, weekly, bi-weekly, monthly, quarterly, yearly or some other specified time. The event-based condition can be receiving a registration request from the IP user-end device, a switch-over to standby, a challenge from an authentication manager, a request for a specified service, a request for access to a specified device, or a failure of a fingerprint match. The fingerprint match may include a change in a format, a value or an order of information in a header, wherein the header information include via, max forwards, contact, user agent, allow, proxy require, supported, route, Cseq, session expires, allow events, content length, SDP bandwidth, SDP silence suppression, SDP connection, SDP originator or SDP payload.

[0143] After the user is authenticated in block 1008, or if the trigger condition has not occurred, as determined in decision block 1006, the IP user-end device 804 is protected by screening incoming IP traffic to the IP user-end device 804 using the client-based security software 802 in block 1010, and detecting an attack or a threat involving the IP user-end device 804 using the network security node 806 in block 1012. The attack or the threat may include DoS/DDoS floods, fuzzing/malformed messages, reconnaissance attacks, spoofing attacks, MIM attacks, stealth call attacks, rogue media, anomalous behavior, and/or SPAM. The process repeats the steps of detecting the trigger condition and protecting the IP user-end device 804 as needed to authenticate and protect the IP user-end device 804. The step of authenticating the IP user-end device 804 can be repeated. Note that this process can be implemented using a computer readable medium executed by the processors wherein the steps are executed by one or more code segments.

[0144] Now referring to FIG. 11, a flow chart 1100 of a method for authenticating and protecting an IP user-end device 804 in accordance with another embodiment of the present invention is shown. A client-based security software 802 resident on the IP user-end device 804 is provided in block 1002. If the IP user-end device 804 is not authorized, as determined in decision block 304, a security incidence is generated in block 306 and the process screens incoming traffic in block 1010. A “white list” or other type of commonly used device authentication can be used to authenticate the IP user-end device. If, however, the IP user-end device 804 is authorized, but a trigger condition does not occur (or is not satisfied), as determined in decision block 310, the process screens incoming traffic in block 1010. The trigger condition can be a time-based condition, an event-based condition or a combination thereof. The time-based condition can be a requirement to authenticate the IP user-end device daily, weekly, bi-weekly, monthly, quarterly, yearly or some other specified time. The event-based condition can be receiving a registration request from the IP user-end device, a switch-over to standby, a challenge from an authentication manager, a request for a specified service, or a request for access to a specified device. If, however, the trigger condition is satisfied, the network security node 806 initiates a call to the IP user-end device 804 in block 312.

[0145] After the call is initiated, the secure server 102 sends a request for the user's passcode to the IP user-end device 804 in block 314. The request for the passcode may include one or more display prompts, one or more voice prompts or a combination thereof. The passcode can be a personal identification code, a token code, a physical key, an electronic key, a biometric identifier, a magnetic signature, an electronic signature, one or more numbers, one or more symbols, one or more alphabet characters, one or more keystrokes, or a combination thereof. If the call is not answered, as determined in decision block 316, and request retries are allowed, as determined in decision block 318, the process waits in block 320 and a new request is sent in block 314. If, however, retries are not allowed, the call is terminated in block 324 and the process screens incoming traffic in block 1010. If, however, the call is answered, as determined in decision block 316, and the passcode is valid, as determined in decision block 322, the call is terminated in block 324 and the process screens incoming traffic in block 1010. If, however, the passcode is not valid, and the maximum number of attempts to enter the passcode have not been exceeded, as determined in decision block 326, the user may try to enter the correct passcode. If, however, the maximum number of attempts has been made, the network security node 806 sends a message to the IP user-end device 804 that will disable the IP user-end device 804 or reject the authentication request in block 328, the user is notified that the IP user-end device 804 has been disabled or the authentication request was rejected in block 330. The notification may include one or more display messages, audio messages, voice mail messages, electronic mail messages, text messages, or a combination thereof. Thereafter, a security incidence is generated in block 332, the call is terminated in block 324 and the process screens incoming traffic in block 1010. After the IP user-end device 804 is authenticated, the IP user-end device 804 will be allowed to access resources or connect to devices protected by the network security node 806.

[0146] The network security node 806 can block any messages from the IP user-end device 804 until the IP user-end device 804 and the user are authenticated. In addition, the network security node 806 can initiate another call to the IP user-end device 804 and send another request for a passcode to the IP user-end device 804 after the IP user-end device 804 has been disabled for a specified period of time or after the specified period of time since the authentication request from the IP user-device 804 was rejected. The network security node 806 can delay registration of the IP user-end device 804 with a call manager until the IP user-end device 804 and the user are authenticated. Moreover, the IP user-end device 804 can be enabled after the IP user-end device 804 has been disabled by using a “clearing” process executed by the user, a technician, a security person, a supervisor or a combination thereof.

[0147] After the user is authenticated in block 1008, or if the trigger condition has not occurred, as determined in decision block 1006, the IP user-end device 804 is protected by screening incoming IP traffic to the IP user-end device 804 using the client-based security software 802 in block 1010, and detecting an attack or a threat involving the IP user-end device 804 using the network security node 806 in block 1012. The process repeats the steps of detecting the trigger condition and protecting the IP user-end device 804 as needed to authenticate and protect the IP user-end device 804.

[0148] Additional steps may include receiving a request for a configuration file from the IP user-end device 804, retrieving the configuration file, sending the configuration file to the IP user-end device 804, requesting the configuration file from a call manager, receiving the requested configuration file, and saving the requested configuration file and sending a reset message to the IP user-end device 804 whenever the requested configuration file is different than the configuration file. In addition, the following steps may be performed: receiving another request for the configuration file in response to the reset message, and sending the requested configuration file to the IP user-end device 804. Note that the client-based security software 802 can split one or more resources of the IP-user-end device 804 into one or more logical access-controlled areas. Note that this process can be implemented using a computer readable medium executed by the processors wherein the steps are executed by one or more code segments.

[0149] The present invention can provide some or all of the following features:

• • [0150] The client-based security software 802 will be supported on mobile phone devices (MSFT WM 6.1 OS), Nokia E and N series dual mode phones with Symbian OS, iPhone, Blackberry (SIP Client) and other phone devices that support VoIP or Unified Communication also apply.
  • [0151] The client-based security software 802 acts as a control point for screening incoming traffic.
  • [0152] The client-based security software 802 will enable Mutual Authentication with TLS/SRTP (for mobile phones that support TLS/SRTP).
  • [0153] The network security node 806 will be deployed in the network and will provide full security functionality as well as TLS/SRTP termination, DPI, admission control and other services.
  • [0154] The system will support Certificate download from SIM and/or Smart Card.
  • [0155] UC-Sec IOT with Singtel, Star Hub, and M1 SIP Trunks.
  • [0156] Logs, Forensics, incidences.
  • [0157] Two Factor Authentication.
  • [0158] Anti-Spam, black list entry via client-based security software 802.
  • [0159] TLS, smart card based certificate authorization.
  • [0160] SRTP via the client-based security software 802.
  • [0161] Support secure messaging, secure SMS and SMS logging via client-based security software 802.
  • [0162] FlexiSIM card based authentication support.
  • [0163] Phone resource virtualization.
  • [0164] Zeroization of cert, key, contacts, messages/logs via client-based security software 802.
  • [0165] Address book with IP-contact (SIP contacts) list.
  • [0166] Separation of GSM calls, IP call contacts in phone list.
  • [0167] The client-based security software 802 will be supported on Soft-phone with SIP stack.
  • [0168] OTP integration with FlexiSIM card will be adopted.
  • [0169] System applies to any device that support VoIP or UC applications such as Video call, IM or Presence services and others.
  • [0170] System compliant with the following call server(s) in the network: Asterisk, OpenSer, Alcatel (model TBD), Singtel, Star Hub, M1 SIP trunks, and other call servers that support VoIP or Unified Communication.

[0171] Other characteristics of the present invention may include:

• • [0172] System will support Mutual authentication with TLS on many dual-mode phones in models where the phone supports TLS and mTLS.
  • [0173] System will support Smartcard based certificate download, authentication with TLS. Reading Smartcard credentials from laptop and using these credentials for TLS session.
  • [0174] TLS certificates can be transferred from the Smartcard onto the phone for example via Bluetooth interface.
  • [0175] Client-based security software 802 will initiate a TLS session for VoIP calls with the network.
  • [0176] Client-based security software 802 will support and initiate an SRTP session for VoIP calls with the network.
  • [0177] Signaling encryption (TLS) will be applied for all users. TLS Encryption will be applied between the network security node 806 and the mobile device outside the Enterprise. The network security node 806 will decrypt the signaling traffic between the network security node 806 and the Call Server 814.
  • [0178] Media encryption (SRTP) will be applied to a Specific user set. This user list will be configured at the Central EMS 824. SRTP Encryption will be applied between the network security node 806 and the client-based security software 802 outside the Enterprise. The network security node 806 will decrypt the part of the call between the network security node 806 and any end device that does not support encryption e.g. PSTN side.
  • [0179] Client-based security software 802 will apply policy enforcement on the mobile device to connect only to the network security node 806.
  • [0180] Client-based security software 802 will provide Anti-Spam, black list entry capability to the user.
  • [0181] The system will provide security Threat protection using the network security node 806 against attacks covering: DoS/DDoS floods, Fuzzing/malformed messages, Reconnaissance attacks, Spoofing, MIM attacks, Stealth call attack, Rogue media, Anomalous behavior and SPAM
  • [0182] The network security node 806 will prevent attacks from reaching the mobile end device.
  • [0183] The network security node 806 will be deployed in the network and will provide full security functionality as well as TLS/SRTP termination, DPI, admission control and other services
  • [0184] The network security node 806 will provide attack information details and threats history.
  • [0185] The network security node 806 will support Audit capability for all mobile phones calls and activities.
  • [0186] Audit logs are to be uploaded to the network security node 806 whenever connection is established. All Audit files collected will be stored on the network security node 806 then forwarded to the Central EMS 824 where there will be a much larger storage and management space.
  • [0187] In cases were network security node 806 local storage memory is full, and connection to the Central EMS 824 is not available, the present invention will provide a configuration option on the network security node 806 to do one of the following 1) new audit log files will override oldest log files on the device, 2) No new audit logging will be done until memory space becomes available on the network security node 806.
  • [0188] Smartcards will be chosen based on the following considerations: small form factor for easy insertion and removal from the phone, should not be cumbersome when operating the phone, and order of choice should be MicroSD followed by FlexiSIM if possible.
  • [0189] The system will support using 2048-bits certificates and 256-bits symmetric key for TLS.
  • [0190] The system will support secure messaging, secure SMS and SMS logging via mobile client.
  • [0191] FlexiSIM card based authentication support.
  • [0192] The system will support Mobile Phone resource virtualization.
  • [0193] The system will support Zeroization of cert, key, contacts, messages/logs via client-based security software 802.
  • [0194] Client-based security software 802 will support Address book with IP-contact (SIP contacts) list.
  • [0195] Client-based security software 802 will support Separation of GSM calls, IP call contacts in phone list.

[0196] Additional aspects regarding the operation of the present invention may include the following:

• • [0197] Support Certificate download from Smart Card/SM card and storing them on the phone.
  • [0198] Support RSA 2-Factor Authentication. The client-based security software 802 will interact with network security node 806 to execute the 2-Factor Authentication.
  • [0199] Network owner shall have the option to configure 2-Factor Authentication to be triggered not necessarily on every call, but on a periodic basis for e.g. only once a day per user.
  • [0200] Network security node 806 will initiate two factor authentications on a specific user when fingerprint match fails (e.g. upon device change).
  • [0201] Provide means to split phone resources into logical access-controlled device/area.
  • [0202] Only when TLS is enabled, will the phone allow access to official contacts, personal contacts will not be enabled at this time.
  • [0203] Provide capability for Smart phones to initiate TLS sessions even if the phone type is not TLS capable.
  • [0204] Support and Integration with Flex-SIM card on the user-end device. i.e. to provide the OTP integration.
  • [0205] Notifications and installations of software upgrades of the client-based security software 802 are done remotely and over the network.

[0206] The User Fingerprint composition is defined during configuration and can be composed of a combination or all of the following information elements:

• • [0207] Via:
  • [0208] Max Forwards
  • [0209] Contact:
  • [0210] User Agent
  • [0211] Allow
  • [0212] Proxy Require
  • [0213] Supported
  • [0214] Route
  • [0215] Cseq
  • [0216] Session Expires
  • [0217] Allow Events
  • [0218] Content Length
  • [0219] SDP Bandwidth
  • [0220] SDP Silence Suppression
  • [0221] SDP Connection
  • [0222] SDP Originator
  • [0223] SDP Payload
    The Fingerprint mismatch Criteria will be based on the change in format, value or order of the header information. Upon fingerprint mismatch, the system can be configured to trigger a user verification in every mismatch scenario, or on a customizable fashion e.g. only if User Agent info changes. The user verification trigger and Fingerprint information are fully customizable in the present invention with default settings.

[0224] It will be understood by those of skill in the art that information and signals may be represented using any of a variety of different technologies and techniques (e.g., data, instructions, commands, information, signals, bits, symbols, and chips may be represented by voltages, currents, electromagnetic waves, magnetic fields or particles, optical fields or particles, or any combination thereof). Likewise, the various illustrative logical blocks, modules, circuits, and algorithm steps described herein may be implemented as electronic hardware, computer software, or combinations of both, depending on the application and functionality. Moreover, the various logical blocks, modules, and circuits described herein may be implemented or performed with a general purpose processor (e.g., microprocessor, conventional processor, controller, microcontroller, state machine or combination of computing devices), a digital signal processor (“DSP”), an application specific integrated circuit (“ASIC”), a field programmable gate array (“FPGA”) or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described herein. Similarly, steps of a method or process described herein may be embodied directly in hardware, in a software module executed by a processor, or in a combination of the two. A software module may reside in RAM memory, flash memory, ROM memory, EPROM memory, EEPROM memory, registers, hard disk, a removable disk, a CD-ROM, or any other form of storage medium known in the art. Although preferred embodiments of the present invention have been described in detail, it will be understood by those skilled in the art that various modifications can be made therein without departing from the spirit and scope of the invention as set forth in the appended claims.