4
STORAGE DELL POWER SOLUTIONS | February 2008 1 Reprinted from Dell Power Solutions, February 2008. Copyright © 2008 Dell Inc. All rights reserved. I nternet SCSI (iSCSI) carries SCSI commands between host systems (initiators) and storage systems (targets) by defining the encapsulation of SCSI packets in TCP and routing them through IP—allowing block-level storage data to be trans- ported seamlessly over IP networks. With Gigabit Ethernet already widespread and 10 Gigabit Ethernet becoming available, IP-based storage has become increasingly viable in enterprise data centers. Appropriately configured iSCSI networks can pro- vide security comparable to or better than Fibre Channel, particularly when a separate Ethernet net- work is used for iSCSI traffic. 1 Because iSCSI runs over TCP/IP, all of the security options for standard network traffic are also available for iSCSI. However, administra- tors should take specific steps when sharing a single physical network to help ensure the separation and security of iSCSI traffic. Key methods include deploy- ing security negotiation and authentication processes and implementing IP security (IPsec), Internet Storage Name Service (iSNS), and virtual LANs (VLANs). SECURITY NEGOTIATION AND AUTHENTICATION The interaction between initiators and targets begins with the iSCSI login process, which establishes the iSCSI connection, sets the protocol parameters, and authenticates initiators and targets with each other. During the initial phase of security negotiation, initia- tors and targets negotiate the security parameters using text keys. The AuthMethod text key passed by the initiator contains a list of authentication methods in order of preference. The available authentication methods are Kerberos V5 (KRB5), Simple Public-Key Generic Security Services Application Programming Interface (GSS-API) Mechanism (SPKM1), Simple Public-Key GSS-API Mechanism 2 (SPKM2), Secure Remote Password (SRP), Challenge Handshake Authentication Protocol (CHAP), and no authentica- tion. The target must reply with the first option in the list it supports and is allowed to use. The initiator and target must implement CHAP, but the other authen- tication methods are optional. After the authentica- tion process is complete, the initiator and target move on to the optional login operational negotiation phase or the iSCSI full feature phase. CHAP, the only required authentication method, defines a methodology for authenticating initiators and targets. It is a form of in-band negotiation that pro- vides end-to-end trust between initiator and target, and periodically verifies peer identity using a three- way handshake. This handshake is performed when Internet SCSI (iSCSI) storage has emerged as a cost- effective alternative to traditional Fibre Channel– based storage area networks. This article describes different methods administrators can use to help them secure their networks when deploying iSCSI in enterprise environments. By Surendra Bhat Lokesh Singh Santosh Bhadri SECURING iSCSI STORAGE NETWORKS Related Categories: Internet SCSI (iSCSI) Network security Security Storage Visit DELL.COM/PowerSolutions for the complete category index. 1 For more information on how iSCSI security compares with Fibre Channel, see “iSCSI: Changing the Economics of Storage; Part 1—Understanding iSCSI in Enterprise Environments,” by Travis Vigil, in Dell Power Solutions, May 2007, DELL.COM/Downloads/Global/Power/ps2q07-20070335-Vigil.pdf.

Securing iScSi Storage networkS - DellReprinted from Dell Power Solutions, February 2008. Copyright © 2008 Dell Inc. All rights reserved. DELL.COM/PowerSolutions 2 the link is initially

  • Upload
    others

  • View
    3

  • Download
    0

Embed Size (px)

Citation preview

Storage

DELL POWER SOLUTIONS | February 20081 Reprinted from Dell Power Solutions, February 2008. Copyright © 2008 Dell Inc. All rights reserved.

Internet SCSI (iSCSI) carries SCSI commands

between host systems (initiators) and storage

systems (targets) by defining the encapsulation

of SCSI packets in TCP and routing them through

IP—allowing block-level storage data to be trans-

ported seamlessly over IP networks. With Gigabit

Ethernet already widespread and 10 Gigabit Ethernet

becoming available, IP-based storage has become

increasingly viable in enterprise data centers.

Appropriately configured iSCSI networks can pro-

vide security comparable to or better than Fibre

Channel, particularly when a separate Ethernet net-

work is used for iSCSI traffic.1 Because iSCSI runs over

TCP/IP, all of the security options for standard network

traffic are also available for iSCSI. However, administra-

tors should take specific steps when sharing a single

physical network to help ensure the separation and

security of iSCSI traffic. Key methods include deploy-

ing security negotiation and authentication processes

and implementing IP security (IPsec), Internet Storage

Name Service (iSNS), and virtual LANs (VLANs).

Security negotiation and authenticationThe interaction between initiators and targets begins

with the iSCSI login process, which establishes the

iSCSI connection, sets the protocol parameters, and

authenticates initiators and targets with each other.

During the initial phase of security negotiation, initia-

tors and targets negotiate the security parameters

using text keys. The AuthMethod text key passed by

the initiator contains a list of authentication methods

in order of preference. The available authentication

methods are Kerberos V5 (KRB5), Simple Public-Key

Generic Security Services Application Programming

