security configuration guide - dell › zh-tw › collaterals › unauth › ...control to the...

Dell EMC Data Domain®Version 6.1

Security Configuration Guide302-003-722

REV 02

Copyright © 2014-2018 Dell Inc. and its subsidiaries. All rights reserved.

Published January 2018

Dell believes the information in this publication is accurate as of its publication date. The information is subject to change without notice.

THE INFORMATION IN THIS PUBLICATION IS PROVIDED “AS-IS.“ DELL MAKES NO REPRESENTATIONS OR WARRANTIES OF ANY KIND

WITH RESPECT TO THE INFORMATION IN THIS PUBLICATION, AND SPECIFICALLY DISCLAIMS IMPLIED WARRANTIES OF

MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. USE, COPYING, AND DISTRIBUTION OF ANY DELL SOFTWARE DESCRIBED

IN THIS PUBLICATION REQUIRES AN APPLICABLE SOFTWARE LICENSE.

Dell, EMC, and other trademarks are trademarks of Dell Inc. or its subsidiaries. Other trademarks may be the property of their respective owners.

Published in the USA.

Dell EMCHopkinton, Massachusetts 01748-91031-508-435-1000 In North America 1-866-464-7381www.DellEMC.com

2 Data Domain 6.1 Security Configuration Guide

Preface 5

Revision history 9

Overview 11Data Domain system security...................................................................... 12The Data Domain Operating System........................................................... 12System interfaces and access control......................................................... 12

Security configuration settings 15Introduction................................................................................................ 16Access control settings............................................................................... 16

System access............................................................................... 16User authentication........................................................................19User authorization ........................................................................ 22Component access control............................................................ 22

Log settings................................................................................................22Log descriptions............................................................................ 23Log management and retrieval.......................................................23

Communication security settings................................................................24Data Domain TCP and UDP ports.................................................. 24System manager port usage.......................................................... 26Administration/Support protocols ................................................ 26Data transfer protocols..................................................................27Network routing management....................................................... 28

Cloud tier network security recommendations............................................28Certificates for cloud providers..................................................... 29

Secure Multi-Tenancy (SMT) security....................................................... 30Data security settings................................................................................. 31

Data Domain Retention Lock software .......................................... 31Data integrity.................................................................................32End-to-End verification................................................................. 33Data erasure.................................................................................. 33System sanitization....................................................................... 33Data encryption............................................................................. 33

EMC Secure Remote Services....................................................................37Security alert system settings.................................................................... 37Other security considerations.....................................................................38

Avoiding man-in-the-middle (MITM) attacks ................................38System hardening..........................................................................38

Secure deployment and usage settings 41Secure deployment settings....................................................................... 42

Secure Maintenance 43Security patch management.......................................................................44Data migration............................................................................................ 44

Chapter 1

Chapter 2

Chapter 3

Chapter 4

CONTENTS

Data Domain 6.1 Security Configuration Guide 3

Physical Security Controls 45Physical controls........................................................................................ 46Baseboard Management Controller (BMC) and Basic Input/Output System(BIOS) recommendations...........................................................................46General USB security best practices.......................................................... 46Securing Integrated Dell Remote Access Controller 9 (iDRAC) for DD3300...47

Chapter 5

CONTENTS


Preface

As part of an effort to improve our products, software and hardware revisions areperiodically released. Therefore, some functions that are described in this documentmight not be supported by all versions of the software or hardware currently in use.The product release notes provide the most up-to-date information on productfeatures, software updates, software compatibility guides, and information about ourproducts, licensing, and service.

Contact a technical support professional if a product does not function correctly ordoes not function as described in this document.

PurposeThis document describes the key security features of Data Domain systems andprovides the procedures that are required to ensure data protection and appropriateaccess control.

AudienceThis document is primarily intended for our Field Engineers, contractedrepresentatives, and business partners who are responsible for configuring,troubleshooting, and upgrading Data Domain systems at customer sites. Systemadministrators or application integrators who are responsible for installing software,maintaining servers and clients on a network, and ensuring network security shouldalso be aware of the contents of this document.

Related documentationThe following publications provide additional information:

l Data Domain Operating System Release Notes

l Data Domain Operating System Administration Guide

l Data Domain Operating System Initial Configuration Guide

l Data Domain Operating System Command Reference Guide

l Data Domain Operating System MIB Quick Reference

l Installation and setup guide for the system, for example, Data Domain DD 2500Storage System, Installation and Setup Guide

l Hardware overview guide for the system, for example, Data Domain DD4200,DD4500, and DD7200 Systems, Hardware Overview

l Data Domain, System Controller Upgrade Guide

l Data Domain Expansion Shelf, Hardware Guide (for shelf model DS60 or ES30)

If you have the optional RSA Data Protection (DPM) Key Manager, see the latestversion of the RSA Data Protection Manager Server Administrator's Guide, available withthe RSA Data Protection Manager product.

Preface 5

Special notice conventions used in this documentThe following conventions are used for special notices:

DANGER

If not avoided, indicates a hazardous situation which results in death or seriousinjury.

WARNING

If not avoided, indicates a hazardous situation which could result in death orserious injury.

CAUTION

If not avoided, indicates a hazardous situation which could result in minor ormoderate injury.

NOTICE

Addresses practices that are not related to personal injury.

Note

Presents information that is important, but not hazard-related.

Typographical conventions

Table 1 Style conventions

Bold Used for names of interface elements, such as names of windows,dialog boxes, buttons, fields, tab names, key names, and menu paths(what the user specifically selects or clicks)

Italic Used for full titles of publications that are referenced in text

Monospace Used for:

l System code

l System output, such as an error message or script

l Pathnames, filenames, prompts, and syntax

l Commands and options

Monospace italic Used for variables

Monospace bold Used for user input

[ ] Square brackets enclose optional values

| Vertical bar indicates alternate selections - the bar means “or”

{ } Braces enclose content that the user must specify, such as x or y orz

... Ellipses indicate nonessential information that is omitted from theexample

Where to get helpSupport, product, and licensing information can be obtained as follows:

Preface


Product information

For documentation, release notes, software updates, or additional productinformation, go to the support site at https://support.emc.com.

Technical support

Go to the online support site and click Service Center. You will see several optionsfor contacting Technical Support. Note that to open a service request, you musthave a valid support agreement. Contact a sales representative for details aboutobtaining a valid support agreement or with account questions.

CommentsSuggestions help continue to improve the accuracy, organization, and overall qualityof the user publications. Send opinions of this document to mailto:[email protected].

Note

This document was accurate at publication time. Go to the online support site toensure that you are using the latest version of this document.

Preface

7

https://support.emc.com

mailto:[email protected]

Preface


Revision history

The following table presents the revision history of this document.

Table 2 Document revision history

Revision Date Description

02 January 2018 Updated to include general information relating to NFSv4,BMC security practices, BIOS password disabling, andiDRAC for the DD3300.

01 June 2017 Updated for DD OS 6.1

Revision history 9

Revision history


CHAPTER 1

Overview

This chapter includes:

l Data Domain system security..............................................................................12l The Data Domain Operating System................................................................... 12l System interfaces and access control................................................................ 12

Overview 11

Data Domain system securityData Domain systems, as central repositories for both structured and unstructuredbackup data, have many security capabilities and attributes to protect the data on theData Domain systems. This document is a supplement to the Data Domain OperatingSystem Administration Guide and provides an overview of key security features andprocedures that are required to ensure data protection and appropriate accesscontrol.

Data Domain High Availability (HA)In a Data Domain High Availability (HA) configuration, there are two controllers, whereonly one at a time is active, and are logically considered as a single file system.

l Both systems have the same Root Certificate Authority.

l To establish mutual trust with the HA system, trust is required to be establishedwith the active node ONLY.

l Mutual trust, Certificate signing request and all the imported certificates on theactive node are mirrored to the standby node.

l Host certificate is generated per node and is used for HTTPS application.Certificate Authority (CA) for secure support bundle upload is also kept per node.

The Data Domain Operating SystemA Data Domain system is an appliance that runs the Data Domain Operating System(DD OS). A web-based graphical user interface (GUI), Data Domain System Manager,is provided for configuration operations, management, and monitoring. In addition, acontrolled command-line interface (CLI) environment is available, which provides acomplete set of Data Domain administrative operations.

