APC SY30K100F Owners Manual

Contents

Introduction--1

Content and Purpose of This Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . 1

User Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2

Security--3

Security Features. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

Authentication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

Encryption . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

Creating and Installing Digital Certificates . . . . . . . . . . . . . . . . . . . . . 11

Firewalls . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

Using the APC Security Wizard--16

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

Create a Root Certificate and Server Certificates . . . . . . . . . . . . . . . . 19

Create a Server Certificate and Signing Request . . . . . . . . . . . . . . . . 23

Create an SSH Host Key. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26

Control Console Access and Security--28

Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28

Telnet and Secure SHell (SSH) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28

Web Interface Access and Security--31
RADIUS--34

Supported RADIUS Functions and Servers . . . . . . . . . . . . . . . . . . . . 34

Configure the Management Card or Device . . . . . . . . . . . . . . . . . . . . 34

Configure the RADIUS Server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36

SECURITY HANDBOOK

Network- Enabl ed Devi ces, AOS v. 3.x. x

Index--40

i

Introduction

Content and Purpose of This Guide

This guide documents security features for firmware version 3.x.x for APC® Network
Management Cards and for devices with embedded components of APC Network
Management Cards, which enable the devices to function remotely over the network.

For information about the security features for a device running firmware
version 5.x.x, see the Security Handbook provided on the Utility CD for that
device.

This guide documents the following protocols and features, how to select which ones
are appropriate for your situation, and how to set up and use them within an overall
security system:

• Telnet and Secure SHell (SSH)

• Secure Sockets Layer (SSL)

•RADIUS

• SNMPv1 and SNMPv3
In addition, this guide documents how to use the APC Security Wizard to create the

components required for the increased security available through SSL and SSH.

SECURITY HANDBOOK

Network-E nabled Dev ices, AOS v.3. x.x

1

User Management

Types of user accounts

A Network Management Card or network-enabled device has three basic levels of
access:

• An Administrator can use all of the management menus available in the Web
interface and control console. The default user name and password are both apc.

• A Device User can access the event log and data log (but cannot delete the contents
of either log), and can use the device-related menus. The default user name is

device, and the default password is apc.

• A Read-Only User can access the same menus as a Device User , but cannot change
configurations, control devices, delete data, delete the content of logs, or use file
transfer options. The default user name is readonly, and the default password is apc.
A Read-Only User cannot log on through the control console.

Some APC devices have additional user accounts, e.g., outlet users for
Switched Rack PDUs and an A/C Manager for some NetworkAIR devices.
See the device’s User’s Guide for information on the additional account type.

SECURITY HANDBOOK

Network-Enabled Devices, AOS v.3.x.x

2

Security

Security Features

Summary of access methods

Serial control console.

Security Access Description

Access i s by user name and password. Always enabled.

Remote control console.

Securit y Access Description

Available methods:

• User name and pass word

• Selectable server port

• Access protocols that can
be enabled or disabled

• Secure SH ell (SSH)

SECURITY HANDBOOK

Network-E nabled Dev ices, AOS v.3. x.x

For high security, use SSH.

• With Telnet, the user name and password are transmitted as
plain te x t.

• Enabling SSH disables Telnet and provides encrypted access
to the control console to provide additional protection from
attempts to intercept, forge, or alter data during transmission.

3

SNMPv1 and SNMPv3 .

Security Access Description

Available methods (SNMPv1):

• Community Name

•Host Name

• NMS IP filte r s

• Agents that can be enabled
or disa bled

• Four access communities
with read/write/disable
capability

Available methods (SNMPv3):

• Four User Profiles

• Authentication through an
authentication passphrase

• Encrypt ion t hro ugh a pri vacy
passphrase

• MD5 authentication

• DES encryption algorithm

• NMS IP filte r s

For both SNMPv1 and SNMPv3, the host name restricts access
to the Network Management System (NMS) at that location
only, and the NMS IP filters allow access only to the NMSs
specified by one of the IP address formats in the fo llowing
examples:

159.215.12.1: O nly the NMS at the IP address 159.215.12.1.

•

• 159.215.12.255: Any NMS on the 159.215.12 segment.

• 159.215.255. 255: Any NMS on the 159.215 segment.

• 159.255.255. 255: Any NMS on the 159 segment.

• 0.0.0.0 or 255.255.255.255: Any NMS.
SNMPv3 has additional security features that include the

following:

• An authentication pas sphrase to ensure that an NMS trying to
access t he N et wor k Man age men t C ard or de v ice i s th e NMS i t
claims to be.

• Encryption of data during transmission, with a privacy
passphrase required for encrypting and decrypting.

File trans fer protocols.

Available methods:

• User nam e and password

• Selectable server port

• FTP Server and access
protoc ols that can be
enabled or disabled

• Secure CoPy (SCP)

SECURITY HANDBOOK

Network-E nabled Devic es, AOS v.3.x.x

Security Access Description

With FTP, the user name and password are transmitted as
plain text, and files are transferre d without encryption.

Using SCP enc r ypt s t he us er n ame a nd p a sswo r d an d th e fi le s
being transferred, such as firmware updates, configuration
files, log files, Secure Sockets Layer (SSL) certificates, and
Secure SHell (SSH) host keys. If you choose SCP as your file
transfer protocol, enable SSH and disable FTP.

4

Web se rver.

Security Access Description

Available methods:

• User nam e and password

• Selectable server port

• Web interface access that
can be enabled or
disabled

• Secure Sockets Layer
(SSL)

RADIUS.

Security Access Description

Available methods:

• Centralized authentication of
access rights

• A server secret shared between
the RADIUS server and the
Manage m en t Ca r d or de v ice

In basic HTTP authentication mode, the user name and
password are transmitted base-64 encod ed (with no encryption).

SSL is available on Web brows ers supported for use with the
Management Card or network-enabled device and on mos t Web
servers. The Web protoc ol HyperText Transfer Protocol over
Secure Sockets La yer (HTTPS) encrypts and decrypts page
requests to the Web server and pages returned by the Web
server to the user.

RADIUS (Remote Authe ntication Dial-In User Service) is
an authentication, authorization, and accounting service
used to c entrally administer remote access for each
Management Card or device. (APC supports the
authentication and authorization functions.)

Access priorities

The priority for access, beginning with the highest priority, is as follows:

• Local access to the control console from a computer with a direct serial connection to
the Management Card or device

• Telnet or Secure SHell (SSH) access to the control console from a remote computer

• Web access, either directly or through the InfraStruXure Central

SECURITY HANDBOOK

Network-E nabled Devic es, AOS v.3.x.x

5

Changing default user names and passwords immediately

After installation and initial configuration of the Network Management Card or
network-enabled device, immediately change the user names and passwords from
their defaults to unique user names and passwords to establish basic security.

Port assignments

If Telnet, the FTP server, SSH/SCP, or the Web server uses a non-standard port, a user
must specify the port in the command line or Web address used to access the
Management Card or device. A non-standard port number provides an additional level
of security. The ports are initially set at the standard “well known ports” for the
protocols. To increase security, reset the ports to any unused port numbers from 5001
to 32768 for the FTP server and from 5000 to 32768 for the other protocols and
servers. (The FTP server uses both the specified port and the port one number lower
than the specified port.)

User names, passwords, and community names with SNMPv1

