Enabling method, system, and program for host port security - Patents.com

The 'audit mode' indicator in Fiber Channel environments enables simultaneous plaintext and encrypted data exchange, addressing connectivity and security challenges in heterogeneous systems by managing the transition period effectively.

JP7582753B2Active Publication Date: 2024-11-13INTERNATIONAL BUSINESS MACHINE CORPORATION
View PDF 5 Cites 0 Cited by

Patent Information

Application Number
JP2022510866
Authority / Receiving Office
JP · JP
Patent Type
Patents
Current Assignee / Owner
Priority Date
2019-09-11
Filing Date
2020-09-02
Publication Date
2024-11-13
Estimated Expiration
2040-09-02

AI Technical Summary

Technical Problem

Existing Fiber Channel environments face challenges in maintaining connectivity and data security when transitioning from plaintext to encrypted data, particularly in heterogeneous systems where not all ports support security protocols, leading to potential loss of access and I/O errors.

Method used

Implementing an 'audit mode' indicator that allows simultaneous exchange of plaintext and encrypted data during the transition period, using a plaintext tolerance indicator and grace period timer to manage the switch from plaintext to encrypted data without causing I/O errors.

Benefits of technology

Ensures seamless transition from plaintext to encrypted data exchange, maintaining connectivity and preventing I/O errors in heterogeneous Fiber Channel environments by allowing a controlled mix of data types during the security protocol establishment.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure 0007582753000001
    Figure 0007582753000001
  • Figure 0007582753000002
    Figure 0007582753000002
  • Figure 0007582753000003
    Figure 0007582753000003
Patent Text Reader

Abstract

The host port is enabled for security. In response to determining that the audit mode indicator is enabled to allow input / output (I / O) even when it is not possible to successfully complete authentication or security association negotiation between the host port and the storage port, the host port performs cleartext I / O on the path between the host port and the storage port. The host port enables data encryption for the I / O on the path while performing cleartext I / O on the path.
Need to check novelty before this filing date? Find Prior Art

Description

[Technical field]

[0001] The present invention generally relates to simultaneous enablement of encryption on operational paths at host ports. [Background technology]

[0002] Fibre Channel refers to a set of unified architectural standards for data transmission developed by the American National Standards Institute (ANSI). Security solutions for the Fibre Channel architecture are provided by the Fibre Channel Security Protocol (FC-SP), also developed by ANSI. FC-SP provides mechanisms for device authentication, per-message security, and policy distribution in a Fibre Channel environment. Further details of FC-SP are provided in the publication "Fibre Channel Security Protocol-2 (FC-SP-2)", Revision 2.72, published by ANSI on June 12, 2012.

[0003] FC-LS-4 provides mechanisms for link services in Fibre Channel and further details are provided in the ANSI publication "Fibre Channel Link Services (FC-LS-4)", Revision 4.04, published on July 16, 2019. FC-FS-5 provides mechanisms for framing and signaling in Fibre Channel and further details are provided in the ANSI publication "Fibre Channel Framing and Signaling-5 (FC-FS-5)", Revision 1.0, published on April 3, 2018.

[0004] In a Fibre Channel environment, to provide secure and encrypted communication between nodes in the fabric, security association (SA) management transactions occur between SA_Initiator and SA_Responder using a security establishment protocol. Initiator and responder may include ports on an adapter of a device in the Fibre Channel network. Separate security associations are established for data transmission and data reception on the port. Completion of an SA establishment transaction results in a set of security associations and associated keying material that are used to encrypt / decrypt data communication between the initiator and responder under the established security association. An example of a security association protocol is the security association management protocol in FC-SP-2. 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 establish security associations that perform authentication of the entities and protect data transferred between them.

[0005] A storage controller may control access to storage for one or more host computing devices connected to the storage controller via a Fibre Channel network. A storage management application running on the storage controller may manage multiple storage devices, such as disk drives, tape drives, flash drives, and direct access storage devices (DASDs), coupled to the storage controller. The host computing devices may send input / output (I / O) commands to the storage controller, which may execute the I / O commands to read data from or write data to the storage devices. Communication between the host and the storage controller occurs through Fibre Channel ports located on the host-to-storage controller adapters.

[0006] US Patent Publication No. 2010-0154053 discusses a storage security mechanism using cryptographic splitting. US Patent Publication No. 2019-0251282 discusses a cyber security mechanism for transferring data between servers. US Patent Publication No. 2016-0139845 discusses storage level access control for data grouping structures. US Patent Publication No. 2016-0378691 discusses a mechanism for protecting storage against attacks. US Patent No. 8,275,950 discusses a Fibre Channel attached storage controller that may manage one-to-one correspondence of host computer and storage controller ports using a login request control table to maintain enhanced security by blocking any unauthorized access attempts from a host computer on a port-by-port basis. US Patent No. 6,219,771 discusses a data storage device with improved security process and split allocation capabilities. U.S. Patent Application Publication No. 2004-0107342 discusses a secure network file access control system. European Patent Application No. EP1276034A2 discusses security for logical units in a storage subsystem. U.S. Patent Application Publication No. 2016-0342798 discusses a system and method for secured device management. U.S. Patent No. 8,799,436 discusses a system and method for auditing and verifying configuration items in an information technology (IT) configuration management database.

[0007] No. 6,832,313 describes a system including a central computer and a remote computer capable of communicating over a link, which are moved from plaintext operation to encrypted operation when the computers receive and install a long-term key necessary for encrypted communications. No. 8,250,625 describes a method of reducing downtime of a communications system when enabling encryption operations of an encryption system of the communications system, the encryption system including a first encryption device operatively coupled to a plurality of second encryption devices via a communications network of the communications system. Summary of the Invention

[0008] A method, system, and computer program product are provided in which a host port is enabled for security. The host port performs input / output (I / O) in the clear on a path between the host port and a storage port in response to determining that an audit mode indicator is enabled to allow I / O even if an authentication or security association negotiation between the host port and the storage port cannot be successfully completed. The host port enables data encryption for I / O on the path simultaneously with performing the I / O in the clear on the path. As a result, a mechanism is provided for transitioning from clear data to encrypted data in embodiments in which the audit mode indicator is enabled.

[0009] In some embodiments, the simultaneous enablement of data encryption includes initiating a security association (SA) management transaction between the host port and the storage port, thereby providing a mechanism that allows these embodiments to be implemented with Fibre Channel security associations.

[0010] In a further embodiment, the host port is programmed with key material for the exchange of encrypted data along with a plaintext tolerance indicator configured to permit the exchange of plaintext data on the path simultaneously with the exchange of encrypted data on the path, such that encrypted data is permitted from a certain point in time.

[0011] In some embodiments, in response to the plaintext tolerance indicator being configured to permit exchange of plaintext data on the path simultaneously with exchange of encrypted data on the path, the host port is configured to receive both plaintext and encrypted data using the keying material, such that a new indicator is used that permits intermixed plaintext and encrypted data.

[0012] In a further embodiment, in response to the host port determining that all cleartext has been received due to a timer expiring after the security association was activated for transmission, the host port is programmed to no longer process cleartext data, resulting in a transition from a mixture of cleartext and encrypted data to only encrypted data.

[0013] In yet a further embodiment, the timer expires after a timeout period sufficient to flush any cleartext data that was queued for transmission on the path at the time transmission of encrypted data began on the path, thereby allowing sufficient time for all queued cleartext I / O to complete.

[0014] In a further embodiment, when both clear and encrypted data are exchanged in the path for a predetermined period of time indicated by a timer, no I / O errors are generated, and as a result, audit mode is integrated into Fibre Channel without causing I / O errors.

