Establishing a security association and authentication to secure communication between an initiator and a responder

- IBM

Provided are a computer program product, system and method embodiments for secure communication between an initiator and a responder over a network. The initiator sends a security association initialization message to the responder to establish a security association including key material used to generate a key for the security association. In response to receiving a security association initialization response to accept the security association, the initiator sends an authentication message to the responder to establish authentication between the responder and the initiator. In response to receiving an authentication message response to the authentication message, the initiator is programmed with the security association. An authentication done message is received from the responder after receiving the authentication message response. The initiator activates the security association to use the key to secure communication between the responder and initiator in response to receiving the authentication done message.

Skip to: Description  ·  Claims  ·  References Cited  · Patent History  ·  Patent History
Description
BACKGROUND OF THE INVENTION 1. Field of the Invention

The present invention relates to a computer program product, system, and method for establishing a security association and authentication to secure communication between an initiator and a responder.

2. Description of the Related Art

In a Fibre Channel environment, to provide for secure and encrypted communication between nodes in a Fabric, a Security Association (SA) management transaction occurs between an SA Initiator and an SA Responder using a security establishment protocol. The security association management protocol may be initiated by an authentication responder of the Fibre Channel authentication protocol. The initiator and responders may comprise ports in host bus adaptors in devices in a Fibre Channel network. Separate security associations are established for data transmission and data reception at a port. Completion of the SA establishment transaction results in a set of security associations and related key material used to encrypt/decrypt data communication between the initiator and the target under the established security association.

The cryptographic keys used to secure data in the security association for transmission and reception may be refreshed periodically as part of a rekey operation, which involves repeating the security establishment protocol and reauthentication. An example of a security association protocol is the Security Association Management protocol in the T11 Fibre Channel Security Protocol Standard FC-SP-2, which is similar to protocols defined by internet protocol standards such as Internet Key Exchange version 2 (IKEv2). The protocol consists of a pair of messages, SA_Init and SA_Init Response to establish a parent association followed by a pair of messages, SA_Auth and SA_Auth Response to perform authentication of the entitles and establish the Security Associations that protect the data transferred between the entitles.

When using re-authentication to perform a rekey operation, multiple security associations are maintained at the initiator and target until the old security association is deleted. In certain implementations, to avoid traffic loss during this time, transmission of data using the new security association is delayed until sometime after reception of a delete request from the responder. If errors occur in the messaging to establish the new security associations, inconsistent states and traffic loss may result.

There is a need in the art for improved techniques for establishing security associations for transmission of data between nodes.

SUMMARY

Provided are a computer program product, system and method embodiments for secure communication between an initiator and a responder over a network. The initiator sends a security association initialization message to the responder to establish a security association with the responder including key material used to generate a key for the security association. In response to receiving a security association initialization response to accept the security association, the initiator sends an authentication message to the responder to program the responder to establish authentication between the responder and the initiator. In response to receiving an authentication message response to the authentication message, the initiator is programmed with the security association and the key generated for the security association. An authentication done message is received from the responder after receiving the authentication message response. The initiator activates the security association to use the key to secure communication between the responder and initiator in response to receiving the authentication done message.

The above embodiments avoids inconsistent states due to errors when establishing a security association and authentication of nodes by having the initiator wait for an authentication done message from the responder to confirm to the initiator that the responder has successfully completed authentication and has activated the new security association for immediate use, also following an authentication message response to an authentication message. This allows the initiator to begin using the new security association for transmission upon the receipt of the authentication done message after the initiator programmed the initiator with the security association and the key such that the initiator is assured by the authentication done message that the responder has successfully completed authentication and activated the new security association message.

Further provided are a computer program product, system and method embodiments for secure communication between an initiator and a responder over a network and to perform a rekey operation. The initiator maintains a first security association with the responder having a first key to use to encrypt and decrypt data transmitted with the responder. The initiator performs a rekey operation to establish a second security association with the responder using a second key. Input/Output (I/O) is queued for transmission using the second key after completing the rekey operation. In response to activating the second security association to use for transmission, the initiator starts an invalidate timer. Both the first and the second keys can be used for transmissions with the responder before the invalidate timer expires after starting. The initiator invalidates the first security association in response to expiration of the invalidate timer.

With the above embodiments, the initiator may initiate a rekey operation to generate a second security association for use at the initiator. After activating the second security association, the initiator starts an invalidate timer to wait before invalidating the first security association to provide time to flush I/O secured using the first security association from the initiator, so that both the first and second keys can be used during the invalidate timer. Thus, when the initiator invalidates the first security association after the invalidate timer expires, the initiator is assured that the first security association is not needed for any pending transmissions in the system.

The subject matter of the embodiments may optionally include an optional embodiment of sending an accept message to the responder in response to the authentication done message. The security association and generated key for the security association are activated to use for communication in response to the sending the accept message. The authentication is established between the initiator and the responder in response to sending the accept message.

With the above optional embodiment, the security association and authentication are coordinated by having the initiator send an accept message to the authentication done message to signal to the responder that both initiator and responder have activated the security association for use and the security association may be used now for further transmissions.

The subject matter of the above embodiments may optionally include an optional embodiment that the accept message comprises a second accept message. The initiator sends a first accept message to the responder in response to the authentication message response to cause the responder to activate the security association to use a key for the security association to secure communication between the initiator and the responder. The authentication done message is received after sending the first accept message.

With the above optional embodiment, after authentication is complete, the initiator may signal the responder with a first accept message to cause the responder to activate the security association, and then the responder signals it has activated the security association through the authentication done message following the first accept message. This allows coordination between the initiator and responder as to when both have activated the security association.

The subject matter of the above embodiments may optionally include an optional embodiment that the initiator comprises a host system and the responder comprises a storage controller providing the host system access to storage resources. The security association and authentication are established for an initiator port at the host system and a responder port at the storage controller.

With the above optional embodiment, the host may implement the initiator to establish the security association with a port at a storage controller. Having the host function as the initiator in establishing a security association with a storage controller avoid having to negotiate between nodes the node that will function as the initiator.

The subject matter of the above embodiments may optionally include an optional embodiment for the rekey operation that in response to receiving a security association initialization response to accept the second security association, the initiator sends an authentication message to the responder to cause the responder to establish authentication between the responder and the initiator. The initiator activates the second security association to use the second key to encrypt and decrypt communication with the responder in response to receiving an authentication done message following the authentication message. The initiator starts the invalidate timer is started in response to the authentication done message.

With the above optional embodiment, the initiator coordinates when it starts the invalidate timer to invalidate the first security association at a point the responder sends the authentication done message to signal that authentication has completed and the second key has been activated for use.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 illustrates an embodiment of a network computing environment.