All user names, passwords, and community names for SNMPv1 are transferred over
the network as plain text. A user who is capable of monitoring the network traffic can
determine the user names and passwords required to log on to the accounts of the
control console or Web interface of the Management Card or network-enabled device.
If your network requires the higher security of the encryption-based options available
for the control console and Web interface, disable SNMPv1 access or set its access to

Read. (Read access allows you to receive status information and use SNMPv1 traps.)

To disable SNMPv1 access, on the Administration tab, select Network on the top
menu bar and access under the SNMPv1 heading on the left navigation menu. Clear
the Enable SNMPv1 access checkbox and click Apply.

To set SNMPv1 access to Read, on the Administration tab, select Network on the top

SECURITY HANDBOOK

Network-E nabled Devic es, AOS v.3.x.x

menu bar and access control under the SNMPv1 heading on the left navigation menu.
Then, for each configured Network Management System (NMS), click the community
names and set the access type to Read.

6

Authentication

You can choose security features for the Network Management Card or
network-enabled device that controls access by providing basic authentication through
user names, passwords, and IP addresses, without using encryption. These basic
security features are sufficient for most environments in which sensitive data is not
being transferred.

SNMP GETS, SETS, and Traps

For enhanced authentication when you use SNMP to monitor or configure the
Management Card or network-enabled device, choose SNMPv3. The authentication
passphrase used with SNMPv3 user profiles ensures that a Network Management
System (NMS) attempting to communicate with the Management Card or device is the
NMS it claims to be, that the message has not been changed during transmission, and
that the message was not delayed, copied and sent again later at an inappropriate
time. SNMPv3 is disabled by default.

The APC implementation of SNMPv3 uses the MD5 protocol for authentication.

Web interface and control console

To ensure that data and communication between the Management Card or
network-enabled device and the client interfaces (the control console and the Web
interface) cannot be intercepted, you can provide a greater level of security by using
one or more of the following encryption-based methods:

• For the Web interface, use the Secure Sockets Layer (SSL) protocol.

• To encrypt user names and passwords for control console access, use the Secure
SHell (SSH) protocol.

• To encrypt user names, passwords, and data for the secure transfer of files, use the
Secure CoPy (SCP) protocol.

SECURITY HANDBOOK

Network-Enabled Devices, AOS v.3.x.x

For more information on encryption-based security, see Encryption.

7

Encryption

SNMP GETS, SETS, and Traps

For encrypted communication when you use SNMP to monitor or configure the
Management Card or network-enabled device, choose SNMPv3. The privacy
passphrase used with SNMPv3 user profiles ensures the privacy of the data (by means
of encryption, using the DES encryption algorithm) that an NMS sends to or receives
from the Management Card or device.

Secure SHell (SSH) and Secure CoPy (SCP) for the control con so le

The Secure SHe ll protocol. SSH provides a secure mechanism to access computer

consoles, or shells, remotely. The protocol authenticates the server (in this case, the
Management Card or network-enabled device) and encrypts all transmissions between
the SSH client and the server.

• SSH is an alternative to Telnet, which does not provide encryption.

• SSH protects the user name and password, which are the credentials for
authentication, from being used by anyone intercepting network traffic.

• To authenticate the SSH server (the Management Card or network-enabled device)
to the SSH client, SSH uses a host key unique to the SSH server. The host key is an
identification that cannot be falsified, and it prevents an invalid server on the network
from obtaining a user name and password by presenting itself as a valid server.

For information on supported SSH client applications, see Telnet and

Secure SHell (SSH). To create a host key, see Create an SSH Host Key.

• The Management Card or device supports version 1 of SSH, which provides faster
log-on, and version 2 of SSH, which provides improved protection from attempts to
intercept, forge, or change data during transmission.

SECURITY HANDBOOK

Network-Enabled Devices, AOS v.3.x.x

• When you enable SSH, Telnet is automatically disabled.

• The interface, user accounts, and user access rights are the same whether you
access the control console through SSH or Telnet.

8

Secure CoPy. SCP is a secure file transfer application that you can use instead of

FTP. SCP uses the SSH protocol as the underlying transport protocol for encryption of
user names, passwords, and files.

• When you enable and configure SSH, you automatically enable and configure SCP.
No further configuration of SCP is needed.

• You must explicitly disable FTP. It is not disabled by enabling SSH. To disable FTP,
on the Administration tab, select Network on the top menu bar and FTP Server on
the side menu bar. Clear the Enable checkbox and click Apply.

Secure Sockets L ayer (SSL) for the Web Interface

For secure Web communication, enable Secure Sockets Layer (SSL) by selecting
HTTPS as the protocol mode to use for access to the Web interface of the
Management Card or network-enabled device. HyperText Transfer Protocol over
Secure Sockets Layer (HTTPS) is a Web protocol that encrypts and decrypts page
requests from the user and pages that are returned by the Web server to the user.

The Management Card or network-enabled device supports SSL version 3.0 and the
associated Transport Layer Security (TLS) version 1.0. Most browsers let you select
the version of SSL to enable.

When SSL is enabled, your browser displays a small lock icon.
SSL uses a digital certificate to enable the browser to authenticate the server (in this

case, the Management Card or device). The browser verifies the following:

• The format of the server certificate is correct.

• The server certificate’s expiration date and time have not passed.

• The DNS name or IP address specified when a user logs on matches the common
name in the server certificate.

• The server certificate is signed by a trusted certifying authority.

SECURITY HANDBOOK

Network-E nabled Devic es, AOS v.3.x.x

9

Each major browser manufacturer distributes Certificate Authority (CA) root certificates
of the commercial Certificate Authorities in the certificate store (cache) of its browser so
that it can compare the signature on the server certificate to the signature on a CA root
certificate.

You can use the APC Security Wizard to create a certificate signing request to an
external Certificate Authority. If you do not want to use an existing Certificate Authority,
you can create an APC root certificate to upload to a browser’s certificate store
(cache). You can also use the Wizard to create a server certificate to upload to the
Management Card or device. The APC Security Wizard is provided on the Utility CD.

See Creating and Installing Digital Certificates for a summary of how these
certificates are used.

To create certificates and certificate requests, see Create a Root Certificate

and Server Certificates and Create a Server Certificate and Signing Request.

SSL also uses various algorithms and encryption ciphers to authenticate the server,
encrypt data, and ensure the integrity of the data, i.e., that it has not been intercepted
and sent by another server.

SECURITY HANDBOOK

Network-E nabled Devic es, AOS v.3.x.x

See Web Interface Access and Security for the procedure to configure SSL,
including the selection of authentication and encryption algorithms.

Web pages that you have recently accessed are saved in your Web browser’s
cache and allow you to return to those pages without re-entering your user
name and password. Always close your browser session before you leave
your computer unattended.

10

Creating and Installing Digit al Ce rtificates

Purpose

For network communication that requires a higher level of security than password
encryption, the Web interface of the Network Management Card or network-enabled
device supports the use of digital certificates with the Secure Sockets Layer (SSL)
protocol. Digital certificates can authenticate the Management Card or device (the
server) to the Web browser (the SSL client).

The sections that follow summarize the three methods of creating, implementing, and
using digital certificates to help you determine the most appropriate method for your
system.

• Method 1: Use the default certificate auto-generated by the Network Management

Card or network-enabled device.

• Method 2: Use the APC Security Wizard to create a CA certificate and a server

