EP1238490A1 - Methods and protocols for intrusion-tolerant management of collaborative network groups - Google Patents
Methods and protocols for intrusion-tolerant management of collaborative network groupsInfo
- Publication number
- EP1238490A1 EP1238490A1 EP01932747A EP01932747A EP1238490A1 EP 1238490 A1 EP1238490 A1 EP 1238490A1 EP 01932747 A EP01932747 A EP 01932747A EP 01932747 A EP01932747 A EP 01932747A EP 1238490 A1 EP1238490 A1 EP 1238490A1
- Authority
- EP
- European Patent Office
- Prior art keywords
- nonce value
- message
- node
- recipient
- sender
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Withdrawn
Links
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L9/00—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols
- H04L9/32—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols including means for verifying the identity or authority of a user of the system or for message authentication, e.g. authorization, entity authentication, data integrity or data verification, non-repudiation, key authentication or verification of credentials
- H04L9/3271—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols including means for verifying the identity or authority of a user of the system or for message authentication, e.g. authorization, entity authentication, data integrity or data verification, non-repudiation, key authentication or verification of credentials using challenge-response
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/34—Signalling channels for network management communication
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L63/00—Network architectures or network communication protocols for network security
- H04L63/02—Network architectures or network communication protocols for network security for separating internal from external traffic, e.g. firewalls
- H04L63/0272—Virtual private networks
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L63/00—Network architectures or network communication protocols for network security
- H04L63/06—Network architectures or network communication protocols for network security for supporting key management in a packet data network
- H04L63/067—Network architectures or network communication protocols for network security for supporting key management in a packet data network using one-time keys
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L63/00—Network architectures or network communication protocols for network security
- H04L63/08—Network architectures or network communication protocols for network security for authentication of entities
- H04L63/0869—Network architectures or network communication protocols for network security for authentication of entities for achieving mutual authentication
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L9/00—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols
- H04L9/08—Key distribution or management, e.g. generation, sharing or updating, of cryptographic keys or passwords
- H04L9/0816—Key establishment, i.e. cryptographic processes or cryptographic protocols whereby a shared secret becomes available to two or more parties, for subsequent use
- H04L9/0819—Key transport or distribution, i.e. key establishment techniques where one party creates or otherwise obtains a secret value, and securely transfers it to the other(s)
- H04L9/083—Key transport or distribution, i.e. key establishment techniques where one party creates or otherwise obtains a secret value, and securely transfers it to the other(s) involving central third party, e.g. key distribution center [KDC] or trusted third party [TTP]
- H04L9/0833—Key transport or distribution, i.e. key establishment techniques where one party creates or otherwise obtains a secret value, and securely transfers it to the other(s) involving central third party, e.g. key distribution center [KDC] or trusted third party [TTP] involving conference or group key
Definitions
- the field of the invention is secure groupware management.
- a virtual private network is an overlay network that provides secure communication channels through an underlying (usually public) network infrastructure (such as the Internet), as a relatively inexpensive alternative to private secure lines. Communications among the members of a VPN are typically automatically encrypted using secure keys known to the members of the group, as a means of achieving the desired privacy for the members.
- a knowledgeable hacker may attempt to interrupt service or otherwise sabotage a NPN by electronic intrusion such as a replay attack (illicit interception, copying, and retransmission of encrypted traffic). To preserve system integrity and availability, it is important that such attacks be easily recognized as illicit communications.
- the present invention is directed toward systems and methods for managing collaborative network groups.
- Collaborating members of the network group may be classified as member nodes.
- Distribution of critical group data to member nodes is generally handled by master nodes in a manner resistant to misbehavior by current, past, or other member nodes.
- Distribution of critical group data is also preferred to be resistant to outsider attacks such as replay attacks.
- Distribution of critical group data by master nodes to member nodes advantageously offers confidentiality (the critical data cannot be read by eavesdropper), integrity (the receiving member node has evidence that the critical data has not been tampered with in transit), authenticity (the receiving member node has evidence that the critical data was sent by a master node), and freshness (the critical data is not a replay of a previous message).
- each member node is provided an encryption key (session key) that is known by the member node and its master node only, and is Valid only for the duration of time that the member node remains legitimately within the group. Cormnunication of critical data between the master node and the member node may be encrypted with the session key, in both directions.
- the transmitting node may generate a new nonce value and may embed it in the encrypted communication, for use by a recipient in the next communication.
- the new nonce value typically becomes the expected nonce, for purposes of the next communication.
- the communication may be readily identified and rejected by the recipient as a replay attack or otherwise illicit communication.
- the member node may first generate and store a nonce value that is communicated to the master node.
- the stored nonce value may thus be established as the expected nonce value for purposes of the next communication, i.e., the master node's response.
- the member and master may use a long-term key for encryption during this initiation process.
- the master node's response can contain a session encryption key for use in subsequent exchanges during the session, and further can contain the stored nonce value in order to verify its authenticity to the member node.
- the master node's response can further contain a new nonce value, for use in the next message from the member.
- Figure 1 is a representation of an intrusion-resistant dialogue between a member node and a master node, in accordance with one embodiment of the present invention.
- Figure 2 depicts a structure of a secure, encrypted message in accordance with one embodiment of the present invention.
- a network “node” may be any type of device or collection of devices capable of processing instructions mcluding (but not limited to) a cellular phone, a PDA, an intelligent household appliance, a general-purpose computer, a network server, a multiprocessor cluster of computers, or a computer network such as a LAN.
- Network nodes are considered “interconnected” if there is a potential path for communication between them, regardless of whether that path is direct.
- a collaboration group typically includes a collection of interconnected network nodes.
- Some collaboration groups such as a virtual private network ( "NPN"), may utilize encrypted communication channels so that group communications cannot be read and understood by nodes that are not members of the group.
- NPN virtual private network
- An example of a NPN is the EnclavesTM system created by the assignee of the present invention and described in L. Gong, Enclaves: Enabling Secure Collaboration Over the Internet, " published in Proceedings of the 6 th USENIX Security Symposium, pp. 149- 159, San Jose, CA (July 1996).
- Enhanced VPN architectures and methods are described in a patent application entitled “Methods And Apparatus For Scalable, Distributed Management Of Virtual Private Networks", serial no. to be determined, filed by the assignee of the present invention on event date with the present filing.
- the teachings of the present invention have utility for VPNs, but may also be applied more generally to network collaboration groups regardless of whether all group communications are encrypted.
- a preferred embodiment of the present invention provides a method for managing a virtual private overlay (or other network collaboration group) in a manner resistant to attacks from outside the group or from misbehaving member nodes.
- the collaboration group typically comprises a plurality of member nodes and one or more master nodes.
- the master nodes are typically responsible for managing membership control tasks, such as arise when a new member node joins the group or when an existing member leaves the group.
- the master nodes may also be responsible for communicating critical data in that regard, such as cryptographic keys, to the member nodes.
- a protocol for communicating such critical data will now be described that offers resilience against replay attacks, eavesdropping, and message corruption.
- the master node, and each member node that wishes to use this node as a master, may be provided with a secret session key that is essentially unique to this pair of member and master nodes, and to their communication session.
- Each communication of critical data between these two nodes is preferably encrypted with the session key and includes two nonce values.
- the first nonce value is usually already known to the recipient of the message (the expected nonce), and the second nonce value is typically a fresh nonce generated by the sender (the sender's nonce).
- the recipient of each such message may verify that the encrypted message includes the expected nonce value.
- the recipient may then acknowledge the message by replying with another message, also encrypted with the session key that includes the sender's nonce just received and a new nonce freshly generated by the recipient. This new nonce generally becomes the expected nonce for the recipient when the next communication is sent.
- nonce denotes a number (or other datum) chosen from a sufficient enough distribution to ensure a relatively high probability of uniqueness.
- a "fresh" nonce is a newly generated nonce.
- the purpose of a nonce, as used herein, is generally to ensure a low probability that a would-be intruder monitoring corrrniunications within the VPN or other collaboration group will be able to launch a replay attack or other illicit infiltration attack.
- a “replay attack” is an attempt to infiltrate an authentication system by a would-be intruder or some other node that records and replays previously sent valid communications.
- steplOO a new member node joins the group by means of abrief authentication and initialization protocol with its assigned master node.
- This authentication protocol is described below in detail in connection with Table 1.
- the authentication protocol may establish (among other things) an initial expected nonce value, known to the new member and the master node.
- the member (or master) node desiring to send a secure message generates a new fresh nonce value, to serve as the expected nonce value for the subsequent round of communication (i.e., in response to the message currently being sent).
- the new nonce and the expected nonce are included in the message to be sent, and at 130, the message is encrypted using the session key and is sent (140) to the receiving node.
- the message is decrypted by the receiving node.
- the expected nonce value is extracted from the decrypted message, and the recipient node can verify that the extracted value matches the expected value.
- the new nonce value is extracted by the recipient, so that it can be used by the recipient as the expected nonce for purposes of the next communication.
- termination sequence 190 is performed, as described below in more detail in connection with Table 4. If instead there is to be another round of communication, then the recipient of the current message prepares to send a response by iterating through process 110- 170 once again, but this time using the previous round's new nonce as the expected nonce. This process preferably continues repeatedly, for the duration of the session between the member and the master.
- FIG. 2 illustrates the general structure of a secure message in accordance with an embodiment of the subject matter.
- the contents of secure message 200 are encrypted, preferably using a shared session key as described.
- Message contents may include:
- header information 210 which may include for example an identification of the node sending the message and the recipient node for whom the message is intended, as illustrated below in connection with Tables 1-4;
- main content 220 i.e., the primary subject matter communicated via the message
- expected nonce 230 i.e., the nonce value that the recipient expects to see and will examine (160) in order to verify authenticity and freshness of the message
- new nonce 240 i.e., the value that the sender generates and establishes as the next expected nonce value to be used in a response message from the recipient.
- the master mode is represented by the letter M
- the member (client) node by the letter ; C.
- This example will illustrate how client C joins the VPN managed by master node M, 5 receives and acknowledges group-management messages from M, and eventually leaves the VPN.
- the content of each group management message is not relevant to the example, rather, we are intending to illustrate that the protocol ensures that C accepts only valid group-management messages and in the order that they were sent by L.
- the protocol as outlined here is a simplified version of what will 0 typically be used in a fully featured VPN system, but is serves to illustrate some relevant aspects for providing the desired intrusion tolerance properties.
- each client C has a secret long-term key (e.g. a password) Pc, initially known at the outset of the example by C and by M.
- Pc a secret long-term key
- C - M Authlnit eq, C, M, ⁇ C, M, Nl ⁇ Pc 2.
- M may generate a fresh session key Kc and a fresh nonce N2 and sends the key distribution message (message 2).
- Message 2 includes both nonces Nl and N2 as well as session key Kc, and again is encrypted by Pc.
- C receives and decrypts this message, checks that Nl matches the nonce 5 sent in message 1, and extracts the key Kc. C then sends to M the key acknowledgement in message 3, which includes fresh nonce N3 (as well as N2) and is encrypted using session key Kc. If this authentication protocol succeeds, then C becomes a member of the VPN and is in possession of session key Kc .
- M -> C AdrninMsg, M, C, ⁇ M, C, N3, N4 ⁇ Kc
- message 1 contains nonce N3 as well as fresh nonce N4 generated by master node M, and is encrypted using Kc.
- N3 assures C that this message is fresh (not a replayed attack), and the encryption with Kc ensures that the message originated from M.
- the acknowledgement (message 2) contains nonce N4 and a further nonce N5 freshly generated by C. Receipt of message 2 is evidence to M that C effectively received message 1, and M will in ttirn use nonce N5 in the next group management message that M sends to C.
- both M and C may memorize a nonce
- N[2i+1] that was generated by C This nonce is usually either the N3 communicated to M at the end of the authentication protocol (per Table 1 above), or the nonce that M received from C in the most recent acknowledgement message.
- a sample group management exchange is then as follows: "
- Message 1 contains N[2i+1] to prove to C that the message is not a replay, and communicates to C the fresh nonce N[2i+2] that M generates.
- Message 2 contains N[2i+2] to prove to M that the acknowledgement is not a replay but rather is an authentic response; and also communicates to M a new fresh nonce N[2i+3] to be used in the next exchange.
- C can leave the VPN session at any time by sending M the message shown below in sample Table 4.
- the key Kc is used both to guarantee that the message originated from C and to prove freshness (i.e. that the message is not a replay attack).
- the message cannot be a replay since there can be at most one authentic closing message per session and hence per session key. No acknowledgement is needed from M. Instead, on receipt of message 1, M simply closes its session with C; key Kc is discarded; and no further group management messages are sent to C.
Abstract
Description
Claims
Applications Claiming Priority (5)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US24748800P | 2000-11-08 | 2000-11-08 | |
US247488P | 2000-11-08 | ||
US24718400P | 2000-11-09 | 2000-11-09 | |
US247184P | 2000-11-09 | ||
PCT/US2001/013848 WO2002039658A1 (en) | 2000-11-08 | 2001-04-26 | Methods and protocols for intrusion-tolerant management of collaborative network groups |
Publications (2)
Publication Number | Publication Date |
---|---|
EP1238490A1 true EP1238490A1 (en) | 2002-09-11 |
EP1238490A4 EP1238490A4 (en) | 2007-07-18 |
Family
ID=26938511
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
EP01932747A Withdrawn EP1238490A4 (en) | 2000-11-08 | 2001-04-26 | Methods and protocols for intrusion-tolerant management of collaborative network groups |
Country Status (2)
Country | Link |
---|---|
EP (1) | EP1238490A4 (en) |
WO (1) | WO2002039658A1 (en) |
Families Citing this family (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
FR2859555B1 (en) * | 2003-09-04 | 2005-12-23 | Fidalis | COMMUNICATION SYSTEM FOR MONITORING TRACEABILITY |
Citations (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5369705A (en) * | 1992-06-03 | 1994-11-29 | International Business Machines Corporation | Multi-party secure session/conference |
EP0915590A2 (en) * | 1997-11-10 | 1999-05-12 | Unwired Planet, Inc. | Method and system for secure lightweight transactions in wireless data networks |
Family Cites Families (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5729608A (en) * | 1993-07-27 | 1998-03-17 | International Business Machines Corp. | Method and system for providing secure key distribution in a communication system |
-
2001
- 2001-04-26 WO PCT/US2001/013848 patent/WO2002039658A1/en active Application Filing
- 2001-04-26 EP EP01932747A patent/EP1238490A4/en not_active Withdrawn
Patent Citations (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5369705A (en) * | 1992-06-03 | 1994-11-29 | International Business Machines Corporation | Multi-party secure session/conference |
EP0915590A2 (en) * | 1997-11-10 | 1999-05-12 | Unwired Planet, Inc. | Method and system for secure lightweight transactions in wireless data networks |
Non-Patent Citations (3)
Title |
---|
MENEZES ET AL: "IDENTIFICATION AND ENTITY AUTHENTICATION" HANDBOOK OF APPLIED CRYPTOGRAPHY, CRC PRESS SERIES ON DISCRETE MATHEMATICES AND ITS APPLICATIONS, BOCA RATON, FL, CRC PRESS, US, 1997, pages 385-424, XP002906549 ISBN: 0-8493-8523-7 * |
NEEDHAM R M ET AL: "Using encryption for authentication in large networks of computers" COMMUNICATIONS OF THE ASSOCIATION FOR COMPUTING MACHINERY, ACM, NEW YORK, NY, US, vol. 21, no. 12, December 1978 (1978-12), pages 993-999, XP002163714 ISSN: 0001-0782 * |
See also references of WO0239658A1 * |
Also Published As
Publication number | Publication date |
---|---|
EP1238490A4 (en) | 2007-07-18 |
WO2002039658A1 (en) | 2002-05-16 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US6038322A (en) | Group key distribution | |
US5638448A (en) | Network with secure communications sessions | |
JP4002380B2 (en) | Multicast system, authentication server terminal, multicast receiver terminal management method, and recording medium | |
US20030084304A1 (en) | System and method for validating a network session | |
CN108243166A (en) | A kind of identity identifying method and system based on USBKey | |
JP2008529326A (en) | Method and system for electronic message management and filtering using cryptographic techniques | |
US20180115520A1 (en) | Dark virtual private networks and secure services | |
CN111935213A (en) | Distributed trusted authentication virtual networking system and method | |
US20040049676A1 (en) | Methods and protocols for intrusion-tolerant management of collaborative network groups | |
Clark et al. | Attacking authentication protocols | |
Huguenin-Dumittan et al. | A message franking channel | |
Mannan et al. | A protocol for secure public instant messaging | |
Chauhan et al. | Computer Security and Encryption: An Introduction | |
EP1238490A1 (en) | Methods and protocols for intrusion-tolerant management of collaborative network groups | |
Mueller | Let’s attest! Multi-modal certificate exchange for the web of trust | |
Arun et al. | Cbca: consignment based communal authentication and encryption scheme for internet of things using digital signature algorithm | |
JP7433620B1 (en) | Communication method, communication device and computer program | |
JP2005167967A (en) | Anonymous communication method | |
Dolnák | Secure mutual exchange of messages between network nodes inspired by security technologies for electronic mail exchange | |
Nikam et al. | Securing MQTT protocol in IoT by payload Encryption Technique and Digital Signature | |
Zhao et al. | An add-on end-to-end secure email solution in mobile communications | |
Aura et al. | Communications security on the Internet | |
Chen et al. | Tailoring authentication protocols to match underlying mechanisms | |
Melchor et al. | pMIX: Untraceability for Small Hiding Groups. | |
Boyd et al. | A Tutorial Introduction to Authentication and Key Establishment |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
PUAI | Public reference made under article 153(3) epc to a published international application that has entered the european phase |
Free format text: ORIGINAL CODE: 0009012 |
|
17P | Request for examination filed |
Effective date: 20020607 |
|
AK | Designated contracting states |
Kind code of ref document: A1 Designated state(s): AT BE CH CY DE DK ES FI FR GB GR IE IT LI LU MC NL PT SE TR |
|
RIN1 | Information on inventor provided before grant (corrected) |
Inventor name: SAIDI, HASSEN Inventor name: DUTERTRE, BRUNO |
|
RBV | Designated contracting states (corrected) |
Designated state(s): DE GB |
|
A4 | Supplementary search report drawn up and despatched |
Effective date: 20070615 |
|
RIC1 | Information provided on ipc code assigned before grant |
Ipc: H04L 29/06 20060101AFI20070611BHEP Ipc: H04L 9/16 20060101ALI20070611BHEP |
|
STAA | Information on the status of an ep patent application or granted ep patent |
Free format text: STATUS: THE APPLICATION IS DEEMED TO BE WITHDRAWN |
|
18D | Application deemed to be withdrawn |
Effective date: 20071205 |