Because DD OS is an embedded operating system, additional software or agentscannot be installed or executed within a Data Domain system. This restriction ensurescontrol and consistency of DD OS releases and provides additional security over thesystem.

Data Domain systems are purpose-built appliances with restricted access to theirinternal operation. Any tampering voids the warranty. Updated versions of embeddedopen source modules are included in DD OS updates as appropriate.

System interfaces and access controlHosts and backup applications interface with the Data Domain systems through one ormore of the standard native server interface protocols: CIFS/NFS, NDMP, VTL, orData Domain Boost.

Access control and user authentication to the Data Domain system is controlled byeither local users, NIS environments, or within a Microsoft Active Directory Domainenvironment. Other points that run the security attributes of the Data Domain systemare listed in the simplified diagram.

Overview


Figure 1 System interfaces and access control

The following Data Domain native protocols and software options depend on or enablesecurity attributes of the Data Domain system. See the current DD OS administrationguide for more information.

Supported Native Ingest ProtocolsData Domain systems support simultaneous access via common network accessprotocols, allowing both backup servers and application servers to send data to theData Domain system. Servers can attach and transfer files and backup images overone or more of these protocols:

l CIFS

l NFS (encryption with Kerberos)

l Data Domain Boost over Ethernet (encryption supported over IP)

l Data Domain Boost over Fibre Channel

l NDMP

l VTL over Fibre Channel

l vDisk over Fibre Channel

Data that is transmitted over CIFS, NDMP, Data Domain Boost, VTL over FibreChannel, and vDisk over Fibre Channel is transported. User authentication and accesscontrol to the related network ports is important.

The following software options are related to security and require separate licenses:

Data Domain Replicator SoftwareAutomated, policy-based, network-efficient replication for disaster recovery, remoteoffice data protection, and multi-site tape consolidation. Data Domain Replicator

Overview

System interfaces and access control 13

software asynchronously replicates only the compressed, deduplicated data over theWAN or LAN during the backup process, making network-based replication fast,reliable, and cost-effective.

For environments that do not leverage a VPN for secure connections between sites,DD Replicator software can securely encapsulate its replication payload over SSL withAES 256-bit encryption for secure transmission over the wire. This process is alsoknown as encrypting data in flight.

Data Domain Encryption SoftwareProtects backup and archive data that is stored on Data Domain systems with dataencryption that is performed inline before the data is written to disk. The Encryptionat Rest feature satisfies internal governance rules, compliance regulations, andprotects against the reading of customer data on individual disks or disk shelves thatare removed from the system due to theft.

Data Domain Retention Lock SoftwarePrevents specified files from being overwritten, modified, or deleted for a user-defined retention period of up to 70 years.

Data Domain Secure Multi-Tenancy SoftwareProvides secure storage consolidation in multi-tenant backup environments. WithSMT, multiple tenants can reside on a single Data Domain system simultaneously andthe data of one tenant cannot be detected or accessed by another.

Overview


CHAPTER 2

Security configuration settings


l Introduction........................................................................................................ 16l Access control settings...................................................................................... 16l Log settings....................................................................................................... 22l Communication security settings....................................................................... 24l Cloud tier network security recommendations................................................... 28l Secure Multi-Tenancy (SMT) security...............................................................30l Data security settings.........................................................................................31l EMC Secure Remote Services........................................................................... 37l Security alert system settings............................................................................37l Other security considerations............................................................................ 38

Security configuration settings 15

IntroductionThis chapter provides an overview of the settings available to ensure the secureoperation of the product.

Access control settingsAccess control settings enable the protection of resources against unauthorizedaccess.

System accessThe Data Domain operating environment provides secure administration through eitherthe Data Domain System Manager via HTTPS or Secure Shell (SSH) for CLI. Eithermethod allows locally defined users, Network Information Service (NIS) users, andMicrosoft Active Directory (AD) domain users.

DD System Manager via HTTPS

The Data Domain system can use its self-signed identity certificate to establish atrusted connection to manage the Data Domain system over SSL.

Secure Shell (SSH) for CLI

The administrator enters a controlled shell environment, where individual CLIcommands are executed to manage the Data Domain system

Note

When connecting to the HA system via the floating hostname/IP using an SSH client,the public key that is stored in the known-hosts list of the local shell may failverification. Each node in the HA pair generates a unique SSH key pair, and the activenode presents the key that it owns. Resolution for this issue is to physically verify thatthe correct system is connecting, and remove the offending key in the known-host listand revalidate the key on the next connection try. Knowledge Base article #212538has been developed to explain this issue in more detail.

Administrative system access can be either local or remote.

Local access

Authorized administrators with valid login credentials have access to CLI via serialconsole or IP in same subnet. User is prompted for username and password, andafter authentication and authorization, they are granted login access.

Note

Policies outside the Data Domain system should be put in place for users to log outafter the session is over.

Remote Access

CLI and Web-based System Manager remote access are available for authorizedadministrators with proper login credentials (username and password). Remoteusers with network access and authorization can remotely administer the DataDomain systems over the network.



Note

Secure shell and secure browsing (HTTPS) are enabled on the Data Domain system bydefault. The recommendation is to configure session timeout values in Data DomainSystem Manager to ensure that users are automatically logged out of the system afterthe session is over. A session timeout maximum of 5 minutes is recommended.

Password-less login is supported by SSH, the GUI, and REST API connections throughthe use of client certificates. For more information about certificate-based login, seethe Data Domain Operating System 6.1 Administration Guide.

Data Domain systems feature security protocols and SSH keys to control access tothe data residing on the system. Data is not readily viewable from anywhere except ahost that has been granted access. The following methods are available in a DataDomain system:

Host-based access lists

Administrator access is required to configure the Data Domain system and adjustwhich physical hosts can view an exported mount point. Users with administrativeaccess can update the access list with a server’s hostname or IP address. A DataDomain system can use DNS for name resolution. For greater protection,administrators can hard code entries in the hosts file to control host/portresolution.

File Permissions

Files that are created on the Data Domain system are “owned” by the creator. Forexample, backup software typically writes files as a particular user, so that userwould own all files that the backup software that is created on the system.Explicit Windows permissions (ACLs) must be set, however, to prevent usersfrom viewing files that are created by others.

Note

NFSv4 also supports the use of ACLs for file permissions.

Microsoft CIFS and NFSv4

For every file or folder that is created through CIFS, the following attributes arecreated:

l Owner SID

l Group SID

l DACL (Discretionary ACL – Permissions)

l SACL (System ACL – Auditing Information)

l DOS Attributes such as READONLY, HIDDEN, SYSTEM & ARCHIVE

In addition, folders and files map UNIX UID/GID/MODE from Windows Owner-SID/Group-SID/DACL. The DACL is inherited from its parent. If the parentdirectory does not have DACL (created though NFS/non-CIFS), then a defaultACL is assigned. The default gives the owner full control and gives others readpermission. Access control is managed through the standard MicrosoftManagement Control (MMC) on any client with permissions to do so.

Linux NFS

Files and folders that are created through the remaining ingest protocols use thePOSIX.1e ACL standard or NFSv4 native ACLs through the nfs4_setaclcommand. Every object is associated with three sets of permissions that define


System access 17

access for the owner, the owning group, and for others. Each set may containRead [r], Write [w], and Execute [x] permissions. This scheme is implementedusing only 9 bits for each object. In addition to these 9 bits, the Set User Id, SetGroup Id, and Sticky bits are used for a number of special cases. Access control ismanaged through a standard Linux client or Data Domain system CLIadministration environment with permissions to do so.

DD Boost™

Files and directories that are created using DD Boost APIs are created with themode (or permission) bits specified by the creator. Thus each object is associatedwith three sets of permissions that define access for the owner, the owninggroup, and for others. Each set may contain Read [r], Write [w], and Execute [x]permissions. The mode bits can be changed appropriately via a DD Boost changemode API.

Microsoft Active Directory (AD) Services

Data Domain systems can use Microsoft Active Directory pass-throughauthentication for the users/servers. Administrators can enable certain domainsand groups of users to access files that are stored on the Data Domain system.

Note

Microsoft Windows NT LAN Managers NTLMv1 and NTLMv2 are both supported.However, NTLMv2 is more secure and is intended to replace NTLMv1.

NIS Directory Services

Data Domain systems can use NIS Directory Authentication for the users inUNIX/LINUX environments. Administrators can enable specific hosts and users toaccess files that are stored on the Data Domain system.