[0015] Reference is now made to the drawings, in which like reference numerals represent corresponding parts throughout the several views. [Brief description of the drawings]

[0016] [Figure 1] 1 illustrates a block diagram of a heterogeneous computing environment including multiple hosts communicating with multiple storage controllers and / or storage devices via a Fibre Channel fabric, according to some embodiments. [Diagram 2] 1 is a block diagram illustration of a system for maintaining access for hosts for security enablement in a heterogeneous computing environment, according to some embodiments. [Diagram 3] 1 illustrates a block diagram showing security bits for login in Fibre Channel and enforcement to Fibre Channel via an audit mode indicator, according to some embodiments. [Figure 4] 1 is an illustration of a block diagram showing login and response in Fibre Channel according to some embodiments. [Diagram 5] 1 is a block diagram illustrating an enhancement to Fibre Channel that provides indications for "security enforcement" and "security enablement" via enabling or disabling of an audit mode indicator, according to some embodiments. [Figure 6] 1 is an illustration of a flow chart showing operation of a security-enforced storage port according to some embodiments. [Figure 7] 1 is an illustration of a flow chart showing operation of a security-enabled storage port according to some embodiments. [Figure 8] 1 is a block diagram illustrating conditions that prevent authentication and management of security associations from being completed successfully, according to some embodiments. [Figure 9]1 is an illustration of a block diagram showing multiple host ports logging into a single storage port, according to some embodiments. [Figure 10] 1 illustrates a flowchart showing operations in a storage device for determining whether to change a storage port to a security enforcement state, according to some embodiments. [Figure 11] 1 is an illustration of a flowchart showing operations for maintaining access for security enablement in a host system, according to some embodiments. [Figure 12] 13 is an illustration of a flowchart showing additional operations for maintaining access for security enablement in a host system, according to some embodiments. [Figure 13] 1 is an illustration of a flowchart showing operations for maintaining access for security enablement in a storage device, according to some embodiments. [Figure 14] 11 is an illustration of a flowchart showing additional operations for maintaining access for security enablement in a storage device, according to some embodiments. [Figure 15] 1 illustrates a block diagram showing a transition from clear text I / O to encrypted I / O after authentication and security association have been successfully completed in an embodiment with audit mode enabled, according to some embodiments. [Figure 16] FIG. 1 is a block diagram illustrating data structures for a grace period that allows cleartext I / O to continue when encrypted I / O begins on a path, according to some embodiments. [Figure 17] 1 is a block diagram illustrating the initiation of cleartext I / O on a path according to some embodiments. [Figure 18] 1 illustrates a block diagram showing the flow from "plaintext I / O" to "mixed plaintext I / O and encrypted I / O" to "encrypted I / O" over one path in accordance with some embodiments. [Figure 19]1 is an illustration of a flow chart showing operations for simultaneous enablement of encryption on operational paths at a host port, according to some embodiments. [Figure 20] 1 is an illustration of a flowchart showing operations for simultaneous enablement of encryption on operational paths at a storage port, according to some embodiments. [Figure 21] 1 is a block diagram illustration of a cloud computing environment according to some embodiments. [Figure 22] 22 is a block diagram illustration of further details of the cloud computing environment of FIG. 21 according to some embodiments. [Figure 23] FIG. 23 illustrates a block diagram of a computing system showing some elements included in the host, storage controller and storage device described in FIGS. 1-22 according to some embodiments. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0017] In the following description, reference is made to the accompanying drawings which form a part hereof, and which illustrate several embodiments, It is to be understood that other embodiments may be utilized and structural and operational changes may be made.

[0018] The standard for encrypting Fibre Channel links (FC-SP-2) includes a protocol for mutual authentication of two endpoints (i.e., ports) and for negotiation of an encryption key to be used in a communications session between those two endpoints. The standard provides support for a variety of mechanisms for authenticating the parties involved and by which keying material is provided or developed.

[0019] In the FC-SP-2 standard, support for authentication within an endpoint is indicated by the setting of the security bit in the common service parameters sent to the peer during a login session. When set to a value of 1 in a login request, the security bit indicates that the sending port can perform authentication. If the responding port sets the security bit to 1 in the reply when it accepts a login request, this indicates that the responding port requires that authentication be performed at this time before granting any further access to the sender of the login.

[0020] The FC-SP-2 standard specifies the behavior of the responding endpoint by accepting or rejecting the login request and setting the security bit based on the security policy in effect at that endpoint at the time the request is received. The standard has no specification as to how this policy is instantiated at the responding endpoint. In an enterprise data center, care must be taken to protect access to data and to provide security for that data. When enabling security in a heterogeneous environment that includes some systems and storage ports that do not support security (e.g., legacy ports), some embodiments provide mechanisms to ensure that connectivity is not lost, in contrast to current standards that do not allow such mechanisms to be provided.

[0021] Some embodiments provide a mechanism for enabling security at the host as an "audit mode" where the host does not lose access to data when security is enabled at the storage device. An indication is provided via the setting of an audit mode indicator at the time of login that allows the host port to continue to access the storage port after security is enabled. Once authentication and security enablement have been successfully completed, security enablement can be changed to a policy of security enforcement. Security enablement means that I / O can be performed even if authentication and security enablement have not been successfully completed, whereas security enforcement means that I / O cannot be performed if authentication and security enablement have not been successfully completed. While in audit mode, the host can provide tools to continue to access the storage device and audit the security state of the connection.

[0022] Some embodiments provide a mechanism for a host to determine that it is unable to successfully complete authentication and / or security association with a storage device and to check whether security is not being enforced on the storage port using an audit mode indicator. If the audit mode indicator is set, the host processor continues to send I / O operations to the storage device along the selected port. If the audit mode indicator is not set, the host processor stops the I / O operations to the storage device and notifies the host application or operating system to find an alternate path to complete the I / O operations.

[0023] Additionally, with Fibre Channel, many host ports can log into a single storage port (as described in FC-FS-5). Of these host ports, some may support security and some may not. If the port setting is set to security enforcement, the host ports that do not support security can lose access to the storage port because they are not allowed to log in.

[0024] In some embodiments, information is provided by the storage device to indicate the current number of logins to each of its ports. For the number of logins, the storage device provides the number of security capable logins and the number of logins that have been successfully authenticated and security enabled. From this information, it can be determined whether access to the port may be lost if the configuration of the storage port is changed to security-enforced. Once all logins are determined to be secure, the configuration is changed without loss of access because all host ports can successfully enable security. In some embodiments, when it is desired to change the configuration to security-enforced, the storage device checks the login counter to determine whether a loss of access may occur (i.e., whether there are logins that are not successfully authenticated) and prevents the configuration from being changed to security-enforced.

[0025] Some embodiments provide a storage port that supports setting to enable security without enforcement and provides auditable statistics (e.g., login count, security capable login count, and security enabled login count) to determine the effects of setting security to enforcement. An audit mode indicator is set in the login response to the host port to indicate that I / O can be sent to this storage port even if authentication cannot be successfully completed. Setting for security enabled or enforced can be performed at the storage array or on an individual storage port basis.

[0026] In some embodiments, a setting is provided for security enforcement with automated checking of login indicators to prevent setting changes where loss of access may occur. An option is also provided to force a change to security enforcement without considering the login indicators.

[0027] As a result, the evolution towards Fibre Channel-based connectivity will require improvements to devices to maintain connectivity in order to perform I / O.

[0028] The above described embodiment enables security at the host in an audit mode where the host does not lose access to data when security is enabled at the storage device. An indication is provided at the time of login that the host port is allowed to continue accessing the storage port after security is enabled. Access without a security association that enables encryption means that the host port and storage port may exchange data in the clear, where exchanging data in the clear means that the data exchanged is not encrypted, and data exchanged in the clear is referred to as "plaintext" data.