FIG. 2 illustrates an embodiment of a host bus adaptor.

FIG. 3 illustrates an embodiment of a security association.

FIG. 4 illustrates an embodiment of operations to establish a security association and authentication between an initiator and responder nodes.

FIG. 5 illustrates a message flow for the operations of FIG. 4.

FIG. 6 illustrates an embodiment of operations to perform a rekey operation to generate a new security association and authentication between an initiator and responder nodes and delete the old security association.

FIG. 7 illustrates a message flow for the operations of FIG. 6.

FIG. 8 illustrates a computing environment in which the components of FIG. 1 may be implemented.

 DETAILED DESCRIPTION

Described embodiments provide improvements to computer technology for establishing a security association between an initiator and responder in a network. Described embodiments avoid inconsistent states due to errors when establishing a security association and authentication of nodes by having the responder node send a final authentication done message to the initiator. The responder sends the authentication done message to confirm to the initiator that the responder has successfully completed authentication and has activated the new security association for immediate use. This allows the responder to begin using the new security association for transmission upon the completion of the security association management transaction rather than waiting to delete the old security association. In described embodiments, the old security association is maintained for reception of data for a period of time after the new security association is established for those messages coded with the key for the old security association. The delay is of sufficient length to allow all messages coded with the old security to be flushed from the system before deleting the old security association. This eliminates any potential issues with loss, as messages encrypted (secured) with the old security association cannot be processed (decrypted) once the old security association is removed.

FIG. 1 illustrates an embodiment of a network computing environment 100 in which a plurality of hosts 1021, 1022 . . . 102n may submit Input/Output (I/O) requests to a storage controller 104 over a fabric (network) 106 to access data at volumes 108 (e.g., Logical Unit Numbers, Logical Devices, Logical Subsystems, etc.) in a storage 110. The storage controller 104 includes one or more processors 112 and an I/O manager 114 for managing the transfer of tracks transferred between the hosts 1021, 1022 . . . 102n and the storage. A track may comprise any unit of data configured in the storage 110, such as a track, Logical Block Address (LBA), storage cell, group of cells (e.g., column, row or array of cells), sector, segment, etc., which may be part of a larger grouping of tracks, such as a volume, logical device, etc.

Each of the hosts, as shown with respect to host 1021 have one or more host bus adaptors (HBAs) 200H having a plurality of ports 210H1 . . . 210Hn to connect to a fabric 106 of switches. The storage controller 140 includes one or more host bus adaptors (HBAs) 200SC having a plurality of ports 210SC1 . . . 210SC n to connect to the fabric 106 of switches. Alternatively, host ports 210Hi and storage controller ports 210SC i may connect directly via cable.

In one embodiment, the fabric 106 may comprise a Storage Area Network (SAN) comprising implemented with a Fibre Channel topology. The 210Hi, 210SCi may comprise Fibre Channel nodes that connect to Fibre Channel switches in the fabric 106. In alternative embodiments, the fabric 106 may comprise other types of networks, such as a Local Area Network (LAN), a Wide Area Network (WAN), the Internet, and Intranet, etc. Alternatively, the hosts 1021, 1022 . . . 102n may connect to the storage controller 104 over a bus interface, such as a Peripheral Component Interconnect (PCI) bus interface and other interfaces known in the art.

In described embodiments, the messaging between an initiator port and responder port are described with respect to the Fibre Channel protocol. In alternative embodiments, alternative network protocols may be used for transmitting messages between an initiator node that initiates establishment of a new security association and authentication and a responder node that responds to the request to establish a new security association and authentication for a pair of ports.

An initiator as that term is used herein refers to any device involved in initiating establishment of a security association and authentication with a responder, which refers to any device involved in responding to the establishment of the security association and authentication initiated by the initiator to provide secure communication between the initiator and the responder. The elements that function as the initiator and responder may be referred to as an initiator and responder, which may also be referred to as initiator port and responder port, initiator node and responder node, initiator HBA and responder HBA, as source node for the initiator and target node for the responder, as host port for the initiator and storage controller port for the responder, etc.

The fabric controller 202 and security association manager 206 may comprise program code loaded into a memory and executed by one or more processors. Alternatively, some or all of the functions may be implemented as microcode or firmware in hardware devices in the storage controller 104, such as in Application Specific Integrated Circuits (ASICs).

The storage 110 may comprise one or more storage devices known in the art, such as a solid state storage device (SSD) comprised of solid state electronics, NAND storage cells, EEPROM (Electrically Erasable Programmable Read-Only Memory), flash memory, flash disk, Random Access Memory (RAM) drive, storage-class memory (SCM), Phase Change Memory (PCM), resistive random access memory (RRAM), spin transfer torque memory (STM-RAM), conductive bridging RAM (CBRAM), magnetic hard disk drive, optical disk, tape, etc. The storage devices may further be configured into an array of devices, such as Just a Bunch of Disks (JBOD), Direct Access Storage Device (DASD), Redundant Array of Independent Disks (RAID) array, virtualization device, etc. Further, the storage devices may comprise heterogeneous storage devices from different vendors or from the same vendor.

FIG. 2 illustrates an embodiment of a host bus adaptor (HBA) 200i, such as a host HBA 200H and storage controller HBA 200SC The HBA 200i includes a fabric controller 202 implementing a fabric protocol, such as the Fibre Channel protocol or other network protocols known in the art, to initialize and authenticate connections and manage I/O operations; an I/O queue 204 to queue I/O requests to send or receive with respect to other HBA ports on other devices; a security association index 300 having initialized security associations providing keys to encrypt and decrypt data from another fabric port; a security association manager 206 to negotiate and establish a security association 300i with another node port in the fabric 106, wherein one port at one node functions as an initiator to communicate with a port on another node functioning as a responder; and an invalidate timer 208 used to determine when to invalidate a previous security association after performing a rekey operation to establish a new security association and new key to use for encryption/decryption. The HBA 200i includes one or more ports 2101 . . . 210n that may function as initiator or responder ports to communicate on the fabric 106.

The security association manager 206 may also implement an authentication protocol to authenticate the identity of an initiator and responder to each other as part of establishing the security association for a security association pair between an initiator port and responder port. In certain embodiments, after the security association exchange has completed, authentication messages may be exchanged to authenticate the initiator port and responder port and exchange identifies. For purposes of describing establishing a security association and authentication between an initiator port and a responder port, reference is made to initiator port 118I in the host HBA 200H and a responder port 1228 in the storage controller HBA 200SC. In further embodiments, the initiator and responder ports may be implemented in other types of devices that communicate over a fabric 106.