The combination of a host-based access list and domain directory services allowsthe administrator to control which users and servers have permissions to viewdata on a Data Domain system.

Note

In addition to NIS, NFSv4 also supports the use of LDAP.

Kerberos Authentication

Data Domain systems can use Kerberos authentication for NFSv3 and NFSv4clients. Kerberos performs in combination with NIS Directory services to identifyconnecting clients. This authentication method allows the administrator to controlwhich users and hosts have permissions to view data on a Data Domain system.

Separate NFS and CIFS shares

Administrators can easily create shares on the Data Domain file system. Using thenative access control methods helps to define more granular share/directory/file-level access control over certain data on the Data Domain system. For example,when setting up a shared system for multiple customers, administrators can havean NFS or CIFS share that is created for each specific customer on the sameData Domain system and specify access controls for each customer/share.



User authenticationUser authentication settings control the process of verifying an identity claimed by theuser for accessing the product.

Default and role-based accountsThe default user account on the Data Domain system is sysadmin. For DD OS, thefactory default password is the Data Domain system's serial number. For its location,refer to the system's hardware overview manual. The default password for DD VE andDD Management Center is changeme. During the initial configuration, theadministrator who logs in as sysadmin is prompted to change the password. Otherthan the password, the sysadmin account cannot be deleted or modified.

After logging in as sysadmin, you can create additional accounts for the roles that aredescribed in the following table.

After additional user accounts are created, those user accounts can change their ownconfiguration, but cannot perform configuration changes on other user accounts ofthe same level.

Table 3 Role-based accounts

Role/AccountType

ID/Password Description

admin Defined at setup An admin role user can configure and monitor theentire Data Domain system. Most configurationfeatures and commands are available only to adminrole users. However, some features and commandsrequire the approval of a security role user before atask is completed.

limited-admin Defined at setup The limited-admin role can configure and monitor theData Domain system with some limitations. Users whoare assigned this role cannot perform data deletionoperations, edit the registry, or enter bash or SEmode.

user Defined at setup The user role enables users to monitor systems andchange their own password. Users who are assignedthe user management role can view system status, butthey cannot change the system configuration.

security (securityofficer)

Defined at setup l A security role user, who may be referred to as asecurity officer, can manage other securityofficers, authorize procedures that requiresecurity officer approval, provide data destructionoversight, and perform all tasks that are supportedfor user-role users.

l The security role is provided to comply with theWrite-Once-Read-Many (WORM) regulation.Most command options for administering sensitiveoperations, such as encryption, Retention LockCompliance, and archiving now require securityofficer approval.


User authentication 19

Table 3 Role-based accounts (continued)

Role/AccountType

ID/Password Description

backup-operator Defined at setup l A backup-operator role user has all user rolepermissions, can create snapshots for MTrees,and can import, export, and move tapes betweenelements in a virtual tape library.

l A backup-operator role user can also add anddelete SSH public keys for non-password-requiredlogins. This function is used mostly for automatedscripting. The backup-operator can add, delete,reset and view CLI command aliases, synchronizemodified files, and wait for replication to completeon the destination system.

none Defined at setup The none role is for DD Boost authentication andtenant-unit users only. A none role user can log in to aData Domain system and can change their password,but cannot monitor, manage, or configure the primarysystem. When the primary system is partitioned intotenant units, either the tenant-admin or the tenant-user role is used to define a user's role with respect toa specific tenant unit. The tenant user is first assignedthe none role to minimize access to the primarysystem, and then either the tenant-admin or thetenant-user role is appended to that user.

tenant-admin Defined at setup A tenant-admin role user can configure and monitor aspecific tenant unit.

tenant-user Defined at setup The tenant-user role enables a user to monitor aspecific tenant unit and change the user password.Users who are assigned the tenant-user managementrole can view tenant unit status, but they cannotchange the tenant unit configuration.

For more information about user roles and instructions for creating users and viewinguser configuration information, see the Data Domain Operating System AdministrationGuide.

Authentication configurationThe sections below explain how to integrate Data Domain systems with MicrosoftActive Directory and how to manage user accounts.

Data Domain system integration into Microsoft’s Active Directory

For information about integrating Data Domain systems into Microsoft's ActiveDirectory (AD), see the Data Domain Operating System Administration Guide.

Modifying user accounts

As an admin-role user, you can change a user's role for an account, password, andaccount expiration parameters. For more information and instructions, or to changejust the password for individual users, see the Data Domain Operating SystemAdministration Guide.



For uniform password management across the enterprise, the default password policycan be changed and applied to all newly created passwords with the default policy set.Parameters include the following:

l Minimum Days Between Change

l Maximum Days Between Change

l Warn Days Before Expire

l Disable Days After Expire

l Minimum Length of Password

l Minimum number of Character Classes

l Lowercase Character Requirement

l Uppercase Character Requirement

l One Digit Requirement

l Special Character Requirement

l Max Consecutive Character Requirement

l Number of Previous Passwords to Block

l Maximum login attempts

l Unlock timeout (seconds)

For more information and instructions, see the Data Domain Operating SystemAdministration Guide.

Note

DD Boost users and passwords are created using the procedure described in the DDBoost chapter in the Data Domain Operating System Administration Guide.

Enabling, disabling, or deleting user accounts

Local user accounts can be enabled, disabled, or deleted by the system administrator.For more information and instructions, see the Data Domain Operating SystemAdministration Guide.

Note

DD Boost user accounts are deleted as described in the DD Boost chapter in the DataDomain Operating System Administration Guide.

System passphrase

The passphrase is used to encrypt the encryption keys, cloud access, and secret keys.It allows a Data Domain system to be transported with encryption keys on the systembut without the passphrase being stored on it. The system uses the passphrase toencrypt imported host private keys and DD Boost token keys. If the system is stolen intransit, an attacker cannot easily recover the data, and at most, they can recover theencrypted user data and the encrypted keys.

Data at rest encryption keys are dependent on this passphrase, and therefore, the useof a stronger passphrase is mandatory. Strong passphrase characteristics include:

l Minimum of 9 characters

l At least 1 lowercase character

l At least 1 uppercase character


User authentication 21

l At least 1 symbol

l At least 1 numeral

For more information, see the Data Domain Operating System Administration Guide

User authorizationUser authorization settings control rights or permissions that are granted to a user foraccessing a resource managed by the product.

Specific authorization levels are defined for each user account created using the Role-Base Access Control scheme (see Default and role-based accounts on page 19). Tochange the authorization for an account, you must change the role specified for theaccount). For instructions, see the Data Domain Operating System Administration Guide.

Component access controlComponent access control settings define control over access to the product byexternal and internal systems or components.

For more information, see the Data Domain Operating System Administration Guide.

Component authenticationFor instructions about configuring remote component authentication, see the DataDomain Operating System Administration Guide.

Component authorizationFor instructions about configuring access restriction to remote components orsystems, such as IP filtering, see the Data Domain Operating System AdministrationGuide.

The adminacess command allows admin-role users to enable and disable protocolaccess and add or delete host machines on access lists (ACLs). The cifs and nfscommands enable admin-role users to control clients access. For more information,see the Data Domain Operating System Command Reference Guide.

Log settingsA log is a chronological record of system activities that is sufficient to enable thereconstruction and examination of the sequence of environments and activitiessurrounding or leading to an operation, procedure, or event from inception to finalresults.

All Data Domain system logs (system, space, errors, access related) are stored on theroot file system partition, and not accessible directly except through these services:

l Logs can be configured to send to a remote syslog server.

l Authorized service personnel can copy logs to another system via FTP or SCP.

l Some logs can be accessed via successful login via the CLI or the SystemManager.

The Data Domain system log file entries contain messages from the alerts feature,autosupport reports, and general system messages. The log directory is /ddvar/log.




Log descriptionsLog files can be bundled and sent to Data Domain Support to provide the detailedsystem information that aids in troubleshooting any system issues that may arise. TheData Domain system log file entries contain information from the alerts feature,autosupport reports, bash scripts, and general system messages.

Audit and secure logs are searchable by multiple parameters, such as username,string, authentication failure/successes, including tenant-units. Users who areassigned the "tenant-admin" role on tenant-units can only see the logs for the tenant-units which belong to them. Any configuration changes that were done on the tenant-units that are owned by the tenant-admins are shown.

This table lists logs important to system security.

Table 4 Log files

Log name Location and description

messages /ddvar/log/messages The system log, generated from Data