[0029] Upon successful creation of a security association that enables encryption, the host port and storage port must be able to transition from exchanging cleartext data to exchanging "encrypted" data, where encrypted data refers to data that is encrypted. There is a transitional period during which both cleartext and encrypted data are flowing on the link between the host port and storage port, and in some embodiments, the security enforcement rules put in place by the security association ensure that such conditions do not result in error detection.

[0030] Some embodiments provide a mechanism for a host system to transition from clear text exchanges to encrypted data exchanges. Such embodiments also provide a mechanism for a storage port to transition from clear text exchanges to encrypted data exchanges. As a result, as an enhancement to a Fibre Channel based connection environment, further improvements are made to devices that maintain connections to perform I / O.

[0031] Exemplary embodiments for implementing audit mode 1 illustrates a block diagram 100 of a heterogeneous computing environment that includes multiple hosts 102, 104 that communicate with multiple storage controllers and / or storage devices 108, 110 via a Fibre Channel fabric 106 according to some embodiments. Both the storage controllers and storage devices are indicated by reference numerals 108, 110, and the hosts 102, 104 may communicate with a storage controller that controls the storage devices or may communicate with the storage devices without involving any storage controller. A storage controller may also be considered an advanced type of storage device because it controls and allows access to one or more storage devices.

[0032] The hosts 102, 104 and storage controllers 108, 110 may include any suitable computing device, including personal computers, workstations, servers, mainframes, hand-held computers, palmtop computers, telephony devices, network appliances, blade computers, processing devices, controllers, etc. The storage devices may include hard disk drives, tape drives, solid state drives, etc., storage devices currently known in the art.

[0033] The hosts 102, 104 and the storage devices 108, 110 may be elements of any suitable network, such as a storage area network, a wide area network, the Internet, an intranet, etc. In some embodiments, the hosts 102, 104 and the storage devices 108, 110 may be elements of a cloud computing environment. The connection between the hosts 102, 104 and the storage devices 108, 110 in the network and / or cloud computing environment may be via a Fibre Channel fabric 106.

[0034] A host may include one or more host ports. For example, host 102 includes multiple host ports 112 and host 104 includes multiple host ports 114. A storage device may include multiple storage ports. For example, storage device 108 includes multiple storage ports 116 and storage device 110 includes multiple storage ports 118. The host ports 112, 114 and the storage ports 116, 118 may communicate over the Fibre Channel fabric 106.

[0035] In some embodiments, not all hosts support security for host ports. For example, some legacy hosts may not support security for Fibre Channel host ports, or some legacy adapters in hosts may not support security for Fibre Channel host ports. For example, host 102 is shown as supporting security for host ports and host 104 is shown as not supporting security for host ports.

[0036] In some embodiments, some storage devices may allow one or more storage ports to be configured as security-enabled with enforcement (i.e., I / O cannot occur from the host port to the storage port unless a secure connection is established between the host port and the storage port). In some embodiments, some storage devices may allow one or more storage ports to be configured as security-enabled without enforcement (i.e., I / O can occur from the host port to the storage port even if a secure connection is not established between the host port and the storage port). For example, storage device 108 may have at least one of storage ports 116 enabled with security with enforcement (other storage ports in storage device 108 may have security enabled without enforcement). In FIG. 1, storage device 110 may have at least one of storage ports 118 enabled with security without enforcement (other storage ports in storage device 110 may have security enabled with enforcement).

[0037] Thus, FIG. 1 illustrates some embodiments that allow I / O operations to be sent from a host port to a storage port even when it is not possible to successfully complete an authentication or security association negotiation between the host port and the storage port.

[0038] FIG. 2 illustrates a block diagram 200 of a system for maintaining access to a host 202 for security enablement in a heterogeneous computing environment according to some embodiments.

[0039] A host 202 is communicatively coupled to multiple storage devices 204, 206 via a Fibre Channel fabric 208. Storage device 204 has storage port 210 of storage device 204 enabled with security enforcement, and storage device 206 has storage port 212 of storage device 206 enabled with security without enforcement. In some embodiments, a storage port can be changed from security enabled without enforcement to security enabled with enforcement, or vice versa.

[0040] Host 202 includes host port 214, which communicates with storage ports 210, 212. In the embodiment shown in FIG. 2, host port 214 can send I / O to storage port 212 even if it is unable to successfully complete authentication or security association negotiation between host port 214 and storage port 212 because storage port 212 has security enabled without enforcement. However, host port 214 cannot send I / O to storage port 210 if it is unable to successfully complete authentication or security association negotiation between host port 214 and storage port 210 because storage port 210 has security enabled with enforcement.

[0041] If the host port 214 is unable to send the I / O operation to the storage port, the operating system 216 of the host 202 attempts to send the I / O operation through another mechanism.

[0042] 3 illustrates a block diagram 300 showing security bits 302 for login in current Fibre Channel standards and enforcement to Fibre Channel via an audit mode indicator 304, according to some embodiments. The audit mode indicator 304 can be enabled (reference numeral 306) or not enabled (reference numeral 308).

[0043] It should be noted that audit mode indicator 304 is not found in existing Fibre Channel standards. Enabling audit mode indicator 304 allows for the enabling of security without enforcement, working in concert with the configuration of security bit 302.

[0044] In some embodiments, the audit mode indicator 304 is enabled via an indication in auxiliary parameters data word 0, bit 23 in a program implementing Fibre Channel Link Service (FC-LS-4). In other embodiments, other mechanisms for implementing the audit mode indicator 304 may be provided. The audit mode indicator 304 and security bit 302 may be part of one or more data structures used to perform the operations.

[0045] 4 illustrates a block diagram 400 showing a login and response in Fibre Channel, according to some embodiments. A host port 402 sends a login request 404 to a storage port 406. The host port 402 is also referred to as the "sending port" and the storage port 406 is also referred to as the "receiving port."

[0046] In a login request 404 from host port 402, the security bit 302 is set to 1 to indicate that the sending port (i.e., host port 402) is capable of performing authentication.

[0047] Upon receiving login request 404, storage port 406 sends a response 408 to host port 402. The response 408 from storage port 406 may set security bit 302 to 1 to indicate that the receiving port (i.e., storage port 406) requires that authentication be performed now before granting any further access to the sending port (i.e., host port 402).

[0048] In some embodiments, even if security bit 302 is set to 1 in the response, if audit mode indicator 304 is enabled (set) to indicate security enabled without enforcement, the requirement to complete authentication before granting any further access is disabled.

[0049] FIG. 5 illustrates a block diagram 500 showing enhancements to Fibre Channel that provide indications for “security enforcement” and “security enablement” via enabling or disabling of audit mode indicator 304, according to some embodiments.

[0050] The indication is provided by a receiving port (e.g., a storage port in a storage device) in response to a login request from a host port (as shown by reference numeral 502). The indication may be provided via the setting of the audit mode indicator 304. Setting the audit mode indicator 304 as enabled may result in a storage port state of "security enabled" 504, meaning that security is enabled without enforcement. Setting the audit mode indicator 304 as not enabled may result in a storage port state of "security enforcement" 506, meaning that security is enabled with enforcement.

[0051] FIG. 6 illustrates a flow chart 600 showing the operation of a security-enforced storage port, according to some embodiments. Control passes to block 604, where authentication and management of security associations is initiated between the host port and the storage port. Control passes to block 606, where a determination is made as to whether the authentication and management of security associations is successfully completed between the host port and the storage port. If it is completed ("yes" branch 608), control passes to block 610, where the host port is allowed to begin performing I / O through the storage port (at block 610). If it is not completed ("no" branch 612), control passes to block 614, where the host port is prevented from performing I / O through the storage port.