FIG. 3 illustrates an embodiment of an instance of a security association 300i in the security association index 300, and includes a security association (SA) number 302; one or more keys 304 used to encrypt and decrypt messages with another node; a role 306 indicating whether a local port 308 involved in the security association is an initiator or responder; a remote port 310 at another device involved in the security association 302 that is subject to secure transmission with the local port 308; security association attributes 312, such as transform type used to encrypt/decrypt messages, transform attributes, nonces, and key material used to seed and generate the key; and an active flag 314 indicating whether the security association 300i is actively being used to encrypt and decrypt messages. Messages would indicate the security association number 302 in the header of the security association used to encrypt and decrypt a message.

FIG. 4 illustrates an embodiment of operations performed by the security association manager 206 implemented in two HBAs 200i, one functioning as an initiator HBA 200I initiating a security association management transaction from an initiator port 210I in the initiator HBA 200I and another functioning as a responder HBA 200R responding to a security association management transaction at a responder port 210R in the responder HBA 200R. In one implementation, the host HBA 200H functions as the initiator and the storage controller HBA 200SC functions as a responder. In further embodiments, other combinations of devices may have the HBAs operating as initiator or responder for different ports. To initiate operations to establish a security association 300i, the initiator HBA 200I sends (at block 400) a security association initialization message (SA_Init) from the initiator port 210I to the responder port 210R to establish a security association with the responder port 210R including key material used to create a encryption key. Upon receiving (at block 402) the security association initialization message, the responder HBA 200R sends (at block 404) an acceptance of the security association initialization message for processing to the initiator port 210I. In Fibre Channel protocol implementations, an accept message indicating processing of a received message may take the form of the link services accept message (LS_ACC). After the accept is sent, the responder HBA 200R sends (at block 406) an initialization response message (SA_Init Resp) to the initiator port 210I to accept the security association, including a selected transform method to use for encryption/decryption. The security association initialization message may include a plurality of different encryption transform methods from which the responder HBA 200R may select to use for the security association 300i being established.

Upon receiving the send initialization response message (SA_Init Resp), the initiator HBA 200I sends (at block 408) an accept (LS_ACC) to the responder port 2108 that the initialization response message is accepted for processing and then sends (at block 410) an authentication message (SA_Auth) to the responder port 2108 to program the responder port 2108 to establish authentication between the responder and the initiator, including initiator identify information. The initiator identity information may comprise a certificate for the entity having the initiator port 210I, such as the host 102i. Upon receiving the security association authentication message (SA_Auth), the responder HBA 2108 sends (at block 412) an accept message (LS_ACC) to the initiator port 210I that the authentication message was accepted for processing and then generates (at block 414) a security association 300i, including the key 304 or keys needed to perform decryption and encryption with messages from the initiator port 210I, to program in the responder security association index 300 indicating the key generated for the security association 300i and other information. After programming the responder HBA 200R with the security association 300i for the responder port 210R, the responder HBA 200R sends (at block 416) an authentication response message (SA_Auth Resp) to the initiator port 210I to accept the authentication, including responder identity information, such as an identity of the entity including the responder HBA 200R, such as a storage controller 104.

Upon receiving the security association authentication response message, the initiator HBA 200I generates (at block 418) a security association 300i to program in the initiator security association index 300 to indicate a key 304 generated for the security association 300i and other information. After programming the security association 300i in the initiator index 300, the initiator HBA 200I sends (at block 420) an accept (LS_ACC) to the responder port 210R that the authentication message is accepted for processing. Upon receiving accept, the responder HBA 200R activates (at block 422) the created security association 300I, such as by setting the active flag 314 to start transmitting to the initiator port 210I using the generated key 304 for the security association 300I. After activating the security association, the responder HBA 200R sends (at block 424) an authentication done message (AUTH Done) to the initiator port 210I indicating that both security association initialization and authentication is completed and transmissions may now be encrypted and decrypted using the key 304 for the newly established security association 300i. Upon receiving the authentication done message, the initiator HBA 200I activates (at block 426) the created security association 300i, such as by setting the active flag 314 to start transmitting to the responder port 210R using the generated key 304 for the security association 300i. After activating the security association, the initiator HBA 200I sends (at block 428) an accept (LS_ACC) to the responder port 220R that the security association 300i is activated and starts transmitting (at block 430) I/O to the responder port 210R using the new security association key 304.

FIG. 5 provides a timing chart illustrating the flow of the messages in FIG. 4 and timing of operations, with transmissions numbered with corresponding blocks in FIG. 4.

With the embodiment of FIGS. 4 and 5, the responder HBA 200R provides notification that all steps to establish the security association and authentication have completed successfully by sending the authentication done message (at block 424). Once the initiator HBA 200I accepts the authentication done message which occurs after the security association 300i has been programmed at the nodes, then both the initiator and responder nodes can begin transmission with the new security association 300i and key 304. With the authentication done message, the responder signals capability to transmit with the new key 304 and signals the initiator to also begin transmission using the new key 304 of the new security association. In this way, with the described embodiment, the security association management protocol is combined with mutual authentication to allow the initiator and responder to begin secure transmissions using a new security association.

Further, with described embodiments, a host 102i may always function as the initiator in establishing a security association with a storage controller 104 to avoid having to negotiate between nodes the node that will function as the initiator.

FIG. 6 illustrates an embodiment of operations performed between the initiator HBA 200I and the responder HBA 200R to perform a rekey operation to establish a new security association for a new child key to use for future transmissions after an initial security association is established according to the operations of FIGS. 4 and 5. To initiate a rekey operation to create a new security association 300i and key 304, the initiator HBA 200I performs (at block 600) operations at blocks 400, 408, 410, 418, 420, 426, 428 in FIG. 4 to establish security association and perform authentication for the new security association. The responder HBA 200R performs (at block 602) operations at blocks 402, 404, 406, 412, 414, 416 in FIG. 4 to establish a security association 300i and perform authentication for the rekey operation. Upon receiving the accept to the authentication response message, sent by the initiator HBA 200I at block 420, the responder HBA 200R starts (at block 604) an invalidate timer 208 when activating the security association 300i (at block 422), before sending the authentication done at (block 424). Upon the invalidate timer 208 expiring (at block 606), the responder HBA 200R invalidates (at block 608) any pending active security associations 300i-1. Upon invalidating the prior security association, the responder HBA 200R would only use the new security association 300i created as part of the rekey operation. Further, when the initiator HBA 200I sends the accept to the authentication done (at block 428), it would also start (at block 610) its own invalidate timer 208. Upon expiration (at block 612) of the invalidate timer 208 the prior security association 300i-1 at the initiator HBA 200I is invalidated (at block 614).