Domain system actions and general system operations.

audit.log /ddvar/log/debug/audit.log Lists all the CLI commands

that are run via DDSH, by user and associated user role. Accessto this log is controlled by user roles. Data Domain admin userscan see all audit logs in the system. Tenant-admin users can seethe audit logs for all tenant-units they own.

access_log /ddvar/log/debug/sm/access_log Tracks users of the

Data Domain System Manager graphical user interface.

secure.log /ddvar/log/debug/secure.log Messages from successful

and unsuccessful logins and logouts, including authenticationfailures by known and unknown users, as well as changes touser accounts, and any other PAM messages.

cifs.log /ddvar/log/debug/cifs/cifs.log Messages about

CIFS-related activity from CIFS clients attempting to connectto the Data Domain system. Messages from the CIFSsubsystem are logged only in cifs.log.

ddsh.info /ddvar/log/debug/sm/ddsh.info Tracks all commands

that are issued by CLI users on the Data Domain system.

bash_audit.log /ddr/log/bash_audit.log All bash operations are logged

for access with the console, Telnet, or SSH. The informationthat is captured includes the command run, username,timestamp, client IP address, and the PID of the client thatinvoked the bash shell.

kmip.log /ddr/var/log/debug/kmip.log

For more information about logs, see the Data Domain Operating System AdministrationGuide.

Log management and retrievalSee the Data Domain Operating System Administration Guide for the following topics:

l Log roll-over


Log descriptions 23

l Viewing log files from the DD System Manager

l Displaying log files using the CLI

l Understanding and saving log messages

l Sending Log Messages to Another System (configuration of an external Syslogserver) - It is recommended to forward system logs to an external server. Logs canstill be evaluated if the local Data Domain system is down or unresponsive.

Additional log management topics are covered in the Data Domain Operating SystemAdministration Guide, as follows:

l To configure CIFS logging levels, see "Setting CIFS Options."

l To configure log alert mechanisms, see "Managing Alert Reporting andConfiguration of Alert Mechanisms."

l To configure time synchronization with an external source, see "Working withTime and Date Settings", "Data Domain System Clock", "Synchronizing from aWindows Domain Controller", and "Synchronize from an NTP Server".

Communication security settingsCommunication security settings enable the establishment of secure communicationchannels between the product components as well as between product componentsand external systems or components.

Data Domain TCP and UDP portsThe tables below show Data Domain's input and output ports for TCP and UDP.

Note

By default, the net filter allows access by additional ports that are not listed in thetables. Use the net filter functionality to disable all ports that are not needed or notused.

Table 5 Data Domain system inbound communication ports

Service Protocol Port Description

Avamar TCP 7 Port is used with Avamar.

FTP TCP 21 Port is used only if FTP is enabled. Runadminaccess show on the Data

Domain system to determine if it isenabled.

SSH & SCP TCP 22 Port is used only if SSH is enabled. Runadminaccess show on the Data

Domain system to determine if it isenabled. SCP is enabled as default.

Telnet TCP 23 Port is used only if Telnet is enabled. Runadminaccess show on the Data




Table 5 Data Domain system inbound communication ports (continued)


HTTP TCP 80 1. Port is used only if HTTP is enabled.Run adminaccess show on the

Data Domain system to determine if itis enabled.

2. Used by Data Domain system foruploading log files to Data DomainSupport via the support bundleupload command.

DD Boost/NFS(portmapper)

TCP 111 Used to assign a random port for themountd service that is used by DD Boostand NFS. Mountd service port can bestatically assigned and can be executedwith the nfs option set mountd-port command.

NTP UDP 123 1. Port is used only if NTP is enabled onthe Data Domain system. Run ntpstatus to determine if it is enabled.

2. Used by the Data Domain system tosynchronize to a time server.

CIFS (NetBIOS NameService)

UDP 137 Port that is used by CIFS for NetBIOSname resolution.

CIFS (NetBIOSDatagram Service)

UDP 138 Port that is used by CIFS for NetBIOSDatagram Service.

CIFS (NetBIOS SessionService)

TCP 139 Port that is used by CIFS for sessioninformation.

SNMP TCP/UDP 161 Port is used only if SNMP is enabled. Runsnmp status to determine if it is

enabled.

HTTPS TCP 443 Port is used only if HTTPS is enabled.Run adminaccess show on the Data


CIFS (Microsoft-DS) TCP 445 Main port that is used by CIFS for datatransfer.

DD Boost/NFS TCP 2049 Main port that is used by NFS. Run thenfs option show command on the

Data Domain system to determine thecurrent NFS server port.

Replication TCP 2051 Port is used only if replication isconfigured on the Data Domain system.Run replication show config to

determine if it is configured. This port can


Data Domain TCP and UDP ports 25

Table 5 Data Domain system inbound communication ports (continued)


be modified via the replicationmodify command.

NFS (mountd) TCP/UDP 2052 Can be hardcoded via the nfs optionset mountd-port command. (This

command is SE mode, which means thatit can be issued only by a ServiceEngineer.) Run nfs option showmountd-port on the Data Domain

system to determine the current port thatmountd is listening on.

Data DomainManagement Center Port

TCP 3009 This port is used only if the Data Domainsystem is managed by the Data DomainManagement Center. It is notconfigurable.

Table 6 Data Domain system outbound communication ports


SMTP TCP 25 Used by the Data Domain system to sendemail autosupports and alerts.

SNMP UDP 162 Used by the Data Domain system to sendSNMP traps to SNMP host. Use snmpshow trap-hosts to see destination

hosts and snmp status to display

service status.

Syslog UDP 514 Used by the Data Domain system to sendsyslog messages, if enabled. Use loghost show to display destination hosts

and service status.

System manager port usageThe System Manager uses HTTP Port 80 and HTTPS Port 443. To reach a DataDomain system behind a firewall, you may need to enable these ports. You can changethe port numbers if security requirements dictate.

Traps are sent out through Port 162.

Port 3009 is not configurable.

Administration/Support protocolsThe Data Domain system supports several services and protocols for administrationand support. Telnet is an administrator option for controller access. SSH is enabled bydefault, and the CLI environment is accessible via SSH and serial connection. You canenable it from the Web-based Data Domain System Manager: Administration > Access> Administrator Access page (Port 23).

These services and protocols include:



l HTTP/HTTPS is used to access the Data Domain System Manager. Open eitherPort 80 or secure Port 443. HTTPS uses the Data Domain system’s internallygenerated signed certificate to establish trust between the client and the DataDomain system’s web browser.

Note

HTTPS is recommended over HTTP.

l SSH is used to access the Data Domain CLI (Port 22) and is enabled by default.You can enable/disable it from the Data Domain System Manager using theAdministration > Access > Administrator Access page.

l Telnet is disabled by default. You can enable/disable it from the Data DomainSystem Manager using the Administration > Access > Administrator Accesspage. Select Telnet and click Configure.

l FTP, FTPS, and SCP are used to download logs, autosupport files and supportbundles, and can be used to upload DD OS Upgrade RPM files.

n FTP is not a secure protocol and allows passwords to pass unencrypted overthe network. FTP is used for moving files to and from the Data Domain systemfor maintenance purposes only (Port 20/21). It can be enabled via theAdministration > Access > Administrator Access page.

n FTPS, or Secure FTP, is used to encrypt FTP traffic because normal FTPtraffic is not secure. This protocol protects sending information to and fromthe Data Domain system for logs, RPM packages, and login credentials.

n FTPS and SCP are recommended as secure file transfer methods foradministrative files.

n SCP is used to securely copy or move internal system files such as system logsin and out of the Data Domain system. SCP is available to any admin user anduses the same port as SSH (Port 22). It is enabled by default.

Data transfer protocolsProtocols that can be enabled on a Data Domain system to ingest data from a serverand to restore data to a server include:

Table 7 Data transfer protocols

NFS (v3 and v4 over TCPonly)

UNIX/LINUX file sharing protocol

CIFS (SMB 2.x only) Microsoft network file sharing protocol

DD Boosta A client-side plug-in with a proprietary protocol over IP networks

Data Domain Virtual TapeLibrary

Tape emulation over Fibre Channel

NDMP An open protocol for transporting data between NAS devices anda Data Domain system

