22.12.2012 Views

Front cover - IBM Redbooks

Front cover - IBM Redbooks

Front cover - IBM Redbooks

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

password being requested and allowed to continue its boot-up sequence after<br />

the password is entered. Ideally, the security policy for the organization will<br />

establish precedence (security over service agreements).<br />

► Supervisory password: This is a password which prevents an unauthorized<br />

user from booting the server into maintenance mode using installation media<br />

(installation CD, mksysb tape/CD). Booting off of such media allows full<br />

access to files and directories without security restrictions that are in place. A<br />

supervisory password locked system, if the password is lost, will need to be<br />

serviced by <strong>IBM</strong> in order to unlock it.<br />

► Root password: This is the super-user password which may need to be used<br />

from the time to time. It’s important to be aware of when the root account will<br />

need to be used, and plans should be in place in the organization’s security<br />

implementation to address these instances.<br />

Security weaknesses<br />

Every good AIX system administrator should be aware of systems in the<br />

organization’s IT infrastructure that might have security weaknesses. If a<br />

would-be intruder breaks into a machine located inside the organization’s<br />

network, access may be granted to other machines through permissions set up<br />

between the point of entry machine and other systems in the network.<br />

Some would-be attackers scan networks for certain machine types and certain<br />

versions of operating systems to find one to break into, and they can then use<br />

that point of entry to gain access to all other machines in the network.<br />

9.5.5 Enabling system auditing<br />

Users regularly perform various system actions that will need to be monitored<br />

more closely. By setting up system auditing, it is possible to record<br />

security-relevant information, which can be analyzed to detect potential and<br />

actual violations of the system security policy.<br />

Predefined audit events can be found in the /etc/security/audit/events file.<br />

Automated auditing can be set up using the cron facility to generate regular<br />

reports.<br />

9.5.6 Monitoring files, directories, and programs<br />

Our discussion on hardening would not be complete without looking at the<br />

mechanisms that can be used to monitor access to files, directories, and<br />

executable programs.<br />

Chapter 9. Server hardening 407

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!