Interface (GSS-API) Mechanism (SPKM1), Simple

Public-Key GSS-API Mechanism 2 (SPKM2), Secure

Remote Password (SRP), Challenge Handshake

Authentication Protocol (CHAP), and no authentica-

tion. The target must reply with the first option in the

list it supports and is allowed to use. The initiator and

target must implement CHAP, but the other authen-

tication methods are optional. After the authentica-

tion process is complete, the initiator and target

move on to the optional login operational negotiation

phase or the iSCSI full feature phase.

CHAP, the only required authentication method,

defines a methodology for authenticating initiators and

targets. It is a form of in-band negotiation that pro-

vides end-to-end trust between initiator and target,

and periodically verifies peer identity using a three-

way handshake. This handshake is performed when

Internet SCSI (iSCSI) storage has emerged as a cost-effective alternative to traditional Fibre Channel–based storage area networks. This article describes different methods administrators can use to help them secure their networks when deploying iSCSI in enterprise environments.

By Surendra Bhat

Lokesh Singh

Santosh Bhadri

Securing iScSi Storage networkS

Related Categories:

Internet SCSI (iSCSI)

Network security

Security

Storage

Visit DELL.COM/PowerSolutions

for the complete category index.

1 For more information on how iSCSI security compares with Fibre Channel, see “iSCSI: Changing the Economics of Storage; Part 1—Understanding iSCSI in Enterprise Environments,” by Travis Vigil, in Dell Power Solutions, May 2007, DELL.COM/Downloads/Global/Power/ps2q07-20070335-Vigil.pdf.

2DELL.COM/PowerSolutionsReprinted from Dell Power Solutions, February 2008. Copyright © 2008 Dell Inc. All rights reserved.

the link is initially established, and may be

subsequently repeated at different times.

The authentication method depends on a

key known only to the authenticator and

the peer, which is not sent over the link.

Unidirectional authentication enables the

target to validate the initiator. Bidirectional

authentication adds an additional level of

security by providing a means for the initia-

tor to authenticate the target.

Figure 1 illustrates the CHAP unidirec-

tional authentication process. After the

initial authentication has succeeded, the

target sends a new challenge to the initia-

tor at random intervals and repeats this

process to verify the authentication. If the

authentication fails, the target rejects the

login attempt.

Each initiator should use a single unique

CHAP authentication key: administrators

should not use the same key for multiple

initiators, and should not configure initia-

tors to use multiple keys. In addition, initia-

tors should not reuse CHAP challenges

sent by targets for the other direction of a

bidirectional authentication.

The other available authentication

methods are more advanced than CHAP.

Kerberos enables authentication through

a trusted third-party service. SPKM1 and

SPKM2 use public keys rather than sym-

metric keys. SRP is well suited for nego-

tiating secure connections with

user-supplied passwords, helping elimi-

nate security problems traditionally asso-

ciated with reusable passwords.

iP SecurityBecause iSCSI uses TCP/IP, administrators

can help secure iSCSI traffic by using

cryptography at the IP layer. IPsec, a set

of security extensions developed by the

IETF, provides privacy and authentication

services at the IP layer by enabling a

system to select the required security pro-

tocols, determining the algorithms to use

for the services, and putting in place the

cryptographic keys required for these ser-

vices. To help protect the contents of IP

datagrams, IPsec uses encryption algo-

rithms to transform the data.

IPsec comprises two primary transfor-

mation protocols: Authentication Header

(AH) and Encapsulating Security Payload

(ESP). AH helps provide connectionless

integrity, data origin authentication, and an

optional anti-replay service. ESP helps pro-

vide confidentiality (encryption) in addition

to the AH services. Each protocol supports

two modes: transport mode and tunnel

mode. In transport mode, they help provide

protection primarily for upper-layer proto-

cols; in tunnel mode, they are applied to

tunneled IP packets. IPsec-compliant iSCSI

security implementations may or may not

support ESP in transport mode, but must

support it in tunnel mode.

IPsec uses multiple security protocols,

a few of which must be supported by IPsec-

compliant iSCSI implementations. A keyed-

hash message authentication code with

Secure Hash Algorithm (SHA-1) must be

supported to help verify data integrity and

authentication. Triple Data Encryption

Standard (3DES) with cipher block chaining

must be supported to provide encryption.

The two systems communicating

through IPsec establish a security associa-

tion (SA), which represents an agreement

between the two systems about how they

exchange and protect data. Internet Key

Exchange (IKE) allows two systems to set

up their SAs, including the keys they use.

Figure 2 illustrates the IPsec and IKE secu-

rity process. Step 2 (IKE phase 1) involves

negotiating authentication and the hash-

ing and encryption algorithms, generating

shared keys, and authenticating the initia-

tor and target. Step 3 (IKE phase 2) occurs

while the systems are protected by the

IKE SA set up in the previous step; two

unidirectional IPsec SAs are generated for

the security protocol (AH or ESP) and

cryptographic algorithms identified during

negotiation.

IPsec may not be supported by all

iSCSI storage systems, and because sig-

nificant resources are required for pro-