a. DD Boost is also available over Fibre Channel networks. It is designed to optimize andaccelerate backup software and product application interaction with Data Domain systems.By distributing parts of the deduplication process to the backup server or application client,DD Boost speeds up aggregate backup throughput on Data Domain systems up to 100percent or more, while reducing load on LANs.

Other protocols that can be enabled on a Data Domain system include:


Data transfer protocols 27

Table 8 Additional transfer protocols

Network TimeProtocol (NTP)

An industry standard protocol for time synchronization

SNMP An industry standard protocol for sending and monitoring MIB data

SSL An industry standard protocol that is used to encapsulate the payloadwhile data is in flight for secure replication between Data Domainsystems

Network routing managementRoutes determine the path taken to transfer data to and from the local host (the DataDomain system) to another network or host.

Data Domain Operating System does not generate or respond to RIP, EGRP/EIGRP,or BGP network routing management protocols in any form or fashion – DD OS cannotperform any IP packet routing or forwarding tasks. The only routing implemented onData Domain systems is based upon the internal route table, where the administratormay define which physical interface [interface group] to use to address a specificnetwork or subnet. In addition, when multiple interfaces have the same subnet whichwill normally allow multiple interfaces to be used for packets going to the specificsubnet, the appliance uses source-based routing. This defines that outbound networkpackets which matches the subnet of multiple interfaces will only be routed over thephysical interface from which they originated from.

Cloud tier network security recommendations

To verify the identity of a cloud provider before backing up data from a Data Domainsystem, the cloud providers have a host certificate issued by a certificate authority(CA). Import the certificate and any applicable certificate revocation lists (CRLs)before backing up any data to the cloud.

The following table shows the recommended settings for securely connecting to cloudtier storage.

Table 9 Cloud tier network security recommendations

Firewall portrequirementsa

l For ECS private cloud, the system must be configured to allowtraffic from ports 9020 and 9021. If a load balancer is configured onECS, port rules have to be configured accordingly.

l For both AWS and Virtustream cloud providers, communication ison port 443 and 80.

OpenSSL ciphersuites

l Ciphers - ECDHE-RSA-AES256-SHA384, AES256-GCM-SHA384

l TLS Version: 1.2

IP address rangefiltering

l Hostnames for AWS cloud provider to be resolved:

n s3.amazonaws.com

n s3-us-west-1.amazonaws.com

n s3-us-west-2.amazonaws.com



Table 9 Cloud tier network security recommendations (continued)

n s3-eu-west-1.amazonaws.com

n s3-ap-northeast-1.amazonaws.com

n s3-ap-southeast-1.amazonaws.com

n s3-ap-southeast-2.amazonaws.com

n s3-sa-east-1.amazonaws.com

l Hostnames for Virtustream cloud provider to be resolved:

n s-us.objectstorage.io

n s-eu.objectstorage.io

n s-eu-west-1.objectstorage.io

n s-eu-west-2.objectstorage.io

n s-us-central-1.objectstorage.io

Proxy settings l A self signed/CA-signed certificate of proxy has to be importedusing adminaccess certificate import ca applicationcloud.

l If there are any existing proxy settings that reject data above acertain size, those settings must be changed to allow object size upto 4.5 MB.

Supported protocols l HTTP

l HTTPS

a. By default, ports 9020 and 9021 are not able to receive incoming network traffic. They mustbe enabled to receive incoming network traffic to use DD Cloud Tier.

For enhanced security, the Cloud Tier feature uses Signature Version 4 for all AWSrequests. AWS V4 signing is enabled by default.

Certificates for cloud providersBefore you can add cloud units for Amazon Web Services S3 (AWS), Azure, ElasticCloud Storage (ECS), and Virtustream Storage Cloud (VSC), you must import CAcertificates.

Data Domain uses secure transport in all its communications with the public cloudproviders and verifies the identity of the cloud provider. Each cloud provider has ahost certificate that identifies the cloud provider and is issued by a certificateauthority (CA).

As part of setting up Data Domain Cloud Tier, you must import the cloud provider'sroot CA certificate and any applicable certificate revocation lists (CRLs) on the DataDomain system. This step must be performed before adding any cloud profile(s) forthis cloud provider.

AWS and Azure

1. Download root CA certificates from https://www.digicert.com/digicert-root-certificates.htm.

2. Convert the downloaded certificate to a PEM-encoded format. The OpenSSLcommand for this conversion is: openssl x509 -inform der -in<root_cert.crt> -out <root_cert.pem>.


Certificates for cloud providers 29

https://www.digicert.com/digicert-root-certificates.htm


3. Import the certificate to the Data Domain system.

AWS S3AWS S3 provides a way to restrict access rights to a specific bucket and IPaddress(es). It is recommended that the bucket policy restricts access rights to onlythat specific bucket. The read/write rights should only be allowed by the DD VEwriting to the specific bucket.

Note

The AWS user credentials must have permissions to create and delete buckets and toadd, modify, and delete files within the buckets they create. S3FullAccess is preferred,but these are the minimum requirements:

l CreateBucket

l ListBucket

l DeleteBucket

l ListAllMyBuckets

l GetObject

l PutObject

l DeleteObject

Elastic Cloud Storage (ECS)ECS is a private cloud provider and resides within the data center, and it gives you thechoice of either configuring the transport over HTTP or HTTPS.

If using HTTPS (secure transport), on the Data Domain system, you must import theCA certificate from the load balancer front-ending the ECS nodes.

Virtustream Storage Cloud

1. Download the DigiCert High Assurance EV Root CA certificate from https://www.digicert.com/digicert-root-certificates.htm.

2. Convert the downloaded certificate to a PEM-encoded format. The OpenSSLcommand for this conversion is: openssl x509 -inform der -in<root_cert.crt> -out <root_cert.pem>.

3. Import the certificate on the Data Domain system.

The Data Domain Operating System Administration Guide provides more details.

Secure Multi-Tenancy (SMT) securityDD OS provides multiple security enhancements to enhance security for tenantadministrators and tenant users.

Unique tenant-unit hostnamesA hostname that is configured for a tenant-unit cannot resolve to an IP addressassociated with another tenant-unit.

Data access isolationData access through the local IP addresses registered to a tenant-unit is restricted tothe storage resources associated with that tenant unit.

The following constraints apply to data access isolation:





l The local IP address for data access must exist on the Data Domain system.

l Existing IP addresses cannot be shared by multiple tenant-units.

l IP ranges are not supported.

l DHCP-assigned IP addresses are not supported.

Network firewallThe Data Domain system can restrict access from specific remote IP addresses toprovide those clients with access to specific tenant-unit IP addresses.

The following constraints apply to the network firewall:

l Remote data-access IP addresses cannot be shared between multiple tenants.

l Tenant exclusion checks are not performed for subnets or IP ranges.

Unique default gatewaysThe Data Domain system can route data from different tenants through differentrouters or gateways, with separate default gateways that are configured for eachtenant-unit, and the tenant-unit IP addresses mapped to the gateways for theirassociated tenant-unit.

The following constraints apply to unique default gateways:

l Targeted default gateways, which are assigned to a specific interface, aresupported with SMT.

l Static, added, or DHCP gateways are not supported with SMT.

l A single default gateway cannot be shared between multiple tenants.

l Unique gateways that are assigned to a tenant cannot be used by non-SMTentities on the Data Domain system.

There are no restrictions to the address used by the gateway.

Data security settingsData security settings (including data encryption) enable controls that prevent datapermanently stored by the product from being disclosed in an unauthorized manner.

Note

For more information about data encryption, see the Data Encryption section in thisguide and the Data Domain Operating System Administration Guide.

Data Domain Retention Lock softwareData Domain Retention Lock software provides immutable file locking and secure dataretention capabilities for customers to meet both corporate governance andcompliance standards, such as SEC 17a-4(f). DD Retention Lock provides thecapability for administrators to apply retention policies at an individual file level. Thissoftware enables customers to leverage their existing Data Domain systems forbackup and archive data. DD Retention Lock ensures that archive data is retainedlong-term with data integrity and secure data retention.

DD Retention Lock Governance edition and DD Retention Lock Compliance edition cancoexist on the same Data Domain system to enable different retention periods fordifferent classes of archive data. DD Retention Lock software is compatible withindustry-standard, NAS-based (CIFS, NFS) Write-Once-Read-Many (WORM)


Data security settings 31

protocols and is qualified with leading archive applications such as EMC SourceOne,EMC DiskXtender, and Veritas Enterprise Vault.