[0052] FIG. 7 illustrates a flow chart 700 showing operation of a security-enabled storage port according to some embodiments.

[0053] Control begins at block 702, where security is enabled for the storage port. Control proceeds to block 704, where authentication and security association management between the host port and the storage port is initiated. The host port is allowed to perform I / O through the storage port (block 706), regardless of whether the authentication and security association management operations have or have not completed successfully (at block 708). The time at which I / O is allowed to begin may vary in different embodiments.

[0054] FIG. 8 illustrates a block diagram 800 showing conditions that prevent successful completion of authentication and management of security associations, according to some embodiments.

[0055] The first condition 802 is an incomplete configuration of the security policy that may prevent successful completion of the authentication and security association management. The second condition 804 includes an inaccessible key server that provides credentials to access the storage device that may prevent successful completion of the authentication and security association management. The third condition 806 is a failure of the authentication and security association management exchange that may prevent successful completion of the authentication and security association management. All of these conditions may prevent successful completion of the authentication and security association management in the operations shown in Figures 6 and 7.

[0056] 9 illustrates a block diagram 900 showing multiple host ports 902, 904, 906 logging into a single storage port 908 according to some embodiments. The single storage port 908 is contained within a storage device or storage controller 910, which may have other storage ports.

[0057] In FIG. 9, host ports 902 and 906 support security, while host port 904 does not support security, possibly because it is contained in a legacy adapter or host, or for other reasons including configuration by an administrator.

[0058] The storage device or storage controller 910 maintains statistics (reference number 912) regarding login characteristics referred to as login counters and login indicators. The statistics include the number of current logins to the storage port (reference number 914), the number of security-enabled logins to the storage port (reference number 916), and the number of security-enabled logins to the storage port (reference number 918). A security-enabled login is one that has been successfully authenticated and has security enabled.

[0059] In some embodiments, the statistics regarding login counters and login characteristics 912 are used by the storage device or storage controller 910 to determine the effect on I / O access by the host when the security enforcement mode is set. In additional embodiments, the statistics regarding login counters and login characteristics 912 are used by the storage device or storage controller to prevent switching from a security enabled mode to a security enforcement mode if switching to the security enforcement mode would result in a loss of I / O access by the host.

[0060] In a further embodiment, the storage device or storage controller 910 provides an option 920 to force a switch to a security enforcement mode without considering statistics 912 regarding login counters and login characteristics.

[0061] FIG. 10 illustrates a flowchart 1000 showing operations in a storage device to determine whether a storage port should be changed to a security enforcing state according to some embodiments.

[0062] Control begins at block 1002 where the storage device determines that multiple host ports have performed logins to a storage port of the storage device. Control proceeds to block 1004 where the storage device maintains statistics regarding login counters and login characteristics. The storage device determines (at block 1006) from the login counters and login characteristics whether any host ports would lose I / O access to the storage device if the storage port configuration were changed to security-enforced. If so ("yes" branch 1008), then not all host port logins are secure (i.e., not all host ports will be successfully authenticated), and control proceeds to block 1010 where the storage port configuration is prevented from being changed to security-enforced.

[0063] If, in block 1006, the storage device determines from the login counter and login characteristics that none of the host ports will lose I / O access to the storage device if the storage port settings are changed to security enforced ("No" branch 1012), then all host port logins are secure (i.e., all host ports are successfully authenticated) and control proceeds to block 1014, where the storage port settings are allowed to be changed to security enforced.

[0064] FIG. 11 illustrates a flowchart 1100 showing operations for maintaining access for security enablement in a host system according to some embodiments.

[0065] Control begins at block 1102 where a host port is enabled for security. The host port determines (at block 1104) that it is unable to successfully complete an authentication or security association negotiation with the storage port.

[0066] In response to the host port determining that it is unable to successfully complete an authentication or security association negotiation with the storage port, the host port determines whether an audit mode indicator is enabled in the login response from the storage port (at block 1106). The host port reserves input / output (I / O) access to the storage port based on determining whether the audit mode indicator is enabled in the login response from the storage port. As a result, the host port may be able to perform I / O through the storage port even if it is unable to successfully complete an authentication or security association negotiation with the storage port.

[0067] In response to determining that the audit mode indicator is enabled in the login response from the storage port ("yes" branch 1108), the host port performs I / O to the storage port (at block 1110). Performing I / O to the storage port means sending an I / O operation to the storage port to perform an I / O operation in which data is read, written, or accessed. As a result, the host port performs I / O through the storage port even if it is unable to successfully complete authentication or security association negotiation with the storage port when the audit mode indicator is enabled.

[0068] In response to determining that the audit mode indicator is not enabled in the login response from the storage port ("no" branch 1112), the host port avoids performing I / O to the storage port (at block 1114). Consequently, if it is not possible to successfully complete an authentication or security association negotiation with the storage port and the audit mode indicator is not enabled, the host port will not perform I / O through the storage port. From block 1114, control passes to block 1116, where the host port returns the I / O request to the operating system of the host computing device. Consequently, if it is not possible to successfully complete an authentication or security association negotiation with the storage port and the audit mode indicator is not enabled, an alternative mechanism is attempted to perform I / O.

[0069] FIG. 12 illustrates a flowchart 1200 showing additional operations for maintaining access for security enablement in a host system according to some embodiments.

[0070] If the host port cannot contact the key server to obtain a certificate to authenticate with the storage port, the host port determines (at block 1202) that it is unable to successfully complete authentication or security association negotiation with the storage port. As a result, the host port may take further action to determine the state of the audit mode indicator to determine whether an I / O request should be sent to the storage port.

[0071] From block 1202, control passes to block 1204, which depicts the host port determining that it is unable to successfully complete authentication or security association negotiation with the storage port if there is a failure in the process for authentication or security association negotiation with the storage port. As a result, the host port may take further action to determine the state of the audit mode indicator to determine whether an I / O request should be sent to the storage port.

[0072] FIG. 13 illustrates a flowchart 1300 showing operations for maintaining access for security enablement in a storage device according to some embodiments.

[0073] Control begins at block 1302, where a storage port receives a login request. From block 1302, control may proceed to block 1304 or block 1306.

[0074] In block 1304, the storage port sets an audit mode indicator to an enabled state in the login response to the host port to enter a security enabled mode to instruct the host port that input / output (I / O) operations should be sent from the host port to the storage port even if it is unable to successfully complete authentication or security association negotiation with the storage device. As a result, an insecure host may perform I / O to the storage device.

[0075] In block 1306, the storage port sets the audit mode indicator to a non-enabled state in the login response to the host port to enter security enforcement mode to instruct the host port that I / O operations should not be sent from the host port to the storage port if it is unable to successfully complete authentication or security association negotiation with the storage device. As a result, an insecure host cannot perform I / O to the storage device.

[0076] FIG. 14 illustrates a flowchart 1400 showing additional operations for maintaining access for security enablement in a storage device.

[0077] Control begins at block 1402 where a storage controller including a storage port maintains statistics regarding login counters and login characteristics, including the current number of logins to the storage port, the number of security-enabled logins to the storage port, and the number of security-enabled logins to the storage port. Accordingly, in some embodiments, the statistics regarding the login counters and login characteristics are used by the storage controller to determine the effect on I / O access by a host when a security enforcement mode is set.

[0078] In a further embodiment, the login counters and statistics regarding login characteristics are used by the storage controller to prevent a switch from the security enabled mode to the security enforcing mode if a switch to the security enforcing mode would result in a loss of I / O access by the host (at block 1404). As a result, a switch to the security enforcing mode is prevented if the host would lose I / O access.