cessing IPsec traffic, many solutions may

not be cost-effective and may reduce per-

formance for iSCSI traffic.

internet Storage name ServiceiSNS facilitates automated discovery,

management, and configuration of iSCSI

devices on TCP/IP networks. It provides

Figure 1. CHAP unidirectional authentication process

Server(initiator)

iSCSI storage array(target)

Authenticator sends challenge message to peer

Peer responds with one-way hash of key

Authenticator compares response with its own expected hash value, then either accepts or rejects the connection

1

2

3

Figure 2. IPsec and IKE security process

Server(initiator)

iSCSI storage array(target)

Initiator initiates communication with target, starting IPsec session

IKE SA is set up (IKE phase 1)

IPsec SAs are set up (IKE phase 2)

1

2

3

Initiator and target perform IPsec secured data transfer

Initiator terminates connection

4

5

Storage

DELL POWER SOLUTIONS | February 20083 Reprinted from Dell Power Solutions, February 2008. Copyright © 2008 Dell Inc. All rights reserved.

intelligent storage services comparable to

those found in Fibre Channel–based SANs

by using discovery domains. Its discovery

domain service enables administrators to

partition storage nodes into manageable

groupings for administrative and login

control purposes. Administrators can limit

login processes for each initiator to an

appropriate subset of targets registered

in iSNS, which can help limit the time that

servers spend initializing login relation-

ships as SANs grow.

iSCSI-based servers and storage act

as iSNS clients, communicating with the

iSNS server using iSNS Protocol (iSNSP).

Storage controllers send storage array

profiles to the iSNS server. Storage clients

can discover accessible storage control-

lers through the iSNS server.

Administrators can place the systems

that should be accessible to each other

in a single discovery domain. Each system

may be part of multiple discovery

domains. If administrators have placed

one or more network portals of a system

into a discovery domain, then queries to

that domain report only portals that have

been explicitly placed there. Administrators

can manage discovery domains offline

through a separate management work-

station using iSNSP or Simple Network

Management Protocol (SNMP). Figure 3

illustrates an example environment using

iSNS zoning.

iSNS also supports discovery domain

sets. Valid and active discovery domains

belong to at least one active discovery

domain set; domains that do not belong

to an activated set are not enabled.

Analogous to zone sets in Fibre Channel–

based SANs, discovery domain sets can

be used to quickly reconfigure an iSCSI-

based SAN for different application

requirements.

virtual lanSVLANs divide physical networks into

separate virtual networks, which helps

reduce broadcast traffic to individual

nodes. Administrators can also use

VLANs to segregate networks to help

increase security. By deploying an iSCSI

network on a separate VLAN, traffic

between the iSCSI network and outside

networks can take place only through a

router or Layer 3 switch. This configura-

tion helps minimize the risk of unauthor-

ized access to iSCSI storage from the

outside network. To help further increase

security, administrators can also deploy

multiple portals for a single storage array

on separate VLANs.

Figure 4 illustrates an example envi-

ronment in which one port of an iSCSI

array has been placed on VLAN 2 with two

servers. VLAN 3 includes the other port

of the storage array and a third server.

Administrators can use the management

station for out-of-band array configura-

tion. Segregating the devices and network

portals into distinct VLANs in this way

helps increase security.

Secure iScSi networkSUsing the methods described in this

article can help administrators secure

iSCSI networks in enterprise environ-

ments. Administrators should keep in

mind that all of these methods may not

be supported on all iSCSI storage arrays;

when planning an iSCSI network, they

should evaluate the available methods

and choose the appropriate ones based

on their security requirements. Doing so

can help administrators deploy iSCSI

over many different types of IP networks

while providing an appropriate level of

security.

Surendra Bhat is a Product Group test

engineer senior analyst in the Enterprise

Server Test Group at the Dell India R&D

Center. His interests include networking and

storage technologies, and he has a bache-

lor’s degree in Electronics Engineering from

the University of Mumbai.

Figure 4. Example environment using iSCSI with multiple virtual LANs

VLAN 3

iSCSI storage array

Server Server

Ethernet switchVLAN 2

Server

Network portals

Management station

Figure 3. Example environment using iSNS zoning

iSCSI storage arrayServer Server

Ethernet switch

Discovery domain 1

iSNS server

iSCSI storage array

Discovery domain 2

Server

4DELL.COM/PowerSolutionsReprinted from Dell Power Solutions, February 2008. Copyright © 2008 Dell Inc. All rights reserved.

Lokesh Singh is a Product Group test engi-

neer analyst in the Sustaining Business

organization at the Dell India R&D Center.

His interests include networking and stor-

age technologies, and he has a B.E. in com-

puter science from Kumaun University.

Santosh Bhadri is a Product Group engi-

neer senior analyst in the Sustaining

Business organization at the Dell India R&D

Center. His interests include computer

architecture and storage technologies, and

he has a bachelor’s degree in Electronics

and Communication from B.M.S. College of

Engineering.

Quick link

Dell™ iSCSI storage solutions:DELL.COM/iSCSI