Dual sign-on requirementWhen DD Retention Lock Compliance is enabled on a Data Domain system, additionaladministrative security is provided in the form of “dual” sign-on. This requirementinvolves a sign-on by the system administrator as well as a sign-on by a secondauthorized authority (the “Security Officer”). The dual sign-on mechanism of the DDRetention Lock Compliance edition acts as a safeguard against any actions that couldpotentially compromise the integrity of locked files before the expiration of theretention period.

Secure system clockDD Retention Lock Compliance implements an internal security clock to preventmalicious tampering with the system clock. The security clock closely monitors andrecords the system clock. If there is an accumulated two-week skew within a yearbetween the security clock and the system clock, the Data Domain file system (DDFS)is disabled and can be resumed only by a security officer.

Data integrityl The DD OS Data Invulnerability Architecture™ protects against data loss from

hardware and software failures.

l When writing to disk, the DD OS creates and stores checksums and self-describing metadata for all data received. After writing the data to disk, the DD OSthen recomputes and verifies the checksums and metadata.

l An append-only write policy guards against overwriting valid data.

l After a backup completes, a validation process examines what was written to diskand verifies that all file segments are logically correct within the file system andthat the data is identical before and after writing to disk.

l In the background, the online verification operation continuously checks that dataon the disks is correct and unchanged since the earlier validation process.

l Storage in most Data Domain systems is set up in a double-parity RAID 6configuration (two parity drives). Additionally, most configurations include a hotspare in each enclosure, except in certain low-end series systems, which haveeight or fewer disks. Each parity stripe has block checksums to ensure that data iscorrect. Checksums are constantly used during the online verification operationand while data is read from the Data Domain system. With double parity, thesystem can fix simultaneous errors on as many as two disks.

l To keep data synchronized during a hardware or power failure, the Data Domainsystem uses NVRAM (non-volatile RAM) to track outstanding I/O operations. AnNVRAM card with fully charged batteries (the typical state) can retain data for aperiod of hours, which is determined by the hardware in use.

l When reading data back on a restore operation, the DD OS uses multiple layers ofconsistency checks to verify that restored data is correct.

Data Domain systems support SNMP V2C and/or SNMP V3. SNMP V3 provides agreater degree of security than V2C by replacing cleartext community strings as ameans of authentication with user-based authentication using either MD5 or SHA1.Also, SNMP V3 user authentication packets can be encrypted and their integrity thatis verified with either DES or AES.

Multiple layers of data verification are performed by the DD OS file system on datathat is received from backup applications to ensure that data is written correctly to



the Data Domain system disks. This process ensures that the data can be retrievedwithout error. The DD OS is purpose-built for data protection and it is architecturallydesigned for data invulnerability. There are four critical areas of focus, described inthe following sections: end-to-end verification, data erasure, system sanitization, anddata encryption.

End-to-End verificationEnd-to-end checks protect all file system data and metadata.

As data comes into the system, a strong checksum is computed. The data isdeduplicated and stored in the file system. After all data is flushed to disk, it is readback, and re-checksummed. The checksums are compared to verify that both the dataand the file system metadata are stored correctly.

Data erasureThe filesys destroy command deletes all data in the Data Domain file system.You can also destroy the file system using the Data Domain System Manager. Formore information on commands, see the Data Domain Operating System CommandReference Guide. See the Data Domain Operating System Administration Guide forinformation about using the System Manager.

Note

The Data Domain data erasure is not compliant with DoD requirements. For DoDcompliance, service Model Number: PS- BAS-DDDE is available.

System sanitizationSystem sanitization was designed to remove all traces of deleted files and restore thesystem to the state prior to the file's existence.

The primary use of the sanitize command is to resolve Classified Message Incidents(CMIs) that occur when classified data is copied inadvertently onto a non-securesystem. System sanitization is typically required in government installations.


Data encryptionThe CA and Host certificates should be compatible with the RSA DPM Key Manageror SafeNet KeySecure Key Manager. A host certificate allows browsers to verify theidentity of the system when establishing management sessions. CA certificatesidentify certificate authorities that are trusted by the system. For information aboutencryption certificates and key managers, see the Encryption chapter in the DataDomain Operating System Administration Guide.

For SSL usage with the Data Domain system, see Manage FTP Access and MonitoringData Domain System in the Data Domain Operating System Administration Guide.

DD Replicator supports encryption of data in flight by using standard SSL. Forinformation about encrypting replicated data, see Working with Replication in the DataDomain Operating System Administration Guide.

Encryption overviewThere are three types of encryption offered with Data Domain systems:

l Encryption of data at rest via the Data Domain Encryption software option


End-to-End verification 33

l Encryption of data in flight via DD Replicator software, used for replicating databetween sites over the WAN

l Encryption of data in flight via DD Boost software, using SSL

Encryption of data at rest

Encryption of data at rest protects user data in the situation where a Data Domainsystem is lost or stolen and eliminates accidental exposure if a failed drive requiresreplacement. When the file system is intentionally locked, an intruder whocircumvents network security controls and gains access to the Data Domain systemwill be unable to read the file system without the proper administrative control,passphrase, and cryptographic key. DD Encryption software is completely transparentto the backup or archive application.

DD Encryption provides inline encryption, which means as data is being ingested, thestream is deduplicated, compressed, and encrypted using an encryption key beforebeing written to the RAID group. Data Domain Encryption software uses RSA BSAFElibraries, which are FIPS 140-2 validated.

By default, the Data Domain Embedded Key Manager (EKM) is in effect unless youconfigure the RSA Data Protection Manager (DPM) or SafeNet KeySecure KeyManager (Key Management Interoperability Protocol (KMIP)) key manager. ExternalCA and Host certificates are required to set up RSA DPM Key Manager or SafeNetKeySecure Key Manager (KMIP). If encryption is enabled on Cloud Tier, only EKM issupported. You can request these certificates from third-party certificate authorities,or create them using appropriate OpenSSL utility.

One of two cipher modes, Cipher Block Chaining mode (CBC) or Galois/Counter mode(GCM), can be selected to best fit security and performance requirements. Inaddition, the system leverages a user-defined passphrase to encrypt that key before itis stored in multiple locations on disk. The system encryption key cannot be changedand is not, in any way, accessible to a user. Without the passphrase, the Data Domainfile system cannot be unlocked, thus data is not accessible.

For the RSA DPM Key Manager, the Data Domain administrator can select a 128-bit or256-bit Advanced Encryption Standard (AES) algorithm for encrypting all data withinthe system. SafeNet KeySecure Key Manager (KMIP) only supports AES-256.

When DD Encryption software is enabled, the system randomly generates a single,static system-wide cryptographic strength encryption key.


Initialization Vector (IV) generationData Domain File System supports AES in CBC and GCM modes, and both the modesrequire an Initialization Vector (IV), and it uses HMAC-SHA256 based RandomNumber Generator (RNG) to generate the first 96-bits of the IV. The last 32-bits arederived from a monotonically increasing counter. The RNG implementation is fromRSA BSAFE MES 4.0.5. DDFS uses an initial 16-byte seed to seed the RNG, which isderived from /dev/random, at the time of file system initialization. If Data DomainFile System fails to generate the initial seed, then Data Domain File System explicitlysets the personalization string to ensure that generated random numbers do notrepeat. The personalization string is based on the current timestamp counter and avariable's memory address.

Salt used for Key Encryption Key (KEK) derivation from system passphraseData Domain File System uses a static hardcoded salt during Key Encryption Key(KEK) derivation from system passphrase. The salt is 16 bytes in size.



Passphrase securityThe passphrase is encrypted and stored in a file on the head unit of the Data Domainsystem. The encryption key that is used to encrypt the passphrase is hardcoded.

Users can choose to not store the passphrase on disk. There is a hidden sysadmincommand to accomplish this task: system passphrase option set store-on-disk no. With DD OS 6.1, there is no need to restart the system after running thiscommand.

Change the passphrase after running the command to not store the passphrase ondisk. A side-effect of not storing the passphrase is that the file system needs to beunlocked every time the Data Domain system is rebooted. Until the file system isunlocked, all backup jobs/replication are impacted.

Note

If there is no concern that an attacker can gain physical access to the appliance in theenvironment, then choose to store the passphrase on disk.

Encryption of data in flight

