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

• US 20100107230A1
• Filed: 10/21/2009
• Published: 04/29/2010
• Est. Priority Date: 02/08/2007
• Status: Active Grant

• Current Assignee: Arlington Technologies, LLC (Dominion Harbor Enterprises, LLC)
• Original Assignee: Sipera Systems Inc (Avaya Incorporated)
• Inventors: Thodime-Venkata, Guru-Prasad, Tyagi, Satyam
• Granted Patent: US 8,503,657 B2
• Time in Patent Office: Days
• US Class Current: 726/6
• CPC Class Codes: H04L 63/08 for authentication of entities cryptographic mechanisms or cryptographic arrangements for entity authentication H04L9/32
• CPC Class Codes: H04L 63/083 using passwords cryptographic mechanisms or cryptographic arrangements for entity authentication using a predetermined code H04L9/3226
• CPC Class Codes: H04L 63/101 Access control lists [ACL]
• CPC Class Codes: H04L 65/1069 Session establishment or de-establishment
• CPC Class Codes: H04L 65/1076 Screening of IP real time communications, e.g. spam over Internet telephony [SPIT]
• CPC Class Codes: H04M 7/0078 Security; Fraud detection; Fraud prevention

Abstract

A system, method and apparatus authenticates and protects 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.

Claims

1. A method for authenticating and protecting an Internet Protocol (IP) user-end device comprising the steps of:

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.

2. The method as recited in claim 1, wherein:

the step of authenticating the IP user-end device uses 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;

the IP user-end device comprises 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; and

the IP user-end device 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.

3. The method as recited in claim 1, wherein:

the trigger condition comprises a time-based condition, an event-based condition or a combination thereof;

the time-based condition comprises a requirement to authenticate the user of the IP user-end device daily, weekly, bi-weekly, monthly, quarterly, yearly or some other specified time; and

the event-based condition comprises 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.

4. The method as recited in claim 3, wherein:

the fingerprint match comprises a change in a format, a value or an order of information in a header; and

the header information comprises 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.

5. The method as recited in claim 1, wherein the attack or the threat comprises DoS/DDoS floods, fuzzing/malformed messages, reconnaissance attacks, spoofing attacks, MIM attacks, stealth call attacks, rogue media, anomalous behavior, and/or SPAM.

6. The method as recited in claim 1, further comprising the step of generating a security incidence whenever the authentication of the IP user-end device fails.

7. The method as recited in claim 1, further comprising the step of blocking any messages from the IP user-end device until the IP user-end device and the user are authenticated.

8. The method as recited in claim 1, wherein the step of authenticating a user of the IP user-end device comprises the steps of:

initiating a call from the network security node to the IP user-end device;

sending a request for a passcode to the IP user-end device;

sending a message to disable the IP user-end device or rejecting an authentication request from the IP user-end device whenever the passcode is invalid; and

terminating the call.

9. The method as recited in claim 8, wherein:

the request for the passcode comprises one or more display prompts, one or more voice prompts or a combination thereof; and

the passcode comprises 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.

10. The method as recited in claim 8, further comprising the step of resending the request for the passcode after a specified period of time whenever the user does not answer the call.

11. The method as recited in claim 8, wherein the step of sending the message to disable the IP user-end device or rejecting the authentication request from the IP user-end device is performed after a specified number of consecutive of authentication attempts have failed.

12. The method as recited in claim 8, further comprising the step of notifying the user that the IP user-end device has been disabled or the authentication request from the IP user-device has been rejected using one or more display messages, audio messages, voice mail messages, electronic mail messages, text messages, or a combination thereof.

13. The method as recited in claim 8, further comprising the steps of initiating another call to the IP user-end device and sending another request for a passcode to the IP user-end device after the IP user-end device 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 was rejected.

14. The method as recited in claim 8, further comprising the step of enabling the IP user-end device after the IP user-end device has been disabled using a “

clearing”

process executed by the user, a technician, a security person, a supervisor or a combination thereof

15. The method as recited in claim 8, further comprising the step of requesting authentication of the received passcode from an authentication server.

16. The method as recited in claim 8, further comprising the step of delaying registration of the IP user-end device with a call manager until the IP user-end device and the user are authenticated.

17. The method as recited in claim 1, further comprising the steps of:

receiving a request for a configuration file from the IP user-end device;

retrieving the configuration file;

sending the configuration file to the IP user-end device;

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 whenever the requested configuration file is different than the configuration file.

18. The method as recited in claim 17, further comprising the steps of:

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.

19. The method as recited in claim 1, wherein the client-based security software splits one or more resources of the IP-user-end device into one or more logical access-controlled areas.

20. An apparatus for authenticating and protecting an Internet Protocol (IP) user-end device comprising:

a communications interface;

a memory; and

a processor communicably coupled to the communications interface and the memory wherein the processor is configured to run a client-based security software resident on the IP user-end device;

wherein 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;

wherein client-based security software protects the IP user-end device by screening incoming IP traffic to the IP user-end device; and

wherein the network security node protects the IP user-end device by detecting an attack or a threat involving the IP user-end device.

21. A system comprising:

one or more Internet Protocol (IP) user-end devices, each IP end-user device comprising 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;

a network security node comprising a second communications interface, a second memory, and a second processor communicably coupled to the second communications interface and the second memory;

an IP network communicably coupling the one or more IP user-end devices to the network security node;

wherein 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;

wherein client-based security software protects the IP user-end device by screening incoming IP traffic to the IP user-end device; and

wherein the network security node protects the IP user-end device by detecting an attack or a threat involving the IP user-end device.

22. The system as recited in claim 21, further comprising an authentication server communicably coupled to the network security node.

23. The system as recited in claim 21, further comprising a call manager communicably coupled to the network security node.