FIG. 7 provides a timing chart illustrating the flow of the messages in FIG. 6 and timing of the rekey operations, with transmissions numbered with corresponding blocks in FIG. 6. Reference numbers from FIG. 4 shown in FIG. 7 refer to the security association initialization operations of FIG. 4 as performed with respect to the establishment of a second or new security association as described in FIG. 6.

With the embodiment of operations of FIGS. 6 and 7, after completion of the rekey operation, both the initiator port 210I and responder port 210R have begun queuing I/O requests for transmission using the new transmission keys. Moreover, both the initiator and responder start invalidate timers 208 that provide sufficient time to allow the queued I/O requests transmitted using the previous key and security association 300i-1 to be processed and flushed out of the I/O queue 204 before invalidating the previous security association 300i-1 needed to process the I/O requests sent before activation of the new keys. In this way, by the time the previous security association 300i-1 is invalidated, there are likely no more I/O requests in the I/O queue 204 encrypted using the previous security association 300i-1. Further, in one embodiment, the responder HBA 200R may start the invalidate timer 208 before the initiator HBA 2001, because the responder activates the new security association in response to the accept (at block 422) before the imitator activates its new security association in response to the later sent authentication done message (at block 424).

The present invention may be a system, a method, and/or a computer program product. The computer program product may include a computer readable storage medium (or media) having computer readable program instructions thereon for causing a processor to carry out aspects of the present invention.

The computer readable storage medium can be a tangible device that can retain and store instructions for use by an instruction execution device. The computer readable storage medium may be, for example, but is not limited to, an electronic storage device, a magnetic storage device, an optical storage device, an electromagnetic storage device, a semiconductor storage device, or any suitable combination of the foregoing. A non-exhaustive list of more specific examples of the computer readable storage medium includes the following: a portable computer diskette, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or Flash memory), a static random access memory (SRAM), a portable compact disc read-only memory (CD-ROM), a digital versatile disk (DVD), a memory stick, a floppy disk, a mechanically encoded device such as punch-cards or raised structures in a groove having instructions recorded thereon, and any suitable combination of the foregoing. A computer readable storage medium, as used herein, is not to be construed as being transitory signals per se, such as radio waves or other freely propagating electromagnetic waves, electromagnetic waves propagating through a waveguide or other transmission media (e.g., light pulses passing through a fiber-optic cable), or electrical signals transmitted through a wire.

Computer readable program instructions described herein can be downloaded to respective computing/processing devices from a computer readable storage medium or to an external computer or external storage device via a network, for example, the Internet, a local area network, a wide area network and/or a wireless network. The network may comprise copper transmission cables, optical transmission fibers, wireless transmission, routers, firewalls, switches, gateway computers and/or edge servers. A network adapter card or network interface in each computing/processing device receives computer readable program instructions from the network and forwards the computer readable program instructions for storage in a computer readable storage medium within the respective computing/processing device.

Computer readable program instructions for carrying out operations of the present invention may be assembler instructions, instruction-set-architecture (ISA) instructions, machine instructions, machine dependent instructions, microcode, firmware instructions, state-setting data, or either source code or object code written in any combination of one or more programming languages, including an object oriented programming language such as Java, Smalltalk, C++ or the like, and conventional procedural programming languages, such as the “C” programming language or similar programming languages. The computer readable program instructions may execute entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer or entirely on the remote computer or server. In the latter scenario, the remote computer may be connected to the user's computer through any type of network, including a local area network (LAN) or a wide area network (WAN), or the connection may be made to an external computer (for example, through the Internet using an Internet Service Provider). In some embodiments, electronic circuitry including, for example, programmable logic circuitry, field-programmable gate arrays (FPGA), or programmable logic arrays (PLA) may execute the computer readable program instructions by utilizing state information of the computer readable program instructions to personalize the electronic circuitry, in order to perform aspects of the present invention.

Aspects of the present invention are described herein with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the invention. It will be understood that each block of the flowchart illustrations and/or block diagrams, and combinations of blocks in the flowchart illustrations and/or block diagrams, can be implemented by computer readable program instructions.

These computer readable program instructions may be provided to a processor of a general purpose computer, special purpose computer, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions/acts specified in the flowchart and/or block diagram block or blocks. These computer readable program instructions may also be stored in a computer readable storage medium that can direct a computer, a programmable data processing apparatus, and/or other devices to function in a particular manner, such that the computer readable storage medium having instructions stored therein comprises an article of manufacture including instructions which implement aspects of the function/act specified in the flowchart and/or block diagram block or blocks.

The computer readable program instructions may also be loaded onto a computer, other programmable data processing apparatus, or other device to cause a series of operational steps to be performed on the computer, other programmable apparatus or other device to produce a computer implemented process, such that the instructions which execute on the computer, other programmable apparatus, or other device implement the functions/acts specified in the flowchart and/or block diagram block or blocks.

The flowchart and block diagrams in the Figures illustrate the architecture, functionality, and operation of possible implementations of systems, methods, and computer program products according to various embodiments of the present invention. In this regard, each block in the flowchart or block diagrams may represent a module, segment, or portion of instructions, which comprises one or more executable instructions for implementing the specified logical function(s). In some alternative implementations, the functions noted in the block may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It will also be noted that each block of the block diagrams and/or flowchart illustration, and combinations of blocks in the block diagrams and/or flowchart illustration, can be implemented by special purpose hardware-based systems that perform the specified functions or acts or carry out combinations of special purpose hardware and computer instructions.

The computational components of FIGS. 1 and 2, including the hosts 1021, 1022 . . . 102n, storage controller 104, and host bus adaptor 200i may be implemented in one or more computer systems, such as the computer system 802 shown in FIG. 8. Computer system/server 802 may be described in the general context of computer system executable instructions, such as program modules, being executed by a computer system. Generally, program modules may include routines, programs, objects, components, logic, data structures, and so on that perform particular tasks or implement particular abstract data types. Computer system/server 802 may be practiced in distributed cloud computing environments where tasks are performed by remote processing devices that are linked through a communications network. In a distributed cloud computing environment, program modules may be located in both local and remote computer system storage media including memory storage devices.