Encryption of data in flight encrypts data being transferred via DD Replicatorsoftware. It uses OpenSSL AES 256-bit encryption to encapsulate the replicated dataover the wire. The encryption encapsulation layer is immediately removed as soon as itlands on the destination Data Domain system. Data within the payload can also beencrypted via Data Domain encryption software.

Note

NFSv3 and NFSv4 support krb5i and krb5p for integrity and privacy, respectively.However, there are performance penalties for encryption.

Encryption of data in flight via DD Boost

DD Boost protocol can be used with or without externally signed certificates forencryption of data and authentication and was introduced to offer a more secure datatransport capability.

In-flight encryption allows applications to encrypt in-flight backup or restore data overLAN from the Data Domain system. When configured, the client can use TLS toencrypt the session between the client and the Data Domain system. If TLS withcertificates is used, then the specific suites that are used are DHE-RSA-AES128-SHAand DHE-RSA-AES256-SHA for medium and high encryption, respectively. Ifanonymous TLS is used to encrypt the session, then is either ADH-AES256-SHA, forthe HIGH encryption option, or ADH-AES128-SHA, for the MEDIUM encryptionoption, are used.

Externally signed certificatesIf the Data Domain system or Cloud Tier use the RSA Data Protection Manager (DPM)external encryption key manager, it requires a PKCS12 host certificate and Certificateof Authority in PEM (public certificate) format to establish a trusted connectionbetween the RSA Data Protection Manager Server and each Data Domain system thatit manages.

The certificate signing requires PKCS10 format. The public certificate key can haveeither PKCS12 (public plus a private key) or PEM format. The host certificate PEMformat is used only with the CSR (Certificate Signing Request) feature.


Data encryption 35

Individual host certificates can be imported for HTTPS and communication with RSADPM Key Manager or SafeNet KeySecure Key Manager (KMIP).

Importing the host certificate in PKCS12 format is supported. If there is a CSR on thesystem, you can import the host certificate in PEM format after the CSR is signed bya Certificate Authority.

Note

The system passphrase is required to import the certificate.

Uploading certificates

Upload a key in PKCS12 format to the Data Domain system via secure FTP in the /ddvar/certificates directory.

Follow these steps:

Note

The following applications are supported for importing the certificates using theupdated import command:adminaccess certificate import {host application {all | aws-federal | ddboost| https | keysecure | rkm | <application-list>} | ca application {all | cloud | ddboost | login-auth | keysecure | rkm | <application-list>}}

[file <file-name>]

Procedure

1. From the local machine, copy the host PKCS12 certificate to the Data Domainsystem by entering:

$ scp Host PKCS12 file admin@Data Domain System:/ddvar/certificates

2. From the Data Domain system, import the host certificate and specify thefilename.

# adminaccess certificate import host application applicationname file Host PKCS12 file

3. When prompted to provide the password to decrypt the PKCS12 file, enter thepassword.

Certificate signing requestDD OS uses the SHA1 Message-Digest algorithm for the certificate signing requestand supports the generation of CSRs in PKCS10 format. The certificate signingrequest is available in this location:

/ddvar/certificates/CertificateSigningRequest.csrYou can use either SCP, FTP, or FTPS to obtain the CSR from the Data Domainsystem.

The command to generate the certificate signing request is:

#adminaccess certificate cert-signing-request generate [{1024bit |2048bit | 3072bit | 4096bit} ] [country-code] [state] [organization-name][organization-unit] [common-name]

Provide the following:



l Private Key strength: The enumeration values allowed are 1024 bit, 2048 bit, 3072bit, or 4096 bit. The default value is 2048 bit.

l Country: The default value is US. This abbreviation cannot exceed two characters.No special characters are allowed.

l State: The default value is California. The maximum entry is 128 characters long.

l City: The default value is Santa Clara. The maximum entry is 128 characters long.

l Organization Name: The default value is My Company Ltd. The maximum entry is64 characters long.

l Organization Unit: The default value is an empty string. The maximum entry is 64characters long.

l Common Name: The default value is system hostname. The maximum entry is 64characters long.

EMC Secure Remote ServicesEMC Secure Remote Services (ESRS) is an IP-based automated connect home andremote support solution. ESRS creates both a unified architecture and a commonpoint of access for remote support activities that are performed on the product. TheESRS IP Solution does the following:

l Provides continuous monitoring, diagnosis, and repair of minor hardware issues.

l Uses the most advanced encryption, authentication, audit, and authorization forultra-high security remote support.

l Addresses compliance with corporate and governmental regulations by providinglogs of all access events.

l Provides easy integration and configuration with the storage management networkand firewalls.

l Provides maximum information infrastructure protection. IP-based sessions enablefast information transfer and resolution.

l Consolidates remote support for the information with the ESRS Gateway Client.

l Provides remote access to the disaster recovery site and makes recovery fromunplanned events seamless.

l Protects information in motion or at rest. AES 256 encryption during informationtransfer protects the information.

l Reduces costs and data center clutter and accelerates time to resolution. Theelimination of modem/phone line costs translates to lower costs.

Note

Use of FTP or not secure email while connecting to ESRS Gateway (ConnectEMC)could be a security risk.

EMC Secure Remote Services technical documentation is available on the onlinesupport site.

Security alert system settingsYou can monitor Data Domain system operation with a variety of DD System Managertools: reporting tools that automatically send emails containing status and alerts, log


EMC Secure Remote Services 37

files that contain a record of important system events, and SNMP monitoring usingthird party SNMP managers.

Automatic logging and reporting tools that provide system status to Support anddesignated email recipients are important in monitoring system operation. Their setupand use are described in this chapter.

Alerts are also sent as SNMP traps. See the Data Domain Operating System MIB QuickReference for the full list of traps.

For more information on handling alerts, see the Data Domain Operating SystemAdministration Guide.

Other security considerationsThe section below describes additional steps you can take to increase your system'ssecurity.

Avoiding man-in-the-middle (MITM) attacksData can be vulnerable to MITM attacks when the attacker can impersonate eachendpoint.

Data Domain systems can avoid MITM attacks by manually verifying if there areshared secret matches on both Data Domain systems. The shared key, which is theshared secret, can be reset by using the replication reauth command.

DD OS supports one-way and two-way authentication between the replication sourceand destination to provide additional security for replication operations.

To avoid MITM attacks when an application is accessing the Data Domain system, twoway authentication which provides mutual verification must be done. Methods fordoing two way authentication include certificates and Kerberos. With DD OS 6.1, DataDomain Boost also supports two way authentication using pre-shared keys (PSK),which does not require certificates. Various applications may support one or moremethods of two way authentication depending on the application and the protocol(such as DD Boost). For example, Avamar supports two-way authentication usingcertificates.

System hardeningThe hardening process is twofold. Traditionally, customers that are looking to harden asystem are doing so because they are either under mandate, or are simply practicingsecure computing practices. The latter group requires only the hardening proceduresthat are listed here, while the former requires a mitigation explanation for all perceivedvulnerabilities as well as the hardening process. These paragraphs provide both thehardening procedures as well as the mitigation steps to comply with federal DefenseInformation Systems Agency (DISA) Security Technical Implementation Guides(STIGs) on the Data Domain device product.

When a DISA STIG or SRR is run against a Data Domain device, the vulnerabilitiesprovided here are reported. While some of these vulnerabilities are false positives,others require actions to be taken to mitigate or resolve the vulnerability. Thefollowing information and where applicable, mitigation procedures, must be used forcustomers that require the use of DISA STIGs or SRRs.

The following processes can be used to harden DD OS to comply with the DISA STIGstandards:



Table 10 DISA STIG standards

GEN000020 - Single User Bootable Mode The Data Domain device CMOS can be setwith a Supervisor and User password.However, the maintenance of the passwords ishandled by the customer unless specificagreement is maintained with EMC to managethese passwords.

GEN000400 - DoD Login Banner forInteractive Sessions

The customer can use the system optionset {login-banner <file>} command

to change the login banner to whatever isrequired to be compliant with regulations.

GEN000540 - Password Change Policy The customer can set/modify the accountpassword policy characteristics and complexityto whatever is desired within the applicationcode. This feature mitigates this finding.

GEN000700 - Password Aging By default the password policy is relaxed to bebackward compatible. The customer can usethe CLIs to modify the password configurationso it is more restrictive and meets the agingrequirements.

CVE-2000-1200 - Null Session Vulnerabilityin NetBIOS

Run the cifs option set restrict-anonymous enabled command to eliminate

