HP UX Bastille Software manual Apache.chrootapache, Apache.deactivatehpwsapache, DNS.chrootbind

Page 40

Apache.chrootapache

Headline

Applies chroot to your HP Web Services Apache Server.

Default

N

Description

The HP Web Services versions of the Apache web server for HP-UX is available

 

free for download at www.hp.com/go/softwaredepot. A chroot script is built

 

into the distribution. This script makes a copy of Apache and related binaries

 

and libraries and places them inside of a chroot jail. This allows Apache to

 

run with limited file system access. If you are not currently running the Apache

 

web server, answer no to this question. The Apache server, httpd, is given

 

access to several compilers and system libraries so it can process cgi's, login

 

attempts, and so forth. One way to lessen the risk presented by this special

 

status is to lock the daemon (httpd) into a "chroot jail." In this case, the daemon

 

has access to only a small segment of the file system, a directory created

 

specifically for the purpose of giving the daemon access to only the files it

 

needs. The adjective "chroot'ed" is derived from "change root", since HP-UX

 

Bastille sets the daemon's root directory ( / ) to some child node in the directory

 

tree. A root process can break out of a chroot jail, but this is still an effective

 

deterrent since HP-UX Bastille limits the number of common root attack vectors

 

within the jail. If a security vulnerability is found in one of the files that has

 

been placed inside of the "chroot jail", that file must be manually patched by

 

copying the fixed file(s) into the jail. This chroot script was written to provide

 

for a fully functional web server inside of a chroot'ed environment. For

 

additional security, remove unneeded libraries and compilers that are not

 

used by your Apache server.

 

IMPORTANT: Manual action is required to complete this configuration. See

 

the TODO.txt file for details.

Actions

Makes a copy of Apache and related binaries and libraries and places them

 

inside of a chroot jail.

Apache.deactivate_hpws_apache

Headline

Deactivate the HP Web Services Apache Web Server.

Default

Y

Description

If you do not plan to use this system as a web server, HP recommends that

 

you deactivate your Apache web server. Programs that require an Apache

 

server installation but do not bind to port 80 can still start their own instances

 

of the web server. If you do not plan to use your Apache server immediately,

 

then you should deactivate it until needed. This item does not turn off copies

 

of Apache or other web servers if they are supplied with individual products,

 

nor does it disable APACHE_SSL.

Actions

Stop the Apache server if it is running. Set HPWS_APACHE_START=0 in the

 

/etc/rc.config.d/hpws_apacheconf file.

DNS.chrootbind

Headline

Names and sets chroot to run as a non-root user.

Default

N

Description

The name server "named" usually runs with privileged access. This allows

 

"named" to function correctly, but increases the security risk if any

 

vulnerabilities are found. Decrease this risk by running "named" as a

non-privileged user and by putting its files in a restricted file system called a chroot jail. If a security vulnerability is found in one of the files that has been placed inside of the chroot jail, that file must be manually patched by copying the fixed file(s) into the jail. For security reasons, restrict every process which

40 Question modules