As shown in FIG. 8, the computer system/server 802 is shown in the form of a general-purpose computing device. The components of computer system/server 802 may include, but are not limited to, one or more processors or processing units 804, a system memory 806, and a bus 808 that couples various system components including system memory 806 to processor 804. Bus 808 represents one or more of any of several types of bus structures, including a memory bus or memory controller, a peripheral bus, an accelerated graphics port, and a processor or local bus using any of a variety of bus architectures. By way of example, and not limitation, such architectures include Industry Standard Architecture (ISA) bus, Micro Channel Architecture (MCA) bus, Enhanced ISA (EISA) bus, Video Electronics Standards Association (VESA) local bus, and Peripheral Component Interconnects (PCI) bus.

Computer system/server 802 typically includes a variety of computer system readable media. Such media may be any available media that is accessible by computer system/server 802, and it includes both volatile and non-volatile media, removable and non-removable media.

System memory 806 can include computer system readable media in the form of volatile memory, such as random access memory (RAM) 810 and/or cache memory 812. Computer system/server 802 may further include other removable/non-removable, volatile/non-volatile computer system storage media. By way of example only, storage system 813 can be provided for reading from and writing to a non-removable, non-volatile magnetic media (not shown and typically called a “hard drive”). Although not shown, a magnetic disk drive for reading from and writing to a removable, non-volatile magnetic disk (e.g., a “floppy disk”), and an optical disk drive for reading from or writing to a removable, non-volatile optical disk such as a CD-ROM, DVD-ROM or other optical media can be provided. In such instances, each can be connected to bus 808 by one or more data media interfaces. As will be further depicted and described below, memory 806 may include at least one program product having a set (e.g., at least one) of program modules that are configured to carry out the functions of embodiments of the invention.

Program/utility 814, having a set (at least one) of program modules 816, may be stored in memory 806 by way of example, and not limitation, as well as an operating system, one or more application programs, other program modules, and program data. Each of the operating system, one or more application programs, other program modules, and program data or some combination thereof, may include an implementation of a networking environment. The components of the computer 802 may be implemented as program modules 816 which generally carry out the functions and/or methodologies of embodiments of the invention as described herein. The systems of FIG. 1 may be implemented in one or more computer systems 802, where if they are implemented in multiple computer systems 802, then the computer systems may communicate over a network.

Computer system/server 802 may also communicate with one or more external devices 818 such as a keyboard, a pointing device, a display 820, etc.; one or more devices that enable a user to interact with computer system/server 802; and/or any devices (e.g., network card, modem, etc.) that enable computer system/server 802 to communicate with one or more other computing devices. Such communication can occur via Input/Output (I/O) interfaces 822. Still yet, computer system/server 802 can communicate with one or more networks such as a local area network (LAN), a general wide area network (WAN), and/or a public network (e.g., the Internet) via network adapter 824. As depicted, network adapter 824 communicates with the other components of computer system/server 802 via bus 808. It should be understood that although not shown, other hardware and/or software components could be used in conjunction with computer system/server 802. Examples, include, but are not limited to: microcode, device drivers, redundant processing units, external disk drive arrays, RAID systems, tape drives, and data archival storage systems, etc.

The terms “an embodiment”, “embodiment”, “embodiments”, “the embodiment”, “the embodiments”, “one or more embodiments”, “some embodiments”, and “one embodiment” mean “one or more (but not all) embodiments of the present invention(s)” unless expressly specified otherwise.

The terms “including”, “comprising”, “having” and variations thereof mean “including but not limited to”, unless expressly specified otherwise.

The enumerated listing of items does not imply that any or all of the items are mutually exclusive, unless expressly specified otherwise.

The terms “a”, “an” and “the” mean “one or more”, unless expressly specified otherwise.

Devices that are in communication with each other need not be in continuous communication with each other, unless expressly specified otherwise. In addition, devices that are in communication with each other may communicate directly or indirectly through one or more intermediaries.

A description of an embodiment with several components in communication with each other does not imply that all such components are required. On the contrary a variety of optional components are described to illustrate the wide variety of possible embodiments of the present invention.

When a single device or article is described herein, it will be readily apparent that more than one device/article (whether or not they cooperate) may be used in place of a single device/article. Similarly, where more than one device or article is described herein (whether or not they cooperate), it will be readily apparent that a single device/article may be used in place of the more than one device or article or a different number of devices/articles may be used instead of the shown number of devices or programs. The functionality and/or the features of a device may be alternatively embodied by one or more other devices which are not explicitly described as having such functionality/features. Thus, other embodiments of the present invention need not include the device itself.

The foregoing description of various embodiments of the invention has been presented for the purposes of illustration and description. It is not intended to be exhaustive or to limit the invention to the precise form disclosed. Many modifications and variations are possible in light of the above teaching. It is intended that the scope of the invention be limited not by this detailed description, but rather by the claims appended hereto. The above specification, examples and data provide a complete description of the manufacture and use of the composition of the invention. Since many embodiments of the invention can be made without departing from the spirit and scope of the invention, the invention resides in the claims herein after appended.

Claims

1. A computer program product for secure communication between an initiator and a responder over a network, the computer program product comprising a computer readable storage medium having computer readable program code implemented at the initiator that when executed performs operations, the operations comprising:

sending a security association initialization message to the responder to establish a security association with the responder including key material used to generate a key for the security association;
in response to receiving a security association initialization response to accept the security association, sending an authentication message to the responder to program the responder to establish authentication between the responder and the initiator;
in response to receiving an authentication message response to the authentication message, programming the initiator with the security association and the key generated for the security association;
receiving an authentication done message from the responder after receiving the authentication message response; and
activating the security association to use the key to secure communication between the responder and initiator in response to receiving the authentication done message.

2. The computer program product of claim 1, wherein the operations further comprise:

sending an accept message to the responder in response to the authentication done message, wherein the security association and generated key for the security association are activated to use for communication in response to the sending the accept message, wherein authentication is established between the initiator and the responder in response to sending the accept message.

3. The computer program product of claim 2, wherein the accept message comprises a second accept message, wherein the operations further comprise:

sending a first accept message to the responder in response to the authentication message response to cause the responder to activate the security association to use a key for the security association to secure communication between the initiator and the responder, wherein the authentication done message is received after sending the first accept message.

4. The computer program product of claim 1, wherein the initiator comprises a host system and the responder comprises a storage controller providing the host system access to storage resources, and wherein the security association and authentication are established for an initiator port at the host system and a responder port at the storage controller.

5. A computer program product for secure communication between an initiator and a responder over a network, the computer program product comprising a computer readable storage medium having computer readable program code implemented at the initiator that when executed performs operations, the operations comprising:

maintaining a first security association with the responder having a first key to use to encrypt and decrypt data transmitted with the responder;
performing a rekey operation to establish a second security association with the responder using a second key;
queuing Input/Output (I/O) for transmission using the second key after completing the rekey operation;
in response to activating the second security association to use for transmission, starting an invalidate timer, wherein both the first and the second keys can be used for transmissions with the responder before the invalidate timer expires after starting; and
invalidate the first security association in response to expiration of the invalidate timer.