[0079] In some embodiments, the storage controller provides an option to force a switch to security-enabled mode without considering statistics regarding login counters and login characteristics.

[0080] In some embodiments, the storage controller sets at least one storage port of the plurality of storage ports to a security enforcing mode, and the storage controller sets at least one other storage port of the plurality of storage ports to a security enabling mode, such that enabling of the audit mode indicator is on a per port basis.

[0081] In a further embodiment, the storage port is included in a storage controller including a first storage array and a second storage array, where the security enforcement mode is set for the first storage array and the security enablement mode is set for the second storage array, and thus enabling of the audit mode indicator is done on a per storage array basis.

[0082] 1-14 thus illustrate some embodiments that enforce or do not enforce security based on the setting of the audit mode indicator to augment operation based on the setting of the security bit in the Fibre Channel. As a result, legacy devices can continue to perform I / O in a heterogeneous computing environment even when the security bit is enabled in the Fibre Channel.

[0083] Exemplary embodiments for transitioning from plaintext to encrypted data In Fibre Channel, a security association (SA) is established between an SA initiator and an SA responder using an SA establishment protocol to enable encryption on the link. An example of an SA initiator is a Fibre Channel initiator (e.g., host ports 112, 114) in a host bus adapter (HBA) of a host computing device 102, 104. An example of an SA responder is a Fibre Channel target port (e.g., storage ports 116, 118) in a storage controller 108, 110. In Fibre Channel, separate security associations are established for sending and receiving data on a port.

[0084] An SA establishment protocol consists of a series of messages sent between two entities (such as a host port and a storage port in a Fibre Channel SAN). One example of such a protocol is the Security Association Management Protocol in the Fibre Channel Security Protocol standard FC-SP-2.

[0085] The protocol includes 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 establish security associations that perform authentication of entities and protect data transferred between them.

[0086] A first set of security associations (SA1) is established the first time the SA establishment protocol is run on a path (e.g., Fibre Channel N_Port login). The set of security associations includes send keying material (K1t) and receive keying material (K1r). The keying material consists of both a key and a SALT (a SALT is random data used as an additional input to a one-way function that "hashes" data used in the encryption mechanism), but will be referred to simply as a key throughout this disclosure. Note that each side has a set of "send keying material" (K1t) that is equivalent to the other's "receive keying material" (K1r).

[0087] At certain points in the protocol, a port is programmed to begin allowing data to be received using K1r and transmitting data using K1t. In some embodiments, the selection of these points in the protocol is such that the receive key K1r is programmed before the other port in the security association can begin transmitting data using that key.

[0088] Programming the new key into the port for receiving data occurs after confirmation of the SA_Auth message. In the case of a target (e.g., a storage port), this is after processing the SA_Auth Request message. In the case of an initiator (e.g., a host port), this is upon receipt of the SA_Auth Response. After the authentication transaction is successfully completed, the queue of I / O requests to send data starts using the new SA1. In the case of a target, this can only be done after the SA_Auth Response is received by the initiator. Receipt of the SA_Auth Response at the initiator is confirmed when the target receives the LS_ACC Extended Link Service (ELS) response. In the case of an initiator, this occurs upon receipt of Auth_Done.

[0089] After the SA establishment operation is complete, both the initiator and target ports begin queuing I / O for transmission using the new transmit key. However, in some embodiments, there may still be I / O in the queue or in the SAN that was queued for transmission prior to SA establishment using cleartext I / O. To avoid errors in reception, these ports continue to tolerate cleartext reception for some period of time before SA1 encryption is forced. This period of time is provided by a timer called the "cleartext grace period timer." This timer is set to expire after a predefined period of time (e.g., 2 seconds).

[0090] When transitioning from plaintext to encryption, in some embodiments, a "plaintext tolerant indicator" is enabled and provided to the data receiver during programming of the security association for receiving the data, which instructs the data receiver (or firmware controlling the data receiver) to tolerate a mix of encrypted and unencrypted data frames.

[0091] At some point, once it has been determined that all plaintext I / O has been cleared from the system, the data receiver is reprogrammed to reset the plaintext acceptance indicator. At this point, the data receiver will accept encrypted data and will not accept plaintext data. This can be accomplished by waiting for a timer to expire from the time the SA1 security keying material is activated for data transmission.

[0092] FIG. 15 illustrates a block diagram 1500 showing the transition from clear text I / O to encrypted I / O after authentication and security association have been successfully completed in an embodiment where audit mode is enabled, according to some embodiments.

[0093] 15, an arrow 1502 indicates the passage of time during the execution of I / O on a path between a host port and a storage port. In other words, time progresses in the direction that the arrow is pointing.

[0094] Initially, clear I / O (i.e., unencrypted I / O) 1504 is sent on the established path between the host port and the storage port. Once authentication and security association are successfully completed (reference number 1506), encrypted I / O 1506 is executed. However, there are overlapping periods (indicated by reference number 1508) during which both clear I / O and encrypted I / O are executed simultaneously (i.e., interspersed with clear I / O). In some embodiments, clear I / O is allowed to continue for a predetermined period of time to complete I / O that was queued but not sent before authentication and security association were successfully completed.

[0095] FIG. 16 illustrates a block diagram 1600 showing data structures for allowing a grace period during which cleartext I / O continues when encrypted I / O begins on a path, according to some embodiments.

[0096] In addition to the security bit 302 and audit mode indicator 304 described in FIG. 3, a plaintext allowed indicator 1602 and a plaintext grace period timer 1604 are provided. The plaintext allowed indicator 1602, when enabled (e.g., by being set to a value of 1), allows encrypted and plaintext data to be interspersed on the path even after authentication and security association have been successfully completed. The plaintext grace period timer 1604 indicates the period of time (e.g., 2 seconds) that plaintext data is allowed on the path after encrypted data is allowed on the path. This period of time is sufficient to flush any plaintext data that was already queued when encrypted I / O began on the path.

[0097] FIG. 17 illustrates a block diagram 1700 showing the initiation of cleartext I / O on a path, according to some embodiments.

[0098] An SA_Initiator (designated by reference numeral 1702), such as a host port, sends a port login (PLOGI 1704) to an SA_Responder (designated by reference numeral 1706), such as a storage port. Upon receiving PLOGI 1704, the storage port 1706 sends a link service accept message (LS_ACC 1708) to the host port 1702, which is received by the host port 1702. The host port 1702 may be included in a host, and the storage port 1706 may be included in a storage controller.

[0099] A process login (PRLI 1710) is then sent from host port 1702 to storage port 1706. Storage port 1706 receives PRLI 1710 and sends a link service accept message (LS_ACC 1712) to host port 1702, which receives LS_ACC 1712. Cleartext I / O begins on the path between host port 1702 and storage port 1706 at a point indicated by reference numeral 1714. Reference numeral 1716 indicates the cleartext I / O being performed on the path.

[0100] 18 illustrates a block diagram 1800 showing an embodiment of operations for a flow from "clear text I / O" to "mixed clear text I / O and encrypted I / O" to "encrypted I / O" occurring between a host port 1702 and a storage port 1706. In one embodiment, the host port 1702 acts as an initiator and the storage port 1706 acts as a responder. It is understood that audit mode is enabled.