Image 40
Contents HP-UX Bastille Version B.3.3 User Guide Trademark Acknowledgments Table of Contents Index List of Figures HP-UX Bastille user interface Standard assessment reportList of Tables Question modules Security levelsFeatures and benefits About this productPerformance CompatibilitySupport Installation requirements Installing HP-UX BastilleInstallation Page Using HP-UX Bastille Creating a security configuration profileIf the Path environment variable has not been updated, use 1shows the main screen of the HP-UX Bastille user interfaceConfiguring a system Assessing a systemUsing scored reports Accepted standard configurations are detectedConfiguration for the corresponding question is not Is not always detected. HP-UX Bastille might not detect allScored assessment report Reverting # bastille -rLocating files Monitoring driftFor more information, see bastilledrift1M Var/opt/secmgmt/bastille/log/Assessment/Drift.txt Check for a TOREVERT.txt file Removing HP-UX BastilleIf the file exists, complete the actions listed Page Troubleshooting Diagnostic tipsKnown issues and workarounds General use tipsProblems opening, copying, or reading files Errors related to individual configuration filesHP-UX Bastille configures a firewall using IPFilter Cannot use X because $DISPLAY is not setContacting HP Support and other resourcesRelated information Typographic conventions To complete a task Or damage to hardware or softwareSupplement important points of the main text Page Install-Time Security ITS using HP-UX Bastille Choosing security levelsEnable kernel-based stack execute protection Table A-3 Additional Sec20MngDMZ security settings1 Selecting security levels during installation Choosing security dependenciesConfiguring Sec20MngDMZ or Sec30DMZ security levels Configuring HP-UX Bastille for use with ServiceguardConfiguring Sec10Host level Page Question modules AccountSecurity.guilogin AccountSecurity.hidepasswordsAccountSecurity.crontabsfile AccountSecurity.cronuserAccountSecurity.MINPASSWORDLENGTH AccountSecurity.NOLOGINAccountSecurity.NUMBEROFLOGINSALLOWED AccountSecurity.lockaccountnopasswdAccountSecurity.NUMBEROFLOGINSALLOWEDyn AccountSecurity.PASSWORDHISTORYDEPTHAccountSecurity.PASSWORDHISTORYDEPTHyn AccountSecurity.PASSWORDMAXDAYS AccountSecurity.passwordpolicies AccountSecurity.serialportlogin AccountSecurity.singleuserpassword AccountSecurity.restricthomeAccountSecurity.SUDEFAULTPATH AccountSecurity.SUDEFAULTPATHynAccountSecurity.systemauditing AccountSecurity.umaskAccountSecurity.umaskyn AccountSecurity.unownedfilesAccountSecurity.userdotfiles AccountSecurity.userrcfilesApache.deactivatehpwsapache Apache.chrootapacheDNS.chrootbind FilePermissions.worldwriteable FTP.ftpusersHPUX.guibanner HPUX.mailconfigHPUX.ndd HPUX.othertools HPUX.screensavertimeout HPUX.restrictswaclsHPUX.scanports HPUX.stackexecuteIPFilter.blockcfservd HPUX.tcpisnIPFilter.blockDNSquery IPFilter.blockhpidsadmin IPFilter.blockhpidsagentYou are managing some remote Hids agents, answer no Hids does notDefault 192.168.1.0/255.255.255.0 Description IPFilter.blocknetrangeIPFilter.blockping IPFilter.blockSecureShellIPFilter.blockwebadmin IPFilter.configureipfilterIPFilter.blockwbem Otherwise, answer no to this questionPage MiscellaneousDaemons.configuressh IPFilter.installipfilterMiscellaneousDaemons.diagnosticslocalonly MiscellaneousDaemons.disablebind MiscellaneousDaemons.disableptydaemonMiscellaneousDaemons.disablepwgrd MiscellaneousDaemons.disablerbootdMiscellaneousDaemons.disablesmbclient MiscellaneousDaemons.disablesmbserverMiscellaneousDaemons.nfscore MiscellaneousDaemons.nobodysecurerpcOtherbootserv MiscellaneousDaemons.xaccessMiscellaneousDaemons.sysloglocalonly Patches.spccronrun Patches.spccrontimePatches.spcproxyyn Patches.spcrunPrinting.printing SecureInetd.deactivatebootpSecureInetd.banners SecureInetd.deactivatebuiltin SecureInetd.deactivatedttoolsSecureInetd.deactivatefinger SecureInetd.deactivateftpSecureInetd.deactivateident SecureInetd.deactivatektoolsSecureInetd.deactivatentalk SecureInetd.deactivateprinterSecureInetd.deactivaterecserv SecureInetd.deactivaterquotadSecureInetd.deactivatertools SecureInetd.deactivateswatSecureInetd.deactivatetftp SecureInetd.deactivatetimeSecureInetd.deactivateuucp SecureInetd.ftploggingSecureInetd.loginetd SecureInetd.inetdgeneralSecureInetd.owner Sendmail.sendmailcronSendmail.sendmaildaemon Sendmail.vrfyexpnPage Sample weight files All.weightCIS.weight Sample weight file below aligns with the CIS standardCIS.weight Page CIS mapping to HP-UX Bastille CIS IDApache.deactivatehpwsapache AccountSecurity.lockaccountnopasswd Page Index