the certificate. Other fields of a certificate are optional
and can specify the services that a client is eligible for
etc.
A more detailed description of FCAP follows.
Step 1. At set up, A presents its credentials off-line
to the CA and requests a digital certificate.
Step 2. After the CA verifies the credentials of A, it
issues a certificate.
Step 3. A sends a signed request for service from B
and includes its certificate to prove its identity
Step 4. B obtains A’s certificate and verifies its va-
lidity (by consulting a Certificate Revocation List
(CRL)).
Step 5. If the certificate is okay, B uses information
from the certificate to interpret A’s request.
The advantages of FCAP is it does not require
a shared secret to be established at the outset and
securely stored (as in passphrase systems such as
CHAP). The only secret that has to be centrally safe-
guarded is the private key(s) of the CA. However, in
general, the implementation of PKI carries an over-
head. It needs to maintain a huge database for certifi-
cates. To verify the validity of the certificate, B has
to consult the CRL (Certificate Revocation List). In
a storage environment, this could create unacceptable
delays as the high speed storage switches will time
out.
2.3 Zoning and Lun Masking
Zoning is a method by which one can control who
can see what in a SAN. It permits communication
only between defined sets by switching port or by
World Wide Name (WWN) of components. It is im-
plemented at the infrastructure level (switches) and is
protocol independent. Within a zone, the member can
have any-to-any connectivity. Hard zoning defines a
zone by linking the ports of members. A zone estab-
lished by linking the member’s WWNs is referred to
as soft zoning. It is also desirable to define zone sets
as small as one can, and disable ports by default.
LUN Masking is a process that makes a LUN
available only to a subset of initiators. It masks off the
LUNs that are not assigned to the application server.
This restricts access even further. LUN Masking is
implemented primarily at end devices and applicable
only to SCSI protocol. Thus, it is another layer of se-
curity above zoning (protocol specific). In the use of
LUN masking, all access should be disabled by de-
fault. Only initiators that need the logical unit are en-
abled. Multi-pathing should be used. If authorization
types is implemented, they should also be used.
3 ID BASED CRYPTOGRAPHY
The purpose of ID based cryptography is to reduce
the overhead in the traditional PKI. In the ID based
environment, the public key is a string which can be
specified easily (eg. email address, IP, device identi-
fier, etc.). It can also incorporate a period of validity.
There is a trusted third party in such a system, which
is also referred to as central authority (CA) or private
key generator (PKG).
In the setup stage, the central authority generates a
key pair, the public key pub
M
and private key priv
M
.
They are called the master public key and private key
of the CA.
The following is how the ID based encryption
(IBE) works. If A is intended to send a cipher to B,
it encrypts a plain text K using B’s identifier ID
B
and
pub
M
, then transmits the cipher to B. To recover the
plaintext, B obtains its private key priv
ID
B
(which key
is computed by CA using priv
M
and ID
B
) from CA
(if it has not done so), then performs the decryption.
A well-known IBE system was proposed by
Boneh and Franklin (Boneh and Franklin, 2001),
which uses a mathematical structure called the Weil
pairing. Digital signatures can be realized in the ID
based system as well.
If A wants tocreate a signature in ID based setting,
it first obtains the private key priv
ID
A
from CA (if it
has not already done so). Then A signs the message
K using priv
ID
A
, and sends the signature to B.
B verifies A’s signature using ID
A
and pub
M
.
An example of ID based signature (IBS) scheme is
found in (Cha and Cheon, 2003). In some sense, this
IBS can be regarded as a dual to the IBE in (Boneh
and Franklin, 2001).
Certificates are eliminated from ID based systems,
it is efficient and easy to use. One of the disadvan-
tages of such systems is that they provide key escrow
since the central authority knows every user’s private
key. Some schemes were proposed to avoid key es-
crow, but they suffer other problems.
4 APPLICATIONS TO SAN
In this section, we propose the use of ID based cryp-
tography in the authentication problem for SANs. It
is parallel to FCAP under PKI, but has the advantage
of being light weight.
Our system contains a central authority (CA) with
a master public key pub
M
and a master private key
priv
M
. For each user A, an identifier will be specified
and denoted by ID
A
. This is A’s identity which can
be IP address, or device identifier, or WWN, or other
SECURITY AND AUTHENTICATION FOR NETWORKED STORAGE
479