[0101] To initiate the operation of establishing a security association, the host port 1702 sends a security association initialization message (SA_Init 1804) from the host port 1702 to the storage port 1706 to establish a security association with the storage port 1706 that includes keying material used to create an encryption key. Upon receiving the security association initialization message, the storage port 1706 sends an acceptance of the security association initialization message to the host port 1702 for processing. In a Fibre Channel protocol implementation, the "acceptance" for processing the message may take the form of a link service accept message (LS_ACC 1806). After the acceptance is sent, the storage port 1706 sends an initialization response message (SA_Init Resp 1808) to the host port 1702 to accept the security association, including the selected transform used for encryption / decryption. The security association initialization message may include a number of different encryption transformation methods from which the storage port 1706 may select for use in the security association being established.

[0102] Upon receiving the sent initialization response message (SA_Init Resp 1808), the host port 1702 sends an acceptance (LS_ACC 1810) to the storage port 1706 that the initialization response message has been accepted for processing, and then sends an authentication message (SA_Auth 1812) to the storage port 1706 to request the storage port 1706 to establish authentication between the storage port 1706 and the host port 1702.

[0103] Upon receiving the security association authentication message (SA_Auth 1812), the storage port 1706 sends an acceptance message (LS_ACC 1814) to the host port 1702 indicating that the authentication message has been accepted for processing, and then programs the receiving security association SA1 (as shown by reference numeral 1816) with key K1r whose plaintext acceptance indicator is set to 1.

[0104] After programming the storage port 1706 with the security association SA1 for the storage port 1706, the storage port 1706 sends an authentication response message (SA_Auth Resp 1818) to the host port 1702 to accept the authentication.

[0105] Upon receiving the security association authentication response message, host port 1702 programs (as shown by reference numeral 1820) a receiving security association SA1 that includes key K1r with the plaintext acceptance indicator set to 1. After programming security association SA1, host port 1702 sends an acceptance (LS_ACC 1822) to storage port 1706 that the authentication message has been accepted for processing.

[0106] Upon receiving acceptance 1822, storage port 1706 activates security association SA1 for transmission (as indicated by reference numeral 1824) using key K1t and starts timer 1826 to indicate the start of transmission of encrypted data from storage port 1706 to host port 1702. Storage port 1706 begins transmitting encrypted data at this point and timer 1826 begins counting down from a predetermined value. Timer 1826 is an instantiation of plaintext grace period timer 1604 shown in FIG.

[0107] After activating security association SA1, storage port 1706 sends an authentication completion message (AUTH Done 1828) to host port 1702 indicating that both security association initialization and authentication are complete and that transmissions can now be encrypted and decrypted for the newly established security association SA1.

[0108] Upon receiving the authentication done message, host port 1702 activates the created security association SA1 for transmission using key K1t (as shown by reference numeral 1830). After activating security association SA1, host port 1702 sends an acceptance (LS_ACC 1832) to storage port 1706 that security association SA1 is activated, begins sending encrypted I / O to the storage port, and starts timer 1834 to count down from a predetermined value. Timer 1834 is an example of plaintext grace period timer 1604 shown in FIG. 16, and in some embodiments, the predetermined values ​​for timer 1834 and timer 1836 may be the same.

[0109] In Figure 18, from the point at which timer 1826 begins counting down, while encrypted data is being sent from storage port 1706, queued plaintext data is also being sent from host port 1702. In Figure 18, from the point at which timer 1834 begins counting down, while encrypted data is being sent from host port 1702, queued plaintext data is also being sent from host port 1702.

[0110] Once timer 1826 expires (i.e., the predetermined time period expires), cleartext I / O is no longer supported by storage port 1706 (as shown by reference numeral 1836). Once timer 1834 expires (i.e., the predetermined time period expires), cleartext I / O is no longer supported by host port 1702 (as shown by reference numeral 1838). In such a state, the cleartext tolerance indicator is set to 0.

[0111] The predetermined time period for the timers 1826, 1834 to expire is set long enough so that all pending plaintext I / O in the queue is cleared at time 1840 and there is a transition from “mixed plaintext and SA1 encrypted I / O” 1842 to “SA1 encrypted” I / O 1844.

[0112] Thus, Figure 18 shows the transition from cleartext I / O 1716 to mixed cleartext and encrypted I / O 1842 to encrypted I / O 1844 over the path between host port 1702 and storage port 1706. This allows all pending cleartext I / O to be cleared from the queue after authentication and security associations are successfully established. The hatching and cross-hatching in Figure 18 indicate time periods corresponding to different types of data transmissions.

[0113] FIG. 19 illustrates a flowchart showing operations for simultaneous enablement of encryption on operational paths at a host port, according to some embodiments.

[0114] Control begins at block 1902 where a host port is enabled for security. In response to determining that the audit mode indicator is enabled to allow input / output (I / O) even if an authentication or security association negotiation between the host port and the storage port cannot be successfully completed, the host port performs (at block 1904) cleartext I / O on a path between the host port and the storage port.

[0115] From block 1904, control proceeds to block 1906, where the host port enables data encryption for I / O on the path simultaneously with performing I / O in clear on the path, and in some embodiments, this simultaneous enabling of data encryption includes initiating a security association (SA) management transaction between the host port and the storage port.

[0116] From block 1906, control passes to block 1908 where, in response to the host port determining that all plaintext reception is complete due to a timer expiration after the security association is activated for transmission, the host port is programmed to no longer process plaintext data. It should be noted that the timer expires after a timeout period sufficient to flush any plaintext data that was queued for transmission on the path at the time that encrypted data transmission began on the path.

[0117] In the context of implementing the embodiment shown in FIG. 19, the host port is programmed with keying material for the exchange of encrypted data along with a plaintext tolerance indicator configured to tolerate the exchange of plaintext data on the path simultaneously with the exchange of encrypted data on the path.

[0118] In response to the plaintext tolerance indicator being configured to tolerate exchanging plaintext data on the path simultaneously with exchanging encrypted data on the path, the host port is configured to receive both plaintext and encrypted data using the keying material, and further, when both plaintext and encrypted data are exchanged on the path during a predetermined period of time indicated by the timer, no I / O errors are generated.

[0119] FIG. 20 illustrates a flowchart 2000 showing operations for simultaneous enabling of encryption on operational paths at a storage port, according to some embodiments.

[0120] Control begins at block 2002 where a storage port is enabled for security. In response to determining that an audit mode indicator is enabled to permit input / output (I / O) even when an authentication or security association negotiation between the storage port and the host port cannot be successfully completed, the storage port performs (at block 2004) cleartext I / O on a path between the storage port and the host port.

[0121] From block 2004, control proceeds to block 2006, where the storage port enables data encryption for I / O on the path simultaneously with performing I / O in clear on the path, and in some embodiments, this simultaneous enabling of data encryption includes initiating a security association (SA) management transaction between the storage port and the host port.

[0122] From block 2006, control passes to block 2008 where, in response to the storage port determining that all plaintext reception has been completed due to a timer expiring after the security association was activated for transmission, the storage port is programmed to no longer process plaintext data. It should be noted that the timer expires after a timeout period sufficient to flush any plaintext data that was queued for transmission on the path at the time that transmission of encrypted data began on the path.

[0123] In the context of performing the embodiment shown in Figure 20, the storage port is programmed with keying material for the exchange of encrypted data along with a plaintext tolerance indicator configured to permit the exchange of plaintext data on the path simultaneously with the exchange of encrypted data on the path. In response to the plaintext tolerance indicator being configured to permit the exchange of plaintext data on the path simultaneously with the exchange of encrypted data on the path, the storage port is configured to receive both plaintext and encrypted data using the keying material. Further, when both plaintext and encrypted data are exchanged on the path for a predetermined period of time indicated by a timer, no I / O errors are generated.

