HP Integrated Lights-Out Security, 7th edition

26
HPONCFG
The HPONCFG utility is a server-based service that can configure iLO using XML scripts. Because it is
server-based, the iLO firmware ignores login credentials and assumes that the user has the rights to
configure iLO. HPONCFG reduces this potential security risk by requiring a root login in Linux
operating systems or administrator login in Windows operating systems to access the utility.
CPQLODOS
You can use the CPQLODOS utility for initial iLO processor deployment, but only locally in a DOS
environment such as during a SmartStart scripted deployment. The administrator must have a DOS
image loaded on a server or a floppy. This means that the user has either physical access or a virtual
media privilege, with all the accompanying user rights and authentications.
Terminal services
iLO uses the pass-thru service HPLOPTS.EXE to access Windows Terminal Services. The iLO remote
console applet activates the Terminal Services client application when you request a remote console
connection. iLO sets up a socket and monitors port 3389. The iLO processor passes thru to the server
all data that it receives from the Terminal Services client and vice-versa. iLO implements security
identically to the Windows Terminal Services Remote Desktop Protocol implementation. This means
that any active security measures are established between the Microsoft terminal services client and
the Microsoft Remote Desktop Protocol service.
The Terminal Services port is the second of two ports in iLO that allow traffic to pass to the OS
through the iLO driver. Administrators can disable the Terminal Services pass-thru port.
IT infrastructure security considerations
The following sections describe iLO security in two particular IT environments:
• When operating in the infrastructure between an external firewall and an internal network (DMZ)
• When operating in a server blade environment
Operating iLO servers in the DMZ
An Internet-connected architecture typically has a more secure, de-militarized zone (DMZ). The DMZ
zone lies between the corporate servers and the Internet. It usually has firewalls that restrict traffic flow
between the corporate/Internet areas. This architecture lets you access servers that provide publicly
available Internet services through a firewall, but you cannot access these services on the internal
network. This more secure zone provides an area isolated from the internal network and hardened
against external attack (Figure 14). The security challenges in the DMZ require a careful balance
between critical security requirements and the need to effectively manage and maintain the systems.