certificate.

• Method 3: Use the APC Security Wizard to create a certificate-signing request to be

signed by the root certificate of an external Certificate Authority and to create a
server certificate.

.

Choosing a method for your system

Using the Secure Sockets Layer (SSL) protocol, you can choose any of the following
methods for using digital certificates.

SECURITY HANDBOOK

Network-E nabled Devic es, AOS v.3.x.x

You can also use Method 3 if your company or agency operates its own
Certificate Authority. Use the APC Security Wizard in the same way , but use
your own Certificate Authority in place of a commercial Certificate Authority.

11

Method 1: Use the default certificate auto-generated by the Network
Management Card or network-enabled device.

reboot the Management Card or device. During rebooting, if no server certificate exists,
the Management Card or device generates a default server certificate that is
self-signed but that you cannot configure.

Method 1 has the following advantages and disadvantages:

• Advantages:
– Before they are transmitted, the user name, password, and all data to and from the

Management Card or device are encrypted.

– You can use this default server certificate to provide encryption-based security

while you are setting up either of the other two digital certificate options, or you can
continue to use it for the benefits of encryption that SSL provides.

• Disadvantages:
– The Management Card or device takes up to 5 minutes to create this certificate,

and the Web interface is not available during that time. (This delay occurs the first
time you log on after you enable SSL.)

– This method does not include the authentication provided by a CA certificate (a

When you enable SSL, you must

– The default server certificate has the serial number of the Management Card or

SECURITY HANDBOOK

Network-E nabled Devic es, AOS v.3.x.x

certificate signed by a Certificate Authority) that Methods 2 and 3 provide. There is
no CA Certificate cached in the browser. Therefore, when you log on to the
Management Card or device, the browser generates a security alert, indicating that
a certificate signed by a trusted authority is not available, and asks if you want to
proceed. To avoid this message, you must install the default server certificate into
the certificate store (cache) of the browser of each user who needs access to the
Management Card or device, and each user must always use the fully qualified
domain name of the server when logging on to the Management Card or device.

device in place of a valid common name (the DNS name or the IP address of the
Management Card or device). Therefore, although the Management Card or
device can control access to its Web interface by user name, password, and
account type (e.g., Administrator, Device User , or Read-Only User), the browser

12

cannot authenticate which Management Card or device is sending or receiving
data.

– The length of the public key (RSA key) that is used for encryption when setting up

an SSL session is only 768 bits. (The public key used in Methods 2 and 3 is 1024
bits, providing more complex encryption and a higher level of security.)

Method 2: Use the APC Security Wizard to cr eate a CA certificate and a server
certificate.

•A CA root certificate (Certificate Authority root certificate) that the APC Security
Wizard uses to sign all server certificates and which you then install into the
certificate store (cache) of the browser of each user who needs access to the
Management Card or device.

•A server certificate that you upload to the Management Card or device. When the
APC Security Wizard creates a server certificate, it uses the CA root certificate to
sign the server certificate.

The Web browser authenticates the Management Card or device sending or requesting
data:

• To identify the Management Card or device, the browser uses the common name (IP
address or DNS name of the Management Card or device) that was specified in the
server certificate’s distinguished name when the certificate was created.

• To confirm that the server certificate is signed by a “trusted” signing authority, the
browser compares the signature of the server certificate with the signature in the root
certificate cached in the browser. An expiration date confirms whether the server

Use the APC Security Wizard to create two digital certificates:

certificate is current.

Method 2 has the following advantages and disadvantages.

• Advantages:
– Before they are transmitted, the user name, password, and all data to and from the

SECURITY HANDBOOK

Network-E nabled Devic es, AOS v.3.x.x

– The length of the public key (RSA key) that is used for encryption when setting up

Management Card or device are encrypted.

an SSL session is 1024 bits, providing more complex encryption and consequently

13

a higher level of security than the public key used in Method 1. (This longer
encryption key is also used in Method 3.)

– The server certificate that you upload to the Management Card or device enables

SSL to authenticate that data is being received from and sent to the correct
Management Card or device. This provides an extra level of security beyond the
encryption of the user name, password, and transmitted data.

– The root certificate that you install to the browser enables the browser to

authenticate the server certificate of the Management Card or device to provide
additional protection from unauthorized access.

• Disadvantage:
Because the certificates do not have the digital signature of a commercial Certificate
Authority, you must load a root certificate individually into the certificate store (cache)
of each user’s browser. (Browser manufacturers already provide root certificates for
commercial Certificate Authorities in the certificate store within the browser, as
described in Method 3.)

Method 3: Use the APC Security Wizard to create a certificate-signing request
to be signed by the root certificate of an external Certificate Authority and to
create a server certificate.

file) to send to a Certificate Authority. The Certificate Authority returns a signed
certificate (a .crt file) based on information you submitted in your request. Y ou then use
the APC Security Wizard to create a server certificate (a .p15 file) that includes the
signature from the root certificate returned by the Certificate Authority. Upload the
server certificate to the Management Card or device.

Method 3 has the following advantages and disadvantages.

SECURITY HANDBOOK

Network-E nabled Devic es, AOS v.3.x.x

• Advantages:
– Before they are transmitted, the user name and password and all data to and from