6. The computer program product of claim 5, wherein the operations further comprise:

in response to receiving a security association initialization response to accept the second security association, sending an authentication message to the responder to cause the responder to establish authentication between the responder and the initiator; and
activating the second security association to use the second key to encrypt and decrypt communication with the responder in response to receiving an authentication done message following the authentication message, wherein the invalidate timer is started in response to the authentication done message.

7. The computer program product of claim 6, wherein the operations further comprise:

sending a security association initialization message to the responder to establish the second security association with the responder including key material used to generate the second key for the second security association, wherein the security association initialization response is received from the responder after sending the security association initialization message to the responder; and
program the second security association at the initiator in response to receiving the security association initialization response.

8. The computer program product of claim 6, wherein the operations further comprise:

receiving an authentication message response from the responder authenticating an identity of the responder in response to the authentication message sent to the responder; and
sending an acknowledgment to the responder in response to the authentication message response to cause the responder to activate the second security association to use for transmissions and to activate an invalidate timer for the responder used to invalidate the first security association, wherein the invalidate timer for the initiator is started after the invalidate timer for the responder is started.

9. The computer program product of claim 8, wherein the sending the authentication message causes the responder to program the second security association at the responder, wherein the responder sends the authentication message response after programming the second security association.

10. A system for secure communication between an initiator and a responder over a network, comprising:

a processor:
a computer readable storage medium having computer readable program code implemented at the initiator that when executed performs operations, the operations comprising: sending a security association initialization message to the responder to establish a security association with the responder including key material used to generate a key for the security association; in response to receiving a security association initialization response to accept the security association, sending an authentication message to the responder to program the responder to establish authentication between the responder and the initiator; in response to receiving an authentication message response to the authentication message, programming the initiator with the security association and the key generated for the security association; receiving an authentication done message from the responder after receiving the authentication message response; and activating the security association to use the key to secure communication between the responder and initiator in response to receiving the authentication done message.

11. The system of claim 10, wherein the operations further comprise:

sending an accept message to the responder in response to the authentication done message, wherein the security association and generated key for the security association are activated to use for communication in response to the sending the accept message, wherein authentication is established between the initiator and the responder in response to sending the accept message.

12. The system of claim 11, wherein the accept message comprises a second accept message, wherein the operations further comprise:

sending a first accept message to the responder in response to the authentication message response to cause the responder to activate the security association to use a key for the security association to secure communication between the initiator and the responder, wherein the authentication done message is received after sending the first accept message.

13. The system of claim 10, wherein the initiator comprises a host system and the responder comprises a storage controller providing the host system access to storage resources, and wherein the security association and authentication are established for an initiator port at the host system and a responder port at the storage controller.

14. A system for secure communication between an initiator and a responder over a network, comprising:

a processor:
a computer readable storage medium having computer readable program code implemented at the initiator that when executed performs operations, the operations comprising: maintaining a first security association with the responder having a first key to use to encrypt and decrypt data transmitted with the responder; performing a rekey operation to establish a second security association with the responder using a second key; queuing Input/Output (I/O) for transmission using the second key after completing the rekey operation; in response to activating the second security association to use for transmission, starting an invalidate timer, wherein both the first and the second keys can be used for transmissions with the responder before the invalidate timer expires after starting; and invalidate the first security association in response to expiration of the invalidate timer.

15. The system of claim 14, wherein the operations further comprise:

in response to receiving a security association initialization response to accept the second security association, sending an authentication message to the responder to cause the responder to establish authentication between the responder and the initiator; and
activating the second security association to use the second key to encrypt and decrypt communication with the responder in response to receiving an authentication done message following the authentication message, wherein the invalidate timer is started in response to the authentication done message.

16. The system of claim 15, wherein the operations further comprise:

sending a security association initialization message to the responder to establish the second security association with the responder including key material used to generate the second key for the second security association, wherein the security association initialization response is received from the responder after sending the security association initialization message to the responder; and
program the second security association at the initiator in response to receiving the security association initialization response.

17. The system of claim 15, wherein the operations further comprise:

receiving an authentication message response from the responder authenticating an identity of the responder in response to the authentication message sent to the responder; and
sending an acknowledgment to the responder in response to the authentication message response to cause the responder to activate the second security association to use for transmissions and to activate an invalidate timer for the responder used to invalidate the first security association, wherein the invalidate timer for the initiator is started after the invalidate timer for the responder is started.

18. The system of claim 17, wherein the sending the authentication message causes the responder to program the second security association at the responder, wherein the responder sends the authentication message response after programming the second security association.

19. A method for secure communication between an initiator and a responder over a network, comprising:

maintaining, by the initiator, a first security association with the responder having a first key to use to encrypt and decrypt data transmitted with the responder;
performing, by the initiator, a rekey operation to establish a second security association with the responder using a second key;
queuing, by the initiator, Input/Output (I/O) for transmission using the second key after completing the rekey operation;
in response to activating the second security association to use for transmission, starting, by the initiator, an invalidate timer, wherein both the first and the second keys can be used for transmissions with the responder before the invalidate timer expires after starting; and
invalidate, by the initiator, the first security association in response to expiration of the invalidate timer.

20. The method of claim 19, further comprising:

in response to receiving a security association initialization response to accept the second security association, sending, by the initiator, an authentication message to the responder to cause the responder to establish authentication between the responder and the initiator; and
activating, by the initiator, the second security association to use the second key to encrypt and decrypt communication with the responder in response to receiving an authentication done message following the authentication message, wherein the invalidate timer is started in response to the authentication done message.

21. The method of claim 20, further comprising:

sending, by the initiator, a security association initialization message to the responder to establish the second security association with the responder including key material used to generate the second key for the second security association, wherein the security association initialization response is received from the responder after sending the security association initialization message to the responder; and
programing, by the initiator, the second security association at the initiator in response to receiving the security association initialization response.

22. The method of claim 19, further comprising:

receiving, by the initiator, an authentication message response from the responder authenticating an identity of the responder in response to the authentication message sent to the responder; and
sending, by the initiator, an acknowledgment to the responder in response to the authentication message response to cause the responder to activate the second security association to use for transmissions and to activate an invalidate timer for the responder used to invalidate the first security association, wherein the invalidate timer for the initiator is started after the invalidate timer for the responder is started.

23. The method of claim 22, wherein the sending the authentication message causes the responder to program the second security association at the responder, wherein the responder sends the authentication message response after programming the second security association.