[0124] 1-20 thus provide a mechanism for a host system to transition from exchanging plaintext to exchanging encrypted data by allowing a period of time during which a mix of plaintext and encrypted data is exchanged in embodiments in which the audit mode indicator is enabled. Such embodiments also provide a mechanism for a storage port to transition from exchanging plaintext to exchanging encrypted data by allowing a period of time during which a mix of plaintext and encrypted data is exchanged in embodiments in which the audit mode indicator is enabled.

[0125] Cloud Computing Environment Cloud computing is a model for enabling convenient, on-demand network access to a shared pool of configurable computing resources (e.g., networks, servers, storage, applications, and services) that can be rapidly provisioned and released with minimal management effort or interaction with a service provider.

[0126] 21, an exemplary cloud computing environment 50 is shown. Security enforcement or enablement and transition to encryption (as indicated by reference numeral 52) is performed in the cloud computing environment 50. As shown, the cloud computing environment 50 includes one or more cloud computing nodes 10 with which the local computing devices used by the cloud consumers, such as, for example, a personal digital assistant (PDA) or cellular phone 54A, a desktop computer 54B, a laptop computer 54C, or an automobile computer system 54N, or combinations thereof, may communicate. The nodes 10 may also communicate with each other. The nodes may be grouped, physically or virtually, in one or more networks, such as a private, community, public, or hybrid cloud, or combinations thereof, as described herein above (not shown). This enables the cloud computing environment 50 to provide infrastructure, platform, or software, or combinations thereof, as a service, without the cloud consumers having to maintain resources on the local computing devices. It should be understood that the types of computing devices 54A-N shown in FIG. 21 are intended to be exemplary only, and that the computing nodes 10 and cloud computing environment 50 can communicate with any type of computerized device via any type of network and / or addressable network connections (e.g., using a web browser).

[0127] Referring now to Figure 22, there is shown a set of functional abstraction layers provided by cloud computing environment 50 (Figure 21). It should be understood that the components, layers, and functions shown in Figure 22 are intended to be merely exemplary, and that embodiments of the present invention are not limited thereto.

[0128] The hardware and software layer 60 includes hardware components and software components. Examples of hardware components include mainframes, such as IBM's ZSERIES* systems, RISC (reduced instruction set computer) architecture based servers, such as IBM's PSERIES* systems, IBM's XSERIES* systems, IBM's BLADECENTER* systems, storage devices, networks, and networking components. Examples of software components include network application server software, such as IBM's WEBSPHERE* application server software, and database software, such as IBM's DB2* database software.

[0129] The virtualization layer 62 provides an abstraction layer from which examples of virtual entities may be provided, such as virtual servers, virtual storage, virtual networks including virtual private networks, virtual applications and operating systems, and virtual clients.

[0130] In one example, the management layer 64 may provide the functions described below: Resource provisioning provides dynamic procurement of computing and other resources used to execute tasks within the cloud computing environment. Metering and pricing provides cost tracking as resources are utilized within the cloud computing environment and charging or billing for the consumption of these resources. In one example, these resources may include application software licenses. Security provides identity verification for cloud consumers and tasks, as well as protection for data and other resources. A user portal provides access to the cloud computing environment for consumers and system administrators. Service level management provides allocation and management of cloud computing resources such that required service levels are achieved. Service level agreement (SLA) planning and fulfillment provides proactive coordination and procurement of anticipated future needs for cloud computing resources according to SLAs.

[0131] The Workloads layer 66 provides examples of functions for which cloud computing environments are utilized. Examples of workloads and functions provided from this layer include mapping and navigation, software development and lifecycle management, virtual classroom instructional delivery, data analytics processing, transaction processing, and security enforcement or enablement and migration to encryption 68 as shown in Figures 1-21.

[0132] Additional embodiment details The described operations may be implemented as a method, apparatus, or computer program product using standard programming and / or engineering techniques to effect software, firmware, hardware, or any combination thereof. Accordingly, aspects of the embodiments may take the form of entirely hardware embodiments, entirely software embodiments (including firmware, resident software, microcode, etc.), or embodiments combining software and hardware aspects, all generally referred to herein as "circuits," "modules," or "systems." Additionally, aspects of the embodiments may take the form of a computer program product. The computer program product may include one or more computer-readable storage media having computer-readable program instructions for causing a processor to perform aspects of the embodiments of the present invention.

[0133] A computer readable storage medium may be a tangible device capable of holding and storing instructions for use by an instruction execution device. A computer readable storage medium may be, for example, but 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 above. A non-exhaustive list of more specific examples of computer readable storage media includes the following: portable computer diskettes, hard disks, random access memories (RAM), read-only memories (ROM), erasable programmable read-only memories (EPROM or flash memory), static random access memories (SRAM), portable compact disk read-only memories (CD-ROM), digital versatile disks (DVD), memory sticks, floppy disks, mechanically encoded devices such as punch cards or ridge structures in grooves on which instructions are recorded, and any suitable combination of the above. As used herein, a computer-readable storage medium should not be construed as a transitory signal per se, such as a radio wave or other freely propagating electromagnetic wave, an electromagnetic wave propagating through a waveguide or other transmission medium (e.g., light pulses passing through a fiber optic cable), or an electrical signal transmitted through wires.

[0134] The computer readable program instructions described herein may be downloaded from a computer readable storage medium into each computing / processing device or may be downloaded to an external computer or storage device via a network, such as the Internet, a local area network, a wide area network, or a wireless network, or a combination thereof. The network may include copper transmission cables, optical transmission fiber, wireless transmission, routers, firewalls, switches, gateway computers, or edge servers, or a combination thereof. A network adapter card or network interface in each computing / processing device receives the computer readable program instructions from the network and transfers the computer readable program instructions to a computer readable storage medium within the respective computing / processing device for storage.

[0135] The computer readable program instructions for carrying out the operations of the embodiments 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 source or object code written in any combination of one or more programming languages, including object oriented programming languages ​​such as Smalltalk®, C++, or similar, and traditional procedural programming languages ​​such as the “C” programming language or similar. The computer readable program instructions may be executed entirely on the user's computer, partially on the user's computer, as a stand-alone software package, partially on the user's computer and partially on a remote computer, or entirely on a remote computer or remote server. In the latter case, 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 may be connected to an external computer (e.g., through the Internet using an Internet Service Provider). In some embodiments, electronic circuitry including, for example, a programmable logic circuit, a field programmable gate array (FPGA), or a programmable logic array (PLA) may execute computer readable program instructions by using state information of the computer readable program instructions to individually configure the electronic circuitry to perform aspects of embodiments of the present invention.

[0136] Aspects of embodiments 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 present 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.

[0137] 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 cause a machine to create means for implementing the functions / operations specified in one or more blocks of the flowcharts and / or block diagrams, and these computer readable program instructions may be stored in a computer readable storage medium capable of instructing a computer, programmable data processing apparatus, or other device, or combination thereof, to function in a particular manner, such that the computer readable storage medium on which the instructions are stored constitutes an article of manufacture containing instructions that implement aspects of the functions / operations specified in one or more blocks of the flowcharts and / or block diagrams.

[0138] Also, the computer readable program instructions may be loaded into a computer, other programmable data processing apparatus, or other device such that the instructions, which execute on the computer, other programmable apparatus, or other device, implement the functions / operations identified in one or more blocks of the flowcharts and / or block diagrams, and a series of operational steps may be executed on the computer, other programmable apparatus, or other device to produce a computer-implemented process.

