This section summarizes the system hardware security requirements and recommendations.
208. C2 evaluation for hardware
Recommended
C2 evaluated hardware meets requirements defined in the Orange Book.
For hardware designed for customers outside the U.S., equivalent evaluation might be defined in local standards, such as F C2/E3 ratings in Europe.
209. Peripherals follow hardware security recommendations
Recommended
OEM-specific solutions can be implemented to meet these recommendations. The following hardware security features are recommended:
-
External drive devices should have locking capabilities. Each removable media device on a server system should be capable of being locked to prevent unauthorized access to data. A single locked door covering the drives is sufficient. The locking mechanism must render the device useless, whether locking is done electronically or mechanically.
-
Computer case and switches should have locking capabilities to prevent unauthorized internal access. An OEM-specific method can be implemented, either electronically or mechanically.
-
Remote software management should be supported for physical components.
-
Controls and remote alerts should be provided for chassis-open intrusion.
For servers running either Windows 2000 Server or Windows 2000 Advanced Server or Datacenter Server, smart card readers and cards should be provided. If provided with a server system, smart card devices must be compatible with Interoperability Specification for ICCs and Personal Computer Systems, available at http://www.pcscworkgroup.com/.
In addition, smart card readers and device drivers must be Plug and Play-compliant and must be implemented as described in “Smart Card Drivers” in the Windows 2000 DDK. Smart card applications and service-provider dynamic link libraries (DLLs) must adhere to the Microsoft Smart Card SDK that is part of the Microsoft Platform SDK.
Chapter 7
Reliability, Availability, and Serviceability Requirements
These requirements and recommendations relate to ease of use, ease of maintenance, manageability, and failure tolerance. Design guidelines that make server configuration, management, and servicing easier for end users and administrators are defined to help reduce the total cost of ownership for servers.
Reducing the total cost of ownership is an important goal for servers; a key priority in this effort for servers is minimizing downtime. This goal is achieved through mechanisms for backup and reliability, remote management, and emergency and preboot management.
Backup and Reliability Requirements
This section summarizes the backup and reliability requirements and recommendations for servers.
Backup Hardware
This section defines the requirements for backup hardware for servers.
Recommended
An integrated tape drive or other device should be included in the system. Although the recommended method to back up files on a server is to use a backup service under Windows 2000 Server, system administrators will commonly want offline backup capabilities to be available.
For information about hardware requirements related to backup capabilities, such as tape drives and so on, see Chapter 5, “Storage Device Requirements.”
Power Supply
This section defines the guaranteed power requirements for servers.
211. System includes UPS provided with system
Recommended
For servers deployed in many corporate environments, the more common choice will be to provide guaranteed power for the server room.
212. System includes power supply protection using N+1 (extra unit)
|
Windows 2000 Server
|
Advanced Server, Datacenter Server
|
Small Business Server
|
Basic Server:
|
Recommended
|
Recommended
|
Recommended
|
Enterprise:
|
Recommended
|
Required
|
Recommended
|
SOHO:
|
Recommended
|
Recommended
|
Recommended
|
The system overvoltage/undervoltage protection and power supply switch-over circuitry should have the capability to regulate according to the system load. For each voltage used in the system, the output voltages of the redundant power supplies should be within the range of values that can guarantee the proper operation of the system, no matter which supply is active. Power-supply switch-over should occur swiftly enough to maintain normal server system operation.
213. System supports replacement of power supplies
Required
Systems are required to allow for the replacement of the module (or modules) constituting their source of power by a qualified individual in the field. The minimum requirement is that this capability be provided when the system is powered off, that is, when the server is in a “down” condition.
Recommendation
Recommended: Hot-swapping capabilities for power supply replacement and power supply redundancy.
214. System supports replacement of fans
Required
Systems are required to allow for the replacement of the fan (or fans) by a qualified individual in the field. The minimum requirement is that this capability be provided when the system is powered off, that is, when the server is in a “down” condition.
Recommendation
Recommended: Hot-swap fans should be implemented to maximize server up time.
215. System includes local hot-swap power supply replacement indicators
|
Windows 2000 Server
|
Advanced Server, Datacenter Server
|
Small Business Server
|
Basic Server:
|
Recommended
|
Required
|
Recommended
|
Enterprise:
|
Recommended
|
Required
|
Recommended
|
SOHO:
|
Recommended
|
Required
|
Recommended
|
Any system that provides hot-swap power supply replacement and power supply redundancy should have local indicators that unambiguously indicate the supplies that must be replaced. These indicators guide service personnel to replace the correct power supply. Automatic retention mechanisms that prevent incorrect supply removal also satisfy this guideline.
Share with your friends: |