Referenced Cited
U.S. Patent Documents
6219771 April 17, 2001 Kikuchi et al.
6832313 December 14, 2004 Parker
6915437 July 5, 2005 Swander
7028183 April 11, 2006 Simon
7234063 June 19, 2007 Baugher
7500102 March 3, 2009 Swander
7565537 July 21, 2009 Morais
7590843 September 15, 2009 Khalil
8250625 August 21, 2012 Risley
8275950 September 25, 2012 Sanada et al.
8327129 December 4, 2012 Ren
8479266 July 2, 2013 Delker et al.
8504823 August 6, 2013 Carpenter et al.
8649768 February 11, 2014 Gaddam et al.
8667151 March 4, 2014 Mizikovsky
8769288 July 1, 2014 Sundaram
8787572 July 22, 2014 Tewari et al.
8799436 August 5, 2014 Ayachitula et al.
8844025 September 23, 2014 Russo et al.
9043883 May 26, 2015 Touve et al.
9058191 June 16, 2015 Gupta et al.
9143937 September 22, 2015 Cherian et al.
9246898 January 26, 2016 McKeeman et al.
9882713 January 30, 2018 Raza et al.
10033702 July 24, 2018 Ford et al.
10324507 June 18, 2019 Mullins et al.
20040107342 June 3, 2004 Pham et al.
20050063352 March 24, 2005 Amara et al.
20050108531 May 19, 2005 Swander
20060104308 May 18, 2006 Pinkerton et al.
20100154053 June 17, 2010 Dodgson et al.
20110252231 October 13, 2011 Mishra
20120036363 February 9, 2012 Langham
20120129492 May 24, 2012 Mechaley, Jr.
20130003975 January 3, 2013 Fukuda et al.
20150350906 December 3, 2015 Patil et al.
20160139845 May 19, 2016 Muhlestein et al.
20160309379 October 20, 2016 Pelletier
20160342798 November 24, 2016 Smith et al.
20160378691 December 29, 2016 Sherman
20170124356 May 4, 2017 Allyn
20180367516 December 20, 2018 Mundra et al.
20190116052 April 18, 2019 Kim et al.
20190213104 July 11, 2019 Qadri et al.
20190251282 August 15, 2019 Patel et al.
Foreign Patent Documents
1980451 June 2007 CN
101119196 February 2008 CN
101911742 December 2010 CN
102063583 May 2011 CN
103425916 December 2013 CN
209057241 July 2019 CN
1276034 January 2003 EP
1657878 May 2006 EP
2763442 October 2019 EP
101552950 September 2015 KR
2018167539 September 2018 WO
2018226265 December 2018 WO
Other references
  • Fereidooni, H. et al. A New Authentication and Key Exchange Protocol for Insecure Networks. 2009 5th International Conference on Wireless Communications, Networking and Mobile Computing. https://ieeexplore.ieee.org/stamp/stamp.jsp?tp=&arnumber=5302478 (Year: 2009).
  • Hossain, Sazzad et al. Generation of one-time keys for single line authentication. 2016 14th Annual Conference on Privacy, Security and Trust (PST). https://ieeexplore.ieee.org/stamp/stamp.jsp?tp=&arnumber=7906957 (Year: 2016).
  • Kaur, Kuljit et al. Adaptive Random Key Scheme for Authentication and Key Agreement (ARKS-AKA) for efficient LTE security. 2015 2nd International Conference on Recent Advances in Engineering & Computational Sciences (RAECS). https://ieeexplore.ieee.org/stamp/stamp.jsp?tp=&arnumber=7453422 (Year: 2015).
  • Zhao, Xin et al. A Novel Authentication and Key Agreement Scheme for Wireless Mesh Networks. 2009 Fifth International Joint Conference on INC, IMS and IDC. https://ieeexplore.ieee.org/stamp/stamp.jsp?tp=&arnumber=5331675 (Year: 2009).
  • Cheneau, Tony et al. A Trustful Authentication and Key Exchange Scheme (TAKES) for ad hoc networks. 2011 5th International Conference on Network and System Security, https://ieeexplore.ieee.org/stamp/stamp.jsp?tp=&arnumber=6060009 (Year: 2011).
  • Abirami, E.; Padmavathy, T. Proficient key management scheme for multicast groups using group key agreement and broadcast encryption. 2017 International Conference on Information Communication and Embedded Systems (ICICES). https://ieeexplore.ieee.org/stamp/stamp.jsp?tp=&arnumber=8070789 (Year: 2017).
  • “Amazon Web Services: Overview of Security Processes”, Amazon, 2018, p. 95.
  • “Introduction to AWS Security Processes”, Amazon, Jun. 2016, p. 45.
  • M.K. Sah, et al., “Security and Concurrency Control in Distributed Database System”, International Journal of scientific research and management, vol. 2, Issue 12, pp. 1839-1845, 2017.
  • Anonymous, “Cognitive Storage Subsystem Secure Volumes”, ip.com, IP.com No. IPCOM000253178D, Mar. 12, 2018, pp. 4.
  • Anonymous, “Methodology and Procedure for Secure Granular Authorization and Audit Implementation in Distributed Enterprise Computing Environment”, ip.com, IP.com No. IPCOM000237293D, Jun. 11, 2014, pp. 18.
  • Anonymous, “A Method and System for Providing High Transaction Rate Authentication using Multiple Secondary Real Time Authentication Parameters”, IP.com, IP.com No. IPCOM000229944D, Aug. 8, 2013, pp. 2.
  • Anonymous, “System for Optimizing Authentication in a Multi-Threaded Environment”, IP.com, IP.com No. IPCOM000223083D, Nov. 1, 2012, pp. 4.
  • “Storage device and system with authentication mechanism”, IP.com, IP.com No. IPCOM000225630D, Feb. 22, 2013, pp. 4.
  • Anonymous, “Method for Flexible and Diverse Error Handling for Storage Devices”, IP.com, IP.com No. IPCOM000233966D, Jan. 6, 2014, pp. 7.
  • Anonymous, “Method and Apparatus for Authentication in Storage Systems using QR code”, IP.com, IP.com No. IPCOM000255722D, Oct. 11, 2018, pp. 6.
  • Anonymous, “Port Based Network Security for communication networks in a gaming environment”, IP.com, IP.com No. IPCOM000166456D, Jan. 11, 2008, pp. 3.
  • IBM, “Automation of authentication with use of internal and external key parameters”, IP.com, IP.com No. IPCOM000180832D, Mar. 18, 2009, pp. 5.
  • Anonymous, “Provide Java APIs into the IUCV protocol”, IP.com, IP.com No. IPCOM000244583D, Dec. 23, 2015, pp. 4.
  • Wale Amol, D., & Rastogi, V. Data Integrity Auditing of Cloud Storage. International Journal of Computer Applications, Jan. 2016, pp. 5.
  • A. Vasudevan, et al., “Lockdown: Towards a safe and practical architecture for security applications on commodity platforms”, In International Conference on Trust and Trustworthy Computing (pp. 34-54). Springer, Berlin, Heidelberg, Jun. 2012.
  • J.K Resch, et al. “AONT-RS: Blending Security and Performance in Dispersed Storage Systems”, 2017, pp. 12.
  • A. Buecker, et al. “Reduce Risk and Improve Security on IBM Mainframes: vol. 3 Mainframe Subsystem and Application Security”, IBM Corporation, Redbooks, Document No. SG24-8196-00, Nov. 2015, pp. 200.
  • F.Majstor, Storage Area Networks Security Protocols and Mechanisms', Apr. 2004, pp. 21.
  • M. Lippett, et al., “Networked Storage Concepts and Protocols”, EMC2 Techbooks, EMC Corporation, 2008, pp. 370.
  • J.Tate, et al., “IBM SAN Survival Guide”, IBM Corporation, Redbooks, Document No. SG24-6143-01, Aug. 2003, pp. 662.
  • “Storage Security: Fibre Channel Security”, SNIA, Technical White Paper, Version 1, May 2016, pp. 29.
  • “Fibre Channel Framing and Signaling-5”, INCITS, INCITS working draft proposed American National Standard for Information Technology, Apr. 3, 2018, pp. 506.
  • “Fibre Channel Link Services Rev 4.04”, INCITS, INCITS working draft proposed American National Standard for Information Technology, Jul. 16, 2019, pp. 238.
  • “Fibre Channel Security Protocols-2”, INCITS, INCITS working draft proposed American National Standard for Information Technology, Jun. 12, 2012, pp. 312.
  • B. Aboba, et al. “Securing Block Storage Protocols over IP”, The Internet Society, Apr. 2004, [online][retrieved 082619] https://tools.ietf.org/html/rfc3723, pp. 70.
  • “Information Technology Fibre Channel Part 432: Security Protocols-2”, ISO/IEC, pp. 312.
  • “Understanding FC (and FCoE) fabric configuration in 5 minutes or less”, STEVENU, Mar. 20, 2012, pp. 8, [online][retrieved 082619] https://blog.osnexus.com/2012/03/20/understanding-fc-fabric-configurati . . . .
  • Anonymous, “USB Trust Extensions for secured USB devices”, IP.com, IP.com No. IPCOM000245301D, Feb. 26, 2016, pp. 8.
  • “Dell EMC PowerMax Reliability, Availability, and Serviceability Technical White Paper”, Dell EMC, Oct. 2018, pp. 32.
  • “vSphere Security”, VMWare, Inc., 2009, pp. 258.
  • U.S. Appl. No. 16/583,173, filed Sep. 25, 2019.
  • U.S. Appl. No. 16/568,117, filed Sep. 11, 2019.
  • U.S. Appl. No. 16/583,178, filed Sep. 25, 2019.
  • U.S. Appl. No. 16/568,160, filed Sep. 11, 2019.
  • U.S. Appl. No. 16/568,124, filed Sep. 11, 2019.
  • U.S. Appl. No. 16/568,131, filed Sep. 11, 2019.
  • U.S. Appl. No. 16/568,176, filed Sep. 11, 2019.
  • English machine translation for CN209057241 dated Dec. 4, 2013, pp. 6.
  • English machine translation for CN103425916 dated Dec. 4, 2013, pp. 12.
  • English machine translation of CN102063583 dated May 18, 2011, pp. 20.
  • English machine translation for KR101552950 dated Sep. 14, 2015, pp. 16.
  • List of IBM Patents and Applications Treated as Related, dated Oct. 21, 2019, pp. 2.
  • Transmittal of Information on Confidential Activities dated Feb. 21, 2020, pp. 1.
  • C. Kaufman, et al., “Internet Key Exchange Protocol Version2 (IKEv2)Internet Engineering Task Force (IETF)”, Oct. 31, 2014, pp. 285.
  • PCT International Search Report and Written Opinion, dated Dec. 16, 2020, pp. 9, for Serial No. PCT IB2020/058331, P201907310PCT01.
  • BG. Lee, et al., “Concatenated Wireless Roaming Security Association and Authentication Protocol Using ID-based Cryptography”, 57th IEEE SemiAnnual Vehicular Technology Conference, 2003, VTC 2003-Spring, https://ieeexplore.ieee.org/stamp/stamp.jsp?tp= arnumber=1207072.
  • YC. Ouyang, et al., “New Security Key Exchange Channel for 802.11 WLANS”, IEEE 37th Annual 2003 International Carnahan Conference on Security Technology, 2003, Proceedings, https://ieeexplore.ieee.org/stamp/stamp.jsp? tp=arnumber=1297562.
  • S. Sumathy, et al., “Secure Key Exchange and Encryption Mechanism for Ad Hoc Networks”, 2009 First International Conference on Networks & Communications, https://ieeexplore.IEEE.org/stamp/stamp.jsp?tp=arnumber=5384027.
  • PCT International Search Report and Written Opinion dated Dec. 16, 2020, pp. 9, for Serial No. PCTI B2020/058331.
  • PCT International Search Report and Written Opinion, dated Dec. 16, 2020, pp. 9, for Serial No. PCT IB2020/058326.
  • Notice of Allowance dated Oct. 15, 2021, pp. 15, for U.S. Appl. No. 16/568,176.
Patent History
Patent number: 11201749
Type: Grant
Filed: Sep 11, 2019
Date of Patent: Dec 14, 2021
Patent Publication Number: 20210075621
Assignee: INTERNATIONAL BUSINESS MACHINES CORPORATION (Armonk, NY)
Inventors: Roger G. Hathorn (Tucson, AZ), Patricia G. Driever (Poughkeepsie, NY), Christopher J. Colonna (Ossining, NY), Mooheng Zee (Fishkill, NY), Richard Mark Sczepczenski (Hyde Park, NY), Mikel William Welsh (Tucson, AZ), John R. Flanagan (Chapel Hill, NC)
Primary Examiner: Jeremiah L Avery
Application Number: 16/568,174
Classifications
Current U.S. Class: Network Resources Access Controlling (709/229)
International Classification: H04L 29/06 (20060101); H04L 9/32 (20060101); H04L 9/08 (20060101);