[0139] The flowcharts and block diagrams in the drawings 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 flowcharts or block diagrams may represent a module, segment, or portion of instructions, including one or more executable instructions for implementing the specified logical function. In some alternative implementations, the functions described in the blocks may occur in a different order than the order described in the drawings. For example, two blocks shown in succession may in fact be executed substantially simultaneously, or the blocks may sometimes be executed in the reverse order, depending on the functionality involved. It should also be noted that each block of the block diagrams and / or flowchart illustrations, and combinations of multiple blocks in the block diagrams and / or flowchart illustrations, may be implemented by a dedicated hardware-based system that executes the specified functions or actions or executes a combination of dedicated hardware and computer instructions.

[0140] FIG. 23 illustrates a block diagram showing some elements that may be included in a computing device, host, storage controller, storage device, or other device shown in FIGS. 1-22, according to some embodiments. The system 2300 may include circuitry 2302, which may include at least a processor 2304 in some embodiments. The system 2300 may also include memory 2306 (e.g., a volatile memory device) and storage 2308. The storage 2308 may include a non-volatile memory device (e.g., EEPROM, ROM, RPOM, flash, firmware, programmable logic, etc.), a magnetic disk drive, an optical disk drive, a tape drive, etc. The storage 2308 may include an internal storage device, an attached storage device, or a network accessible storage device, or a combination thereof. The system 2300 may include program logic 2310, which includes code 2312 that is loaded into the memory 2306 and executed by the processor 2304 or the circuitry 2302. In some embodiments, program logic 2310 including code 2312 may be stored in storage 2308. In some other embodiments, program logic 2310 may be implemented in circuitry 2302. One or more of the components in system 2300 may communicate via a bus or other couplings or connections 2314. Thus, although FIG. 23 shows program logic 2310 separate from other elements, program logic 2310 may be implemented in memory 2306 or circuitry 2302 or both.

[0141] Some embodiments may be directed to methods for deploying computing instructions, either by a human or by an automated process of incorporating computer readable code into a computing system, where the code, in combination with the computing system, is capable of performing the operations of the described embodiments.

[0142] Terms such as "an embodiment," "an embodiment," "some embodiments," "the embodiment," "the embodiments," "one or more embodiments," "some embodiments," and "one embodiment" mean "one or more, but not necessarily all, embodiments of the invention," unless otherwise specified.

[0143] The terms "including," "comprising," "having," and variations thereof mean "including, but not limited to," unless expressly stated otherwise.

[0144] An enumerated listing of items does not imply that any or all of the items are mutually exclusive, unless specifically stated.

[0145] The terms "a," "an," and "the" mean "one or more," unless otherwise specified.

[0146] Devices that are in communication with each other need not be in continuous communication with each other unless specified otherwise. Further, devices that are in communication with each other may communicate directly or indirectly through one or more intermediaries.

[0147] Describing an embodiment having several components in communication with each other does not imply that all such components are required, but rather, various components that are optional are described to illustrate the wide variety of possible embodiments of the present invention.

[0148] Additionally, although process steps, method steps, algorithms, or the like may be described in a sequential order, such processes, methods, and algorithms may be configured to function in other orders. In other words, any sequence or order of steps described does not necessarily indicate that the steps must be performed in that order. Steps of processes described herein may be performed in any order that is practical. Additionally, some steps may be performed simultaneously.

[0149] It will be readily apparent that where a single device or product is described herein, multiple devices / products (whether or not they cooperate) may be used rather than a single device / product. Similarly, it will be readily apparent that where multiple devices or products are described herein (whether or not they cooperate) a single device / product may be used rather than multiple devices or products, or a different number of devices / products may be used rather than the number of devices or programs shown. The functionality and / or features of a device may instead be realized by one or more other devices not explicitly described as having such functionality / features. Thus, it is not necessary for other embodiments of the invention to include the device itself.

[0150] At least some of the operations that may be illustrated in the figures show some events occurring in a particular order. In alternative embodiments, some operations may be performed in a different order, modified, or removed. Also, steps may be added to the logic described above while still being in accordance with the described embodiment. Furthermore, operations described herein may occur sequentially, or some operations may be processed in parallel. Still further, operations may be performed by a single processing device, or may be performed by multiple distributed processing devices.

[0151] The above description of various embodiments of the invention has been presented for 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 accordance with the above teachings. 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 details, 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 scope of the invention, the invention resides in the claims appended hereto.

Claims

1. Enabling a host port for security; and performing input / output (I / O) in the clear by the host port in response to determining that an audit mode indicator is enabled to allow I / O on a path between the host port and the storage port even if an authentication or security association negotiation between the host port and the storage port cannot be successfully completed; enabling data encryption for I / O on said path by said host port simultaneously with performing I / O in clear on said path; A method comprising:

2. 2. The method of claim 1, wherein the simultaneous enabling of data encryption includes initiating a security association (SA) management transaction between the host port and the storage port.

3. 3. The method of claim 2, wherein the host port is programmed with keying material for the exchange of encrypted data along with a plaintext permissive indicator configured to permit the exchange of plaintext data on the path simultaneously with the exchange of encrypted data on the path.

4. 4. The method of claim 3, further comprising: in response to the plaintext permissive indicator being configured to permit exchange of plaintext data on the path simultaneously with exchange of encrypted data on the path, the host port being configured to receive both plaintext and encrypted data using the keying material.

5. 5. The method of claim 4, further comprising: in response to the host port determining that all cleartext reception has been completed due to a timer expiring after a security association was activated for transmission, programming the host port to no longer process cleartext data.

6. 6. The method of claim 5, wherein the timer expires after a timeout period sufficient to flush any cleartext data that was queued for transmission on the path at the time transmission of the encrypted data began on the path.

7. 2. The method of claim 1, wherein no I / O errors are generated when both cleartext data and encrypted data are exchanged on the path during a predetermined period of time indicated by a timer.

8. Memory, a processor coupled to the memory for executing operations, the operations including: Enabling a host port for security; and performing input / output (I / O) in the clear by the host port in response to determining that an audit mode indicator is enabled to allow I / O on a path between the host port and the storage port even if an authentication or security association negotiation between the host port and the storage port cannot be successfully completed; enabling data encryption for I / O on said path by said host port simultaneously with performing I / O in clear on said path; the processor, Including, the system.

9. 9. The system of claim 8, wherein the simultaneous enabling of data encryption includes initiating a security association (SA) management transaction between the host port and the storage port.

10. 10. The system of claim 9, wherein the host port is programmed with keying material for the exchange of encrypted data along with a plaintext permissive indicator configured to permit the exchange of plaintext data on the path simultaneously with the exchange of encrypted data on the path.

11. The operation, 11. The system of claim 10, further comprising: in response to the plaintext permissive indicator being configured to permit exchange of plaintext data on the path simultaneously with exchange of encrypted data on the path, the host port being configured to receive both plaintext and encrypted data using the keying material.

12. The operation, 12. The system of claim 11, further comprising: in response to the host port determining that all cleartext reception is complete due to a timer expiring after a security association is activated for transmission, programming the host port to no longer process cleartext data.

13. 13. The system of claim 12, wherein the timer expires after a timeout period sufficient to flush any cleartext data that was queued for transmission on the path at the time transmission of the encrypted data began on the path.

14. 9. The system of claim 8, wherein no I / O errors are generated when both cleartext data and encrypted data are exchanged on the path during a predetermined period of time indicated by a timer.

15. A computer program product for causing a computer to execute the method according to any one of claims 1 to 7.

16. A storage medium having the computer program according to claim 15 stored therein, the computer readable storage medium.

Citation Information

Patent Citations

  • Computer system, and authentication information change method of computer system

    JP2008009777A

  • Storage system

    JP2014041580A

  • Computer system and method of updating authentication information of computer system

    US20080005565A1

  • Storage system in which information is prevented

    US20140032867A1

  • Storage device, control method, and program

    WO2006090455A1