this vulnerability. Also, Data Domain hasapplied all security patches for NETBIOSavailable in Samba.

Use the following recommendations as precautions when hardening a Data DomainOS:

l When configuring a client list, do not use a wildcard character enabling access forany user. Type individual IP addresses or client names instead.

l Enable HTTPS and disable HTTP.

l Do not enable Telnet.

l Use FTPS and SCP, but not FTP.

l Use Kerberos with NFS.

l Use strong passwords.

l Change the default SSH port.


System hardening 39

Note

Changing the SSH port may cause three concerns:

n The Admin interface allows only two ports: 22 and 443. If the ports change,there is no way to change the ports of the Admin interface and are leftexposed. The safest way to handle this exposure is to assign the Admininterface to a temporary interface, and then bring that interface down so thereare no processes listening to the old port numbers.

n The default filter function for SSH is 22 and it remains 22. The default functioncan be disabled. Going into SE mode a new port number can be used via the senet filter add operation. Specific addresses that are allowed to access itand a specific interface can be identified. Once the filter function is added, allthe "normal" operations, such as enable, disable, destroy, and move, can apply.

n If the SSH port changes, it is blocked by the net filter unless auto is enabled.(While this option is enabled by default, it is recommended to turn off thisoption in a secure customer environment.) The only way to enable the new portwithout auto is via SE mode.



CHAPTER 3

Secure deployment and usage settings


l Secure deployment settings...............................................................................42

Secure deployment and usage settings 41

Secure deployment settingsYour contracted service provider is responsible for deployment settings. ContactSupport for additional information.

Secure deployment and usage settings


CHAPTER 4

Secure Maintenance


l Security patch management.............................................................................. 44l Data migration....................................................................................................44

Secure Maintenance 43

Security patch managementYour contracted service provider is responsible for installing the latest securitypatches. Contact Support for additional information.

Data migrationData migration offers Data Domain customers the ability to transfer data from oneData Domain system to another for maintenance, which is primarily used for retiring anolder system or for upgrading to a newer Data Domain system.

The migration function is available for administrators only and is usually executed overa LAN. Administrators must use the command line interface. The migrationcommand copies all data, metadata, replication contexts (configurations), and user-configuration information from one Data Domain system to another. Data migrationconsiderations follow:

l Data migration assumes the Data Domain systems are properly configured for thenetwork, with both systems having properly configured security access.

l The system migrates all MTrees, including data, to the destination DDR,reproducing the same paths and file names.

l After migrating replication contexts, the migrated contexts remain on themigration source. The administrator needs to disable replication on the migrationsource.

l Backup operations to the migration source should be paused during migration.

l The migration destination does not need a replication license for migration alone.

l The migration destination must have a capacity that is the same size as or largerthan the used space on the migration source.

l The migration destination must have an empty file system.

l Migration to a system with Extended Retention software option is supported onlyif the source system also has the Extended Retention software option.

Secure Maintenance


CHAPTER 5

Physical Security Controls


l Physical controls................................................................................................46l Baseboard Management Controller (BMC) and Basic Input/Output System

(BIOS) recommendations...................................................................................46l General USB security best practices..................................................................46l Securing Integrated Dell Remote Access Controller 9 (iDRAC) for DD3300.......47

Physical Security Controls 45

Physical controlsPhysical security controls enable the protection of resources against unauthorizedphysical access and physical tampering.

The ES20, DS60, and DD690 have a disk-drive locking mechanism that prevents theremoval of a disk drive without the appropriate tool, which is a T10 Torx screwdriver.The bezel on the ES30/FS15 has a lock and key that prevents access to the drives.

DD2200, DD2500, DD4200, DD4500, DD7200, DD6300, DD6800, DD9300, andDD990 systems have ES30-style bezels, although there is no key lock on the DD990.

DD880, DD160, DD620, and DD860 systems have no physical access controls.

DD9500/DD9800 systems have a lock and a key, which prevents access to the drives.

For more information, see the following related expansion shelf and hardware guide ordisk FRU replacement documentation for your product.

Baseboard Management Controller (BMC) and Basic Input/Output System (BIOS) recommendations

This list contains the recommended good security practices.

l Always flash the latest BMC and BIOS images as they are released even if therelease notes do not explicitly state a security fix.

l Use the Administrator Password in BIOS setup.

l Use strong passwords for IPMI user accounts and BIOS administrator password.

l Set up an isolated network for manageability and never expose that network to theinternet.

l If using onboard NICs for manageability is required, configure VLANs to isolate itfrom the host network.

General USB security best practices

1. Prohibit booting from USB (or any device other than the hard disks) in BIOS.

2. Disable the USB ports completely in BIOS (if possible).

3. Setting a password in BIOS.

The following sections provide the general operations for disabling USB and passwordsetup in BIOS.

Disabling USB in BIOS

1. Browse to IntelRCSetup > PCH Configuration > PCH Devices > USBConfiguration.

2. Set USB Controller 0 Enable to Disabled.

Note

Another available option is to set USB Ports Per-port Disable to Enabled, andthen disable each port respectively.



Setting BIOS password

1. Browse to Security > Administrator Password.

2. Enter the password to be set in Create New Password.

3. Confirm New Password window.

4. After reset, system will ask you for password if you want to enter BIOS setupmenu.

Clearing BIOS password

1. Browse to Security > Administrator Password.

2. Enter the current password in Enter Current Password window.

3. Without any input in Create New Password window, press Enter from keyboard.

Securing Integrated Dell Remote Access Controller 9(iDRAC) for DD3300

iDRAC featuresiDRAC provides user with the following features:

l Monitors server health

l Remotely power on/off/cycle system

l Provides view of system's inventory

Because iDRAC is independent from the Data Domain Operating System (DD OS),users still can access a powered on system even if DD OS is not running.

iDRAC physical connectioniDRAC can be accessed through the dedicated iDRAC port in the back of the DD3300system. By default, this port is enabled with IP address 192.168.0.120. If this port isnot used, users can choose to disable iDRAC port.

iDRAC services and portsiDRAC supports many services that are separated from DD OS services. Configurethese services appropriately to correctly secure the system.

The following table shows the available iDRAC services, ports, and their defaultsetting.

Table 11 iDRAC services and ports

Services Ports Description Default Setting

Local Configuration Not applicable Disable access toiDRAC configuration(from the hostsystem) using localRACADM and iDRACSetting utility

Disabled

Web Server * 80 & 443 iDRAC web interface Enabled

SSH * 22 Access iDRACthrough SSH

Enabled


Securing Integrated Dell Remote Access Controller 9 (iDRAC) for DD3300 47

Table 11 iDRAC services and ports (continued)

Services Ports Description Default Setting

Telnet 23 Access iDRACthrough Telnet

Disabled

Remote RACADM * Not applicable Remotely accessiDRAC

Enabled

SNMP Agent 161 Enable support forSNMP queries iniDRAC

Disabled

Automated SystemRecovery Agent

Not applicable Enable Last SystemCrash Screen

Disabled

Redfish * Not applicable Redfish RESTful API Enabled

VNC Server 5901 VNC Server on iDRAC Disabled

Virtual Console 5900 Virtual Console ofiDRAC

Disabled

* These services must be enabled for system's functionality.

To configure iDRAC services, please see Integrated Dell Remote Access Controller 9User's Guide.

The following diagram shows the iDRAC NIC port, DD OS serial console port, and P1-P4 DD OS NIC ports.



Figure 2 DD3300 iDRAC ports

If an attempt is made through iDRAC access to unlock the virtual console, thefollowing warning is displayed.


Securing Integrated Dell Remote Access Controller 9 (iDRAC) for DD3300 49

Figure 3 DD3300 DD OS iDRAC banner

See the Knowledge Base article "Security Considerations and Best Practices foriDRAC et SNMP monitoring" for more information.

iDRAC accountsiDRAC has the following password-protected default accounts:

l Root: The default password is the system serial number. User can use this accountto monitor system's hardware. User is recommended to change the defaultpassword.

l Reserved: The account is disabled by default. It is reserved for system internalfunctionality. User must not use, edit, or remove this account.

l PTAdmin: The account is enabled by default. It is reserved for system internalfunctionality. User must not use, edit, or remove this account.

For detailed instruction how to configure account, please see Integrated Dell RemoteAccess Controller 9 User's Guide.



security configuration guide - dell › zh-tw › collaterals › unauth › ...control to the...

Documents