Use the APC Security Wizard to create a request (a .csr

You can also use Method 3 if your company or agency operates its own
Certificate Authority. Use the APC Security Wizard in the same way, but use
your own Certificate Authority in place of a commercial Certificate Authority.

the Management Card or device are encrypted.

14

– You have the benefit of authentication by a Certificate Authority that already has a

signed root certificate in the certificate cache of the browser . (The CA certificates of
commercial Certificate Authorities are distributed as part of the browser software,
and a Certificate Authority of your own company or agency has probably already
loaded its CA certificate to the browser store of each user’s browser.) Therefore,
you do not have to upload a root certificate to the browser of each user who needs
access to the Management Card or device.

– The length of the public key (RSA key) that is used for setting up an SSL session is

1024 bits, providing more complex encryption and a higher level of security than
the public key used in Method 1. (This longer encryption key is also used in
Method 2.)

– The server certificate that you upload to the Management Card or device enables

SSL to authenticate that data are being received from and sent to the correct
Management Card or device. This provides an extra level of security beyond the
encryption of the user name, password, and transmitted data.

– The browser matches the digital signature on the server certificate that you

uploaded to the Management Card or device with the signature on the CA root

• Disadvantages:
– Setup requires the extra step of requesting a signed root certificate from a

– An external Certificate Authority may charge a fee for providing signed certificates.

Firewalls

Although some methods of authentication provide a higher level of security than others,
complete protection from security breaches is almost impossible to achieve.
Well-configured firewalls are an essential element in an overall security scheme.

SECURITY HANDBOOK

Network-E nabled Devic es, AOS v.3.x.x

certificate that is already in the browser’s certificate cache to provide additional
protection from unauthorized access.

Certificate Authority.

15

Using the APC Security Wizard

Overview

The APC Security Wizard creates components needed for high security for a Network
Management Card or network-enabled device on the network when you are using
Secure Sockets Layer (SSL) and related protocols and encryption routines.

The Security Wizard can create security components for Management Cards
or devices running firmware version 5.x.x. or firmware version 3.x.x. For
information about using the Security Wizard with a Management Card or
device running firmware version 5.x.x, see the Security Handbook provided on
the Utility CD for that device.

Authentication by certificates and host keys

Authentication verifies the identity of a user or a network device (such as an APC
Network Management Card or network-enabled device). Passwords typically identify
computer users. However, for transactions or communications requiring more stringent
security methods on the Internet, the Management Card or device supports more
secure methods of authentication.

• Secure Sockets Layer (SSL), used for secure Web access, uses digital certificates for
authentication. A digital CA root certificate is issued by a Certificate Authority (CA) as
part of a public key infrastructure, and its digital signature must match the digital
signature on a server certificate on the Management Card or device.

• Secure SHell (SSH), used for remote terminal access to the control console of the
Management Card or device, uses a public host key for authentication.

How certificates are used. Most Web browsers, including all browsers supported by

APC Network Management Cards or network-enabled devices, contain a set of CA root

SECURITY HANDBOOK

Network-E nabled Dev ices, AOS v.3. x.x

certificates from all of the commercial Certificate Authorities.

16

Authentication of the server (in this case, the Management Card or device) occurs each
time a connection is made from the browser to the server. The browser checks to be
sure that the server’s certificate is signed by a Certificate Authority known to the
browser.

For authentication to occur:

• Each server (Network Management Card or device) with SSL enabled must have a
server certificate on the server itself.

• Any browser that is used to access the Web interface of the Management Card or
device must contain the CA root certificate that signed the server certificate.

If authentication fails, a browser message asks you whether to continue even though it
cannot authenticate the server.

If your network does not require the authentication provided by digital certificates, you
can use the default certificate that the Management Card or device generates
automatically. The default certificate’s digital signature will not be recognized by
browsers, but a default certificate enables you to use SSL for the encryption of
transmitted user names, passwords, and data. (If you use the default certificate, the
browser prompts you to agree to unauthenticated access before it logs you on to the
Web interface of the Management Card or device.)

How SSH host keys are used. An SSH host key authenticates the identity of the

server (the Management Card or device) each time an SSH client contacts that server.
Each server with SSH enabled must have an SSH host key on the server itself.

Files you create for SSL and SSH security

Use the APC Security Wizard to create these components of an SSL and SSH security
system:

• The server certificate for the Network Management Card or network-enabled device,

SECURITY HANDBOOK

Network-E nabled Devic es, AOS v.3.x.x

if you want the benefits of authentication that such a certificate provides. You can
create either of the following types of server certificate:

17

– A server certificate signed by a custom CA root certificate also created with the

APC Security Wizard. Use this method if your company or agency does not have
its own Certificate Authority and you do not want to use an external Certificate
Authority to sign the server certificate.

– A server certificate signed by an external Certificate Authority. This Certificate

Authority can be one that is managed by your own company or agency or can be
one of the commercial Certificate Authorities whose CA root certificates are
distributed as part of a browser’s software.

• A certificate signing request containing all the information required for a server
certificate except the digital signature. You need this request if you are using an
external Certificate Authority.

• A CA root certificate.

• An SSH host key that your SSH client program uses to authenticate the Management
Card or device when you log on to the control console interface.

You must define an RSA key size of 1024 bits for all public keys for SSL
certificates and all host keys for SSH that are created with the APC Security
Wizard. Management Cards and devices running AOS firmware version 3.x.x
cannot generate 2048-bit keys.

Only APC server management and key management products can use server
certificates, host keys, and CA root certificates created by the APC Security Wizard.
These files will not work with products such as OpenSSL
Information Services (IIS).

SECURITY HANDBOOK

Network-E nabled Devic es, AOS v.3.x.x

If you do not create and use SSL server certificates and SSH host keys with
the APC Security Wizard, the Management Card or device generates 768-bit
RSA keys.

®

and Microsoft® Internet

18

Create a Root Certificate and Server Certificates

Summary

Use this procedure if your company or agency does not have its own Certificate
Authority and you do not want to use a commercial Certificate Authority to sign
your server certificates.

You must define the size of the public RSA key that is part of a certificate
generated by the APC Security Wizard as 1024 bits. Devices running
firmware version 3.x.x cannot generate 2048-bit keys.

The default key generated by the Network Management Card or
network-enabled device, if you do not use the Wizard, is 768 bits.

• Create a CA root certificate that will sign all server certificates to be used with
Network Management Cards or network-enabled devices. During this task, two files
are created:

– The file with the .p15 suffix is an encrypted file that contains the Certificate

Authority’s private key and public root certificate. This file signs server certificates.

– The file with the .crt suffix contains only the Certificate Authority’s public root

certificate. Load this file into each Web browser that will be used to access the
Management Card or device so that the browser can validate the server certificate
of that Management Card or device.

• Create a server certificate, which is stored in a file with a .p15 suffix. During this task,
you are prompted for the CA root certificate that signs the server certificate.

• Load the server certificate onto the Management Card or device.

• For each Management Card or device that requires a server certificate, repeat the
tasks that create and load the server certificate.

SECURITY HANDBOOK

Network-Enabled Devices, AOS v.3.x.x

19

The procedure

Create the CA root certifi cate.

1. If the APC Security Wizard is not already installed on your computer, run the
installation program (APC Security Wizard.exe) by clicking the link Install the

Wizard in the interface of the Utility CD for the Management Card or device.

2. On the Windows Start menu, select Programs, then APC Security Wizard.

3. On the screen labeled Step 1, select CA Root Certificate as the type of file to
create, and then select the length of the key to generate (use 1024 bits, which is
the default setting).

4. Enter a name for this file, which will contain the Certificate Authority’s public root
certificate and private key. The file must have a .p15 suffix and, by default, will be
created in the installation folder C:\Program Files\American Power

Conversion\APC Security Wizard.

5. On the screen labeled Step 2, provide the information to configure the CA root
certificate. The Country and Common Name fields are the only required fields.
For the Common Name field, enter an identifying name of your company or
agency. Use only alphanumeric characters, with no spaces.

6. On the next screen, review the summary of the certificate. Scroll downward to view
the certificate’s unique serial number and fingerprints. To make any changes to the
information you provided, click Back, and revise the information.

SECURITY HANDBOOK

Network-E nabled Devic es, AOS v.3.x.x

By default, a CA root certificate is valid for 10 years from the current date
and time, but you can edit the V alidity Period St art and Validity Period

End fields.

The certificate’s subject information and the certificate’s issuer
information should be identical.

20

7. The last screen verifies that the certificate was created and displays information
you need for the next tasks:

• The location and name of the .p15 file that you will use to sign the server
certificates.

• The location and name of the .crt file, which is the CA root certificate to load into
the browser of each user who needs to access the management card or device.

Load the CA ro ot certificate to your browser. Load the .crt file to the browser of

each user who needs to access the Management Card or device.

See the help system of the browser for information on how to load the .crt file
into the browser’s certificate store (cache). Following is a summary of the
procedure for Microsoft Internet Explorer.

1. Select Tools, then Internet Options from the menu bar.

2. In the dialog box, on the Content tab click Certificates and then Import.

3. The Certificate Import Wizard guides you through the rest of the procedure. The file
type to select is X.509, and the CA Public Root Certificate is the .crt file created in
the procedure Create a Root Certificate and Server Certificates.

Create an SSL Server User Certificate.

1. On the Windows Start menu, select Programs, then APC Security Wizard.

2. On the screen labeled Step 1, select SSL Server Certificate as the type of file,
and then select the length of the key to generate (use 1024 bits, which is the
default setting).

3. Enter a name for this file, which will contain the server certificate and the private
key. The file must have a .p15 suffix and, by default, will be created in the folder

C:\Program Files\American Power Conversion\APC Security Wizard.

4. Click Browse, and select the CA root certificate created in the procedure Create a

Root Certificate and Server Certificates. The CA Root Certificate is used to sign the

SECURITY HANDBOOK

Network-E nabled Devic es, AOS v.3.x.x

Server User Certificate being generated.

5. On the screen labeled Step 2, provide the information to configure the server
certificate. Country and Common Name are the only required fields. For the

21

Common Name field, enter the IP address or DNS name of the server (the

Management Card or device). By default, a server certificate is valid for 10 years,
but you can edit the Validity Period Start and Validity Period End fields.

Because the configuration information is part of the signature, the
information for every certificate must be unique. The configuration of a
server certificate cannot be the same as the configuration of the CA root
certificate. (The expiration date is not considered part of the unique
configuration. Some other configuration information must also differ.)

6. On the next screen, review the summary of the certificate. Scroll downward to view
the certificate’s unique serial number and fingerprints. To make any changes to the
information you provided, click Back, and revise the information.

7. The last screen verifies that the certificate has been created and instructs you on
the next task, to load the server certificate to the Network Management Card or
network-enabled device. It displays the location and name of the Server Certificate,
which has a .p15 file suffix and contains the private key and public root certificate
of the Management Card or device.

Load the server certificate to the Ma nagement Card or device.

1. On the Administration tab, select Network on the top menu bar and ssl

certificate under the Web heading on the left navigation menu.

2. Select Add or Replace Certificate File, and browse to the server certificate, the

.p15 file you created in the procedure Create a Root Certificate and Server

Certificates. (The default location is C:\Program Files\American Power

Conversion\APC Security Wizard.)

SECURITY HANDBOOK

Network-E nabled Devic es, AOS v.3.x.x

If you use FTP or Secure CoPy (SCP) instead to transfer the server
certificate, you must specify the correct location, \sec, on the Management
Card or device. For SCP, the command to transfer a certificate named

cert.p15 to a Management Card or device with an IP address of

156.205.6.185 would be:

scp cert.p15 apc@156.205.6.185:\sec\cert.p15

22

Create a Server Certificate and Signing Request

Summary

Use this procedure if your company or agency has its own Certificate Authority
or if you plan to use a commercial Certificate Authority to sign your server
certificates.

• Create a Certificate Signing Request (CSR). The CSR contains all the information for
a server certificate except the digital signature. This process creates two output files:

– The file with the .p15 suffix contains the private key of the Network Management

Card or network-enabled device.

– The file with the .csr suf fix contains the certificate signing request, which you send

to an external Certificate Authority.

• When you receive the signed certificate from the Certificate Authority, import that
certificate. Importing the certificate combines the .p15 file containing the private key
and the file containing the signed certificate from the external Certificate Authority.
The output file is a new encrypted server certificate file with a .p15 suffix.

• Load the server certificate onto the Management Card or device.

• For each Management Card or device that requires a server certificate, repeat the
tasks that create and load the server certificate.

The procedure

Create the Certificat e Signing Request (CSR).

1. If the APC Security Wizard is not already installed on your computer, run the
installation program (APC Security Wizard.exe) by clicking the link Install the

Wizard in the interface of the Utility CD for the Management Card or device.

2. On the Windows Start menu, select Programs, then APC Security Wizard.

3. On the screen labeled Step 1, select Certificate Request as the type of file to

SECURITY HANDBOOK

Network-Enabled Devices, AOS v.3.x.x

create, and then select the length of the key to generate (use 1024 bits, which is
the default setting).

23

4. Enter a name for this file, which will contain the private key of the Management
Card or device. The file must have a .p15 suffix and, by default, will be created in
the installation folder C:\Program Files\American Power Conversion\APC

Security Wizard.

5. On the screen labeled Step 2, provide the information to configure the certificate
signing request (CSR), i.e., the information that you want the signed server
certificate to contain. The Country and Common Name fields are required. Other
fields are optional. For the Common Name field, enter the IP Address or DNS
name of the Management Card or device.

By default, a server certificate is valid for 10 years from the current date
and time, but you can edit the Validity Period Start and Validity Period

End fields.

6. On the next screen, review the summary of the certificate. Scroll downward to view
the certificate’s unique serial number and fingerprints. To make any changes to the
information you provided, click Back, and revise the information.

7. The last screen verifies that the certificate signing request was created and
displays the location and name of the file, which has a .csr extension.

8. Send the certificate signing request to an external Certificate Authority, either a
commercial Certificate Authority or, if applicable, a Certificate Authority managed
by your own company or agency.

SECURITY HANDBOOK

Network-E nabled Devic es, AOS v.3.x.x

The certificate’s subject information and the certificate’s issuer
information should be identical.

See the instructions provided by the Certificate Authority regarding the
signing and issuing of server certificates.

24

Import the si gned certificate. When the external Certificate Authority returns the

signed certificate, import the certificate. This procedure combines the signed certificate
and the private key into an SSL server certificate that you then upload to the Network
Management Card or network-enabled device.

1. On the Windows Start menu, select Programs, then APC Security Wizard.

2. On the screen labeled Step 1, select Import Signed Certificate.

3. Browse to and select the signed server certificate that you received from the
external Certificate Authority. The file has a .cer or .crt suffix.

4. Browse to and select the file you created in step 4 of the task Create the Certificate

Signing Request (CSR). This file has a .p15 extension, contains the private key of

the Management Card or device, and, by default, is in the installation folder

C:\Program Files\American Power Conversion\APC Security Wizard.

5. Specify a name for the output file that will be the signed server certificate that you
upload to the Management Card or device. The file must have a .p15 suffix.

6. Click Next to generate the server certificate. Issuer Information on the summary
screen confirms that the external Certificate Authority signed the certificate.

7. The last screen verifies that the certificate has been created and instructs you on
the next task, to load the server certificate to the Management Card or device. It
displays the location and name of the server certificate, which has a .p15 file
extension and contains the private key of the Management Card or device and the
public key obtained from the .cer or .crt file.

Load the server certificate to the Ma nagement Card or device.

1. On the Administration tab, select Network on the top menu bar and ssl

certificate under the Web heading on the left navigation menu.

2. Select Add or Replace Certificate File, and browse to the server certificate, the

.p15 file you created in the procedure Create a Root Certificate and Server

Certificates. (The default location is C:\Program Files\American Power

SECURITY HANDBOOK

Network-E nabled Devic es, AOS v.3.x.x

Conversion\APC Security Wizard.)

25

Alternatively, you can use FTP or Secure CoPy (SCP) to transfer the server
certificate to the Management Card or device. If you use FTP or SCP for the
transfer, you must specify the location, \sec, on the Management Card or
device. For SCP, the command to transfer a certificate named cert.p15 to a
Management Card or device with an IP address of 156.205.6.185 would be:

scp cert.p15 apc@156.205.6.185:\sec\cert.p15

Create an SSH Host Key

Summary

This procedure is optional. If you select SSH encryption, but do not create a host key,
the Network Management Card or network-enabled device generates a 768-bit RSA
key when it reboots. You must define a key size of 1024 bits for SSH host keys that are
created with the APC Security Wizard.

• Use the APC Security Wizard to create a host key, which is encrypted and stored in a
file with the .p15 suffix.

• Load the host key onto the Management Card or device.

The procedure

Create the host key.

1. If the APC Security Wizard is not already installed on your computer, run the
installation program (APC Security Wizard.exe) by clicking the link Install the

Wizard in the interface of the Utility CD for the Management Card or device.

2. On the Windows Start menu, select Programs, then APC Security Wizard.

3. On the Step 1 screen, select SSH Server Host Key as the type of file to create,
and then select the length of the key to generate (use 1024 bits, which is the
default setting).

SECURITY HANDBOOK

Network-E nabled Devic es, AOS v.3.x.x

26

4. Enter a name for this file, which will contain the host key. The file must have a .p15
suffix. By default, the file will be created in the installation folder C:\Program

Files\American Power Conversion\APC Security Wizard.

5. Click Next to generate the host key.

6. The summary screen displays the SSH version 1 and version 2 fingerprints, which
are unique for each host key and identify the host key. After you load the host key
onto the Management Card or device, you can verify that the correct host key was
uploaded by verifying that the fingerprints displayed here match the SSH
fingerprints on the Management Card or device, as displayed by your SSH client
program.

7. The last screen verifies that the host key was created, instructs you to load the host
key to the Management Card or device, and displays the location and name of the
host key, which has a .p15 file suffix.

Load the host key to the Manage me nt Card or device.

1. On the Administration tab, select Network on the top menu bar, and ssh host

key under the Console heading on the left navigation menu.

2. Select Add or Replace Host Key, and browse to the host key, the .p15 file you
created in the procedure Create the host key. (The default location is C:\Program

Files\American Power Conversion\APC Security Wizard.)

3. At the bottom of the User Host Key page, note the fingerprint for the version (or
versions) of SSH you are using. Then log on to the Management Card or device
through your SSH client program, and verify that the correct host key was uploaded
by verifying that these fingerprints match the fingerprints that the client program
displays.

SECURITY HANDBOOK

Network-E nabled Devic es, AOS v.3.x.x

Alternatively , you can use FTP or Secure CoPy (SCP) to transfer the host key
file to the Management Card or device. If you use FTP or SCP for the transfer ,
you must specify the location, \sec, on the Management Card or device. For
SCP, the following command would transfer a host key named hostkey.p15
to a Management Card or device with an IP address of 156.205.6.185:

scp hostkey.p15 apc@156.205.6.185:\sec\hostkey.p15

27

Control Console Access and Security

Introduction

You can access the control console through Telnet or Secure SHell (SSH), depending
on which is enabled. (An Administrator can enable these access methods by selecting
the Administration tab, then Network on the top menu bar and access under the

Console heading on the left navigation menu.) By default, Telnet is enabled. Enabling

SSH automatically disables Telnet.

Telnet for basic access. Telnet provides the basic security of authentication by user

name and password, but not the high-security benefits of encryption.

SSH for high-security access. If you use the high security of SSL for the Web

interface, use Secure SHell (SSH) for access to the control console. SSH encrypts user
names, passwords, and transmitted data.

The interface, user accounts, and user access rights are the same whether you access
the control console through SSH or Telnet, but to use SSH, you must first configure
SSH and have an SSH client program installed on your computer.

Telnet and Secure SHell (SSH)

While SSH is enabled, you cannot use Telnet to access the control console. Enabling
SSH enables SCP automatically.

When SSH is enabled and its port and encryption ciphers are configured, no
further configuration is required to use Secure CoPy (SCP). SCP uses the
same configuration as SSH.

SECURITY HANDBOOK

Network-E nabled Dev ices, AOS v.3. x.x

Do not enable both versions of SSH unless you require that both be activated at the
same time. (Security protocols use extensive processing power.)

28

To use SSH, you must have an SSH client installed. Most Linux and other
UNIX
systems do not. SSH clients are available from various vendors.

To configure the options for Telnet and Secure SHell (SSH):

1. On the Administration tab of the Web interface, select Network on the top menu
bar, and select access under the Console heading on the left navigation menu.

2. Configure the port settings for Telnet and SSH.

3. Under Console on the left navigation menu, select ssh encryption, and select
one or more data encryption algorithms for SSH version 1, SSH version 2, or both.

Option Description

SSH v1 Enables or disables DES and displays the status (always enabled) of Blowfish,

®

platforms include an SSH client, but Microsoft Windows operating

For information on the extra security a non-standard port provides, see

Port assignments.

two encryption algorithms (block ciphers) compatible with SSH version 1 clients.

•DES

• Blowfish: Yo u cannot disable this algorithm.

SECURITY HANDBOOK

Network-E nabled Devic es, AOS v.3.x.x

OTE: Not all SSH clients can use every algorithm. If your SSH client cannot use

N
Blowfish, you must also enable DES.

SSH v2 Enables or disables the following encryption algorithms (block ciphers) that are

compatible with SSH version 2 clients.

• 3DES (enabled by default)

• Blowfish (enabled by default)

• AES 128

• AES 256

OTE: Your SSH client selects the algorithm that provides the highest security

N

from among the enabled algorithms that it is able to us e. (If your SSH client
cannot use either default algorithm, you must enable an AES algorithm that it can
use.)

29

4. Under Console on the left navigation menu, select ssh host key, specify a host
key file previously created with the APC Security Wizard, and load it to the
Management Card or device.

If you do not specify a host key file here, if you install an invalid host key, or if you
enable SSH with no host key installed, the Management Card or device generates
an RSA host key of 768 bits, instead of the 1024-bit RSA host key that you create
using the Security Wizard. For the Management Card or device to create a host
key, it must reboot. The Management Card or device can take up to 5 minutes

to create this host key, and SSH is not accessible during that time.

Alternatively, from a command line interface, such as the command
prompt on Windows operating systems, you can use FTP or Secure
CoPy (SCP) to transfer the host key file. You must transfer the file to the
location \sec on the Management Card or device.

5. Display the fingerprint of the SSH host key for SSH versions 1 and 2. Most SSH
clients display the fingerprint at the start of a session. Compare the fingerprint
displayed by the client to the fingerprint that you recorded from the Web interface
or control console of the Management Card or device

SECURITY HANDBOOK

Network-E nabled Devic es, AOS v.3.x.x

.

If you are using SSH version 2, expect a noticeable delay when logging on to
the control console of the Management Card or device.

30

Web Interface Access and Security

HTTP and HTTP S (with SSL)

HyperText Transfer Protocol (HTTP) provides access by user name and password, but
does not encrypt user names, passwords, and data during transmission. HyperText
Transfer Protocol over Secure Sockets Layer (HTTPS) encrypts user names,
passwords, and data during transmission, and provides authentication of the Network
Management Card or network-enabled device by means of digital certificates.

See Creating and Installing Digital Certificates to choose among the
several methods for using digital certificates.

To configure HTTP and HTTPS:

1. On the Administration tab, select Network on the top menu bar and access
under Web on the left navigation menu.

2. Enable either HTTP or HTTPS and configure the ports that each of
the two protocols will use. Changes take effect the next time you log
on. When SSL is activated, your browser displays a small lock icon.

For information on the extra security a non-standard port provides, see

Port assignments.

3. Select ssl cipher suites under Web on the left navigation menu, and select the
encryption ciphers that SSL will use.

4. Select ssl certificate under Web on the left navigation menu to determine
whether a server certificate is installed on the Management Card or device. If a
certificate was created with the APC Security Wizard but is not installed:

• In the Web interface, browse to the certificate file and upload it to the
Management Card or device.

SECURITY HANDBOOK

Network-E nabled Devic es, AOS v.3.x.x

• Alternatively, use the Secure CoPy (SCP) protocol or FTP to upload the
certificate file to the location \sec on the Management Card or device.

31

Creating and uploading a server certificate in advance reduces the time
required to enable HTTPS. If you enable HTTPS with no server certificate
loaded, the Management Card or device creates one when it reboots.

The Management Card or device can take up to 5 minutes to create
the certificate, and the SSL server is unavailable during that time.

A certificate that the Management Card or device generates has some
limitations. See Method 1: Use the default certificate auto-generated by

the Network Management Card or network-enabled device

5. If a valid digital server certificate is loaded, the Status field displays the link

Valid Certificate. Click the link to display the parameters of the certificate.

Parameter Description

Issued To: Common Name (CN): The I P Address or DNS name of the Management

Card or device. This field controls how you must log on to the Web interface.

• If an IP address was specified for this field when the certificate was
created, use an IP address to log on.

• If the DNS name was specified for this field when the certificate was
created, use the DNS name to log on.

If you do not use the IP address or DNS name that was specified for the
certificate, authenticatio n fails, and you receive an error message asking if
you want to continue.

For a server certificate generated by default by the Management Card or
device, this f ield displays the serial number of the Management Card or
device instead.

Organization (O), Organizational Unit (OU), and Local ity, Countr y: The

name, organizational unit, and location of the organization using the server
certificate. For a server cert ificate generated by default by the Management
Card or device, the Organizational Unit (OU) field displays “Internally
Gener a te d Ce rti fic at e. ”

.

SECURITY HANDBOOK

Network-E nabled Devic es, AOS v.3.x.x

Serial Number: The serial number of the server certificate.

32

Parameter Description

Issued By: Common Name (CN): The Common Name as specified in the CA root

certificate. For a server cert ificate generated by default by the Management
Card or devi ce, this field disp lays t he ser ial n umber of the Mana gement Card
or device instead.

Organization (O) an d Organizational Uni t (OU): The name and

organi zat io nal un i t of t he o r ga niza t ion th at is s ued th e se r ver ce rt i fi cat e . I f the
server certificate was generated by default by the Management Card or
device, this field displays “Internally Generated Certificate.”

Validity: Issued on: The date and time at which the certificate was issued.

Expires on: The date and time at which the certificate expires.

Fingerprints Each of the two fingerprints is a long string of alphanumeric characters,

punctuated by colons. A fingerprint is a unique identifier to further
authenticate the server. Record the fingerprints to compare them with the
fingerprints contained in the certificate, as displayed in the browser.

SHA1 Fingerprint: A fingerprint created by a Secure Hash Algorithm (SHA).
MD5 Fingerprint: A fingerprint created by a Message Digest 5 (MD5)

algorithm.

SECURITY HANDBOOK

Network-E nabled Devic es, AOS v.3.x.x

33

RADIUS

Supported RADIUS Functions and Servers

Supported functions

APC supports the authentication and authorization functions of Remote Authentication
Dial-In User Service (RADIUS). Use RADIUS to administer remote access for each
Network Management Card or network-enabled device centrally. When a user
accesses the Management Card or device, an authentication request is sent to the
RADIUS server to determine the user’s permission level.

For more information on permission levels, see Types of user accounts.

Supported RADIUS servers

APC supports FreeRADIUS and Microsoft IAS 2003. Other commonly available
RADIUS applications may work but have not been fully tested by APC.

Configure the Management Card or Device

Authentication

RADIUS user names used with APC Network Management Cards or devices
are limited to 32 characters.

On the Administration tab, select Security on the top menu bar . Then, under Remote

Users on the left navigation menu, select Authentication Method:

SECURITY HANDBOOK

Network-E nabled Dev ices, AOS v.3. x.x

• Local Authentication Only: RADIUS is disabled. Local authentication is enabled.

34

• RADIUS, then Local Authentication: Both RADIUS and local authentication are
enabled. Authentication is requested from the RADIUS server first; local
authentication is used only if the RADIUS server fails to respond.

• RADIUS Only: RADIUS is enabled. Local authentication is disabled.

If RADIUS Only is selected, and the RADIUS server is unavailable,
improperly identified, or improperly configured, remote access is
unavailable to all users. You must use a serial connection to the control
console and change the Access setting to Local Authentication Only or

RADIUS, then Local Authentication to regain access.

RADIUS

To configure RADIUS, on the Administration tab, select Security on the top menu
bar. Then, under Remote Users on the left navigation menu, select RADIUS.

Setting Definition
RADIUS

Server

Secret The secret shared between the RADIUS server and the Management Card or

Timeout The time in seconds that the Management Card or device waits for a response

Test
Settings

Skip Test
and Apply

Switch
Server

SECURITY HANDBOOK

Network-E nabled Devic es, AOS v.3.x.x

Priority

The server name or IP address of the RADIUS server.

OTE: RADIUS servers use port 1812 by default to authenticate users. To use a

N

different port, add a colon followed by the new port number to the end of the
RADIUS server name or IP address

device.

from the RADIUS server.
Enter th e Admin i st rat or user nam e and pa sswo r d to te st t he RA DI US ser ve r pat h

that you have configured.
Do not test the RADIUS server path.

Change which RADIUS server will authenticate users if two configured servers
are listed and RADIUS, then Local Authentication or RADIUS Only is the
enabled authentication method.

35

.

Configure the RADIUS Server

You must configure your RADIUS server to work with the Management Card or
network-enabled device. The examples in this section may differ somewhat from the
required content or format of your specific RADIUS server. In the examples, any
reference to outlets applies only to APC devices that support outlet users.

1. Add the IP address of the Network Management Card or network-enabled
device to the RADIUS server client list (file).

2. Users must be configured with Service-Type attributes unless Vendor Specific
Attributes (VSAs) are defined instead. If no Service-Type attribute is configured,
the user has read-only access (to the Web interface only). The two acceptable
values for Service-Type are Administrative-User (6), which gives the user
Administrator permissions, and Login-User (1), which gives the user Device
permissions.

See your RADIUS server documentation for information about the
RADIUS users file.

Example using Service-Type Attributes

In the following example of a RADIUS users file:
– UPSAdmin corresponds to Service-Type: Administrative-User, (6)
– UPSDevice corresponds to Service-Type: Login-User, (1)
– UPSReadOnly corresponds to Service-Type: null

UPSAdmin Auth-Type = Local, Password = "admin"

Service-Type = Administrative-User

UPSDevice Auth-Type = Local, Password = "device"

Service-Type = Login-User

SECURITY HANDBOOK

Network-Enabled Devices, AOS v.3.x.x

UPSReadOnly Auth-Type = Local, Password = "readonly"

36

Examples using Vendor Specific Attributes

Vendor Specific Attributes (VSAs) can be used instead of the Service-Type attributes
provided by your RADIUS server. This method requires a dictionary entry and a
RADIUS users file. In the dictionary file, you can define the names for the ATTRIBUTE
and VALUE keywords, but not the numeric values. If you change the numeric values,
RADIUS authentication and authorization will not work correctly. VSAs take
precedence over standard RADIUS attributes.

Dictionary file. Following is an example of a RADIUS dictionary file (dictionary.apc):

#
# dictionary.apc
#
#
VENDOR APC 318
#
# Attributes
#
ATTRIBUTE APC-Service-Type 1 integer APC
ATTRIBUTE APC-Outlets 2 string APC

VALUE APC-Service-Type Admin 1
VALUE APC-Service-Type Device 2
VALUE APC-Service-Type ReadOnly 3
#
# For devices with outlet users only
#
VALUE APC-Service-Type Outlet 4

SECURITY HANDBOOK

Network-E nabled Devic es, AOS v.3.x.x

37

RADIUS Users file with VSAs. Following is an example of a RADIUS users file with

VSAs:

VSAAdmin Auth-Type = Local, Password = "admin"

APC-Service-Type = Admin

VSADevice Auth-Type = Local, Password = "device"

APC-Service-Type = Device

VSAReadOnly Auth-Type = Local, Password = "readonly"

APC-Service-Type = ReadOnly

# Give user access to device outlets 1, 2 and 3.
VSAOutlet Auth-Type = Local, Password = "outlet"

APC-Service-Type = Outlet,

APC-Outlets = "1,2,3"

See the following related topics:

• Types of user accounts for information on the three basic user permission
levels (Administrator, Device User, and Read-Only User). If your APC
device has an additional user account type, e.g., outlet user for a Switched

SECURITY HANDBOOK

Network-E nabled Devic es, AOS v.3.x.x

Rack PDU, see the device’s User’s Guide for information on the additional
account type

• Supported RADIUS servers for information on RADIUS servers tested and
supported by APC.

38

Example with UNIX shadow passwords. If UNIX shadow password files are used

(/etc/passwd) with the RADIUS dictionary files, the following two methods can be used
to authenticate users:

• If all UNIX users have administrative privileges, add the following to the RADIUS
“user” file. To allow only Device Users, change the APC-Service-Type to Device.

DEFAULT Auth-Type = System
APC-Service-Type = Admin

• Add user names and attributes to the RADIUS "user" file, and verify password
against /etc/passwd. The following example is for users bconners and thawk:

bconners Auth-Type = System

APC-Service-Type = Admin

thawk Auth-Type = System

APC-Service-Type = Outlet
APC-Outlets = "1,2,3"

SECURITY HANDBOOK

Network-E nabled Devic es, AOS v.3.x.x

39

Index

A

Access options for each interface 3
Administrator account 2
Authentication

for Web Int erf ace and Control Cons ole 7
with RADIUS 34
with SNMPv3 7
with SSL 9

B

Browsers

CA certificates in browser’s store (cache) 10
danger o f le av ing browser open 10
lock icon w hen SSL is inst alled 9

E

Encryption

with SNMPv3 8
with SSH and SCP for the Control Console 8
with SSL for the Web interface 31

F

Fingerprints, displaying and comparing 30
FTP

disabling FTP if you use SSH and SCP 9
for transferring host keys 30
for transferring server certificates 22, 31
using a non-standard port for extra security 6

H

C

Host keys

Certificates

choosing which method to use 11
creating and installing for SSL 11
methods

APC Security Wizard creates all

certificates

Use a Certificate Authority (CA) 14
Use the APC default certificate 12

Cipher suites

encryption ciphers for SSH v1 and v2. 29
purpose of t he algorithms and ciphers 10

Configuring

SSH 28
SSL 31

SECURITY HANDBOOK

Network-E nabled Dev ices, AOS v.3. x.x

D

13

creating with the Security Wizard 26
generated by the Management Card or device 30
transferring to the Management Card or device 30

P

Passwords

change im mediately f or s ecurity 6
using non-standards ports a s ex tr a password s 6

Ports, assigning 6

R

RADIUS Server setting 35
Read-only user account 2
Root certificates, creating 19

Device user account 2

40

S

SCP

enabled and configured with SSH 9, 28
for encrypted file transfer 8
for transferring host keys 27
for transferring server certif icate s 22, 26
using non-standard port 6

Secure CoPy. See SCP.
Secure SHell. See SSH.
Secure Sockets Layer. See SSL
Security

authentication

through digital certificates with SSL 9
through RADIUS 34
with SSH and SCP 8

certificate-signing requests 10
disabling less secure interfaces 8, 9
encryption with SSH and SCP 8
how certificates are used 16
how SSH host keys are u sed 17
immedia t ely c hanging us ername an d password 6
options for each interface 3
SCP as al te rnative to FT P 9
SSL

choosing a method to use certificates 11
cipher suites algorithms and ciphers 10

summary of access methods 3
supported SSH clien t s 29
using non-standards ports as ex t ra passwo rds 6

Security menu

local users, defining access 2
RADIUS settings 35
remote users, authentication 34

Security Wizard 16

creating ce rt if ic at es

to use with a Certificate Authority 23
without a Certificate Authority 19

SECURITY HANDBOOK

Network-Enabled Devices, AOS v.3.x.x

creating si gning reques t s 23
creating SSH host keys 26

Server certificates

creating to use with a Certificate Authority 23
creating without a Certificate Authority 19

Signing requests, creating 23
SNMP

v1

disabling 6
REA D access 6

v3

authentication 7
encryption 8

SSH

configuring 28
enabling 28
encryption 8
fingerprints, displaying and comparing 30
host key

as identifier that cannot be falsified 8
creating with the Security Wizard 26
transferring to the Management Card or device 30

obtaining an SSH client 29
server configuration 29
v1 and v2 en c ryption algorithms 29

SSL

authentication thro ugh digital

certificates 9

certific at e s igning requests 10

T

Timeout setting for RADIUS 35

U

User accounts, types 2
User Name, change immediately for security 6

41

APC Worldwide Customer Support

Customer support for this or any other APC product is available at no charge in any of the
following ways:

• Visit the APC We b site to access documents in the AP C K nowled ge Ba se a nd to submit
customer support requests.

– www.apc.com (Corporate Headquarters)

Connect to localized APC Web sites for specific countries, each of which provides
customer support information.

– www.apc.com/support/

Global support searching APC Knowledge Base and usi ng e-support.

• Contact the APC Customer Support Center by telephone or e-mail.
– Local, country-specific centers: go to www.apc.com/support/contact for contact

information.

For information on how to obtain local customer support, contact the APC representative or
other distributors from whom you purchased your APC product.

SECURITY HANDBOOK

Network-E nabled Devic es, AOS v.3.x.x

42

Copyright

Entire contents copyright 2009 American Power Conversion Corporation. All
rights reserved. Reproduction in whole or in part without permission is prohibited.
APC, the APC logo, and InfraStruXure are trademarks of American Power
Conversion Corporation. All other trademarks, product names, and corporate
names are the property of their respective owners and are used for informational
purposes only.

Cryptlib, the toolkit used to develop the library of cryptographic routines in the
Network Management Card: copyright © 1998 Digital Data Security, Ltd., New
Zealand.

SECURITY HANDBOOK

Network-E nabled Devic es, AOS v.3.x.x

990-2417D-001 1/2009

43