ࡱ>  g2\p Christa Bator Ba= =뜽P[,8X@"1Calibri1Helv1Helv1Calibri1Calibri1Arial1Arial1Arial1Arial1Arial1Arial1Arial1Arial1Calibri12Calibri1 2Calibri12Calibri142Calibri1 2Calibri12Calibri12Calibri12Calibri1,>21>21>21'21>21421<2Calibri1?2Calibri1h>2Cambria12Calibri152Calibri12Arial12Arial12Arial152Arial12Arial12Tahoma"$"#,##0_);\("$"#,##0\)!"$"#,##0_);[Red]\("$"#,##0\)""$"#,##0.00_);\("$"#,##0.00\)'""$"#,##0.00_);[Red]\("$"#,##0.00\)7*2_("$"* #,##0_);_("$"* \(#,##0\);_("$"* "-"_);_(@_).))_(* #,##0_);_(* \(#,##0\);_(* "-"_);_(@_)?,:_("$"* #,##0.00_);_("$"* \(#,##0.00\);_("$"* "-"??_);_(@_)6+1_(* #,##0.00_);_(* \(#,##0.00\);_(* "-"??_);_(@_) m/d/yyyy;@,'[<=9999999]###\-####;\(###\)\ ###\-####0.0"Yes";"Yes";"No""True";"True";"False""On";"On";"Off"],[$ -2]\ #,##0.00_);[Red]\([$ -2]\ #,##0.00\)$[$-409]dddd\,\ mmmm\ dd\,\ yyyy[$-409]mmmm\ d\,\ yyyy;@[$-409]h:mm:ss\ AM/PM                                                                      ff      P  P         `               a !   ? ? ,  @ ? ,  @ ? ,  ? @ ,  ,   , " ? @ ,  ,   ,  ,   ,  ? ,  @ ,  @ ,  ? ?   @ ?   @ ?  ? @     ?  @  @     ? 7  @ 7  @ 7  ?    ?  ?  ? , @ , @ , "@  "@  "@  "@     x? 7   x@ 7   x7   x? ?   x@ ?   x?   @ x? @  x x@  x?  x@  x   x@ ? ,   x? ,  `   x?    x@    x   x@ ,   x,   x p? , p,  x,   `@   8?   8 <  8  8 @    h? ?   `? ?   ` ?   8@ ?  <@ ?    h?   `@   `   8 <  x,  x!,  x  8 0  4!  x  4!!    8! 0!! 0  @   `   ? 7   @ 7   7   ? ,  @ ,  ,  ? ?  @ ?  ?   ? @   @  ?  @     ? ?   @ ?   ?   ?   @     ?   @    ?  @    ? @     @   1 |@ 7  x,  1|, a 4 a 4?  1a 4 8   1   x? ,  x@ ,  x,  P x? ?  x@ ?  x?   x? ? ,  x@ ? ,  x? , x? , x@ , x,  ?,     ?,  , #@ @  #@ @  #!@ @  $@ @  $@ @  $@ @  $!@ @  $!@ @  $!!@ @  $!@ @ +  x@ @  x@ @    x@ @  a p@ @  a x@ @    @ @    @ @  q p@ @   @ @   @ @   ?5  ?,   |  @ @    |@ @   (         @ @      ? ? 5  @ ? 5   ? 5  @ 5  ?5  @ 5  5  ? @    !? !@  ! !  !  !  !|  @@  @   @   x@ ? ,  @ ? 5   x@ ,  @ 5  @ @   ? 5  8@ @  %?  %!?     0  @   @      `   ?  ? @   ? ? ,  @ ? ,  ? ,   @ @   @@ @  @ @ @    @    ? ?  @ ?  ?  ? @  @  ?  @   $@ @  $@ @  &!@ @  #@ @  #@ @  #!@ @  ||?䪻}A} yyyy_)ef[$ -}A} yyyy_)ef[$ -}A} yyyy_)ef[$ -}A} yyyy_)ef[$ -}A} yyyy_)ef[$ -}A} yyyy_)ef [$ -}A} yyyy_)L[$ -}A} yyyy_)L[$ -}A} yyyy_)L[$ -}A} yyyy_)L[$ -}A} yyyy_)L[$ -}A} yyyy_)L [$ -}A} yyyy_)23[$ -}A} yyyy_)23[$ -}A} yyyy_)23[$ -}A} yyyy_)23[$ -}A}  yyyy_)23[$ -}A}! yyyy_)23 [$ -}A}" yyyy_)[$ -}A}# yyyy_)[$ -}A}$ yyyy_)[$ -}A}% yyyy_)[$ -}A}& yyyy_)[$ -}A}' yyyy_) [$ -}A}( yyyy_)[$ -}}) }yyyy_)[$ -##0.  }}* yyyy_)[$ -???##0.??? ??? ???}-}+ yyyy_)}(},  yyyy_)}A}- ayyyy_)[$ -}A}. yyyy_)[$ -}A}/ yyyy_)?[$ -}A}0 yyyy_)23[$ -}-}1 yyyy_)}(}2  yyyy_)}}3 ??vyyyy_)̙[$ -##0.  }A}4 }yyyy_)[$ -}A}5 eyyyy_)[$ -}x}:yyyy_)[$##  }}; ???yyyy_)[$???## ???  ??? ???}-}< yyyy_)}U}= yyyy_)[$## }-}> yyyy_)}(}F yyyy_)}(}_yyyy_)}(}`yyyy_)}(}ayyyy_)}(}b yyyy_)}(}c yyyy_)}(}d yyyy_)}(}e yyyy_)}(}uyyyy_)}(}vyyyy_)}(}{yyyy_)}(}|yyyy_)}(}~yyyy_)}(}yyyy_)}(}yyyy_)}(}yyyy_)}(}yyyy_)}(}yyyy_)}(}yyyy_)}(}yyyy_)}(}yyyy_)}(}yyyy_)}(}yyyy_)}(}yyyy_)}(}yyyy_)}(}yyyy_)}(}yyyy_)}(}yyyy_)}(}yyyy_)}(}yyyy_)}(}yyyy_)}(}yyyy_)}(}yyyy_)}(}yyyy_)}(}yyyy_)}(}yyyy_)}(}yyyy_)}(}yyyy_)}(}yyyy_)}(}yyyy_)}(}yyyy_)}(}yyyy_)}(}yyyy_)}(}yyyy_)}(}yyyy_)}(}yyyy_)}<} yyyy_)[$}<} yyyy_)[$}<} yyyy_)[$}<} yyyy_)[$}<} yyyy_)[$}<} yyyy_)[$}<} yyyy_)[$}<} yyyy_)[$}<} yyyy_)[$}<} yyyy_)[$}(}yyyy_)}(}yyyy_)}(}{!yyyy_)}(}{!yyyy_)}(}{!yyyy_)}(}{!yyyy_)}(}{!yyyy_)}(}{!yyyy_)}(}{!yyyy_)}(}yyyy_)}(}{!yyyy_)}(}yyyy_)}(}{!yyyy_)}(}{!yyyy_)}(} yyyy_)}(} yyyy_)}(}!yyyy_)}(}"yyyy_)}(}$yyyy_)}(}%yyyy_)}(}&yyyy_)}<}9 yyyy_)[$}<}: yyyy_)[$}<}; yyyy_)[$}<}< yyyy_)[$}<}= yyyy_)[$}<}> yyyy_)[$9 +  !%9  * !%9 +  !%9  * !%9 +  !%9  * !%9 +  !%9 +  !%9 +  !%9 +  !%9 +  !%9 +  !% 20% - Accent1M 20% - Accent1 ef % 20% - Accent2M" 20% - Accent2 ef % 20% - Accent3M& 20% - Accent3 ef % 20% - Accent4M* 20% - Accent4 ef % 20% - Accent5M. 20% - Accent5 ef % 20% - Accent6M2 20% - Accent6  ef % 40% - Accent1M 40% - Accent1 L % 40% - Accent2M# 40% - Accent2 L渷 % 40% - Accent3M' 40% - Accent3 L % 40% - Accent4M+ 40% - Accent4 L % 40% - Accent5M/ 40% - Accent5 L % 40% - Accent6M3 40% - Accent6  Lմ % 60% - Accent1M 60% - Accent1 23 % 60% - Accent2M$ 60% - Accent2 23ږ % 60% - Accent3M( 60% - Accent3 23כ % 60% - Accent4M, 60% - Accent4 23 % 60% - Accent5M0 60% - Accent5 23 %! 60% - Accent6M4 60% - Accent6  23 % "Accent1AAccent1 O % #Accent2A!Accent2 PM % $Accent3A%Accent3 Y % %Accent4A)Accent4 d % &Accent5A-Accent5 K % 'Accent6A1Accent6  F %(Bad9Bad  %) Calculation Calculation  }% * Check Cell Check Cell  %????????? ???+Explanatory TextG5Explanatory Text %, F Followed Hyperlink   -Good;Good  a%. Heading 1G Heading 1 I}%O/ Heading 2G Heading 2 I}%?0 Heading 3G Heading 3 I}%231 Heading 49 Heading 4 I}%24 Hyperlink   3InputuInput ̙ ??v% 4 Linked CellK Linked Cell }% 5NeutralANeutral  e%"Normal 6Normal 2 7Normal 3 8Normal 49 Normal_Sheet1 :Noteb Note   ;OutputwOutput  ???%????????? ??? <Title1Title I}% =TotalMTotal %OO> Warning Text? Warning Text %XTableStyleMedium9PivotStyleMedium483ffff̙̙3f3fff3f3f33333f33333\`k Dashboard6Results Instructions?Gen Test CasesRHEL6 Test Cases Change LogiAppendix!  =&&!  ; 8 h0 .5b-!ODw30@Gbe n!ODw30@GbePNG  IHDR<qsBIT|d IDATx^}``SJsH JH" btJww `ynw]^O9f3 o7𿴾gN3ڍR+[V]ò2 -EcYt޸!V66+-{mUu?RN}>_:ϭ՛ֳ*իd~=qك۽rn}L=Q"))),g%6$.(~f8x|G=1%1 ";KaL!w8يZdy(%,"ZBf鴵(4\JV-- 8+x9|o=ywOևo1|WFo9h4dqp56kWP8>7J( })ᑱ'$8\t"\&{r9|)4 JSkWMjJBve |>xW?3_T;F ߶3>b'{j-&VK)Xܒ[wBD86XۊNORK,"*JKz[6,goóIF7x,bڮ~)w-έf0aC[cwnݱHGbo^rΓƠw @?"< /7*kTK7e+600hGK/)Xj\Ir`7VFd 0|˗0o[мl;޻u3~Y+## ݈Je-NJ*"ݛ֔ƕ}&0X !%?"c6^^^jR]J|K8gK keeج_)eݬtTz_XAz VWӻE- f|rJH19&UDG.LXDI${J30 o"Ψ"zɪ}`2E]Wz-%;Yj?`}ŔwX#IoG>m eŻO0q{He,H}Hs$M^xaRTŊ2uYuB:DY:i_#?; CG-C`סO/spCnO 5 ~`_o]Gɗv" ^żd\צҶ{>?Հ܉5~vyd~D7Gt1痲sH~uwC:Ke\x+D⁰仡]doP_Kh$Rĭ{V;ӆu.2%FZV/'͖% ˹γWeEnߌF ߢ^i߶1Xg!Oi ^ ],&Z׷uW|g[kko^3cuDBy䎋c^84$ٓ$fljK2 {K@=yB bSIݭj4Ho M 7tl+I]'eڢmK:345P5g 8}LEloun탽l'011XO%R`~C)T4j6`9kEr$X}Pa\Zש$H(I cz8߮إmS} zH 1yVvd[=q3@ӍQnT.zLM!L?t8w9 o =nI̝w0_k;#|O:sAS{:h|чZV/+-G dJ2/&>nW Zʜ-G,<0ƯS,9$r%t_E zs,>tml+f|%_ D>⵼Nп 6?O?Q U;PA2 Rȥ  xH"}ֿ8Y **!mGȗ)Xv9;[2 lCsӹVB+N?0].]~ÜU*&0 JDRP|hkeܜ `Rcf>$ɪ7<+Ae 0G2$;Ag2HI9)Cț~ue)ɛ~% ϟfB x%> soL=yDAwym]0Mo* ;^AV}4@y%$_kn)nBa`X*rGvLIaZ7MeΓr;ުƁewi Gk@?(6lĈ>[  :@dߍ_̇Judߜ|`2CFK~r כ߭C7qd7iS'iO]xG~B/-xݨ_'tq/ : 76wɟkk&%мO_H_)otCw%yrn(35GA,ÿ[.Q5Q7 #z1oP/_ݓ^ع}{G_WuymfK>oLӘs,z`K0St@_TGb1M)C( DB? U[+H H)W&rD!wzC'E,jQ!|@~X3Jj8oveqr-5'k{N;u`BD0w|6&_/HLQEz6)VմѷPEGk8:L`Xxn7*-ںx:?`06ʖ/]JBݦU:o;(c025^5ߐW^HX]o+Z~[ L2}r ׃GOltc!9pŰ>*@H%kPHipA% oՓmWI~.͔ݫxm3sp2 s5=Z~m7-'/hX 0/ЭGMv}9Đz_H7.x|˄ߍPmCiiX~z~e$5 篷+vK , 8.O @/eLL:mkWP )gYI4 ͰNV]Jκ <4( yHcown,KiKR.S%CA|X/ʬ]"ƮN=e 4BkۦCmQsosY rdCgL͸7b-\w,1ֵ g_C&i]cPH.s)\,H_ ` `d?6J0R< `>E Hf{p0g+x|Wl9w&P#0Y):4&t/ޒUx`p KƆH:C̃D% B65gn/zbAf> rfҤ 5QGkeJV=yw̍:@?Co2A0ߏzECs=5vxz/(sL8e{N 5lXouUy$]J>гm$&.@=>+ e㴑pV,/Ni46!opu1A#6hվYk!^>x+?g찭Sg& >k˼AV#5\=n , `jF_l^Sz4.;ay~860KH[谺gK^?10zai ,X`g+~ !T@=%__ӄ)0.MgJ?{w_ md %d|?Tω4W&fv򛡆5kWOMҼV`|Ń94ss1Xbk3Ǒ%;aA*A)>~]jJ2|5rQ NP<s4Dn~(& s T/n{~փLZkO tGY}:hCy>}ʲ,尪P?$ڲT2mնĹ;帿7ρ%綊<\M:Nއ\)g mݍ!M}*ǻa^& Cwlp h:M&i <1T0,٥0h%=}jwJ->܌W.~ܨջN)TSL_eI󷾕4T+(.(JVOck>[ &~}@vE-&>SkZU;Gk|Oy.^-_}/.7{2 \ƞ#QJϵRuVzg7 , 'Icp\>{31݇Ӂr²Ѳֽ|5ea';+价!97WQ͚:j9= 9Hh#Eo Q5cJ?q7$__ >ytik>}fvX6~D!+7P^Mcҋڜa""=YbHD~:,?wE )x"`3QitOU|*Za(t( IيfsI[ݣ?H Caֿ>V |38c({7SB#˱fKZux=IdkOADtuiL_M`7( F0Q.bJM@ 8Jp#iN5f dv_ ܼf-to![(d%B=?~$ab夡Sߕ [g EKֽkbw5oڜrq߹V@G߁;pdP'W3 V\֧\p j`iûɅ[e1kUJ!|> =m*˟̼60oT~[`GX#HJE9/,*`Wf$zl(, Owz<ȑrꮭ| @/faj>p6+`,.J z_U]j2!O0q1CpVG>@o&wpi ';b%'Vi- l?{쫈<(|1Q5*+ i|֭SޘA8>RɈ1R ݧ%H}V陫a*mհ zIzFH$2ZL6~怖If{ŠLep[I<@gx`Mn·!ǾXb+uCױqɺ8YFá Kf# `yW+FGm5d`0D?I3䑘ۿrUk|qNrg潨O1O'e\D4VC]'ĽG1Wb@\ ʋR &A*]=!u JcxN6Q 9SwT--MǟB>[ϲ4`ک53KUG^sr 4h$N=-HR_W$խ˹qSn8BƊ]ⅲ޲R%֫yc6CJMm-_{懳'җz] 1~A |P ;XrZ#?oE``]W4H^vN7K.*wFJ26~k9n c i.f6ۼ:ㇿ&VMP{U-$ރZn=0^׶miKfu]uٻcۢ^wm[ґ݉.C-:Ȓـ &A@g u9ɌS):D*<`mFzZD.Ŗr)(Kwkr3Sj9zsx*>xKL KBwlq2s IDATbch͜{i}06DYr/lf`q1t&yU lBH͂ Cjmrŭw:]@]V@N3)y xO@8T\2H4gx br=8W/'ۏ>* qNoD=ADebk.LOt ,X-%@чR9nx$ޑB#I׃?@ouz5Z #zo.KW\rbwxS̿e"߱W!FKcXU 2q Sgl`b%mҵ)5%[[9񤸜,)Jky7ڋUJ<ɮ[ mfRiZI6R)Rk Ћ{CR{]$%%*Xiy_' ݑ̿귕:zicD{ Z50y` zOI50Oq_O[~¯fq2?a܍(=CmAJ-np6WQ: k/BztDc Ⱦ e&=]D qf֑g%,G\]AqDLEnBU)|VѮކ.aY4y6|l@ɭHjyJ ;ҥ5U>dycjjgeR PfS LBZ('91iCn u.JPa/;<~  /5&{dkgY)\`jlBJ]͸ nlKd֬QVܯ.}_G3X-+N5o_Olh b %Pa֯Jo~6lhՁX@Y'5lUd2L{g)}A<~'z2$#<-j*BPT$u{\k9~űeiK{J05ԯrq/Cc/E`鮙 k~E629DiE# FE!jee#n]Urc { &e>H x&p{jy)3褴ǪJ~ӽKM?S0y)hhfCus̪YUN lK#J.zg,Bq}ە06T\']ʑ8Y;],'$eYڥrj ì -Y1ݸAI^1Rʧ앣jQw;W5C%61EJ#-LjRyhI6lϰEڭ:Y3&Bk =^߭ | H =N*r*mՂr/aNhf2 EsoGWe4 s~|~ t`ːkB62váǰ0GR'n]!wo#& Ą6^!JUF<* P3D.+UðV&5= ԰+4h\Mmj!W g12s*\#Ћt";5Sl1֑o>~Eg(S,reל@Rm-`&@uИAQ(l7ێp3z,eZ?*;Y+S-&Hj^ҿF xjYpÙƞs:_,}%A~ ,'ˁeWW֫/wQ:= I=R>g.l:=ͦKQdP/2kf ]U,5><#؁J̴ͤ9OUbKRIu6I rH<s35`@lHy\[H]q?v.7_$ M˪넒ZKI4+6 vRf58AO3OJWdnVՕ#a"L '} qrcunצZll LO#n'gZ&v 5`SbxY}Rb t^ ߇qZԮ).A0l;N(a5w+- 6[KU PqB%-bX43 v-V>}\Sz ϗ y 8y1;58&T @ bL׺b3f*?o;.Cn,… eJBRZ)CL Ľ,y*%=H_>J%}Pf/"iڳ!8]9_ݺ[ԼZ}kXoVT5^=;o[[4Q cn*ŒPuF/j=|[miQD2S){4y*2K~eldZ$,k $p{t̩U  y]t[iKB͊ff!.B@;&6vt'Z_L_y؇^` y׬]ccVEUĻPS耭>s>N`R3}Sx+fݑH~erbKG0 *?0.^O 怅[$2) ̫b\qez ki;gzK!yGrB]/4lu(0UXZNsv͝2BkkeəP5AfGF ?AءR GZ ;N+3m僣a0Rj,-EY oX;Z'X{kI c_Δ@H=X˔@ԉ]&*Cn$!>b`Ɗ@LS[!Fc*m Dnar0X P%P [+ ˫X?ӻZˎea\n ض/6u7դ7u?Y>oXFy^?sdL\C1 8Qy4+CWbFæK=W<8R>ޜ2|Jڸl,J% d,.6GScM0 :Ex11`\wpaH Ҡb)9q%H-Kg{ 0PpƇ#!W} BNZŅ k#_s0 kuL76 [Y*&9P( gj6&TWSI24ws{>󴥘?< ǵ€ 7a bt~X$vb\\ ,4kEUulf5s`,d%(oY #,@.wϷjJG'Jg < ǰ!8:+sR@ !@I2cn' ]:,p !ϵ~'^E/멐-⠸0X`Lflu M+L֗Fe62n E4/<ɝx5udu"78jN}3ve&q݊u+~NUeHrLEjtoB JzZ1ٔ۴,U" KJBB( {!O+":IA2ֺիSF?'x S`@'xF_sQOwJ mlh5Ov`" =IWiOJە ;hQFR2xQ14o˺L2ES[#=7rS-`B#^UsS(w %:8TvrILoyt0)(ʰ7V5wHT:aߴ~J D 5Ϭ%ij,{q>P5ݼ@:6v2 0KR^Z3ݠ/u!Z|'[#z $'m6rp<~*Rui $tMAz!tz_{ߐw#bhNZq7;Yw9\~M6ȋ0Zv`0[0I4 ["%_}sx;}A W7,8H>{9<@:Co_gŒ픲K#1P6Wz|__f>?r:[S )Oa,iH鉶6(z SHi^w r*UQko!>uYmz2RU쟐Q3 T0B ?fxyS ,jQ(Z$}7'(Ld]Uw8ixfm4HѦ$Y9HYH;Pj}:%2fDZ±-H_$K[nqm T \ ~kC5v %^7da'`Yc`/`M1`SLmd2 PyO45dKuVFQrCHJK  ;L FpA&Q&zJ%|Fr\M6:A7͗*N2}_?JCr=ӡY- -_M$[bQg5L. 9CKPꑶʶz)".AU/Etå}, {Kr ̋Hh)\ܧo?YR 6æ)P=6 YVjTw%JBewlTyU v0E5=rHB| qmz {<j|SQqM?TZK: UPW.K X"yfju᯲=3 8ːr⢭3!M߉>8@Lƒ c?e;_TCn IDAT+ u NJq. >HYUqxIφ0\#I!)RUe026°s@ޫCrRYI;W^ SR5Tk& gCvW@_]%>Y$gi`֢ 3&_},GI@ dWCT7m)r/M@JwʞQlZ|Z*9oM1Fʌu1UdgITa5`i9NBԌ@:3dK%eFmTMȍV QBc|_|%PXRz (EkNε'η2Ln"^s GHjo:T8+:$' !Xh9c2`]JWA=G `k ~~fn p'@6>=Zޡ._ 2nS4L̴E?6uT: |Q0x S39YBT ;ZLCL-lM'=q`2)WYl̃XK#W>dF~J ,0LJ?N3BI%.FbƮ ]I:2U)l&3`uoo\38:4_o% @*oہzHta x]~t}<]8SV&~ژLJs1x{QN^*J'2Ep:2ZDd2np/$N^ZC^=U- Ju`>dMلVˢsbwK_8*(kȺkU uK|Z{ߑnGɩqlL^$E3Hy24EDbܛ'W:#*hEgʬC΀ԃYvkI3Iop?zh7⣑|=?K 6#nN۶l%}X:% ڽE ]Jh|cVzOouW I="SIw*uSom-j*Ҍr&h]J>v]l~!O;> 4]T&U:(V:چ|ҀP2>`\jx69H~5).b)PN@jP uc7N8w7hWweܤr$Ϯ BZ!2@Ό0o@9[%1a :+CqhpwgXH~N.aJoxhwp0:ZM,L, : 57AG'ϐ"QPEp[9 E#eMu*\2=rZu; ~,_ '?@A ʯv(.Uۿ4~^ju V"_LmG{u q\NrCMesd'*R6Q Š)j.,ڡ2׉E xӋP\q*v#ke6`UPeTJ#&Y>~R -bD@00XU_w2*3"Xq./K_RP&( W8>Of6ZOw/XB;M~5rM$g± {T.h@nCZJ zJƛB\>βb` pڌZ<h\u{2K̻k2q2 N<>N>XT=Qd`t>͢$Ac'=ض{Yt(.#vp~^j Nz"Q 5!wr^*_L׃uRǶzYx Bcsh<$ftJԌ4;C6ïҭx48mBD@n'U{k4N&2H HSJӿ8#,*x^IzKJf[EK~6qbT-ފk ‰E_,LTqgkq35K7aAGɯ>\dßٴ{w`Q/GXS1[2HT:ҰV( L~ۈ)Gpns5CUH+Y Δ_;qfث!`0A(l!'+G n? fG(G<|*C@'Mљ{T]y R9$iz٬I[fFt2 䪅)=?|7JYOt%e?!k[\)?D|#KHcqNbu9 n+uIuG4KlM/&%B@J8go%(7 ?P#S^o/c{3|SIn+CIW#Y5o;|^N]*G sF=|,ҴvuOIHV8௞8:YM6BbB}a;6Ej?4(`*t`AUРvf|[뇍HdBlCq:ӣ$ S NJϩ2hg?7iy}Ƴ-x*Y)wm ?~vX3S[[A BD#.&ݥkz<+~sdɎF0FUL؈. ppWn^NҸ->P{=JPz{խYM75d"-kxqbL5 (@`*KNM7d5YVlḽ>Jx_`@C 0}8#?A +gh4OPSTAA1/&:WJ7&Y˱`'_ _ E6Sjp@KoD&ei;PY}'8<2]:M|*fp>5E{¼1kǸy<;x>>0~15%Ė}7^Ta=5pѰ¹7??l1֧5ؘٿg$gcQDp_u7K(H|8 ~\p8;7ˑ0d֛Mn#zHO`eMY/ IUFis\U(tQ^mZ#)/khV'}N'i9{ ۧ.c\h^3ռ%+? #;6-3dN'P$ޞ!u!Bݞd;~w„-~ls A#~j8)Y5vvqTT BL*[HT !ʐ$/k 'e?E}FDA;i|YzdߝlS&x_ s7R%}[rV*ѰݸkwXط6iMN3-ŗ /9LqF*n>"?ݳ#<'e^odB_BiPxH\9.9IBaВyhh鬹`"Пud Tnh9v%hP"!p L%jipX'pCy- g8VY^w=tuZ~0e58Q0DN^4KotQT'/`]a2}>ˊ˾dASTFIx>tu .|ӜX=;߲:99*i ϭxy[)[QHzr0>`EG!9YpN#gxXRjd+ar9ҫ5IMh,S dzA]|n:Bb" e43el 8"\&&ݥ?xXfp11,M"Q=1@0dƁll>ҪS*ƺܱ<BXٚ_AE}h1B}4? @ Kӡ]CPZzugټԏU<*iEbCb53Sn>NP k%dyy)Aʅ,,Ze~B?,r+6 _ij%Ŝ׉!W@Bqw')IE.¸5zR|`e% 'HFk Ye$n1IAkV1%DͱIbT#hn0wʝvo){wK矁mTm| ><> Ѯ)eEdx>W'js /o8IU\ky\xvrYڲp!^e~s\>3|h7wmܟpTl7^ \-O$[8;,tr5%M*S˜?:E{cR#wǍPJz9-ţfBs,lj!}{bL:1c'RV2x] Q9 L8 ĘZMLM$L*K`nd7YeU)Y}=F %7-H_-wVQlgkɛ%x7!n)@#Q_FmuRN% Ut3߉3y(`PgDfrHB] !!&8^~ pW%2P8A:܏ xTENqyH (0::ā~u wmWVݳASRx!iz;m\a*8vZvCf yYE՞.{g?-i6zXyØ\7؍OBhei6M2r08yh; k'{Iw8Jm4 4dyZr|VP8LAţ3,tjA_4 f}]-,SJ), _.c RajAvX ˦T-ք:\߶|Ы kfFJU8tA_.ޮa6\Jkz2\l\JmHس}8o922 "RfISG4{S\2&Ϛ3y2kdqZWܡ%HVN:B_HJyl)NJ%aFBEeߢRi+ĬGF'*>R0PrMN+[V(i_&.6IX[Sn]oڔ6ڛ5fzF[|Cزb6LIV;qp)C2?Q q{:2zJӺ6Bk r爄\>ڔ1oW>1J_A8O:cu\~W;s@M|:6W$2)LHvxS等jJ~󅲦{rfWbu([Q1,Wd]nVA Ѹ2mLÁy,/ۼCʛU);Zc7rWhQ3}VRTO/ej`֍@PEB#0 oܞz~ d:0n~ce1.1T J0l""EiOZYN"v56a%2dQN =VtZBO*,;33g3q\ηZ]Pz"R Nϗ4W h(S}(\“ɧswt9> p(1nbMBg\DU%,st_{\p;U5&$2C>Xt6qܕP*.JiyW>dX7C:#xܒ9 s;Sz<-M BN~yy:_T[-#VzBDnʛX_4FmH6D>Jf.;f0 ˍFz:ߤgYi9ԞHV_XD̑꬙]4yΛiYU@jO#x$PӳlGϐ$f}Խf%?(cLB۞ȓc5!`~SbH?jryUU16O29p?$7J=>t$s᭒>zٖːx٬>&}Ϸ[F,zΌiVJ>],a_ӉK:Dמ#Ĥ}~S g&ӋlQS+,Zf;jF+ FL a}}⇥zy1E3IqǓ9/oQ䘟H'1S7%uHZoƢϒE-!F12*7U8u@/\X)ή3]cBYR;y 2TTog,T4ר[ǭ[b\V? /N~E:ݘɗ6Ϻ?aav` Hs X 'c 464|X$ё&Sә6sR蓉o]ÓUxJJ4&kzLߖD*CVS|KۇTlaJ0pfA36cf =Jqd_OSg3 >4ȗa@*n v׿M;v\4.Y?){S>a6~IxH 8ӈmmfpoi3ԛ,dPF.M7| x)}?o׸kn'^=v4Da"6Qu09XLZ FZR3U'YyכCfJra!_tG =||5+mkrw-RH})Lŏ;b3k6R~ѱ I&ARSޭ;Pք@RG ~uo{"jCڒ^7,ڸ۬"tdH$SggEDG65oSw;ogxZ47QV93 |Z~tweBA=0~ q0vu^6QqL¤4D˵[kz_(,Qӳ=ʟ2OuE'⟤*$[AR;w:hw:X0M68D+wL l W܁͵^=Iý?MiM]b+:G"8 JbXڞLVUw{wuVQGT'rśwt<>E)[ ?GST0\oTu0sa)?R-Ǭa=īE%2L&m6\#Ysl35w~S|HZr u&ƾ)Z~ZLMfhiۀq؊ zHnԇT́Bs{@qn[Z˼`$;pSV-:u{g p+q`+>\]oZ_}|;lP;uy) )rKLlzB^Lv:R:(i1NGjSwl Z6i@]1NrX0֯*>,E*H%,<&R/ .򩛅Mp+YV|5ެI\҇##z<2e*5B /s/bfV*]O|)3!s@[x "w.ђBWE0)c !S/T=ze$᣹f0Z!&gͶ!͂T/i{-wɘV U"7 ~StO54d C7}##-H[<$KB|ROۦkD/ g(9l O$¨V%Zc_P Yyy&~cA.%k~ӕU UD}W?sAH èlI?NDH>B'vDFYW KkH) UIwn#*iW/>9!U'/\ʰ|8P)e;>Ypʏ@3@_ET]6)h#&8؇0('F#T:Q_8A#~UJA~aifu8C ~[KÍhj*k'8W!|XBlFf$2cꂆ*{Cjbi/İʁUL@fG6P;eU#P-n&)Gi@,Iv)I?6#'dǤ:4UU~SAv )GHGy-4-|.3@U0Elv|gLj_5+ddF݅ +oq=@k#!%B[Z1yIgrŔuhl:ѻͤ(&j0pK[Y.5&[|Crf_P08m%/Q;?|cNk[Ӗ]/DXY"Y(cP(E|&SKd o]R佰 64S]ܧl1sU[8.mx^z:'}N t36XLg-|:όMp`vCHlQv>!7<0L1=u $R%GxA\s2C6sS&kc)8c bWOz Mti 9 (*O5 @TnOeEWxƔ%YP #q ƣF3fHz-vu_CZc6ij?Ԫ;S5w^!Y9S/6UnФa;kh5Xl,+{;X`N6v]Ù J?Hx~6=*N>#g5:YWCló+׌@0ݤl4`"/>txWa3c{ 4խ9G/I=-0P[ꅭYOmfJ!QKL(ؖmc\0ERM"?;XٓckS)?v/%Kw)JpL4tT+{?xʘG)c|seհ07!GBV-Z6U9$ "4˱v4˄GD _(]H.3i) (| @Q%QgK_@C)y(2 !>$ٶ< !j ;#歱;W|y4GkrH >kO*OBs3cGE+*1rz߷ [no ?h|O8h(?Q}ɼ=k%_NXK}K @i:z԰i^ BS1g}TBR$( njcQ`<.e>֥`b$&Cה5f|)-bȖ5Z3l| [$D2=a8O= ug" NjVޠtsM',85⊊e tɼ~@J0v07dx@mwbYV&)f Y7(B CJ΄/<i)@ykh>u\ꩽJ}p QvRl{kwh2"P M%!\bx2@z彗 `xH"5Z|<Σnmj VY`':1%P,߰\BϔJ}tW-_)3mznUbfr&Jbj5ݔc~'9arx/6 Q8[udU96 K:/ITH?c۾́Yl&Wv}.,ujj@R.W5"급L`Slb^c/OD`R(ՑUk-[$oyg}t-G3N"g 11r[JRLD|QG~EKaiqf N蔶N~DiҲMstpI~uuWg+T`_16Xג" @vdtyp ,9kAȥipߣ#ְݕմө<ң=bbwV&r_;I2JCy*YՃƄ,r..&`VRuQ3BBЊ-^9ζXr.畕x"x$ψߙR @n~};/ӛ.,-N$9yڛOʘ9آe?2;;\ݯo}͍4G1{;*QyxDHr;2* 'ͥ X_qDT"suC2ezSG}\IUBG#IQ9A *UMI:Ʒ])@rr"8?]bSOf4 c:m?lױ 픱>DҜ?7uf=)ҥϣ;(UWKS yKzJd /i63OdfZe{R-YS- $߻sC\6Zrjr61_AC>'*4ѥ߶mNxS[5!~U m{ti)aڷI) vFyٔ{6R()?~ܵ}\m>mz})=t^}_-̧pD'nRUh}d܇.·!:"=>j\HY'{!b6ᇂ`T6)3tlGd4s/ϔɗՄʼ@3xc՛|ʷ/B#Bk#ysUev JwXMˉ-&#vp|He`N\"D9If7,_G4IOrub ~mES^k׮١U;Jt *4i0oE@r8KQoPf*]"ʳ-O贵T,KG̽u)4G=c!ȕ9 /%x8 ޻_I=☓4Edy4SG)pxYi]/dev/null | xargs chmod a+t# df --local -P | awk {'if (NR!=1) print $6'} | xargs -I '{}' find '{}' -xdev -type d ( -perm -0002 -a ! -perm -1000 ) 2>/dev/null1.2.10Configure Connection to the RHN RPM RepositoriesSystems need to be registered with the Red Hat Network (RHN) to receive patch updates. This is usually configured during initial installation.It is important to register with the Red Hat Network to make sure that patches are updated on a regular basis. This helps to reduce the exposure time as new vulnerabilities are discovered.YIf your system is not listed on the RHN site as a registered system, run the Red Hat Network Registration tool as follows: # rhn_register Follow the prompts on the screen. If successful, the system will appear on the RHN web site and be subscribed to one or more software update channels. Additionally, a new daemon, rhnsd, will be enabled.]Verify that the system is registered by executing the following command: # yum check-update1.2.2#Verify Red Hat GPG Key is InstalledURed Hat cryptographically signs updates with a GPG key to verify that they are valid.It is important to ensure that updates are obtained from a valid source to protect against spoofing that could lead to the inadvertent installation of malware on the system. Compare the GPG fingerprint with the one from Red Hat's web site at http://www.redhat.com/security/team/key [http://www.redhat.com/security/team/key]. The following command can be used to print the installed release key's fingerprint, which is actually contained in the file referenced below: # gpg --quiet --with-fingerprint /etc/pki/rpm-gpg/RPM-GPG-KEY-redhat-release More information on package signing is also available at https://access.redhat.com/security/team/key [https://access.redhat.com/security/team/key].Run the following command to ensure that the system has the Red Hat GPG key properly installed: # rpm -q --queryformat "%{SUMMARY}n" gpg-pubkey1.2.3*Verify that gpgcheck is Globally ActivatedThe gpgcheck option, found in the main section of the /etc/yum.conf file determines if an RPM package's signature is always checked prior to its installation.It is important to ensure that an RPM's package signature is always checked prior to installation to ensure that the software is obtained from a trusted source.NEdit the /etc/yum.conf file and set the gpgcheck to 1 as follows: gpgcheck=1Run the following command to verify that gpgcheck is set to 1 in all occurrences of the /etc/yum.conf file: # grep gpgcheck /etc/yum.conf gpgcheck=11.2.5(Obtain Software Package Updates with yum The yum update utility performs software updates, including dependency analysis, based on repository metadata and can be run manually from the command line, invoked from one of the provided front-end tools, or configured to run automatically at specified intervals.The yum update utility is the preferred method to update software since it checks for dependencies and ensures that the software is installed correctly. Refer to your local patch management procedures for the method used to perform yum updates. # yum updaterPerform the following command to determine if there are any packages that need to be updated: # yum check-update1.2.6"Verify Package Integrity Using RPMRPM has the capability of verifying installed packages by comparing the installed files against the file information stored in the package.Verifying packages gives a system administrator the ability to detect if package files were changed, which could indicate that a valid binary was overwritten with a trojaned binary.>Address unexpected discrepancies identified in the audit step.FPerform the following to verify integrity of installed packages. # rpm -qVa | awk '$2 != "c" { print $0}' If any output shows up, you may have an integrity issue with that package NOTE: Actions in other areas of the benchmark change permissions on some files to make them more secure than the default, which would cause this check to fail. It is important to validate the packages either have the permissions they were intended to have, or have been intentionally altered. It is recommended that any output generated in the audit step be investigated to justify the discrepancy.1.5.1&Set User/Group Owner on /etc/grub.conf;Set the owner and group of /etc/grub.conf to the root user.SSetting the owner and group to root prevents non-root users from changing the file. # chown root:root /etc/grub.confPerform the following to determine if the /etc/grub.conf file has the correct ownership: # stat -L -c "%u %g" /etc/grub.con< f | egrep "0 0" If the above command emits no output then the system is not configured as recommended.1.5.2!Set Permissions on /etc/grub.confJSet permission on the /etc/grub.conf file to read and write for root only.Setting the permissions to read and write for root only prevents non-root users from seeing the boot parameters or changing them. Non-root users who read the boot parameters may be able to identify weaknesses in security upon boot and be able to exploit them.# chmod og-rwx /etc/grub.confPerform the following to determine if the /etc/grub.conf file permissions are correct: # stat -L -c "%a" /etc/grub.conf | egrep ".00" If the above command emits no output then the system is not configured as recommended.1.5.3Set Boot Loader PasswordSetting the boot loader password will require that the person who is rebooting the must enter a password before being able to set command line boot parametersRequiring a boot password upon execution of the boot loader will prevent an unauthorized user from entering boot parameters or changing the boot partition. This prevents users from weakening security (e.g. turning off SELinux at boot time).Use grub-md5-crypt to produce an encrypted password: # grub-md5-crypt Password: Retype password: _[Encrypted Password]_ Set the password parameter to_[Encrypted Password]_ in /etc/grub.conf: password --md5 _[Encrypted Password]_Perform the following to determine if a password is required to set command line boot parameters: # grep "^password" /etc/grub.conf password --md5 _[Encrypted Password]_ NOTE: Requirement is only that a password is set, other encryption options are available.1.5.4+Require Authentication for Single-User ModeSince /etc/init determines what run state the system is in, setting the entry in /etc/sysconfig/init will force single user authentication.Requiring authentication in single user mode prevents an unauthorized user from rebooting the system into single user to gain root privileges without credentials.hRun the following to edit /etc/sysconfig/init: sed -i "/SINGLE/s/sushell/sulogin/" /etc/sysconfig/initPerform the following to determine if /etc/sysconfig/init is configured correctly: # grep SINGLE /etc/sysconfig/init SINGLE=/sbin/sulogin1.5.5Disable Interactive BootThe PROMPT option provides console users the ability to interactively boot the system and select which services to start on boot .}Turn off the PROMPT option on the console to prevent console users from potentially overriding established security settings.BSet the PROMPT parameter in /etc/sysconfig/init to no. PROMPT=nokPerform the following to determine if PROMPT is disabled: # grep "^PROMPT=" /etc/sysconfig/init PROMPT=no1.6.1Restrict Core Dumps A core dump is the memory of an executable program. It is generally used to determine why a program aborted. It can also be used to glean confidential information from a core file. The system provides the ability to set a soft limit for core dumps, but this can be overridden by the user.Setting a hard limit on core dumps prevents users from overriding the soft variable. If core dumps are required, consider setting limits for user groups (see limits.conf(5)). In addition, setting the fs.suid_dumpable variable to 0 will prevent setuid programs from dumping core.Add the following line to the /etc/security/limits.conf file. * hard core 0 Add the following line to the /etc/sysctl.conf file. fs.suid_dumpable = 0Perform the following to determine if core dumps are restricted. # grep "hard core" /etc/security/limits.conf * hard core 0 # sysctl fs.suid_dumpable fs.suid_dumpable = 01.6.2Configure ExecShieldExecshield is made up of a number of kernel features to provide protection against buffer overflow attacks. These features include prevention of execution in memory data space, and special handling of text buffers.jEnabling any feature that can protect against buffer overflow attacks enhances the security of the system.MAdd the following line to the /etc/sysctl.conf file. kernel.exec-shield = 1qPerform the following to determine if ExecShield is enabled. # sysctl kernel.exec-shield kernel.exec-shield = 11.6.31Enable Randomized Virtual Memory Region PlacementHSet the system flag to force randomized virtual memory region placement.Randomly placing virtual memory regions will make it difficult for to write memory page exploits as the memory placement will be consistently shifting.TAdd the following line to the /etc/sysctl.conf file. kernel.randomize_va_space = 2Perform the following to determine if virtual memory is randomized. # sysctl kernel.randomize_va_space kernel.randomize_va_space = 2Use the Latest OS ReleasePeriodically, Red Hat releases updates to the Red Hat operating system to support new hardware platforms, deliver new functionality as well as the bundle together a set of patches that can be tested as a unit.Newer updates may contain security enhancements that would not be available through the standard patching process. As a result, it is recommended that the latest update of the Red Hat software be used to take advantage of the latest functionality. As with any software installation, organizations need to determine if a given update meets their requirements and verify the compatibility and supportability of any additional software against the update revision that is selected.Use the latest update when installing new systems and upgrade to or reinstall with the latest update as appropriate for existing systems.kRun the following command to determine the current OS level: # uname -r or # cat /etc/redhat-release2.1.1Remove telnet-serverThe telnet-server package contains the telnetd daemon, which accepts connections from users from other systems via the telnet protocol.1The telnet protocol is insecure and unencrypted. The use of an unencrypted transmission medium could allow a user with access to sniff network traffic the ability to steal credentials. The ssh package provides an encrypted session and stronger security and is included in most Red Hat Linux distributions.# yum erase telnet-serverPerform the following to determine if the telnet-server package is on the system. # rpm -q telnet-server package telnet-server is not installed2.1.2Remove telnet ClientsThe telnet package contains the telnet client, which allows users to start connections to other systems via the telnet protocol. The telnet protocol is insecure and unencrypted. The use of an unencrypted transmission medium could allow an authorized user to steal credentials. The ssh package provides an encrypted session and stronger security and is included in most Red Hat Linux distributions.# yum erase telnet|Perform the following to determine if the telnet package is on the system. # rpm -q telnet package telnet is not installed2.1.3Remove rsh-servertThe Berkeley rsh-server (rsh, rlogin, rcp) package contains legacy services that exchange credentials in clear-text.qThese legacy service contain numerous security exposures and have been replaced with the more secure SSH package.# yum erase rsh-serverPerform the following to determine if rsh-server is installed on the system. # rpm -q rsh-server package rsh-server is not installed2.1.4 Remove rshBThe rsh package contains the client commands for the rsh services.These legacy clients contain numerous security exposures and have been replaced with the more secure SSH package. Even if the server is removed, it is best to ensure the clients are also removed to prevent users from inadvertently attempting to use these commands and therefore exposing their credentials. Note that removing the rsh package removes the clients for rsh, rcp and rlogin.# yum erase rshqPerform the following to determine if rsh is installed on the system. # rpm -q rsh package rsh is not installed2.1.5Remove NIS ClientThe Network Information Service (NIS), formerly known as Yellow Pages, is a client-server directory service protocol used to distribute system configuration files. The NIS < client (ypbind) was used to bind a machine to an NIS server and receive the distributed configuration files./The NIS service is inherently an insecure system that has been vulnerable to DOS attacks, buffer overflows and has poor authentication for querying NIS maps. NIS generally has been replaced by such protocols as Lightweight Directory Access Protocol (LDAP). It is recommended that the service be removed.# yum erase ypbindzPerform the following to determine if ypbind is installed on the system. # rpm -q ypbind package ypbind is not installed2.1.6Remove NIS ServerThe Network Information Service (NIS) (formally known as Yellow Pages) is a client-server directory service protocol for distributing system configuration files. The NIS server is a collection of programs that allow for the distribution of configuration files.SThe NIS service is inherently an insecure system that has been vulnerable to DOS attacks, buffer overflows and has poor authentication for querying NIS maps. NIS generally been replaced by such protocols as Lightweight Directory Access Protocol (LDAP). It is recommended that the service be disabled and other, more secure services be used# yum erase ypservzPerform the following to determine if ypserv is installed on the system. # rpm -q ypserv package ypserv is not installed2.1.7 Remove tftp2Trivial ob Transfer Protocol (TFTP) is a simple file transfer protocol, typically used to automatically transfer configuration or boot files between machines. TFTP does not support authentication and can be easily hacked. The package tftp is a client program that allows for connections to a tftp server.It is recommended that TFTP be removed, unless there is a specific need for TFTP (such as a boot server). In that case, use extreme caution when configuring the services.# yum erase tftptPerform the following to determine if tftp is installed on the system. # rpm -q tftp package tftp is not installed2.1.8Remove tftp-serverTrivial ob Transfer Protocol (TFTP) is a simple file transfer protocol, typically used to automatically transfer configuration or boot machines from a boot server. The package tftp-server is the server package used to define and support a TFTP server.TFTP does not support authentication nor does it ensure the confidentiality of integrity of data. It is recommended that TFTP be removed, unless there is a specific need for TFTP. In that case, extreme caution must be used when configuring the services.# yum erase tftp-serverPerform the following to determine if tftp-server is installed on the system. # rpm -q tftp-server package tftp-server is not installed2.1.9 Remove talkThe talk software makes it possible for users to send and receive messages across systems through a terminal session. The talk client (allows initialization of talk sessions) is installed by default.YThe software presents a security risk as it uses unencrypted protocols for communication.# yum erase talktPerform the following to determine if talk is installed on the system. # rpm -q talk package talk is not installed2.1.10Remove talk-serverThe talk software makes it possible for users to send and receive messages across systems through a terminal session. The talk client (allows initiate of talk sessions) is installed by default.# yum erase talk-serverPerform the following to determine if talk-server is installed on the system: # rpm -q talk-server package talk-server is not installed2.1.12Disable chargen-dgramchargen-dram is a network service that responds with 0 to 512 ASCII characters for each datagram it receives. This service is intended for debugging and testing purposes. It is recommended that this service be disabled.KDisabling this service will reduce the remote attack surface of the system.cDisable the chargen-dgram service by running the following command: # chkconfig chargen-dgram off4# chkconfig --list chargen-dgram chargen-dgram: off2.1.13Disable chargen-streamchargen-stream is a network service that responds with 0 to 512 ASCII characters for each connection it receives. This service is intended for debugging and testing purposes. It is recommended that this service be disabled.eDisable the chargen-stream service by running the following command: # chkconfig chargen-stream off6# chkconfig --list chargen-stream chargen-stream: off2.1.14Disable daytime-dgramdaytime-dgram is a network service that responds with the server's current date and time. This service is intended for debugging and testing purposes. It is recommended that this service be disabled.cDisable the daytime-dgram service by running the following command: # chkconfig daytime-dgram off4# chkconfig --list daytime-dgram daytime-dgram: off2.1.15Disable daytime-streamdaytime-stream is a network service that responds with the server's current date and time. This service is intended for debugging and testing purposes. It is recommended that this service be disabled.eDisable the daytime-stream service by running the following command: # chkconfig daytime-stream off6# chkconfig --list daytime-stream daytime-stream: off2.1.16Disable echo-dgramecho-dgram is a network service that responds to clients with the data sent to it by the client. This service is intended for debugging and testing purposes. It is recommended that this service be disabled.]Disable the echo-dgram service by running the following command: # chkconfig echo-dgram off.# chkconfig --list echo-dgram echo-dgram: off2.1.17Disable echo-streamecho-stream is a network service that responds to clients with the data sent to it by the client. This service is intended for debugging and testing purposes. It is recommended that this service be disabled._Disable the echo-stream service by running the following command: # chkconfig echo-stream off0# chkconfig --list echo-stream echo-stream: off2.1.18Disable tcpmux-servertcpmux-server is a network service that allows a client to access other network services running on the server. It is recommended that this service be disabled.tcpmux-server can be abused to circumvent the server's host based firewall. Additionally, tcpmux-server can be leveraged by an attacker to effectively port scan the server.cDisable the tcpmux-server service by running the following command: # chkconfig tcpmux-server off3# chkconfig --list tcpmux-server tcpmux-server: offSet Daemon umaskSet the default umask for all processes started at boot time. The settings in umask selectively turn off default permission when a file is created by a daemon process.NSetting the umask to 027 will make sure that files created by daemons will not be readable, writable or executable by any other than the group and owner of the daemon process and will not be writable by the group of the daemon process. The daemon process can manually override these settings if these files need additional permission.CAdd the following line to the /etc/sysconfig/init file. umask 027lPerform the following to determine if the daemon umask is set. # grep umask /etc/sysconfig/init umask 027Remove the X Window System The X Window system provides a Graphical User Interface (GUI) where users can have multiple windows in which to run programs and various add on. The X Window system is typically used on desktops where users login, but not on servers where users typically do not login.Unless your organization specifically requires graphical login access via the X Window System, remove the server to reduce the potential attack surface.Edit the /etc/inittab file to set the default runlevel as follows: id:3:initdefault Uninstall the X Window Server: # yum remove xorg-x11-server-commonPerform the following to determine if the X Window server is installed on the system: # grep "^id:" /etc/inittab id:3:initdefault # rpm -q xorg-x11-server-commonDisable Avahi ServerAvahi is a free zeroconf implementation, including a system for multicast DNS/DNS-SD service discovery. Avahi allows programs to publish and discover services and hosts runni< ng on a local network with no specific configuration. For example, a user can plug a computer into a network and Avahi automatically finds printers to print to, files to look at and people to talk to, as well as network services running on the machine.>Since servers are not normally used for printing, this service is not needed unless dependencies require it. If this is the case, disable the service to reduce the potential attack surface. If for some reason the service is required on the server, follow the recommendations in sub-sections 3.2.1 - 3.2.5 to secure it.f# chkconfig avahi-daemon off In addition, edit the /etc/sysconfig/network file and remove zeroconf.Perform the following to determine if Avahi is disabled. # chkconfig --list avahi-daemon avahi-daemon: 0:off 1:off 2:off 3:off 4:off 5:off 6:offDisable Print Server - CUPS The Common Unix Print System (CUPS) provides the ability to print to both local and network printers. A system running CUPS can also accept print jobs from remote systems and print them to local printers. It also provides a web based remote administration capability.If the system does not need to print jobs or accept print jobs from other systems, it is recommended that CUPS be disabled to reduce the potential attack surface.# chkconfig cups offPerform the following to determine if CUPS is disabled. # chkconfig --list cups chkconfig: 0:off 1:off 2:off 3:off 4:off 5:off 6:offRemove DHCP ServeryThe Dynamic Host Configuration Protocol (DHCP) is a service that allows machines to be dynamically assigned IP addresses.Unless a server is specifically set up to act as a DHCP server, it is recommended that this service be deleted to reduce the potential attack surface.# yum erase dhcpePerform the following to determine if DHCP is disabled. # rpm -q dhcp package dhcp is not installed%Configure Network Time Protocol (NTP)'The Network Time Protocol (NTP) is designed to synchronize system clocks across a variety of systems and use a source that is highly accurate. The version of NTP delivered with Red Hat can be found at http://www.ntp.org [http://www.ntp.org]. NTP can be configured to be a client and/or a server.gIt is recommended that physical systems and virtual guests lacking direct access to the physical host's clock be configured as NTP clients to synchronize their clocks (especially to support time sensitive security mechanisms like Kerberos). This also ensures log files have consistent time records across the enterprise, which aids in forensic investigations.NTP is configured by default in RHEL6. If for some reason, it is not configured on your system, set the following restrict parameters in /etc/ntp.conf: restrict default kod nomodify notrap nopeer noquery restrict -6 default kod nomodify notrap nopeer noquery Also, make sure /etc/ntp.conf has an NTP server specified: server NOTE: __ is the IP address or hostname of a trusted time server. Configuring an NTP server is outside the scope of this benchmark..The following script checks for the correct parameters on restrict default and restrict -6 default: # grep "restrict default" /etc/ntp.conf restrict default kod nomodify notrap nopeer noquery # grep "restrict -6 default" /etc/ntp.conf restrict -6 default kod nomodify notrap nopeer noquery Perform the following to determine if the system is configured to use an NTP Server and that the ntp daemon is running as an unprivileged user. # grep "^server" /etc/ntp.conf server # grep "ntp:ntp" /etc/sysconfig/ntpd OPTIONS="-u ntp:ntp -p /var/run/ntpd.pid" Remove LDAPThe Lightweight Directory Access Protocol (LDAP) was introduced as a replacement for NIS/YP. It is a service that provides a method for looking up information from a central database. The default client/server LDAP application for Red Hat is OpenLDAP.If the server will not need to act as an LDAP client or server, it is recommended that the software be disabled to reduce the potential attack surface.If LDAP is running on the system and is not needed, remove it as follows: # yum erase openldap-servers # yum erase openldap-clientsDisable NFS and RPCThe Network ob System (NFS) is one of the first and most widely distributed file systems in the UNIX environment. It provides the ability for systems to mount file systems of other servers through the network.If the server does not export NFS shares or act as an NFS client, it is recommended that these services be disabled to reduce remote attack surface.|# chkconfig nfslock off # chkconfig rpcgssd off # chkconfig rpcbind off # chkconfig rpcidmapd off # chkconfig rpcsvcgssd offPerform the following to determine if NFS is disabled. # chkconfig --list nfslock nfslock: 0:off 1:off 2:off 3:off 4:off 5:off 6:off # chkconfig --list rpcgssd rpcgssd: 0:off 1:off 2:off 3:off 4:off 5:off 6:off # chkconfig --list rpcbind rpcbind: 0:off 1:off 2:off 3:off 4:off 5:off 6:off # chkconfig --list rpcidmapd rpcidmapd: 0:off 1:off 2:off 3:off 4:off 5:off 6:off # chkconfig --list rpcsvcgssd rpcsvcgssd: 0:off 1:off 2:off 3:off 4:off 5:off 6:offRemove DNS ServerThe Domain Name System (DNS) is a hierarchical naming system that maps names to IP addresses for computers, services and other resources connected to a network.Unless a server is specifically designated to act as a DNS server, it is recommended that the package be deleted to reduce the potential attack surface.# yum erase bindrPerform the following to determine if DNS is disabled on the system. # rpm -q bind package bind is not installedRemove FTP ServeraThe ob Transfer Protocol (FTP) provides networked computers with the ability to transfer files.HFTP does not protect the confidentiality of data or authentication credentials. It is recommended sftp be used if file transfer is required. Unless there is a need to run the system as a FTP server (for example, to allow anonymous downloads), it is recommended that the package be deleted to reduce the potential attack surface.# yum erase vsftpdhPerform the following to determine if FTP is disabled. # rpm -q vsftpd package vsftpd is not installedRemove HTTP ServerHTTP or web servers provide the ability to host web site content. The default HTTP server shipped with Red Hat Linux is Apache.Unless there is a need to run the system as a web server, it is recommended that the package be deleted to reduce the potential attack surface.# yum erase httpdiPerform the following to determine if apache is disabled. # rpm -q httpd package httpd is not installed'Remove Dovecot (IMAP and POP3 services)GDovecot is an open source IMAP and POP3 server for Linux based systems.Unless POP3 and/or IMAP servers are to be provided to this server, it is recommended that the service be deleted to reduce the potential attack surface.# yum erase dovecot}Perform the following to determine if dovecot is installed on the system. # rpm -q dovecot package dovecot is not installed Remove Samba_The Samba daemon allows system administrators to configure their Linux systems to share file systems and directories with Windows desktops. Samba will advertise the file systems and directories via the Small Message Block (SMB) protocol. Windows desktop users will be able to mount these directories and file systems as letter drives on their systems.If there is no need to mount directories and file systems to Windows systems, then this service can be deleted to reduce the potential attack surface.# yum erase sambawPerform the following to determine if samba is installed on the system. # rpm -q samba package samba is not installedRemove HTTP Proxy ServerCThe default HTTP proxy package shipped with Red Hat Linux is squid.If there is no need for a proxy server, it is recommended that the squid proxy be deleted to reduce the potential attack surface.# yum erase squidwPerform the following to determine if squid is installed on the system. # rpm -q squid package squid is not installedRemove SNMP ServerThe Simple Network Management Protocol (SNMP) server is used to listen for SNMP commands from an SNMP management system, execute th< e commands or collect the information and then send results back to the requesting system.The SNMP server communicates using SNMP v1, which transmits data in the clear and does not require authentication to execute commands. Unless absolutely necessary, it is recommended that the SNMP service not be used.# yum erase net-snmpPerform the following to determine if net-snmp is installed on the system. # rpm -q net-snmp package net-snmp is not installed1Configure Mail Transfer Agent for Local-Only Mode\Mail Transfer Agents (MTA), such as sendmail and Postfix, are used to listen for incoming mail and transfer the messages to the appropriate user or mail server. If the system is not intended to be a mail server, it is recommended that the MTA be configured to only process local mail. By default, the MTA is set to loopback mode on RHEL5 and RHEL6.The software for all Mail Transfer Agents is complex and most have a long history of security issues. While it is important to ensure that the system can process local mail messages, it is not necessary to have the MTA's daemon listening on a port unless the server is intended to be a mail server that receives and processes mail from other systems. NOTE: RHEL5 uses sendmail as the default MTA while RHEL6 uses Postfix. The recommendation to set the default MTA to local-only mode applies regardless of the MTA that is used.Edit /etc/postfix/main.cf and add the following line to the RECEIVING MAIL section. If the line already exists, change it to look like the line below. inet_interfaces = localhost # Execute the following command to restart postfix # service postfix restartPerform the following command and make sure that the MTA is listening on the loopback address (127.0.0.1): # netstat -an | grep LIST | grep ":25[[:space:]]" tcp 0 0 127.0.0.1:25 0.0.0.0:* LISTEN4.1.1Disable IP ForwardingThe net.ipv4.ip_forward flag is used to tell the server whether it can forward packets or not. If the server is not to be used as a router, set the flag to 0.Setting the flag to 0 ensures that a server with multiple interfaces (for example, a hard proxy), will never be able to forward packets, and therefore, never serve as a router.Set the net.ipv4.ip_forward parameter to 0 in /etc/sysctl.conf: net.ipv4.ip_forward=0 Modify active kernel parameters to match: # /sbin/sysctl -w net.ipv4.ip_forward=0 # /sbin/sysctl -w net.ipv4.route.flush=1Perform the following to determine if net.ipv4.ip_forward is enabled on the system. # /sbin/sysctl net.ipv4.ip_forward net.ipv4.ip_forward = 04.1.2Disable Send Packet RedirectsICMP Redirects are used to send routing information to other hosts. As a host itself does not act as a router (in a host only configuration), there is no need to send redirects.An attacker could use a compromised host to send invalid ICMP redirects to other router devices in an attempt to corrupt routing and have users access a system set up by the attacker as opposed to a valid system.Set the net.ipv4.conf.all.send_redirects and net.ipv4.conf.default.send_redirects parameters to 0 in /etc/sysctl.conf: net.ipv4.conf.all.send_redirects=0 net.ipv4.conf.default.send_redirects=0 Modify active kernel parameters to match: # /sbin/sysctl -w net.ipv4.conf.all.send_redirects=0 # /sbin/sysctl -w net.ipv4.conf.default.send_redirects=0 # /sbin/sysctl -w net.ipv4.route.flush=1Perform the following to determine if send packet redirects is disabled. # /sbin/sysctl net.ipv4.conf.all.send_redirects net.ipv4.conf.all.send_redirects = 0 # /sbin/sysctl net.ipv4.conf.default.send_redirects net.ipv4.conf.default.send_redirects = 04.2.1'Disable Source Routed Packet AcceptanceIn networking, source routing allows a sender to partially or fully specify the route packets take through a network. In contrast, non-source routed packets travel a path determined by routers in the network. In some cases, systems may not be routable or reachable from some locations (e.g. private addresses vs. Internet routable), and so source routed packets would need to be used.Setting net.ipv4.conf.all.accept_source_route and net.ipv4.conf.default.accept_source_route to 0 disables the system from accepting source routed packets. Assume this server was capable of routing packets to Internet routable addresses on one interface and private addresses on another interface. Assume that the private addresses were not routable to the Internet routable addresses and vice versa. Under normal routing circumstances, an attacker from the Internet routable addresses could not use the server as a way to reach the private address servers. If, however, source routed packets were allowed, they could be used to gain access to the private address systems as the route could be specified, rather than rely on routing protocols that did not allow this routing.Set the net.ipv4.conf.all.accept_source_route and net.ipv4.conf.default.accept_source_route parameters to 0 in /etc/sysctl.conf: net.ipv4.conf.all.accept_source_route=0 net.ipv4.conf.default.accept_source_route=0 Modify active kernel parameters to match: # /sbin/sysctl -w net.ipv4.conf.all.accept_source_route=0 # /sbin/sysctl -w net.ipv4.conf.default.accept_source_route=0 # /sbin/sysctl -w net.ipv4.route.flush=1Perform the following to determine if accepting source routed packets is disabled. # /sbin/sysctl net.ipv4.conf.all.accept_source_route net.ipv4.conf.all.accept_source_route = 0 # /sbin/sysctl net.ipv4.conf.default.accept_source_route net.ipv4.conf.default.accept_source_route = 04.2.2 Disable ICMP Redirect AcceptanceICMP redirect messages are packets that convey routing information and tell your host (acting as a router) to send packets via an alternate path. It is a way of allowing an outside routing device to update your system routing tables. By setting net.ipv4.conf.all.accept_redirects to 0, the system will not accept any ICMP redirect messages, and therefore, won't allow outsiders to update the system's routing tables.Attackers could use bogus ICMP redirect messages to maliciously alter the system routing tables and get them to send packets to incorrect networks and allow your system packets to be captured.Set the net.ipv4.conf.all.accept_redirects and net.ipv4.conf.default.accept_redirects parameters to 0 in /etc/sysctl.conf: net.ipv4.conf.all.accept_redirects=0 net.ipv4.conf.default.accept_redirects=0 Modify active kernel parameters to match: # /sbin/sysctl -w net.ipv4.conf.all.accept_redirects=0 # /sbin/sysctl -w net.ipv4.conf.default.accept_redirects=0 # /sbin/sysctl -w net.ipv4.route.flush=1 Perform the following to determine if ICMP redirect messages will be rejected. # /sbin/sysctl net.ipv4.conf.all.accept_redirects net.ipv4.conf.all.accept_redirects = 0 # /sbin/sysctl net.ipv4.conf.default.accept_redirects net.ipv4.conf.default.accept_redirects = 04.2.4Log Suspicious Packets\When enabled, this feature logs packets with un-routable source addresses to the kernel log.Enabling this feature and logging these packets allows an administrator to investigate the possibility that an attacker is sending spoofed packets to their server.Set the net.ipv4.conf.all.log_martians and net.ipv4.conf.default.log_martians parameters to 1 in /etc/sysctl.conf: net.ipv4.conf.all.log_martians=1 net.ipv4.conf.default.log_martians=1 net.ipv4.route.flush=1 Modify active kernel parameters to match: # /sbin/sysctl -w net.ipv4.conf.all.log_martians=1 # /sbin/sysctl -w net.ipv4.conf.default.log_martians=1 # /sbin/sysctl -w net.ipv4.route.flush=1Perform the following to determine if suspicious packets are logged. # /sbin/sysctl net.ipv4.conf.all.log_martians net.ipv4.conf.all.log_martians = 1 # /sbin/sysctl net.ipv4.conf.default.log_martians net.ipv4.conf.default.log_martians = 14.2.5 Enable Ignore Broadcast RequestsSetting net.ipv4.icmp_echo_ignore_broadcasts to 1 will cause the system to ignore all ICMP echo and timestamp requests to broadcast and multicast addresses.(Accepting ICMP echo and timestamp requests with broadcast or multicast destinations for your network could be used to trick your host into start< ing (or participating) in a Smurf attack. A Smurf attack relies on an attacker sending large amounts of ICMP broadcast messages with a spoofed source address. All hosts receiving this message and responding would send echo-reply messages back to the spoofed address, which is probably not routable. If many hosts respond to the packets, the amount of traffic on the network could be significantly multiplied. Set the net.ipv4.icmp_echo_ignore_broadcasts parameter to 1 in /etc/sysctl.conf: net.ipv4.icmp_echo_ignore_broadcasts=1 Modify active kernel parameters to match: # /sbin/sysctl -w net.ipv4.icmp_echo_ignore_broadcasts=1 # /sbin/sysctl -w net.ipv4.route.flush=1Perform the following to determine if all ICMP echo and timestamp requests to broadcast and multicast addresses will be ignored. # /sbin/sysctl net.ipv4.icmp_echo_ignore_broadcasts net.ipv4.icmp_echo_ignore_broadcasts = 14.2.6#Enable Bad Error Message ProtectionSetting icmp_ignore_bogus_error_responses to 1 prevents the kernel from logging bogus responses (RFC-1122 non-compliant) from broadcast reframes, keeping file systems from filling up with useless log messages.Some routers (and some attackers) will send responses that violate RFC-1122 and attempt to fill up a log file system with many useless error messages.Set the net.ipv4.icmp_ignore_bogus_error_responses parameter to 1 in /etc/sysctl.conf: net.ipv4.icmp_ignore_bogus_error_responses=1 Modify active kernel parameters to match: # /sbin/sysctl -w net.ipv4.icmp_ignore_bogus_error_responses=1 # /sbin/sysctl -w net.ipv4.route.flush=1Perform the following to determine if bogus messages will be ignored. # /sbin/sysctl net.ipv4.icmp_ignore_bogus_error_responses net.ipv4.icmp_ignore_bogus_error_responses = 14.2.8Enable TCP SYN CookiesWhen tcp_syncookies is set, the kernel will handle TCP SYN packets normally until the half-open connection queue is full, at which time, the SYN cookie functionality kicks in. SYN cookies work by not using the SYN queue at all. Instead, the kernel simply replies to the SYN with a SYN|ACK, but will include a specially crafted TCP sequence number that encodes the source and destination IP address and port number and the time the packet was sent. A legitimate connection would send the ACK packet of the three way handshake with the specially crafted sequence number. This allows the server to verify that it has received a valid response to a SYN cookie and allow the connection, even though there is no corresponding SYN in the queue.Attackers use SYN flood attacks to perform a denial of service attacked on a server by sending many SYN packets without completing the three way handshake. This will quickly use up slots in the kernel's half-open connection queue and prevent legitimate connections from succeeding. SYN cookies allow the server to keep accepting valid connections, even if under a denial of service attack.Set the net.ipv4.tcp_syncookies parameter to 1 in /etc/sysctl.conf: net.ipv4.tcp_syncookies=1 Modify active kernel parameters to match: # /sbin/sysctl -w net.ipv4.tcp_syncookies=1 # /sbin/sysctl -w net.ipv4.route.flush=1Perform the following to determine if TCP SYN Cookies is enabled. # /sbin/sysctl net.ipv4.tcp_syncookies net.ipv4.tcp_syncookies = 14.3.1Deactivate Wireless InterfacesWireless networking is used when wired networks are unavailable. Red Hat contains a wireless tool kit to allow system administrators to configure and use wireless networks.gIf wireless is not to be used, wireless devices can be disabled to reduce the potential attack surface.Use the following commands to list all interfaces and identify devices with wireless interfaces. Once identified, shutdown the interface and remove it. # ifconfig -a # iwconfig # ifdown __ # rm /etc/sysconfig/network-scripts/ifcfg-__Perform the following to determine if wireless interfaces are active. # ifconfig -a Validate that all interfaces using wireless are down.4.4.14.4.1.1"Disable IPv6 Router AdvertisementsIThis setting disables the systems ability to accept router advertisementsIt is recommended that systems not accept router advertisements as they could be tricked into routing traffic to compromised machines. Setting hard routes within the system (usually a single default route to a trusted router) protects the system from bad routes.hSet the net.ipv6.conf.all.accept_ra and net.ipv6.conf.default.accept_ra parameter to 0 in /etc/sysctl.conf: net.ipv6.conf.all.accept_ra=0 net.ipv6.conf.default.accept_ra=0 Modify active kernel parameters to match: # /sbin/sysctl -w net.ipv6.conf.all.accept_ra=0 # /sbin/sysctl -w net.ipv6.conf.default.accept_ra=0 # /sbin/sysctl -w net.ipv6.route.flush=1Perform the following to determine if the system is disabled from accepting router advertisements: # /sbin/sysctl net.ipv6.conf.all.accept_ra net.ipv6.conf.all.accept_ra = 0 # /sbin/sysctl net.ipv6.conf.default.accept_ra net.ipv6.conf.default.accept_ra = 04.4.1.2 Disable IPv6 Redirect AcceptanceThis setting prevents the system from accepting ICMP redirects. ICMP redirects tell the system about alternate routes for sending traffic.It is recommended that systems not accept ICMP redirects as they could be tricked into routing traffic to compromised machines. Setting hard routes within the system (usually a single default route to a trusted router) protects the system from bad routes.Set the net.ipv6.conf.all.accept_redirects and net.ipv6.conf.default.accept_redirects parameters to 0 in /etc/sysctl.conf: net.ipv6.conf.all.accept_redirects=0 net.ipv6.conf.default.accept_redirects=0 Modify active kernel parameters to match: # /sbin/sysctl -w net.ipv6.conf.all.accept_redirects=0 # /sbin/sysctl -w net.ipv6.conf.default.accept_redirects=0 # /sbin/sysctl -w net.ipv6.route.flush=1Perform the following to determine if IPv6 redirects are disabled. # /sbin/sysctl net.ipv6.conf.all.accept_redirects net.ipv6.conf.all.accept_redirect = 0 # /sbin/sysctl net.ipv6.conf.default.accept_redirects net.ipv6.conf.default.accept_redirect = 04.4.2 Disable IPv6UAlthough IPv6 has many advantages over IPv4, few organizations have implemented IPv6.lIf IPv6 is not to be used, it is recommended that it be disabled to reduce the attack surface of the system.Edit /etc/sysconfig/network, and add the following line: NETWORKING_IPV6=no IPV6INIT=no Create the file /etc/modprobe.d/ipv6.conf and add the following lines: options ipv6 disable=1 Perform the following command to turn ip6tables off: # /sbin/chkconfig ip6tables offPerform the following to determine if IPv6 is enabled # grep NETWORKING_IPV6 /etc/sysconfig/network NETWORKING_IPV6=no # grep IPV6INIT /etc/sysconfig/network IPV6INIT=no # grep ipv6 /etc/modprobe.d/ipv6.conf options ipv6 disable=1Install TCP Wrappers4.5.1]TCP Wrappers provides a simple access list and standardized logging method for services capable of supporting it. In the past, services that were called from inetd and xinetd supported the use of tcp wrappers. As inetd and xinetd have been falling in disuse, any service that can support tcp wrappers will have the libwrap.so library attached to it.TCP Wrappers provide a good simple access list mechanism to services that may not have that support built in. It is recommended that all services that can support TCP Wrappers, use it.# yum install tcp_wrappers To verify if a service supports TCP Wrappers, run the following command: # ldd | grep libwrap.so If there is any output, then the service supports TCP Wrappers.fPerform the following to determine if TCP Wrappers is enabled. # yum list tcp_wrappers tcp_wrappers.4.5.2Create /etc/hosts.allowThe /etc/hosts.allow file specifies which IP addresses are permitted to connect to the host. It is intended to be used in conjunction with the /etc/hosts.deny file.The /etc/hosts.allow file supports access control by IP and helps ensure that only authorized systems can connect to the server.Create /etc/hosts.allow: # echo "ALL: /, /, " >/etc/hosts.allow where each _/_ combination (for example, "192.168.1.0/255.255.255.0< ") represents one network block in use by your organization that requires access to this system.Run the following command to verify the contents of the /etc/hosts.allow file. # cat /etc/hosts.allow [contents will vary, depending on your network configuration]4.5.3&Verify Permissions on /etc/hosts.allowThe /etc/hosts.allow file contains networking information that is used by many applications and therefore must be readable for these applications to operate.It is critical to ensure that the /etc/hosts.allow file is protected from unauthorized write access. Although it is protected by default, the file permissions could be changed either inadvertently or through malicious actions.If the permissions of the /etc/hosts.allow file are incorrect, run the following command to correct them: # /bin/chmod 644 /etc/hosts.allowRun the following command to determine the permissions on the /etc/hosts.allow file. # /bin/ls -l /etc/hosts.allow -rw-r--r-- 1 root root 2055 Jan 30 16:30 /etc/hosts.allow4.5.4Create /etc/hosts.denyThe /etc/hosts.deny file specifies which IP addresses are NOT permitted to connect to the host. It is intended to be used in conjunction with the /etc/hosts.allow file.The /etc/hosts.deny file serves as a failsafe so that any host not specified in /etc/hosts.allow is denied access to the server.>Create /etc/hosts.deny: # echo "ALL: ALL" >> /etc/hosts.deny4.5.5%Verify Permissions on /etc/hosts.denyThe /etc/hosts.deny file contains network information that is used by many system applications and therefore must be readable for these applications to operate.It is critical to ensure that the /etc/hosts.deny file is protected from unauthorized write access. Although it is protected by default, the file permissions could be changed either inadvertently or through malicious actions.If the permissions of the /etc/hosts.deny file are incorrect, run the following command to correct them: # /bin/chmod 644 /etc/hosts.denyRun the following command to determine the permissions on the /etc/hosts.deny file. # /bin/ls -l /etc/hosts.deny -rw-r--r-- 1 root root 2055 Jan 30 16:30 /etc/hosts.deny4.6.1 Disable DCCPThe Datagram Congestion Control Protocol (DCCP) is a transport layer protocol that supports streaming media and telephony. DCCP provides a way to gain access to congestion control, without having to do it at the application layer, but does not provide in-sequence delivery.}If the protocol is not required, it is recommended that the drivers not be installed to reduce the potential attack surface.;# echo "install dccp /bin/true" >> /etc/modprobe.d/CIS.confPerform the following to determine if DCCP is disabled. # grep "install dccp /bin/true" /etc/modprobe.d/CIS.conf install dccp /bin/true4.6.2 Disable SCTPxThe Stream Control Transmission Protocol (SCTP) is a transport layer protocol used to support message oriented communication, with several streams of messages in one connection. It serves a similar function as TCP and UDP, incorporating features of both. It is message-oriented like UDP, and ensures reliable in-sequence transport of messages with congestion control like TCP.If the protocol is not being used, it is recommended that kernel module not be loaded, disabling the service to reduce the potential attack surface.;# echo "install sctp /bin/true" >> /etc/modprobe.d/CIS.confPerform the following to determine if SCTP is disabled. # grep "install sctp /bin/true" /etc/modprobe.d/CIS.conf install sctp /bin/true4.6.3 Disable RDSThe Reliable Datagram Sockets (RDS) protocol is a transport layer protocol designed to provide low-latency, high-bandwidth communications between cluster nodes. It was developed by the Oracle Corporation.:# echo "install rds /bin/true" >> /etc/modprobe.d/CIS.confPerform the following to determine if RDS is disabled. # grep "install rds /bin/true" /etc/modprobe.d/CIS.conf install rds /bin/true4.6.4 Disable TIPCwThe Transparent Inter-Process Communication (TIPC) protocol is designed to provide communication between cluster nodes.;# echo "install tipc /bin/true" >> /etc/modprobe.d/CIS.confPerform the following to determine if TIPC is disabled. # grep "install tipc /bin/true" /etc/modprobe.d/CIS.conf install tipc /bin/trueEnable IPtablesIPtables is an application that allows a system administrator to configure the IPv4 tables, chains and rules provided by the Linux kernel firewall.IPtables provides extra protection for the Linux system by limiting communications in and out of the box to specific IPv4 addresses and ports.2# service iptables restart # chkconfig iptables onPerform the following to determine if IPtables is enabled: # chkconfig --list iptables iptables 0:off 1:off 2:on 3:on 4:on 5:on 6:offEnable IP6tablesIP6tables is an application that allows a system administrator to configure the IPv6 tables, chains and rules provided by the Linux kernel firewall.IP6tables provides extra protection for the Linux system by limiting communications in and out of the box to specific IPv6 addresses and ports. NOTE: IP6Tables should only be enabled if IPv6 has been enabled on your system.4# service ip6tables restart # chkconfig ip6tables onPerform the following to determine if IP6Tables is enabled: # chkconfig --list ip6tables ip6tables 0:off 1:off 2:on 3:on 4:on 5:on 6:off5.1.1Install the rsyslog packageThe rsyslog package is a third party package that provides many enhancements to syslog, such as multi-threading, TCP communication, message filtering and data base support. As of RHEL 5.2, rsyslog is available as part of the core distribution.The security enhancements of rsyslog such as connection-oriented (i.e. TCP) transmission of logs, the option to log to database formats, and the encryption of log data en route to a central logging server) justify installing and configuring the package.# yum install rsyslog_Perform the following command to verify that rsyslog is installed. # rpm -q rsyslog rsyslog..5.1.2Activate the rsyslog Service|The chkconfig command can be used to ensure that the syslog service is turned off and that the rsyslog service is turned on.kIt is important to ensure that syslog is turned off so that it does not interfere with the rsyslog service.-# chkconfig syslog off # chkconfig rsyslog on# chkconfig --list syslog syslog 0:off 1:off 2:off 3:off 4:off 5:off 6:off # chkconfig --list rsyslog rsyslog 0:off 1:off 2:on 3:on 4:on 5:on 6:off5.1.3Configure /etc/rsyslog.confyThe /etc/rsyslog.conf file specifies rules for logging and which files are to be used to log certain classes of messages.A great deal of important security-related information is sent via rsyslog (e.g., successful and failed su attempts, failed login attempts, root login attempts, etc.).iEdit the following lines in the /etc/rsyslog.conf file as appropriate for your environment: auth,user.* /var/log/messages kern.* /var/log/kern.log daemon.* /var/log/daemon.log syslog.* /var/log/syslog lpr,news,uucp,local0,local1,local2,local3,local4,local5,local6.* /var/log/unused.log # Execute the following command to restart rsyslogd # pkill -HUP rsyslogdReview the contents of the /etc/rsyslog.conf file to ensure appropriate logging is set. In addition, perform the following command and ensure that the log files are logging information: # ls -l /var/log/5.1.4/Create and Set Permissions on rsyslog Log obsDA log file must already exist for rsyslog to be able to write to it.It is important to ensure that log files exist and have the correct permissions to ensure that sensitive rsyslog data is archived and protected.For sites that have NOT implemented a secure admin group: Create the /var/log/ directory and for each __ listed in the /etc/rsyslog.conf file, perform the following commands: # touch __ # chown root:root # chmod og-rwx __ For sites that HAVE implemented a secure admin group: Create the /var/log/ directory and for each __ listed in the /etc/rsyslog.conf file, perform the following commands (where is the name of the security group): # touch __ # chown r< oot:__ __ # chmod g-wx,o-rwx__1For each __ listed in the /etc/rsyslog.conf file, perform the following command and verify that the _:_ is root:root and the permissions are 0600 (for sites that have not implemented a secure group) and root:securegrp with permissions of 0640 (for sites that have implemented a secure group): # ls -l __5.1.53Configure rsyslog to Send Logs to a Remote Log HostThe rsyslog utility supports the ability to send logs it gathers to a remote log host running syslogd(8) or to receive messages from remote hosts, reducing administrative overhead.Storing log data on a remote host protects log integrity from local attacks. If an attacker gains root access on the local system, they could tamper with or remove log data that is stored on the local systemEdit the /etc/rsyslog.conf file and add the following line (where _logfile.example.com_ is the name of your central log host). *.* @@loghost.example.com # Execute the following command to restart rsyslogd # pkill -HUP rsyslogd NOTE: The double "at" sign (@@) directs rsyslog to use TCP to send log messages to the server, which is a more reliable transport mechanism than the default UDP protocol.Review the /etc/rsyslog.conf file and verify that logs are sent to a central host (where _logfile.example.com_ is the name of your central log host). # grep "^*.*[^I][^I]*@" /etc/rsyslog.conf *.* @@loghost.example.com5.1.6;Accept Remote rsyslog Messages Only on Designated Log HostsBy default, rsyslog does not listen for log messages coming in from remote systems. The ModLoad tells rsyslog to load the imtcp.so module so it can listen over a network via TCP. The InputTCPServerRun option instructs rsyslogd to listen on the specified TCP port.The guidance in the section ensures that remote log hosts are configured to only accept rsyslog data from hosts within the specified domain and that those systems that are not designed to be log hosts do not accept any remote rsyslog messages. This provides protection from spoofed log data and ensures that system administrators are reviewing reasonably complete syslog data in a central location.EOn hosts that are designated as log hosts edit the /etc/rsyslog.conf file and un-comment the following lines: $ModLoad imtcp.so $InputTCPServerRun 514 NOTE: On hosts that are not designated log hosts these lines should be commented out instead. Execute the following command to restart rsyslogd: # pkill -HUP rsyslogdRun the following to determine if rsyslog is listening for remote messages: # grep '$ModLoad imtcp.so' /etc/rsyslog.conf $ModLoad imtcp.so # grep '$InputTCPServerRun' /etc/rsyslog.conf $InputTCPServerRun 514Configure logrotate\The system includes the capability of rotating log files regularly to avoid filling up the system with logs or making the logs unmanageable large. The file /etc/logrotate.d/syslog is the configuration file used to rotate log files created by syslog or rsyslog. These files are rotated on a weekly basis via a cron job and the last 4 weeks are kept.By keeping the log files smaller and more manageable, a system administrator can easily archive these files to another system and spend less time looking through inordinately large log files.Edit the /etc/logrotate.d/syslog file to include appropriate system logs: /var/log/messages /var/log/secure /var/log/maillog /var/log/spooler /var/log/boot.log /var/log/cron {Perform the following to determine if the appropriate system logs are rotated. # grep '{' /etc/logrotate.d/syslog /var/log/messages /var/log/secure /var/log/maillog /var/log/spooler /var/log/boot.log /var/log/cron {6.1.1Enable anacron DaemonThe anacron daemon is used on systems that are not up 24x7. The anacron daemon will execute jobs that would have normally been run had the system not been down.Cron jobs may include critical security or administrative functions that need to run on a regular basis. Use this daemon on machines that are not up 24x7, or if there are jobs that need to be executed after the system has been brought back up after a maintenance window.# yum install cronie-anacron NOTE: NSA Guidance recommends disabling anacron for systems that are intended to be up 24X7, with the rationale that unnecessary software should be disabled to reduce risk. However, even systems that are designed to be up at all times can experience downtime that could prevent important system maintenance jobs from running. Review the requirements for your site to determine your appropriate risk level.dPerform the following to determine if anacron is enabled. # rpm -q cronie-anacron cronie-anacron..6.1.2Enable crond Daemon=The crond daemon is used to execute batch jobs on the system.While there may not be user jobs that need to be run on the system, the system does have maintenance jobs that may include security monitoring that have to run and crond is used to execute them.# chkconfig crond on~Perform the following to determine if cron is enabled. # chkconfig --list crond crond: 0:off 1:off 2:on 3:on 4:on 5:on 6:off6.1.36Set User/Group Owner and Permission on /etc/anacrontabThe /etc/anacrontab file is used by anacron to control its own jobs. The commands in this item make sure that root is the user and group owner of the file and is the only user that can read and write the file.lThis file contains information on what system jobs are run by anacron. Write access to these files could provide unprivileged users with the ability to elevate their privileges. Read access to these files could provide users with the ability to gain insight on system jobs that run on the system and could provide them a way to gain unauthorized privileged access.@# chown root:root /etc/anacrontab # chmod og-rwx /etc/anacrontabPerform the following to determine if the /etc/anacrontab file has the correct permissions. # stat -L -c "%a %u %g" /etc/anacrontab | egrep ".00 0 0" If the above command emits no output then the system is not configured as recommended.6.1.43Set User/Group Owner and Permission on /etc/crontabThe /etc/crontab file is used by cron to control its own jobs. The commands in this item make here sure that root is the user and group owner of the file and is the only user that can read and write the file.iThis file contains information on what system jobs are run by cron. Write access to these files could provide unprivileged users with the ability to elevate their privileges. Read access to these files could provide users with the ability to gain insight on system jobs that run on the system and could provide them a way to gain unauthorized privileged access.:# chown root:root /etc/crontab # chmod og-rwx /etc/crontabPerform the following to determine if the /etc/crontab file has the correct permissions. # stat -L -c "%a %u %g" /etc/crontab | egrep ".00 0 0" If the above command emits no output then the system is not configured as recommended.6.1.57Set User/Group Owner and Permission on /etc/cron.hourlyeThis directory contains system cron jobs that need to run on an hourly basis. The files in this directory cannot be manipulated by the crontab command, but are instead edited by system administrators using a text editor. The commands below restrict read/write and search access to user and group root, preventing regular users from accessing this directory.Granting write access to this directory for non-privileged users could provide them the means for gaining unauthorized elevated privileges. Granting read access to this directory could give an unprivileged user insight in how to gain elevated privileges or circumvent auditing controls.B# chown root:root /etc/cron.hourly # chmod og-rwx /etc/cron.hourlyPerform the following to determine if the /etc/cron.hourly file has the correct permissions. # stat -L -c "%a %u %g" /etc/cron.hourly | egrep ".00 0 0" If the above command emits no output then the system is not configured as recommended.6.1.66Set User/Group Owner and Permission on /etc/cron.dailyrThe /etc/cron.daily directory contains system cron jobs that need to run on a daily basis. The files in this directo< ry cannot be manipulated by the crontab command, but are instead edited by system administrators using a text editor. The commands below restrict read/write and search access to user and group root, preventing regular users from accessing this directory.@# chown root:root /etc/cron.daily # chmod og-rwx /etc/cron.dailyPerform the following to determine if the /etc/cron.daily directory has the correct permissions. # stat -L -c "%a %u %g" /etc/cron.daily | egrep ".00 0 0" If the above command emits no output then the system is not configured as recommended.6.1.77Set User/Group Owner and Permission on /etc/cron.weeklytThe /etc/cron.weekly directory contains system cron jobs that need to run on a weekly basis. The files in this directory cannot be manipulated by the crontab command, but are instead edited by system administrators using a text editor. The commands below restrict read/write and search access to user and group root, preventing regular users from accessing this directory.B# chown root:root /etc/cron.weekly # chmod og-rwx /etc/cron.weeklyPerform the following to determine if the /etc/cron.weekly directory has the correct permissions. # stat -L -c "%a %u %g" /etc/cron.weekly | egrep ".00 0 0" If the above command emits no output then the system is not configured as recommended.6.1.88Set User/Group Owner and Permission on /etc/cron.monthlyvThe /etc/cron.monthly directory contains system cron jobs that need to run on a monthly basis. The files in this directory cannot be manipulated by the crontab command, but are instead edited by system administrators using a text editor. The commands below restrict read/write and search access to user and group root, preventing regular users from accessing this directory.D# chown root:root /etc/cron.monthly # chmod og-rwx /etc/cron.monthlyPerform the following to determine if the /etc/cron.monthly directory has the correct permissions. # stat -L -c "%a %u %g" /etc/cron.monthly | egrep ".00 0 0" If the above command emits no output then the system is not configured as recommended.6.1.92Set User/Group Owner and Permission on /etc/cron.dThe /etc/cron.d directory contains system cron jobs that need to run in a similar manner to the hourly, daily weekly and monthly jobs from /etc/crontab, but require more granular control as to when they run. The files in this directory cannot be manipulated by the crontab command, but are instead edited by system administrators using a text editor. The commands below restrict read/write and search access to user and group root, preventing regular users from accessing this directory.8# chown root:root /etc/cron.d # chmod og-rwx /etc/cron.dPerform the following to determine if the /etc/cron.d directory has the correct permissions. # stat -L -c "%a %u %g" /etc/cron.d | egrep ".00 0 0" If the above command emits no output then the system is not configured as recommended.6.1.10Restrict at DaemonWGranting write access to this directory for non-privileged users could provide them the means to gain unauthorized elevated privileges. Granting read access to this directory could give an unprivileged user insight in how to gain elevated privileges or circumvent auditing controls. In addition, it is a better practice to create a white list of users who can execute at jobs versus a blacklist of users who can't execute at jobs as a system administrator will always know who can create jobs and does not have to worry about remembering to add a user to the blacklist when a new user id is created.Perform the following to determine if at jobs are restricted. # stat -L /etc/at.deny > /dev/null # stat -L -c "%a %u %g" /etc/at.allow | egrep ".00 0 0" If the above command emits no output then the system is not configured as recommended.6.1.11$Restrict at/cron to Authorized UsersUConfigure /etc/cron.allow and /etc/at.allow to allow specific users to use these services. If /etc/cron.allow or /etc/at.allow do not exist, then /etc/at.deny and /etc/cron.deny are checked. Any user not specifically defined in those files is allowed to use at and cron. By removing the files, only users in /etc/cron.allow and /etc/at.allow are allowed to use at and cron. Note that even though a given user is not listed in cron.allow, cron jobs can still be run as that user. The cron.allow file only controls administrative access to the crontab command for scheduling and modifying cron jobs.EOn many systems, only the system administrator is authorized to schedule cron jobs. Using the cron.allow file to control who can run cron jobs enforces this policy. It is easier to manage an allow list than a deny list. In a deny list, you could potentially add a user ID to the system and forget to add it to the deny files._If /etc/cron.allow or /etc/at.allow do not exist on your system create them. Run the following to ensure cron.deny and at.deny are removed and permissions are set correctly: # /bin/rm /etc/cron.deny # /bin/rm /etc/at.deny # chmod og-rwx /etc/cron.allow # chmod og-rwx /etc/at.allow # chown root:root /etc/cron.allow # chown root:root /etc/at.allow*Perform the following to determine if the remediation in the section has been performed: # ls -l /etc/cron.deny [no output returned] # ls -l /etc/at.deny [no output returned] # ls -l /etc/cron.allow -rw------- 1 root root /etc/cron.allow # ls -l /etc/at.allow -rw------- 1 root root /etc/at.allow6.2.1Set SSH Protocol to 2SSH supports two different and incompatible protocols: SSH1 and SSH2. SSH1 was the original protocol and was subject to security issues. SSH2 is more advanced and secure.;SSH v1 suffers from insecurities that do not affect SSH v2.PEdit the /etc/ssh/sshd_config file to set the parameter as follows: Protocol 2To verify the correct SSH setting, run the following command and verify that the output is as shown: # grep "^Protocol" /etc/ssh/sshd_config Protocol 26.2.2Set LogLevel to INFOKThe INFO parameter specifies that login and logout activity will be logged.'SSH provides several logging levels with varying amounts of verbosity. DEBUG is specifically _not_ recommended other than strictly for debugging SSH communications since it provides so much data that it is difficult to identify important security information. INFO level is the basic level that only records login activity of SSH users. In many situations, such as Incident Response, it is important to determine when a particular user was active on a system. The logout record can eliminate those users who disconnected, which helps narrow the field.SEdit the /etc/ssh/sshd_config file to set the parameter as follows: LogLevel INFOTo verify the correct SSH setting, run the following command and verify that the output is as shown: # grep "^LogLevel" /etc/ssh/sshd_config LogLevel INFO6.2.3'Set Permissions on /etc/ssh/sshd_configThe /etc/ssh/sshd_config file contains configuration specifications for sshd. The command below sets the owner and group of the file to root.The /etc/ssh/sshd_config file needs to be protected from unauthorized changes by non-privileged users, but needs to be readable as this information is used with many non-privileged programs.If the user and group ownership of the /etc/ssh/sshd_config file are incorrect, run the following command to correct them: # chown root:root /etc/ssh/sshd_config If the permissions are incorrect, run the following command to correct them: # chmod 600 /etc/ssh/sshd_configRun the following command to determine the user and group ownership on the /etc/ssh/sshd_config file. # /bin/ls -l /etc/ssh/sshd_config -rw------- 1 root root 762 Sep 23 002 /etc/ssh/sshd_config6.2.4Disable SSH X11 ForwardingThe X11Forwarding parameter provides the ability to tunnel X11 traffic through the connection to enable remote graphic connections.`Disable X11 forwarding unless there is an operational requirement to use X11 applications directly. There is a small risk that the remote X11 servers of users who are logged in via SSH with X11 forwarding could be compromised by other users on the X11 server. Note that even if X11 forwarding is disabled, us< ers can always install their own forwarders.VEdit the /etc/ssh/sshd_config file to set the parameter as follows: X11Forwarding noTo verify the correct SSH setting, run the following command and verify that the output is as shown: # grep "^X11Forwarding" /etc/ssh/sshd_config X11Forwarding no6.2.5The MaxAuthTries parameter specifies the maximum number of authentication attempts permitted per connection. When the login failure count reaches half the number, error messages will be written to the syslog file detailing the login failure.6.2.6Set SSH IgnoreRhosts to YesThe IgnoreRhosts parameter specifies that .rhosts and .shosts files will not be used in RhostsRSAAuthentication or HostbasedAuthentication.USetting this parameter forces users to enter a password when authenticating with ssh.VEdit the /etc/ssh/sshd_config file to set the parameter as follows: IgnoreRhosts yesTo verify the correct SSH setting, run the following command and verify that the output is as shown: # grep "^IgnoreRhosts" /etc/ssh/sshd_config IgnoreRhosts yes6.2.7%Set SSH HostbasedAuthentication to NoThe HostbasedAuthentication parameter specifies if authentication is allowed through trusted hosts via the user of .rhosts, or /etc/hosts.equiv, along with successful public key client host authentication. This option only applies to SSH Protocol Version 2.Even though the .rhosts files are ineffective if support is disabled in /etc/pam.conf, disabling the ability to use .rhosts files in SSH provides an additional layer of protection .`Edit the /etc/ssh/sshd_config file to set the parameter as follows: HostbasedAuthentication noTo verify the correct SSH setting, run the following command and verify that the output is as shown: # grep "^HostbasedAuthentication" /etc/ssh/sshd_config HostbasedAuthentication no6.2.8Disable SSH Root LogindThe PermitRootLogin parameter specifies if the root user can log in using ssh(1). The default is no. Disallowing root logins over SSH requires server admins to authenticate using their own individual account, then escalating to root via sudo or su. This in turn limits opportunity for non-repudiation and provides a clear audit trail in the event of a security incidentXEdit the /etc/ssh/sshd_config file to set the parameter as follows: PermitRootLogin noTo verify the correct SSH setting, run the following command and verify that the output is as shown: # grep "^PermitRootLogin" /etc/ssh/sshd_config PermitRootLogin no6.2.9"Set SSH PermitEmptyPasswords to NopThe PermitEmptyPasswords parameter specifies if the server allows login to accounts with empty password strings.Disallowing remote shell access to accounts that have an empty password reduces the probability of unauthorized access to the system]Edit the /etc/ssh/sshd_config file to set the parameter as follows: PermitEmptyPasswords noTo verify the correct SSH setting, run the following command and verify that the output is as shown: # grep "^PermitEmptyPasswords" /etc/ssh/sshd_config PermitEmptyPasswords no6.2.10-Do Not Allow Users to Set Environment Options_The PermitUserEnvironment option allows users to present environment options to the ssh daemon.Permitting users the ability to set environment variables through the SSH daemon could potentially allow users to bypass security controls (e.g. setting an execution path that has ssh executing trojaned programs).^Edit the /etc/ssh/sshd_config file to set the parameter as follows: PermitUserEnvironment noTo verify the correct SSH setting, run the following command and verify that the output is as shown: # grep PermitUserEnvironment /etc/ssh/sshd_config PermitUserEnvironment no6.2.11(Use Only Approved Cipher in Counter ModePThis variable limits the types of ciphers that SSH can use during communication.Based on research conducted at various institutions, it was determined that the symmetric portion of the SSH Transport Protocol (as described in RFC 4253) has security weaknesses that allowed recovery of up to 32 bits of plaintext from a block of ciphertext that was encrypted with the Cipher Block Chaining (CBC) method. From that research, new Counter mode algorithms (as described in RFC4344) were designed that are not vulnerable to these types of attacks and these algorithms are now recommended for standard use.nEdit the /etc/ssh/sshd_config file to set the parameter as follows: Ciphers aes128-ctr,aes192-ctr,aes256-ctrTo verify the correct SSH setting, run the following command and verify that the output is as shown: # grep -v "Ciphers" /etc/ssh/sshd_config Ciphers aes128-ctr,aes192-ctr,aes256-ctr6.2.12(Set Idle Timeout Interval for User LoginThe two options ClientAliveInterval and ClientAliveCountMax control the timeout of ssh sessions. When the ClientAliveInterval variable is set, ssh sessions that have no activity for the specified length of time are terminated. When the ClientAliveCountMax variable is set, sshd will send client alive messages at every ClientAliveInterval interval. When the number of consecutive client alive messages are sent with no response from the client, the ssh session is terminated. For example, if the ClientAliveInterval is set to 15 seconds and the ClientAliveCountMax is set to 3, the client ssh session will be terminated after 45 seconds of idle time.6.2.13Limit Access via SSHThere are several options available to limit which users and group can access the system via SSH. It is recommended that at least of the following options be leveraged: AllowUsers The AllowUsers variable gives the system administrator the option of allowing specific users to ssh into the system. The list consists of comma separated user names. Numeric userIDs are not recognized with this variable. If a system administrator wants to restrict user access further by only allowing the allowed users to log in from a particular host, the entry can be specified in the form of user@host. AllowGroups The AllowGroups variable gives the system administrator the option of allowing specific groups of users to ssh into the system. The list consists of comma separated user names. Numeric groupIDs are not recognized with this variable. DenyUsers The DenyUsers variable gives the system administrator the option of denying specific users to ssh into the system. The list consists of comma separated user names. Numeric userIDs are not recognized with this variable. If a system administrator wants to restrict user access further by specifically denying a user's access from a particular host, the entry can be specified in the form of user@host. DenyGroups The DenyGroups variable gives the system administrator the option of denying specific groups of users to ssh into the system. The list consists of comma separated group names. Numeric groupIDs are not recognized with this variable.}Restricting which users can remotely access the system via SSH will help ensure that only authorized users access the system.Edit the /etc/ssh/sshd_config file to set one or more of the parameter as follows: AllowUsers AllowGroups DenyUsers DenyGroupsATo verify the correct SSH setting, run the following command and verify that the output is as shown: # grep "^AllowUsers" /etc/ssh/sshd_config AllowUsers # grep "^AllowGroups" /etc/ssh/sshd_config AllowGroups # grep "^DenyUsers" /etc/ssh/sshd_config DenyUsers # grep "^DenyGroups" /etc/ssh/sshd_config DenyGroups6.2.14Set SSH BannerThe Banner parameter specifies a file whose contents must be sent to the remote user before authentication is permitted. By default, no banner is displayed.Banners are used to warn connecting users of the particular site's policy regarding connection. Consult with your legal department for the appropriate warning banner for your site.[Edit the /etc/ssh/sshd_config file to set the parameter as follows: Banner /etc/issue.netTo verify the correct SSH setting, run the following command and verify that is either /etc/issue or /etc/issue.net: # grep "^Banner" /etc/ssh/sshd_config Banner6.3.1-Upgrade Password Hashing Algorithm to SHA-512< The SHA-512 encryption has been available since Red Hat release 5.2,. The commands below change password encryption from md5 to sha512 (a much stronger hashing algorithm). All existing accounts will need to perform a password change to upgrade the stored hashes to the new algorithm.The SHA-512 algorithm provides much stronger hashing than MD5, thus providing additional protection to the system by increasing the level of effort for an attacker to successfully determine passwords. Note that these change only apply to accounts configured on the local system.kPerform the following to configure the system as recommended: # authconfig --passalgo=sha512 --update NOTE: If it is determined that the password algorithm being used is not SHA-512, once it is changed, it is recommended that all userID's be immediately expired and forced to change their passwords on next login. To accomplish that, the following commands can be used. Any system accounts that need to be expired should be carefully done separately by the system administrator to prevent any potential problems. # cat /etc/passwd | awk -F: '( $3 >=500 && $1 != "nfsnobody" ) { print $1 }' | xargs -n 1 chage -d 0Perform the following to determine if the password-hashing algorithm is set to SHA-512: # authconfig --test | grep hashing | grep sha512 If the above command emits no output then the system is not configured as recommended6.3.2?Set Password Creation Requirement Parameters Using pam_cracklibOStrong passwords protect systems from being hacked through brute force methods.6.3.3(Set Lockout for Failed Password AttemptsLock out users after _n_ unsuccessful consecutive login attempts. The first sets of changes are made to the PAM configuration file /etc/pam.d/system-auth. The second set of changes are applied to the program specific PAM configuration file. The second set of changes must be applied to each program that will lock out users. Check the documentation for each secondary program for instructions on how to configure them to work with PAM. Set the lockout number to the policy in effect at your site.Locking out userIDs after _n_ unsuccessful consecutive login attempts mitigates brute force password attacks against your systems.6.3.4Limit Password ReuseThe /etc/security/opasswd file stores the users' old passwords and can be checked to ensure that users are not recycling recent passwords.Forcing users not to reuse their past 5 passwords make it less likely that an attacker will be able to guess the password. Note that these change only apply to accounts configured on the local system.%Restrict root Login to System ConsolebThe file /etc/securetty contains a list of valid terminals that may be logged in directly as root.Since the system console has special properties to handle emergency situations, it is important to ensure that the console is in a physically secure location and that unauthorized consoles have not been defined.MRemove entries for any consoles that are not in a physically secure location.# cat /etc/securetty!Restrict Access to the su CommandiThe su command allows a user to run a command or shell as another user. The program has been superseded by sudo, which allows for more granular control over privileged access. Normally, the su command can be executed by any user. By uncommenting the pam_wheel.so statement in /etc/pam.d/su, the su command will only allow users in the wheel group to execute su.]Restricting the use of su, and using sudo in its place, provides system administrators better control of the escalation of user privileges to execute privileged commands. The sudo utility also provides a better logging and audit mechanism, as it can log each command executed via sudo, whereas su can only record that a user executed the su program.Set the pam_wheel.so parameters as follows in /etc/pam.d/su: auth required pam_wheel.so use_uid Set the proper list of users to be included in the wheel group in /etc/groups.m# grep pam_wheel.so /etc/pam.d/su auth required pam_wheel.so use_uid # grep wheel /etc/group wheel:x:10:root,7.1.1Set Password Expiration DaysThe PASS_MAX_DAYS parameter in /etc/login.defs allows an administrator to force passwords to expire once they reach a defined age. It is recommended that the PASS_MAX_DAYS parameter be set to less than or equal to 90 days. The window of opportunity for an attacker to leverage compromised credentials or successfully compromise credentials via an online brute force attack is limited by the age of the password. Therefore, reducing the maximum age of a password also reduces an attacker's window of opportunity.7.1.2*Set Password Change Minimum Number of DaysBy restricting the frequency of password changes, an administrator can prevent users from repeatedly changing their password in an attempt to circumvent password reuse controls.7.1.3"Set Password Expiring Warning DaysProviding an advance warning that a password will be expiring gives users time to think of a secure password. Users caught unaware may choose a simple password or write it down where it may be discovered.Set the PASS_WARN_AGE parameter to 7 in /etc/login.defs: PASS_WARN_AGE 7 Modify active user parameters to match: # chage --warndays 7Disable System AccountsThere are a number of accounts provided with the Red Hat that are used to manage applications and are not intended to provide an interactive shell.It is important to make sure that accounts that are not being used by regular users are locked to prevent them from being used to provide an interactive shell. By default, Red Hat sets the password field for these accounts to an invalid string, but it is also recommended that the shell field in the password file be set to /sbin/nologin. This prevents the account from potentially being used to run any commands.%Accounts that have been locked are prohibited from running commands on the system. Such accounts are not able to login to the system nor are they able to use scheduled execution facilities such as cron. To make sure system accounts cannot be accessed, using the following script: #!/bin/bash for user in `awk -F: '($3 < 500) {print $1 }' /etc/passwd`; do if [ $user != "root" ] then /usr/sbin/usermod -L $user if [ $user != "sync" ] && [ $user != "shutdown" ] && [ $user != "halt" ] then /usr/sbin/usermod -s /sbin/nologin $user fi fi doneRun the following script to determine if any system accounts can be accessed: egrep -v "^+" /etc/passwd | awk -F: '($1!="root" && $1!="sync" && $1!="shutdown" && $1!="halt" && $3"Set Default Group for root AccountThe usermod command can be used to specify which group the root user belongs to. This affects permissions of files that are created by the root user.Using GID 0 for the _root_ account helps prevent _root_-owned files from accidentally becoming accessible to non-privileged users.# usermod -g 0 root+# grep "^root:" /etc/passwd | cut -f4 -d: 0Set Default umask for UsersThe default umask determines the permissions of files created by users. The user creating the file has the discretion of making their files and directories readable by others via the chmod command. Users who wish to allow their files and directories to be readable by others by default may choose a different default umask by inserting the umask command into the standard shell configuration files (.profile, .cshrc, etc.) in their home directories.MSetting a very secure default value for umask ensures that users make a conscious choice about their file permissions. A default umask setting of 077 causes files and directories created by users to not be readable by any other user on the system. A umask of 027 would make files and directories readable by users in the same Unix group, while a umask of 022 would make files readable by every user on the system. NOTE: The directives in this section apply to bash and shell. If other shells are supported on the system, it is recommended that their configuration files also are checked.Edit the /etc/bashrc and /etc/profile.d/cis.sh files (and the appropriate files for any other shell support< ed on your system) and add the following the UMASK parameter as shown: umask 77X# grep "^umask 077" /etc/bashrc umask 077 # grep "^umask 077" /etc/profile.d/* umask 077Lock Inactive User AccountsInactive accounts pose a threat to system security since the users are not logging in to notice failed login attempts or other anomalies.# useradd -D | grep INACTIVE.Set Warning Banner for Standard Login ServicesThe contents of the /etc/issue file are displayed prior to the login prompt on the system's console and serial devices, and also prior to logins via telnet. The contents of the /etc/motd file is generally displayed after all successful logins, no matter where the user is logging in from, but is thought to be less useful because it only provides notification to the user after the machine has been accessed.OWarning messages inform users who are attempting to login to the system of their legal status regarding the system and must include the name of the organization that owns the system and any monitoring policies that are in place. Consult with your organization's legal counsel for the appropriate wording for your specific organization.i# touch /etc/motd # echo "Authorized uses only. All activity may be monitored and reported." > /etc/issue # echo "Authorized uses only. All activity may be monitored and reported." > /etc/issue.net # chown root:root /etc/motd # chmod 644 /etc/motd # chown root:root /etc/issue # chmod 644 /etc/issue # chown root:root /etc/issue.net # chmod 644 /etc/issue.netRun the following commands and ensure that the files exist and have the correct permissions. # /bin/ls -l /etc/motd -rw-r--r-- 1 root root 2055 Jan 30 16:30 /etc/motd # ls /etc/issue -rw-r--r-- 1 root root 2055 Jan 30 16:30 /etc/issue # ls /etc/issue.net -rw-r--r-- 1 root root 2055 Jan 30 16:30 /etc/issue.net The commands above simply validate the presence of the /etc/motd, /etc/issue and /etc/issue.net files. Review the contents of these files with the "cat" command and ensure that it is appropriate for your organization.0Remove OS Information from Login Warning BannersUnix-based systems have typically displayed information about the OS release and patch level upon logging in to the system. This information can be useful to developers who are developing software for a particular OS platform. If mingetty(8) supports the following options, they display operating system information: m - machine architecture (uname -m) r - operating system release (uname -r) s - operating system name v - operating system version (uname -v)*Displaying OS and patch level information in login banners also has the side effect of providing detailed system information to attackers attempting to target specific exploits of a system. Authorized users can easily get this information by running the "uname -a" command once they have logged in.eEdit the /etc/motd, /etc/issue and /etc/issue.net files and remove any lines containing m, r, s or v.Perform the following commands to check if OS information is set to be displayed in the system login banners: # egrep '(\v|\r|\m|\s)' /etc/issue # egrep '(\v|\r|\m|\s)' /etc/motd # egrep'(\v|\r|\m|\s)' /etc/issue.netSet GNOME Warning BannerThe GNOME Display Manager is used for login session management. See the manual page gdm(1) for more information. The remediation action for this item sets a warning message for GDM users before they log in.\# /bin/su -s /bin/sh gdm # gconftool-2 -direct -config-source=xml:readwrite:$HOME/.gconf -type bool -set /apps/gdm/simple-greeter/banner_message_enable true # gconftool-2 -direct -config-source=xml:readwrite:$HOME/.gconf -t string -s /apps/gdm/simple-greeter/banner_message_text "Your-Login-Banner" Restart gdm for these settings to take effect.?# gconftool-2 -get /apps/gdm/simple-greeter/banner_message_text9.1.2!Verify Permissions on /etc/passwdThe /etc/passwd file contains user account information that is used by many system utilities and therefore must be readable for these utilities to operate.It is critical to ensure that the /etc/passwd file is protected from unauthorized write access. Although it is protected by default, the file permissions could be changed either inadvertently or through malicious actions.If the permissions of the /etc/passwd file are incorrect, run the following command to correct them: # /bin/chmod 644 /etc/passwdRun the following command to determine the permissions on the /etc/passwd file. # /bin/ls -l /etc/passwd -rw-r--r-- 1 root root 2055 Jan 30 16:30 /etc/passwd9.1.3!Verify Permissions on /etc/shadowThe /etc/shadow file is used to store the information about user accounts that is critical to the security of those accounts, such as the hashed password and other security information.If attackers can gain read access to the /etc/shadow file, they can easily run a password cracking program against the hashed password to break it. Other security information that is stored in the /etc/shadow file (such as expiration) could also be useful to subvert the user accounts.If the permissions of the /etc/shadow file are incorrect, run the following command to correct them: # /bin/chmod 000 /etc/shadowRun the following command to determine the permissions on the /etc/shadow file. # /bin/ls -l /etc/shadow ---------- 1 root root 633 Sep 23 2002 /etc/shadow9.1.4"Verify Permissions on /etc/gshadowThe /etc/gshadow file contains information about group accounts that is critical to the security of those accounts, such as the hashed password and other security information. If attackers can gain read access to the /etc/gshadow file, they can easily run a password cracking program against the hashed password to break it. Other security information that is stored in the /etc/gshadow file (such as expiration) could also be useful to subvert the group accounts.If the permissions of the /etc/gshadow file are incorrect, run the following command to correct them: # /bin/chmod 000 /etc/gshadowRun the following command to determine the permissions on the /etc/gshadow file. # /bin/ls -l /etc/gshadow ---------- 1 root root 633 Sep 23 2002 /etc/gshadow9.1.5 Verify Permissions on /etc/groupThe /etc/group file contains a list of all the valid groups defined in the system. The command below allows read/write access for root and read access for everyone else.The /etc/group file needs to be protected from unauthorized changes by non-privileged users, but needs to be readable as this information is used with many non-privileged programs.If the permissions of the /etc/group file are incorrect, run the following command to correct them: # /bin/chmod 644 /etc/groupRun the following command to determine the permissions on the /etc/group file. # /bin/ls -l /etc/group -rw-r--r-- 1 root root 762 Sep 23 002 /etc/group9.1.6*Verify User/Group Ownership on /etc/passwdThe /etc/passwd file contains a list of all the valid userIDs defined in the system, but not the passwords. The command below sets the owner and group of the file to root.The /etc/passwd file needs to be protected from unauthorized changes by non-privileged users, but needs to be readable as this information is used with many non-privileged programs.If the user and group ownership of the /etc/passwd file are incorrect, run the following command to correct them: # /bin/chown root:root /etc/passwdRun the following command to determine the user and group ownership on the /etc/passwd file. # /bin/ls -l /etc/passwd -rw-r--r-- 1 root root 762 Sep 23 002 /etc/passwd9.1.7*Verify User/Group Ownership on /etc/shadowThe /etc/shadow file contains the one-way cipher text passwords for each user defined in the /etc/passwd file. The command below sets the user and group ownership of the file to root.If the ownership of the /etc/shadow file are incorrect, run the following command to correct them: # /bin/chown root:root /etc/shadowRun the following command to determine the permissions on the /etc/shadow file. # /bin/ls -l /etc/shadow ---------- 1 root root 762 Sep 23 2002 /etc/shadow9.1.8+Verify User/Group Ownership on /etc/< gshadowIf the ownership of the /etc/gshadow file are incorrect, run the following command to correct them: # /bin/chown root:root /etc/gshadow9.1.9)Verify User/Group Ownership on /etc/groupIf the ownership of the /etc/group file are incorrect, run the following command to correct them: # /bin/chown root:root /etc/groupRun the following command to determine the permissions on the /etc/group file. # /bin/ls -l /etc/group -rw-r--r-- 1 root root 762 Sep 23 002 /etc/group9.1.10Find World Writable obsUnix-based systems support variable settings to control access to files. World writable files are the least secure. See the chmod(2) man page for more information.Data in world-writable files can be modified and compromised by any user on the system. World writable files may also indicate an incorrectly written script or program that could potentially be the cause of a larger compromise to the system's integrity.Removing write access for the "other" category (chmod o-w ___)_ is advisable, but always consult relevant vendor documentation to avoid breaking any application dependencies on a given file.k#!/bin/bash df --local -P | awk {'if (NR!=1) print $6'} | xargs -I '{}' find '{}' -xdev -type f -perm -00029.1.11#Find Un-owned obs and DirectoriesSometimes when administrators delete users from the password file they neglect to remove all files owned by those users from the system.A new user who is assigned the deleted user's user ID or group ID may then end up "owning" these files, and thus have more access on the system than was intended.Locate files that are owned by users or groups not listed in the system configuration files, and reset the ownership of these files to some active user on the system as appropriate.c#!/bin/bash df --local -P | awk {'if (NR!=1) print $6'} | xargs -I '{}' find '{}' -xdev -nouser -ls9.1.12%Find Un-grouped obs and Directoriesd#!/bin/bash df --local -P | awk {'if (NR!=1) print $6'} | xargs -I '{}' find '{}' -xdev -nogroup -ls9.1.13Find SUID System ExecutablesDThe owner of a file can set the file's permissions to run with the owner's or group's permissions, even if the user running the program is not the owner or a member of the group. The most common reason for a SUID program is to enable users to perform functions (such as changing their password) that require root privileges.There are valid reasons for SUID programs, but it is important to identify and review such programs to ensure they are legitimate.Ensure that no rogue set-UID programs have been introduced into the system. Review the files returned by the action in the Audit section and confirm the integrity of these binaries as described below: # rpm -V `rpm -qf /usr/bin/sudo` .......T /usr/bin/sudo SM5....T /usr/bin/sudoeditr#!/bin/bash df --local -P | awk {'if (NR!=1) print $6'} | xargs -I '{}' find '{}' -xdev -type f -perm -4000 -print9.1.14Find SGID System ExecutablesDThe owner of a file can set the file's permissions to run with the owner's or group's permissions, even if the user running the program is not the owner or a member of the group. The most common reason for a SGID program is to enable users to perform functions (such as changing their password) that require root privileges.There are valid reasons for SGID programs, but it is important to identify and review such programs to ensure they are legitimate. Review the files returned by the action in the audit section and check to see if system binaries have a different md5 checksum than what from the package. This is an indication that the binary may have been replaced. The following is an example of checking the "sudo" executable: # rpm -V `rpm -qf /usr/bin/sudo` .......T /usr/bin/sudo SM5....T /usr/bin/sudoeditnEnsure that no rogue set-GID programs have been introduced into the system # /bin/rpm -V `/bin/rpm -qf sudo`r#!/bin/bash df --local -P | awk {'if (NR!=1) print $6'} | xargs -I '{}' find '{}' -xdev -type f -perm -2000 -print9.2.1$Ensure Password Fields are Not EmptypAn account with an empty password field means that anybody may log in as that user without providing a password.mAll accounts must have passwords or be locked to prevent the account from being used by an unauthorized user.GIf any accounts in the /etc/shadow file do not have a password, run the following command to lock the account until it can be determined why it does not have a password: # /usr/bin/passwd -l Also, check to see if the account is logged in and investigate what it is being used for to determine if it needs to be forced off.Run the following command and verify that no output is returned: # /bin/cat /etc/shadow | /bin/awk -F: '($2 == "" ) { print $1 " does not have a password "}'9.2.26Verify No Legacy "+" Entries Exist in /etc/passwd ob The character + in various files used to be markers for systems to insert data from NIS maps at a certain point in a system configuration file. These entries are no longer required on RHEL6 systems, but may exist in files that have been imported from other platforms.ZThese entries may provide an avenue for attackers to gain privileged access on the system.#Delete these entries if they exist.aRun the following command and verify that no output is returned: # /bin/grep '^+:' /etc/passwd9.2.36Verify No Legacy "+" Entries Exist in /etc/shadow obaRun the following command and verify that no output is returned: # /bin/grep '^+:' /etc/shadow9.2.45Verify No Legacy "+" Entries Exist in /etc/group ob`Run the following command and verify that no output is returned: # /bin/grep '^+:' /etc/group9.2.5.Verify No UID 0 Accounts Exist Other Than root>Any account with UID 0 has superuser privileges on the system.This access must be limited to only the default root account and only from the system console. Administrative access must be through an unprivileged account using an approved mechanism as noted in Item 7.5 Restrict root Login to System Console.,Delete any other entries that are displayed.Run the following command and verify that only the word "root" is returned: # /bin/cat /etc/passwd | /bin/awk -F: '($3 == 0) { print $1 }' root9.2.6Ensure root PATH IntegrityThe root user can execute any command on the system and could be fooled into executing programs unemotionally if the PATH is not set correctly.Including the current working directory (.) or other writable directory in root's executable path makes it likely that an attacker can gain superuser access by forcing an administrator operating as root to execute a Trojan horse program.:Correct or justify any items discovered in the Audit step.#!/bin/bash if [ "`echo $PATH | /bin/grep :: `" != "" ]; then echo "Empty Directory in PATH (::)" fi if [ "`echo $PATH | bin/grep :$`" != "" ]; then echo "Trailing : in PATH" fi p=`echo $PATH | /bin/sed -e 's/::/:/' -e 's/:$//' -e 's/:/ /g'` set -- $p while [ "$1" != "" ]; do if [ "$1" = "." ]; then echo "PATH contains ." shift continue fi if [ -d $1 ]; then dirperm=`/bin/ls -ldH $1 | /bin/cut -f1 -d" "` if [ `echo $dirperm | /bin/cut -c6 ` != "-" ]; then echo "Group Write permission set on directory $1" fi if [ `echo $dirperm | /bin/cut -c9 ` != "-" ]; then echo "Other Write permission set on directory $1" fi dirown=`ls -ldH $1 | awk '{print $3}'` if [ "$dirown" != "root" ] ; then echo $1 is not owned by root fi else echo $1 is not a directory fi shift done9.2.7*Check Permissions on User Home DirectoriesWhile the system administrator can establish secure permissions for users' home directories, the users can easily override these.Group or world-writable user home directories may enable malicious users to steal or modify other users' data or to gain another user's system privileges.6Making global modifications to user home directories without alerting the user community can result in unexpected outages and unhappy users. Therefore, it is recommended that a monitoring policy be established to report user file permissions and determine the action to be taken in accordance with site policy.j#!/bin/bash for dir i< n `/bin/cat /etc/passwd | /bin/egrep -v '(root|halt|sync|shutdown)' | /bin/awk -F: '($8 == "PS" & do dirperm=`/bin/ls -ld $dir | /bin/cut -f1 -d" "` if [ `echo $dirperm | /bin/cut -c6 ` != "-" ]; then echo "Group Write permission set on directory $dir" fi if [ `echo $dirperm | /bin/cut -c8 ` != "-" ]; then echo "Other Read permission set on directory $dir" fi if [ `echo $dirperm | /bin/cut -c9 ` != "-" ]; then echo "Other Write permission set on directory $dir" fi if [ `echo $dirperm | /bin/cut -c10 ` != "-" ]; then echo "Other Execute permission set on directory $dir" fi done9.2.8Check User Dot ob Permissions|While the system administrator can establish secure permissions for users' "dot" files, the users can easily override these.Group or world-writable user configuration files may enable malicious users to steal or modify other users' data or to gain another user's system privileges.1Making global modifications to users' files without alerting the user community can result in unexpected outages and unhappy users. Therefore, it is recommended that a monitoring policy be established to report user dot file permissions and determine the action to be taken in accordance with site policy.#!/bin/bash for dir in `/bin/cat /etc/passwd | /bin/egrep -v '(root|sync|halt|shutdown)' | /bin/awk -F: '($7 != "/sbin/nologin") { print $6 }'`; do for file in $dir/.[A-Za-z0-9]*; do if [ ! -h "$file" -a -f "$file" ]; then fileperm=`/bin/ls -ld $file | /bin/cut -f1 -d" "` if [ `echo $fileperm | /bin/cut -c6 ` != "-" ]; then echo "Group Write permission set on file $file" fi if [ `echo $fileperm | /bin/cut -c9 ` != "-" ]; then echo "Other Write permission set on file $file" fi fi done done9.2.9&Check Permissions on User .netrc obs}While the system administrator can establish secure permissions for users' .netrc files, the users can easily override these.X.netrc files may contain unencrypted passwords that may be used to attack other systems.4Making global modifications to users' files without alerting the user community can result in unexpected outages and unhappy users. Therefore, it is recommended that a monitoring policy be established to report user .netrc file permissions and determine the action to be taken in accordance with site policy.A#!/bin/bash for dir in `/bin/cat /etc/passwd | /bin/egrep -v '(root|sync|halt|shutdown)' | /bin/awk -F: '($7 != "/sbin/nologin") { print $6 }'`; do for file in $dir/.netrc; do if [ ! -h "$file" -a -f "$file" ]; then fileperm=`/bin/ls -ld $file | /bin/cut -f1 -d" "` if [ `echo $fileperm | /bin/cut -c5 ` != "-" ] then echo "Group Read set on $file" fi if [ `echo $fileperm | /bin/cut -c6 ` != "-" ] then echo "Group Write set on $file" fi if [ `echo $fileperm | /bin/cut -c7 ` != "-" ] then echo "Group Execute set on $file" fi if [ `echo $fileperm | /bin/cut -c8 ` != "-" ] then echo "Other Read set on $file" fi if [ `echo $fileperm | /bin/cut -c9 ` != "-" ] then echo "Other Write set on $file" fi if [ `echo $fileperm | /bin/cut -c10 ` != "-" ] then echo "Other Execute set on $file" fi fi done done9.2.10(Check for Presence of User .rhosts obsLWhile no .rhosts files are shipped with RHEL6, users can easily create them.0This action is only meaningful if .rhosts support is permitted in the file /etc/pam.conf. Even though the .rhosts files are ineffective if support is disabled in /etc/pam.conf, they may have been brought over from other systems and could contain information useful to an attacker for those other systems.=If any users have .rhosts files determine why they have them.#!/bin/bash for dir in `/bin/cat /etc/passwd | /bin/egrep -v '(root|halt|sync|shutdown)' | /bin/awk -F: '($7 != "/sbin/nologin") { print $6 }'`; do for file in $dir/.rhosts; do if [ ! -h "$file" -a -f "$file" ]; then echo ".rhosts file in $dir" fi done done9.2.11Check Groups in /etc/passwdzOver time, system administration errors and changes can lead to groups being defined in /etc/passwd but not in /etc/group.Groups defined in the /etc/passwd file but not in the /etc/group file pose a threat to system security since group permissions are not properly managed.qAnalyze the output of the Audit step above and perform the appropriate action to correct any discrepancies found.Create a script as shown below and run it: #!/bin/bash for i in $(cut -s -d: -f4 /etc/passwd | sort -u ); do grep -q -P "^.*?:x:$i:" /etc/group if [ $? -ne 0 ]; then echo "Group $i is referenced by /etc/passwd but does not exist in /etc/group" fi done9.2.124Check That Users Are Assigned Valid Home DirectoriesnUsers can be defined in /etc/passwd without a home directory or with a home directory does not actually exist.If the user's home directory does not exist or is unassigned, the user will be placed in "/" and will not be able to write any files or have local environment variables set.If any users' home directories do not exist, create them and make sure the respective user owns the directory. Users without assigned should be removed or assigned a home directory as appropriate.LThis script checks to make sure that home directories assigned in the /etc/passwd file exist. #!/bin/bash cat /etc/passwd | awk -F: '{ print $1 " " $3 " " $6 }' | while read user uid dir; do if [ $uid -ge 500 -a ! -d "$dir" -a $user != "nfsnobody" ]; then echo "The home directory ($dir) of user $user does not exist." fi done9.2.13#Check User Home Directory OwnershipThe user home directory is space defined for the particular user to set local environment variables and to store personal files.wSince the user is accountable for files stored in the user home directory, the user must be the owner of the directory.eChange the ownership any home directories that are not owned by the defined user to the correct user.This script checks to make sure users own the home directory they are assigned to in the /etc/passwd file. #!/bin/bash cat /etc/passwd | awk -F: '{ print $1 " " $3 " " $6 }' | while read user uid dir; do if [ $uid -ge 500 -a -d "$dir" -a $user != "nfsnobody" ]; then owner=$(stat -L -c "%U" "$dir") if [ "$owner" != "$user" ]; then echo "The home directory ($dir) of user $user is owned by $owner." fi fi done9.2.14Check for Duplicate UIDsAlthough the useradd program will not let you create a duplicate User ID (UID), it is possible for an administrator to manually edit the /etc/passwd file and change the UID field.cUsers must be assigned unique UIDs for accountability and to ensure appropriate access protections.Based on the results of the script, establish unique UIDs and review all files owned by the shared UID to determine which UID they are supposed to belong to.This script checks to make sure all UIDs in the /etc/passwd file are unique. #!/bin/bash echo "The Output for the Audit of Control 9.2.15 - Check for Duplicate UIDs is" /bin/cat /etc/passwd | /bin/cut -f3 -d":" | /bin/sort -n | /usr/bin/uniq -c | while read x ; do [ -z "${x}" ] & then users=`/bin/gawk -F: '($3 == n) { print $1 }' n=$2 /etc/passwd | /usr/bin/xargs` echo "Duplicate UID ($2): ${users}" fi done9.2.15Check for Duplicate GIDsAlthough the groupadd program will not let you create a duplicate Group ID (GID), it is possible for an administrator to manually edit the /etc/group file and change the GID field.aUser groups must be assigned unique GIDs for accountability and to ensure appropriate access protections. NOTE: In the case of extremely large groups it can become necessary to split a GID across group names due to character limits per line. Any such instances should be carefully audited, unless absolutely necessary such instances should be avoided.Based on the results of the script, establish unique GIDs and review all files owned by the shared GID to determine which group they are supposed to belong to.This script checks to make sure all GIDs in the /etc/group file are unique. You can also use the /usr/sbin/grpck command to check for other inconsistencies in the /etc/group file. #!/bin/bash echo "The Output for the Audit of Control 9.2.16 - Chec< k for Duplicate GIDs is" /bin/cat /etc/group | /bin/cut -f3 -d":" | /bin/sort -n | /usr/bin/uniq -c | while read x ; do [ -z "${x}" ] & then grps=`/bin/gawk -F: '($3 == n) { print $1 }' n=$2 /etc/group | xargs` echo "Duplicate GID ($2): ${grps}" fi done9.2.16Check for Duplicate User NamesAlthough the useradd program will not let you create a duplicate user name, it is possible for an administrator to manually edit the /etc/passwd file and change the user name.KIf a user is assigned a duplicate user name, it will create and have access to files with the first UID for that username in /etc/passwd. For example, if "test4" has a UID of 1000 and a subsequent "test4" entry has a UID of 2000, logging in as "test4" will use UID 1000. Effectively, the UID is shared, which is a security problem.Based on the results of the script, establish unique user names for the users. ob ownerships will automatically reflect the change as long as the users have unique UIDs.This script checks to make sure all user names in the /etc/passwd file are unique. #!/bin/bash echo "The Output for the Audit of Control 9.2.18 - Check for Duplicate User Names is" cat /etc/passwd | cut -f1 -d":" | /bin/sort -n | /usr/bin/uniq -c | while read x ; do [ -z "${x}" ] & then uids=`/bin/gawk -F: '($1 == n) { print $3 }' n=$2 /etc/passwd | xargs` echo "Duplicate User Name ($2): ${uids}" fi done9.2.17Check for Duplicate Group NamesAlthough the groupadd program will not let you create a duplicate group name, it is possible for an administrator to manually edit the /etc/group file and change the group name.If a group is assigned a duplicate group name, it will create and have access to files with the first GID for that group in /etc/group. Effectively, the GID is shared, which is a security problem.Based on the results of the script, establish unique names for the user groups. ob group ownerships will automatically reflect the change as long as the groups have unique GIDs.This script checks to make sure all group names in the /etc/group file are unique. #!/bin/bash echo "The Output for the Audit of Control 9.2.19 - Check for Duplicate Group Names is" cat /etc/group | cut -f1 -d":" | /bin/sort -n | /usr/bin/uniq -c | while read x ; do [ -z "${x}" ] & then gids=`/bin/gawk -F: '($1 == n) { print $3 }' n=$2 /etc/group | xargs` echo "Duplicate Group Name ($2): ${gids}" fi done9.2.18'Check for Presence of User .netrc obsXThe .netrc file contains data for logging into a remote host for file transfers via FTP.The .netrc file presents a significant security risk since it stores passwords in unencrypted form. Even if FTP is disabled, user accounts may have brought over .netrc files from other systems which could pose a risk to those systems.)Making global modifications to users' files without alerting the user community can result in unexpected outages and unhappy users. Therefore, it is recommended that a monitoring policy be established to report user .netrc files and determine the action to be taken in accordance with site policy.#!/bin/bash for dir in `/bin/cat /etc/passwd | /bin/awk -F: '{ print $6 }'`; do if [ ! -h "$dir/.netrc" -a -f "$dir/.netrc" ]; then echo ".netrc file $dir/.netrc exists" fi done9.2.19)Check for Presence of User .forward obsKThe .forward file specifies an email address to forward the user's mail to.Use of the .forward file poses a security risk in that sensitive data may be inadvertently transferred outside the organization. The .forward file also poses a risk as it can be used to execute commands that may perform unintended actions.+Making global modifications to users' files without alerting the user community can result in unexpected outages and unhappy users. Therefore, it is recommended that a monitoring policy be established to report user .forward files and determine the action to be taken in accordance with site policy.,This script checks for the presence of .forward files that may be in violation of the site security policy. #!/bin/bash for dir in `/bin/cat /etc/passwd | /bin/awk -F: '{ print $6 }'`; do if [ ! -h "$dir/.forward" -a -f "$dir/.forward" ]; then echo ".forward file $dir/.forward exists" fi doneInternal Revenue ServiceOffice of Safeguards % SCSEM Version: 1.0NOTICE:The IRS strongly recommends agencies test all Safeguard Computer Security Evaluation Matrix (SCSEM) settings in a development or testenvironment prior to deployment in production. In some cases a security setting mayimpact a system s functionality and usability. Consequently,it is important to perform testing to determine the impact on system security, functionality, and usability. Ideally, the test system configurationshould match the production system configuration. Prior to making changes to the production system, agencies should back up all critical datafiles on the system and if possible, make a full backup of the system to ensure it can be restored to its pre-SCSEM state if necessary.General Testing Information Agency Name: Agency Code:Test Location: Test Date: Closing Date:Shared Agencies:Name of Tester: Device Name:OS/App Version:.Agency Representatives and Contact InformationName:Org:Title:Phone:E-mail:LThis SCSEM was designed to comply with Section 508 of the Rehabilitation ActHPlease submit SCSEM feedback and suggestions to SafeguardReports@IRS.govHObtain SCSEM updates online at http://www.irs.gov/uac/Safeguards-ProgramIgnore fields below)Test (Automated SCAP & Manual Test Cases)Test (Manual Test Cases Only)Testing Results INSTRUCTIONS:The 'Info' status is provided for use by the tester during test execution to indicate more information is needed to complete the test.sIt is not an acceptable final test status, all test cases should be Pass, Fail or N/A at the conclusion of testing.6 Use this box if all SCSEM tests were conducted.CompleteBlank AvailableAll SCSEM TestsThis table calculates all Final Test ResultsAutomatically CalculatedTotal%PassFailInfoN/ATest (Automated) Test (Manual) InstructionsIntroduction and Purpose:Test Cases Legend: % Test IDtPre-populated number to uniquely identify SCSEM test cases. The ID format includes the platform, platform version dand a unique number (01-XX) and can therefore be easily identified after the test has been executed. % NIST IDkMapping of test case requirements to one or more NIST SP 800-53 control identifiers for reporting purposes.% NIST Control Name&Full name which describes the NIST ID.% Test Method:oDescription of specifically what the test is designed to accomplish. The objective should be a summary of the test case and expected results.% Test ProceduresuA detailed description of the step-by-step instructions to be followed by the tester. The test procedures should be % Expected ResultshProvides a description of the acceptable conditions allowed as a result of the test procedure execution.% Actual ResultszThe tester shall provide appropriate detail describing the outcome of the test. The tester is responsible for identifyingeInterviewees and Evidence to validate the results in this field or the separate Notes/Evidence field.% StatuszThe tester indicates the status for the test results (Pass, Fail, Info, N/A). "Pass" indicates that the expected results ywere met. "Fail" indicates the expected results were not met. "Info" is temporary and indicates that the test executionris not completed and additional information is required to determine a Pass/Fail status. "N/A" indicates that the ttest subject is not capable of implementing the expected results and doing so does not impact security. The tester 7must determine the appropriateness of the "N/A" status.< % Notes/EvidencevAs determined appropriate to the tester or as required by the test method, procedures or expected results, the tester nmay need to provide additional information pertaining to the test execution (Interviewee, Documentation, etc.) Change LogVersionDateDescription of ChangesAuthor First ReleaseBooz Allen HamiltonAppendixSCSEM Sources:YThis SCSEM was created for the IRS Office of Safeguards based on the following resources.p% IRS Publication 1075, Tax Information Security Guidelines for Federal, State and Local Agencies (January 2014)u% NIST SP 800-53 Rev. 4, Recommended Security Controls for Federal Information Systems and Organizations (April 2013)7Out of Scope Controls - Unselected NIST 800-53 ControlsQReason: Not required by Publication 1075. See Publication 1075 for more details.|AC-21, AU-13, AU-14, CP-3, CP-8, CP-9, CP-10, IA-8, PE-9, PE-10, PE-11, PE-12, PE-13, PE-14, PE-15, PM-1, PM-3, PM-5, PM-6, zPM-7, PM-8, PM-9, PM-10, PM-11, SA-12, SA-13, SA-14, SC-16, SC-20, SC-22, SC-25, SC-26, SC-27, SC-28, SC-29, SC-30, SC-31,SC-33, SC-34, SI-8, SI-134Out of Scope Controls - Policy & Procedural ControlsGReason: Tested in the Management, Operational and Technical (MOT) SCSEMAC-1, AC-14, AC-18, AC-19, AC-20, AC-22, AT-3, AT-4, AU-1, AU-7, AU-11, CA-1, CA-2, CA-3, CA-5, CA-6, CA-7, CM-1, CM-2, CM-3, CM-4, CM-5, CM-6, CM-7, CM-8, CM-9, CP-1, CP-2, CP-4, CP-6, IA-1, IR-3, IR-7, IR-8, MA-1, MA-2, MA-3, MA-4, MA-5, PL-1, PL-2, PL-4, PL-5, PL-6, PM-2, RA-1, RA-2, RA-3, RA-5, SA-1, SA-2, SA-3, SA-4, SA-5, SA-6, SA-7, SA-8, SA-10, SA-11, SC-1, SC-5, SC-7, SC-12, SC-15, SC-17, SC-18, SC-19, SC-32, *SI-1, SI-4, SI-5, SI-7, SI-9, SI-10, SI-11@Out of Scope Controls - Physical Security or Disclosure ControlsMReason: Tested in the Safeguard Disclosure Security Evaluation Matrix (SDSEM)AT-1, AT-2, CP-7, IR-1, IR-2, IR-4, IR-5, IR-6, MP-1, MP-2, MP-3, MP-4, MP-5, MP-6, MP-7, PE-1, PE-2, PE-3, PE-4, PE-5, PE-6, PE-7, PE-8, PE-16,P PE-17, PE-18, PM-4, PS-1, PS-2, PS-3, PS-4, PS-5, PS-6, PS-7, PS-8, SA-9, SI-12Test IDNIST IDNIST Control ID Test MethodRHL6-01RHL6-02RHL6-03RHL6-04RHL6-05RHL6-06RHL6-07RHL6-08RHL6-09RHL6-10RHL6-11RHL6-12RHL6-13RHL6-14RHL6-15RHL6-16RHL6-17RHL6-18RHL6-19RHL6-20RHL6-21RHL6-22RHL6-23RHL6-24RHL6-25RHL6-26RHL6-27RHL6-28RHL6-29RHL6-30RHL6-31RHL6-32RHL6-33RHL6-34RHL6-35RHL6-36RHL6-37RHL6-38RHL6-39RHL6-40RHL6-41RHL6-42RHL6-43RHL6-44RHL6-45RHL6-46RHL6-47RHL6-48RHL6-49RHL6-50RHL6-51RHL6-52RHL6-53RHL6-54RHL6-55RHL6-56RHL6-57RHL6-58RHL6-59RHL6-60RHL6-61RHL6-62RHL6-63RHL6-64RHL6-66RHL6-67RHL6-69RHL6-70RHL6-71RHL6-72RHL6-73RHL6-74RHL6-76RHL6-78RHL6-79RHL6-80RHL6-81RHL6-82RHL6-83RHL6-84RHL6-85RHL6-86RHL6-87RHL6-88RHL6-89RHL6-90RHL6-91RHL6-92RHL6-93RHL6-94RHL6-95RHL6-96RHL6-97RHL6-98RHL6-99RHL6-100RHL6-101RHL6-102RHL6-103RHL6-104RHL6-105RHL6-106RHL6-107RHL6-108RHL6-109RHL6-110RHL6-111RHL6-112RHL6-113RHL6-114RHL6-115RHL6-116RHL6-117RHL6-118RHL6-119RHL6-120RHL6-121RHL6-122RHL6-123RHL6-124RHL6-125RHL6-126RHL6-127RHL6-128RHL6-129RHL6-130RHL6-131RHL6-132RHL6-133RHL6-134RHL6-135RHL6-136RHL6-138RHL6-139RHL6-140RHL6-141RHL6-142RHL6-143RHL6-144RHL6-145RHL6-146RHL6-147RHL6-148RHL6-149RHL6-150RHL6-151RHL6-152RHL6-153RHL6-154RHL6-155RHL6-156RHL6-157RHL6-158RHL6-159RHL6-160RHL6-161RHL6-162RHL6-163RHL6-164RHL6-165RHL6-166RHL6-167CIS Benchmark Section #Recommendation # Section TitleActual ResultsStatusNotes/Evidence Update MaxAuth Tries from 4 to 33 * minlen=14 - Was updated to 8 characters or more Updated from 5 to 246Added language to cover administrator password change.Changed Min Days from 7 to 1SEdit the /etc/ssh/sshd_config file to set the parameter as follows: MaxAuthTries 3To verify the correct SSH setting, run the following command and verify that the output is as shown: # grep "^MaxAuthTries" /etc/ssh/sshd_config MaxAuthTries 3!Set SSH MaxAuthTries to 3 or LessSetting the MaxAuthTries parameter to a low number will minimize the risk of successful brute force attacks to the SSH server. While the recommended setting is 3, it is set the number based on site policy.cThe pam_cracklib module checks of the strength of passwords. It performs checks such as making sure a password is not a dictionary word, it is a certain length, contains a mix of characters (e.g. alphabet, numeric, other) and more. The following are definitions of the pam_cracklib.so options. * try_first_pass - retrieve the password from a previous stacked PAM module. If not available, then prompt the user for a password. * retry=3 - Allow 3 tries before sending back a failure. * minlen=14 - password must be 8 characters or more * dcredit=-1 - provide at least 1 digit * ucredit=-1 - provide at least one uppercase character * ocredit=-1 - provide at least one special character * lcredit=-1 - provide at least one lowercase character The setting shown above is one possible policy. Alter these values to conform to your own organization's password policies.Set the pam_cracklib.so parameters as follows in /etc/pam.d/system-auth: password required pam_cracklib.so try_first_pass retry=3 minlen=8 dcredit=-1 ucredit=-1 ocredit=-1 lcredit=-1Perform the following to determine the current settings in the pam_cracklib.so file. # grep pam_cracklib.so /etc/pam.d/system-auth password required pam_cracklib.so try_first_pass retry=3 minlen=8 dcredit=-1 ucredit=-1 ocredit=-1 lcredit=-1Edit the /etc/pam.d/system-auth file and add the "auth" line as highlighted below: auth required pam_env.so auth required pam_tally2.so onerr=fail audit silent deny=3 unlock_time=900 auth required pam_deny.so NOTE: If a user has been locked out because they have reached the maximum consecutive failure count defined by deny= in the pam_tally2.so module, the user can be unlocked by issuing the command /sbin/pam_tally2 -u __ --reset. This command sets the failed count to 0, effectively unlocking the user.tSet the pam_unix.so remember parameter to 24 in /etc/pam.d/system_auth: password sufficient pam_unix.so remember=24Perform the following to determine the current setting for reuse of older passwords: # grep "remember" /etc/pam.d/system_auth password sufficient pam_unix.so remember=24Set the PASS_MIN_DAYS parameter to 1 in /etc/login.defs: PASS_MIN_DAYS 1 Modify active user parameters to match: # chage --mindays 1v# grep PASS_MIN_DAYS /etc/login.defs PASS_MAX_DAYS 1 # chage --list Minimum number of days between password change: 1The PASS_MIN_DAYS parameter in /etc/login.defs allows an administrator to prevent users from changing their password until a minimum number of days have passed since the last time the user changed their password. It is recommended that PASS_MIN_DAYS parameter be set to 1 day.4Normal Users Set the PASS_MAX_DAYS parameter to 90 in /etc/login.defs: PASS_MAX_DAYS 90 Modify active user parameters to match: # chage --maxdays 90 Privilege Accounts Set the PASS_MAX_DAYS parameter to 60 in /etc/login.defs: PASS_MAX_DAYS 60 Modify active user parameters to match: # chage --maxdays 60Normal Users # grep PASS_MAX_DAYS /etc/login.defs PASS_MAX_DAYS 90 # chage --list Maximum number of days between password change: 90 Privilege Accounts # grep PASS_MAX_DAYS /etc/login.defs PASS_MAX_DAYS 60 # chage --list Maximum number of days between password change: 60GExpected Results: The warning banner is compliant with IRS guidelines and contains the follow< ing 4 elements: - the system contains US government information - users actions are monitored and audited - unauthorized use of the system is prohibited - unauthorized use of the system is subject to criminal and civil penaltiesExpected ResultsTest ProcedureRemediation Procedure Release DateEnd of Production 1 PhaseEnd of Production 2 PhaseEnd of Production 3 PhaseEnd of Extended Life PhaseRed Hat Enterprise Linux 2.126 March 2002 (AS)1 May 2003 (ES)Red Hat Enterprise Linux 3Red Hat Enterprise Linux 4Red Hat Enterprise Linux 5Red Hat Enterprise Linux 6Q2 2016Q2 2017Red Hat Enterprise Linux 7Q4 2019Q4 2020 Support TableSC-8*Transmission Confidentiality and Integrity Interview?Verifies FTI is encrypted when in transit across a WAN or LAN. 1. Confirm whether all FTI data in transit is encrypted when moving across a Wide Area Network (WAN) and within the agency s Local Area Network (LAN). 1. All FTI data in transit is encrypted when moving across a Wide Area Network (WAN) and within the agency s Local Area Network (LAN). AC-2Account Management_Verify the agency has implemented an account management process for the Red Hat Linux Server. 1. Interview the Red Hat administrator to verify documented operating procedures exist for user and system account creation, termination, and expiration. Z1. The Red Hat administrator can demonstrate that documented operating procedures exist. Verify that audit trails are reviewed at a minimum weekly for anomalies (i.e. standard operations, unauthorized access attempts, etc.). Exceptions and violations are properly analyzed and appropriate actions are taken.AU-6%Audit Review, Analysis, and Reporting1. Interview Red Hat administrator and ask for the system documentation that states how often audit logs are reviewed. Also, determine when the last audit logs were reviewed. 2. Examine reports that demonstrate monitoring of security violations, such as unauthorized user access. B1. The Red Hat administrator administrator can provide system documentation identifying how often the auditing logs are reviewed. 2. The audit trail is reviewed weekly or more frequently at the discretion of the information system owner for indications of unusual activity related to potential unauthorized FTI access. AC-5Separation of DutiesInterview the DBA to identify the following: - Personnel that review and clear audit logs. - Personnel that perform non-audit administration such as create, modify, and delete access control rules; DB user access management.mPersonnel who review and clear audit logs are separate from personnel that perform non-audit administration. Verify that the system enforces a separation of duties for sensitive administrator roles. There is an effective segregation of duties between the administration functions and the auditing functions of the system.Interview the Red Hat administrator to identify the following: - Personnel that review and clear audit logs. - Personnel that perform non-audit administration such as create, modify, and delete access control rules; system user access management.IRS Safeguards RequirementAU-9Protection of Audit InformationCAudit trails cannot be read or modified by non-administrator users.1. Interview the Red Hat administrator to determine the application audit log location. Examine the permission settings of the log files. V1. Log files have appropriate permissions assigned and permissions are not excessive.Interview ExamineAn authoritative (U.S. IRS approved source) time-server is used. Approved sources include the US Naval Observatory NTP servers or the NIST Internet Time Service.CM-7Least Functionality%Unneeded functionality is disabled. 1. Any functions installed by default that are not required by the application are disabled. 2. Services or software which are not needed are not present or disabled on the server.51. Interview the Red Hat administrator to determine what functionality is installed and enabled by default for the application. 2. Determine what software is installed on the servers. Determine which services are needed by examining the system documentation and interviewing the Application Administrator. AU-12Audit Generation1. Audit data is captured, backed up, and maintained. IRS requires agencies to retain archived audit logs/trails for the remainder of the year they were made plus six years.1. Interview the Red Hat administrator to determine if audit data is captured, backed up, and maintained. IRS practice has been to retain archived audit logs/trails for the remainder of the year they were made plus six years.Verify that there is a /tmp file partition in the /etc/fstab file. Run the following command. # grep "[[:space:]]/tmp[[:space:]]" /etc/fstab5A separate partition for /tmp exists on the system. DescriptionRationale StatementRun the following commands to determine if the system is configured as recommended. # grep /tmp /etc/fstab | grep nodev # mount | grep /tmp | grep nodev If either command emits no output then the system is not configured as recommend. This is a finding.Run the following commands to determine if the system is configured as recommended. # grep /tmp /etc/fstab | grep nosuid # mount | grep /tmp | grep nosuid If either command emits no output then the system is not configured as recommende. This is a finding.Run the following commands to determine if the system is configured as recommended. # grep /tmp /etc/fstab | grep noexec # mount | grep /tmp | grep noexec If either command emits no output then the system is not configured as recommended. This is a finding.(Output is emitted and it contains nodev.)Output is emitted and it contains nosuid.)Output is emitted and it contains noexec.5A separate partition for /var exists on the system. @Perform the following to determine if the system is configured as recommended: # grep -e "^/tmp" /etc/fstab | grep /var/tmp /tmp /var/tmp none none 0 0 # mount | grep -e "^/tmp" | grep /var/tmp /tmp on /var/tmp type none (rw,bind) If the above commands emit no output then the system is not configured as recommended.TOutput is emitted and it contains something similar to the following line: none 0 0 9A separate partition for /var/log exists on the system. ?A separate partition for /var/log/audit exists on the system. 6A separate partition for /home exists on the system. Output contains "nodev".Output contains "noexec".Output contains "nosuid".POutput is emitted and it contains something similar to the following line: nodevQOutput is emitted and it contains something similar to the following line: nosuidQOutput is emitted and it contains something similar to the following line: noexecInterview/Examine_Red Hat GPG Key is installed and the GPG fingerprint matches the one from Red Hat's web site. Output should contain "nodev".6# grep /etc/fstab Verify that nodev is an option. 9# grep /etc/fstab Verify that noexec is an option. 7# grep /etc/fstab Verify that nosuid is an option. *gpgcheck is set to "1" in all occurrences.+All software packages have been updated. Output is not emitted. If output is emitted, all packages must have permissions they were intended to have and are authorized. The agency must maintain justification for these permissions.2 /etc/grub.conf is User and Group owned by root. j/etc/grub.conf file only allows read and write access to root. The file must be less permissive than 600.aLatest update of the Red Hat software be used. Refer to the vendors support website to verify that support for it has not expired. Note: Each organization responsible for the management of the agency's operating systems software shall ensure< that unsupported software is removed or upgraded to a supported version prior to a vendor dropping support.3Sticky Bit is set on all World-Writable DirectoriesGThe latest security patches are installed and the system is registered telnet-server has been removed from the system. Output should contain something similar to the following: package telnet-server is not installedwVirtual memory is randomized. Output should contain something similar to the following: kernel.randomize_va_space = 2telnet package has been removed from the system. Output should contain something similar to the following: package telnet is not installediExecShield is enabled. Output should contain something similar to the following: kernel.exec-shield = 1Core Dumps are restricted. Output should contain something similar to the following: hard core 0 and/or fs.suid_dumpable = 0Interactive boot is disabled. The PROMPT parameter should be set to "no". Output should contain something similar to the following: PROMPT=noThe UNIX host should not allow booting to single user mode without authentication. Output should contain something similar to the following: SINGLE=/sbin/sulogingBoot Loader Password is set. Output should contain something similar to the following: password --md5rsh-server has been removed from the system. Output should contain something similar to the following: package rsh-server is not installedrsh has been removed from the system. Output should contain something similar to the following: package rsh is not installedypbind has been removed from the system. Output should contain something similar to the following: package ypbind is not installedypserv has been removed from the system. Output should contain something similar to the following: package ypserv is not installedtftp has been removed from the system. Output should contain something similar to the following: package tftp is not installedtftp-server has been removed from the system. Output should contain something similar to the following: package tftp-server is not installedtalk-server has been removed from the system. Output should contain something similar to the following: package talk-server is not installedtalk has been removed from the system. Output should contain something similar to the following: package talk is not installednchargen-dgram is disabled. Output should contain something similar to the following: chargen-dgram: off pchargen-stream is disabled. Output should contain something similar to the following: chargen-stream: off ndaytime-dgram is disabled. Output should contain something similar to the following: daytime-dgram: off pdaytime-stream is disabled. Output should contain something similar to the following: daytime-stream: off hecho-dgram is disabled. Output should contain something similar to the following: echo-dgram: off jecho-stream is disabled. Output should contain something similar to the following: echo-stream: off ntcpmux-server is disabled. Output should contain something similar to the following: tcpmux-server: off oThe system and user default umask is 027. Output should contain something similar to the following: umask 027 X Windows Server is not installed on the system. If X Windwos Server is running the agency must present a strong justification for its necessity. Justification must be documented. Avahi is disabled. Output should contain something similar to the following: avahi-daemon: 0:off 1:off 2:off 3:off 4:off 5:off 6:off CUPS is disabled. Output should contain something similar to the following: chkconfig: 0:off 1:off 2:off 3:off 4:off 5:off 6:off oDHCP is disabled. Output should contain something similar to the following: package dhcp is not installedInterview SA to determine if LDAP is running on the system. Perform the following to determine if LDAP is running. # rpm -q openldap-servers package openldap-servers is not installed # rpm -q openldap-clients package openldap-clients is not installed~DNS is disabled on the system. Output should contain something similar to the following: package bind is not installed pFTP is disabled. Output should contain something similar to the following: package vsftpd is not installedpLDAP should be removed if not needed. If LDAP is not needed and it has not been removed then this is a finding.AApache should be removed if not needed. If apache is not needed and it has not been removed then this is a finding. Output should contain something similar to the following: package httpd is not installed Note: If there is a business requirement to run this server as a web server then this control is a N/A. dovecot has been removed from the system. Output should contain something similar to the following: package dovecot is not installedSamba has been removed from the system. Output should contain something similar to the following: package samba is not installedsquid has been removed from the system. Output should contain something similar to the following: package squid is not installednet-snmp has been removed from the system. Output should contain something similar to the following: package net-snmp is not installed^NFS and RPC is disabled. Output should contain something similar to the following: nfslock: 0:off 1:off 2:off 3:off 4:off 5:off 6:off rpcgssd: 0:off 1:off 2:off 3:off 4:off 5:off 6:off rpcbind: 0:off 1:off 2:off 3:off 4:off 5:off 6:off rpcidmapd: 0:off 1:off 2:off 3:off 4:off 5:off 6:off rpcsvcgssd: 0:off 1:off 2:off 3:off 4:off 5:off 6:offFSource Routed Packet Acceptance is disabled. net.ipv4.conf.all.accept_source_route and net.ipv4.conf.default.accept_source_route parameters is set to 0 in /etc/sysctl.conf. Output should contain something similar to the following: net.ipv4.conf.all.accept_source_route = 0 net.ipv4.conf.default.accept_source_route = 0)Send Packet Redirects is disabled. net.ipv4.conf.all.send_redirects and net.ipv4.conf.default.send_redirects parameters is set to 0 in /etc/sysctl.conf. Output should contain something similar to the following: net.ipv4.conf.all.send_redirects = 0 net.ipv4.conf.default.send_redirects = 0IP Forwarding is disabled. The net.ipv4.ip_forward flag is set to 0. Output should contain something similar to the following: net.ipv4.ip_forward = 0 4ICMP Redirect Acceptance is disabled. net.ipv4.conf.all.accept_redirects and net.ipv4.conf.default.accept_redirects parameters is set to 0 in /etc/sysctl.conf. Output should contain something similar to the following: net.ipv4.conf.all.accept_redirects = 0 net.ipv4.conf.default.accept_redirects = 0Suspicious packets are logged and retained for 7 years. Output should contain something similar to the following: net.ipv4.conf.all.log_martians = 1 net.ipv4.conf.default.log_martians = 1Ignore Broadcast Requests is enabled. net.ipv4.icmp_echo_ignore_broadcasts parameter is set to 1 in /etc/sysctl.conf. Output should contain something similar to the following: net.ipv4.icmp_echo_ignore_broadcasts = 1Bad Error Message Protection is enabled. net.ipv4.icmp_ignore_bogus_error_responses parameter is set to 1 in /etc/sysctl.conf. Output should contain something similar to the following: net.ipv4.icmp_ignore_bogus_error_responses = 1TCP SYN Cookies is enabled. net.ipv4.tcp_syncookies parameter is set to 1 in /etc/sysctl.conf. Output should contain something similar to the following: net.ipv4.tcp_syncookies = 1mWireless Interfaces are deactivated. If any interfaces using wireless are active then this is a finding. CCE-14171-3 CCE-14412-1 CCE-14940-1 CCE-14927-8 CCE-14777-7CM-6 CCE-14011-1 CCE-14559-9 CCE-15007-8 CCE-14306-5 CCE-4526-0 CCE-14440-2 CCE-3818-2 CCE-4241-6 CCE-4245-7 CCE-4225-9 CCE-4146-7 CCE-4220-0 CCE-4462-8 CCE-3755-6 CCE-3487-6 CCE-4514-6 CCE-4186-3 CCE-4320-8 CCE-4269-7 CCE-4313-3 CCE-3377-9 CCE-14268-7 CCE-14132-5< CCE-14027-7 CCE-14911-2 CCE-18095-0 CCE-17248-6 CCE-4379-4 CCE-3851-3 CCE-4054-3 CCE-4450-3 CCE-4331-5 CCE-4322-4 CCE-4387-7 CCE-3660-8 CCE-14716-5 CCE-14491-5 CCE-3845-5 CCE-4431-3 CCE-14063-2IA-5 CCE-14122-6 CCE-3410-8 CCE-14939-3 CCE-4044-4 CCE-4180-6 CCE-3870-3 CCE-18412-7 CCE-4060-0 CCE-3717-6 CCE-3324-1 CCE-4178-0 CCE-4090-7 CCE-3522-0 CCE-4275-4 CCE-4042-8 CCE-3399-3 CCE-4197-0 CCE-4144-2 CCE-4330-7 CCE-4308-3 CCE-3705-1 CCE-4348-9 CCE-4273-9 CCE-3916-4 CCE-18200-6 CCE-18151-1 CCE-4365-3 CCE-4464-4 CCE-4491-7 CCE-4219-2 CCE-3919-8 CCE-4239-0 CCE-4076-6 CCE-4091-5 CCE-4276-2 CCE-4189-7 CCE-17742-8 CCE-17698-2 CCE-17639-6 CCE-4406-5 CCE-4324-0 CCE-4325-7 CCE-4097-2 CCE-3566-7 CCE-3988-3 CCE-4210-1 CCE-3883-6 CCE-3495-9 CCE-3795-2 CCE-3685-50A separate /tmp partition has not been created. 9The nodev option has not been set on the /tmp partition. :The nosuid option has not been set on the /tmp partition. :The noexec option has not been set on the /tmp partition. 0A separate /var partition has not been created. 3The /var/tmp directory has not been bound to /tmp. 4A separate /var/log partition has not been created. :A separate /var/log/audit partition has not been created. 1A separate /home partition has not been created. -The nodev option has not been added to /home.BThe nodev option has not been added to removable media partitions.CThe noexec option has not been added to removable media partitions.CThe nosuid option has not been added to removable media partitions.>The nodev option has not been added to the /dev/shm partition.?The nosuid option has not been added to the /dev/shm partition.?The noexec option has not been added to the /dev/shm partition.@Sticky Bit has not been set on all World-Writable directories. CThe latest security patches have not been installed on the system. )Red Hat GPG Key has not been installed. ,gpgcheck is has not been globally activated.+Software packages have not been updated. 0Packages do not have appropriate permissions. 8/etc/grub.conf file does not have the correct ownership.6/etc/grub.conf file does not have correct permissions.;Boot password has not been configured on the boot loader. 5Authentication is not required in single user mode. (Interactive Boot has not been disabled. &Core Dumps have not been restricted. "ExecShield has not been enabled. &Virtual memory has not been randomized5telnet-server has not been removed from the system. 6telnet package has not been removed from the system. 2rsh-server has not been removed from the system. +rsh has not been removed from the system. .ypbind has not been removed from the system. .ypserv has not been removed from the system. ,tftp has not been removed from the system. 3tftp-server has not been removed from the system. ,talk has not been removed from the system. 3talk-server has not been removed from the system. 'chargen-dgram has not been disabled. (chargen-stream has not been disabled. (daytime-stream has not been disabled. #echo-dgram has not been disabled. $echo-stream has not been disabled. 'tcpmux-server has not been disabled. 'daytime-dgram has not been disabled. *The default umask has not been set to 027./X Windows has not been removed from the system.$Avahi server has not been disabled. 7Common Unix Print System (CUPS) has not ben disabled. BDynamic Host Configuration Protocol (DHCP) has not been disabled. WNetwork Time Protocol (NTP) has not been synchronized to an authorative time server. ELightweight Directory Access Protocol (LDAP) has not been disabled. "NFS and RPC has not been disabled..Domain Name System (DNS) has been disabled. 6ob Transfer Protocol (FTP) has not been disabled. Apache has not been removed. /dovecot has not been removed from the system. -Samba has not been removed from the system. -squid has not been removed from the system. 0net-snmp has not been removed from the system. Mail transfer agents are set to Local-Only Mode. Output should contain something similar to the following: tcp 0 0 127.0.0.1:25 0.0.0.0:* LISTEN:Mail transfer agents have not been set to Local-Only Mode.&IP Forwarding has not been disabled. 5Source Routed Packet Acceptance has not been disabled.ICMP redirect messages are not being rejected..Logging is not being performed on the system. /Ignore Broadcast Requests has not been enabled.2Bad Error Message Protection has not been enabled.'TCP SYN Cookies has not been enabled. 0Wireless Interfaces have not been deactivated. 4IPv6 Router Advertisements have not been disabled. 2IPv6 Redirect Acceptance have not been disabled. IPv6 has not been disabled. $TCP Wrappers have not been enabled. 7/etc/hosts.deny has not been configured appropriately. DDatagram Congestion Control Protocol (DCCP) has not been disabled. CStream Control Transmission Protocol (SCTP) has not been disabled. AReliable Datagram Sockets (RDS) protocol has not been disabled. OTransparent Inter-Process Communication (TIPC) protocol has not been disabled. IPtables has not been enabled.!IP6Tables has not been enabled. rsyslog has not been installed.Dsyslog has not been turned off and rsyslog has not been turned on. :/etc/rsyslog.conf has not been configured appropriately. -Logs are not being sent to a remote log host.,rsyslog is not listening for remote messages%Systems logs are not being rotated. F/etc/at.deny and /etc/at.allow have not been configured appropriately.SUser/Group Owner permissions on /etc/cron.d have not been configured appropriately.YUser/Group Owner permissions on /etc/cron.monthly have not been configured appropriately.XUser/Group Owner permissions on /etc/cron.weekly have not been configured appropriately.WUser/Group Owner permissions on /etc/cron.daily have not been configured appropriately.XUser/Group Owner permissions on /etc/cron.hourly have not been configured appropriately.TUser/Group Owner permissions on /etc/crontab have not been configured appropriately.WUser/Group Owner permissions on /etc/anacrontab have not been configured appropriately.Configuration Settings Protection of Audit Information AU-9 CM-7 Least Functionality SI-7,Software, Firmware and Information Integrity-Software, Firmware and Information Integrity AC-3 Access Enforcement AC-3Access Enforcement Authenticator Management SC-2 Application PartitioningSC-28!Protection of Information at RestAccess Enforcement SI-16Memory ProtectionAC-3 Access Enforcement AU-8 Time StampsSC-7Boundary ProtectionAU-2 Audit Events$Audit Review, Analysis and ReportingAccess EnforcementIA-7#Cryptographic Module AuthenticationBoundary ProtectionsLeast PrivilegeAC-8System Use NotificationAuthenticator ManagementAC-7Unsuccessful Logon AttemptsAccount Management AC-2 Finding (Internal Use Only)-SSH v2 is not being utilized on the system. "LogLevel has not been set to INFO.\User/Group Owner permissions on /etc/ssh/sshd_config have not been configured appropriately.*SSH X11 forwarding has not been disabled. /SSH MaxAuthTries has not been set to 3 or less.)SSH IgnoreRhosts has not been set to Yes.3SSH HostbasedAuthentication has not been set to No.%SSH Root Login has not been disabled.2Users are allowed to the Set Environment Options.&Approved ciphers are not being used. Idle timeout has not been set. "Having no timeout value associated with a connection could allow an unauthorized user access to another user's ssh session (e.g. user walks away from their computer and doesn't lock the screen). Setting a timeout value at least reduces the risk of this happening.. While the recommended setting is 900 seconds (15 minutes), set this timeout value based on site policy. The recommended setting for ClientAliveCountMax is 0. In this case, the client session will be terminated a< fter 15 minutes of idle time and no keepalive messages will be sent.rEdit the /etc/ssh/sshd_config file to set the parameter as follows: ClientAliveInterval 900 ClientAliveCountMax 0To verify the correct SSH setting, run the following command and verify that the output is as shown: # grep "^ClientAliveInterval" /etc/ssh/sshd_config ClientAliveInterval 900 # grep "^ClientAliveCountMax" /etc/ssh/sshd_config ClientAliveCountMax 0 0Remote access via SSH has not been restricted. 6The warning banner is not Publication 1075 compliant. 7Password-hashing algorithm has not been set to SHA-512.'Passwords do not my IRS requirements. :Root login has not been restricted on the system console. 2Access to the su command has not been restricted. QPassword expiration warning days have not been configured per IRS requirements. EPassword Minimum age has not been configured per IRS requirements. CPassword Expiration has not been configured per IRS requirements. @Password History has not been configured per IRS requirements. TLockout for failed password attempts has not been configured per IRS requirements. RHL6-65RHL6-68RHL6-75RHL6-77RHL6-137!.netrc file exists on the system.#.forward files exist on the system..There are duplicate User names on the system. /There are duplicate Group names on the system. )There are duplicate GID's on the system. )There are duplicate UID's on the system. 2Users are not the owner of their home directory. 6Users have not been assigned valid home directories. HGroups exist in the /etc/password file that are not in the /etc/group. ".rhost files exists on the system.AAccounts with a UID of 0 exist on the system that are not root. 2Legacy "+" entries exist in the /etc/group file. 3Legacy "+" entries exist in the /etc/shadow file. 5Legacy "+" entries exist in the /etc/password file. *The system has accounts without passwords.2The Root account has not been assigned a GID of 0.3System accounts may be accessed by regular users. 3The default umask for users has not been set to 77.# useradd -D -f 120User accounts that have been inactive for over a given period of time can be automatically disabled. It is recommended that accounts that are inactive for 120 or more days be disabled.MInactive user accounts have not been disabled after 120 days of inactivity. 3Warning Banner is not Publication 1075 compliant. +Permissions are excessive on /etc/passwd. ,Permissions are excessive on /etc/shadow. -Permissions are excessive on /etc/gshadow. +Permissions are excessive on /etc/group. SUser/Group Owner permissions on /etc/passwd have not been configured appropriately.SUser/Group Owner permissions on /etc/shadow have not been configured appropriately.TUser/Group Owner permissions on /etc/gshadow have not been configured appropriately.RUser/Group Owner permissions on /etc/group have not been configured appropriately.-There are World Writable files on the system.7There are Un-owned files and Directories on the system.-There are Un-grouped obs and Directories. CThere are SUID programs on the system that have not been approved. DThere are SGID programs on the system that have not been approved. DOS information has not been removed from the Login Warning Banner. )The root PATH has not been set correctly.5at/cron has not been restricted to authorized users. Note: An authoritative (U.S. IRS approved source) time-server is used. Approved sources include the US Naval Observatory NTP servers or the NIST Internet Time Service.Updated to 15 Minutes from 5Changed to 14 daysChanged to 120 days RHLGEN-01 RHLGEN-02 RHLGEN-03 RHLGEN-04 RHLGEN-05 RHLGEN-06 RHLGEN-07+1A. Red Hat Entrprise Linux 6 Test Results!2A. Generic Contols Test Results1B. Overall System Statistics2B. Overall Statistics-Section 1 ans 2 are automatically calculated.tests in the RHEL6 Test Cases tab. tests in the Gen Total Count (not percentage)Enter Results :Total Tests Performed =Verify that audit data is archived and maintained. IRS practice has been to retain archived audit logs/trails for the remainder of the year they were made plus six years. Logs must be retained for a total of 7 years. 0The Red Hat operating system is not up-to-date. /Send Packet Redirects have not been disabled. 8/etc/hosts.allow has not been configured appropriately. 0Permissions are excessive on /etc/hosts.allow. /Permissions are excessive on /etc/hosts.deny. ?/etc/rsyslog.conf file has not been configured appropriately. anacron has not been enabled. Cron has not been enabled.0SSH PermitEmptyPasswords has not been set to No.@The system has Group or World-Writeable user home directories. 6Dot files have Group or world-writeable permissions. IPv6 Router Advertisements are disabled. Output should contain something similar to the following: net.ipv6.conf.all.accept_ra = 0 net.ipv6.conf.default.accept_ra = 0IPv6 Redirect Acceptance is disabled. Output should contain something similar to the following: net.ipv6.conf.all.accept_redirect = 0 net.ipv6.conf.default.accept_redirect = 0IPv6 is disabled. Output should contain something similar to the following: NETWORKING_IPV6=no IPV6INIT=no options ipv6 disable=1dTCP Wrappers are enabled. Output should contain something similar to the following: tcp_wrappers RThe access control program is configured to grant system access to specific hosts.?Permission on /etc/hosts.allow is not more permissive than 644.v/etc/hosts.deny exists on the system and it is configured to deny all hosts not explicitly listed in /etc/hosts.allow.Verify that /etc/hosts.deny exists and is configured to deny all hosts not explicitly listed in /etc/hosts.allow: # grep "ALL: ALL" /etc/hosts.deny ALL: ALL If the 'ALL: ALL' is in the /etc/hosts.deny file, then any tcp service from a host or network not listed in the /etc/hosts.allow file will not be allowed access. If the entry is not in /etc/hosts.deny or if either of the two files do not exist, then this is a finding. >Permission on /etc/hosts.deny is not more permissive than 644.gDCCP is disabled. Output should contain something similar to the following: install dccp /bin/true fSCTP is disabled. Output should contain something similar to the following: install sctp /bin/trueeDCCP is disabled. Output should contain something similar to the following: install rds /bin/truefDCCP is disabled. Output should contain something similar to the following: install tipc /bin/trueIPtables is enabled. Output should contain something similar to the following: iptables 0:off 1:off 2:on 3:on 4:on 5:on 6:offIP6tables is enabled. Output should contain something similar to the following: ip6tables 0:off 1:off 2:on 3:on 4:on 5:on 6:offZrsyslog is enabled. Output should contain something similar to the following: rsyslog..syslog service is turned off and the rsyslog service is turned on. Output should contain something similar to the following: syslog 0:off 1:off 2:off 3:off 4:off 5:off 6:off rsyslog 0:off 1:off 2:on 3:on 4:on 5:on 6:offrsyslog is capturing important security-related events such as (e.g., successful and failed su attempts, failed login attempts, root login attempts, etc.). Output should be logging the following: auth,user.* /var/log/messages kern.* /var/log/kern.log daemon.* /var/log/daemon.log syslog.* /var/log/syslog lpr,news,uucp,local0,local1,local2,local3,local4,local5,local6.* /var/log/unused.log0rsyslog Log ob permissions are not excessive. FLog files are sent to a central host and stored in a secure location. rsyslog is listening for remote messages. Output should contain something similar to the following: $ModLoad imtcp.so $InputTCPServerRun 514Log files are being rotated. aAnacron is enabled. Output should contain something similar to the following: cronie-anacron..zCron is enabled. Output should contain something similar to the following: crond: 0:off 1:off 2:on 3:on 4:on 5:on 6:offOutput is emitted and it contains someth< ing similar to the following line: /etc/anacrontab is User and Group owned by root and no other user. Output is emitted and it contains something similar to the following line: /etc/crontab is User and Group owned by root and no other user. Output is emitted and it contains something similar to the following line: /etc/cron.hourly is User and Group owned by root and no other user. Output is emitted and it contains something similar to the following line: /etc/cron.daily is User and Group owned by root and no other user. Output is emitted and it contains something similar to the following line: /etc/cron.weekly is User and Group owned by root and no other user. Output is emitted and it contains something similar to the following line: /etc/cron.monthly is User and Group owned by root and no other user. Output is emitted and it contains something similar to the following line: /etc/cron.d is User and Group owned by root and no other user. SSH is not using v1 compatibility, only v2 connections are accepted. Output should contain something similar to the following: Protocol 2aLogLevel is set to INFO Output should contain something similar to the following: LogLevel INFOp/etc/ssh/sshd_config file only allows read and write access to root. The file must be less permissive than 600.tSSH X11 Forwarding has been disabled. Output should contain something similar to the following: X11Forwarding nooSSH MaxAuthTries is set to 3 or Less Output should contain something similar to the following: MaxAuthTries 3kSSH IgnoreRhosts is set to Yes Output should contain something similar to the following: IgnoreRhosts yesSSH HostbasedAuthentication is set to No Output should contain something similar to the following: HostbasedAuthentication noiSSH Root Login is disabled Output should contain something similar to the following: PermitRootLogin noySSH PermitEmptyPasswords is set to No Output should contain something similar to the following: PermitEmptyPasswords no~PermitUserEnvironment option is set to No Output should contain something similar to the following: PermitUserEnvironment noOnly approved Ciphers are used. Output should contain something similar to the following: Ciphers aes128-ctr,aes192-ctr,aes256-ctrIdle Timeout has been set to 15 minutes or 900 seconds. Output should contain something similar to the following: ClientAliveInterval 900 ClientAliveCountMax 0 cDefault Umask for users is set to 077. Output should contain something similar to the following: Root Account has a GID 0. ,System accounts cannot be accessed by users.!Password Warning age is 14 days. {# grep PASS_WARN_AGE /etc/login.defs PASS_WARN_AGE 14 # chage --list Number of days of warning before password expires: 14The PASS_WARN_AGE parameter in /etc/login.defs allows an administrator to notify users that their password will expire in a defined number of days. It is recommended that the PASS_WARN_AGE parameter be set to 14 or more days.Password Minimum age is 1 day. TPassword expiration is 60 days for privilege accounts and 90 days for normal users. 0Lockout for Failed Password Attempts is set to 3Perform the following to determine the current settings for user lockout. # grep "pam_tally2" /etc/pam.d/system-auth auth required pam_tally2.so onerr=fail audit silent deny=3 unlock_time=7200 =Updated from 5 to 3 Updated Unlock time to 7200 (120 Minutes)8User accounts are locked after 120 days of inactivity. Mob permissions on the file /etc/passwd are set to 644 or more restrictive. 7ob permissions on the file /etc/shadow are set to 0008ob permissions on the file /etc/gshadow are set to 000Lob permissions on the file /etc/group are set to 644 or more restrictive. 7The file /etc/passwd is owned and group owned by root. 7The file /etc/shadow is owned and group owned by root. 8The file /etc/gshadow is owned and group owned by root. 6The file /etc/group is owned and group owned by root. 1World-Writable files do not exist on the system. *All files have a user ownership assigned. +All files have a group ownership assigned. Dobs within the system do not have the Set User ID (SUID) bit set. Eobs within the system do not have the Set Group ID (SGID) bit set. ,All user accounts have a password assigned. 0The + flag is not set on entries in /etc/passwd.0The + flag is not set on entries in /etc/shadow.0The + flag is not set on entries in /etc/group. 4Root is the only account with a User ID (UID) of 0. EAll files or directories that are PATH variables, are owned by root. =Users do not have excessive permissions to home directories. <Users do not have excessive permissions to the "dot" files. JThe .netrc file is not used on the system to store remote FTP login data. ^The .rhosts file is not used on the system to provide remote system access without a password.VFor each group on the system, there must be a definition in /etc/passwd and /etc/group=For each system user, there is an associated home directory. YFor each system user, the /etc/passwd file defines the user owning their home directory. HThe system will not contain duplicate User IDs in the /etc/passwd file. HThe system will not contain duplicate Group IDs in the /etc/group file. EThe system will not contain duplicate names in the /etc/passwd file. DThe system will not contain duplicate names in the /etc/group file. GThe .forward file is not used on the system to forward the user's mail.eThe at daemon works with the cron daemon to allow non-privileged users to submit one time only jobs at their convenience. There are two files that control at: /etc/at.allow and /etc/at.deny. If /etc/at.allow exists, then users listed in the file are the only ones that can create at jobs. If /etc/at.allow does not exist and /etc/at.deny does exist, then any user on the system, with the exception of those listed in /etc/at.deny, are allowed to execute at jobs. An empty /etc/at.deny file allows any user to create at jobs. If neither /etc/at.allow nor /etc/at.deny exist, then only superuser can create at jobs. The commands below remove the /etc/at.deny file and create an empty /etc/at.allow file that can only be read and modified by user and group root. # rm /etc/at.deny # touch /etc/at.allow # chown root:root /etc/at.allow # chmod og-rwx /etc/at.allowAccess to the at utility is controlled via the /etc/at.allow file and /etc/at.deny file(s) are removed. The /etc/at.allow file is user owned and group owned by root.6Access to the at/cron is controlled via the /etc/at.allow and /etc/cron.allow file(s). /etc/at.deny and /etc/cron.deny file (s) are removed. The /etc/at.allow and /etc/cron.allow file(s) are user owned and group owned by root. The /etc/at.allow and /etc/cron.allow file(s) are not more permissive than 600.Review output and ensure that at least one of these options is being leveraged AllowUsers, AllowGroups, DenyUsers, and/or DenyGroups. :Passwords meet Publication 1075 requirements. Password Min Length is 8 characters or more Password is not a dictionary word Password is complex Output should contain something similar to the following: password required pam_cracklib.so try_first_pass retry=3 minlen=8 dcredit=-1 ucredit=-1 ocredit=-1 lcredit=-1eAll consoles are in a physically secure location and any unauthorized consoles have not been defined.Access has been restricted to the su Command Output should contain something similar to the following: auth required pam_wheel.so use_uid wheel:x:10:root,qPassword hashing algorithm is set to SHA-512. Output should contain something similar to the following: sha515Password history is set to 24 passwords remembered. COS information is not being displayed in the system login banners. ) % SCSEM Release Date: Novmenber 18, 2014! % SCSEM Subject: Red Hat Linux 6This SCSEM is used by the IRS Office of Safeguards to evaluate compliance with IRS Publication 1075 for agencies that have implemented Red Hat Linux operating systems for systems that receiv<e, store or process or transmit Federal Tax Information (FTI). Agencies should use this SCSEM to prepare for an upcoming Safeguards review. It is also an effective tool for agency use as part of internal periodic security assessments or internal inspections to ensure continued compliance in the years when a Safeguards review is not scheduled. The agency can also use the SCSEM to identify the types of policies and procedures required to ensure continued compliance with IRS Publication 1075.KThe test case is executed by Interview or Examine methods in accordance with the test methodology specified in NIST SP 800-53A. In test plans where Automated testing is available, Automated and Manual indicators are added to the Test method to indicate whether the test can be accomplished through the Automated Assessment tool. % DescriptionLexecuted using the applicable NIST 800-53A test method (Interview, Examine).3% CIS Red Hat Enterprise Linux 6 Security Checklist F Ps:  1{  '6 ,4I9uCAKaFi cKkOHVP_vjZarEMx1M`  ƶb5 <hjI{Gc "R!&') $00N==E VNEVfJ n0v{g(֘}& h ]&1(1wOe A  'm  S 0  4z~0vd  3 ' 0:;g<I(= =>x?ZTB6E Hg KiNQlUNVWY#`cb! f i kXnWuHa}|~'џGcc PK![Content_Types].xmlN0EH-J@%ǎǢ|ș$زULTB l,3;rØJB+$G]7O٭VѠԯٴ++2a,/$nECA6٥D-ʵ? dXiJF8,nx (MKoP(\HbWϿ})zg'8yV#x'˯?oOz3?^?O?~B,z_=yǿ~xPiL$M>7Ck9I#L nꎊ)f><|HL|3.ŅzI2O.&e>Ƈ8qBۙ5toG1sD1IB? }J^wi(#SKID ݠ1eBp{8yC]$f94^c>Y[XE>#{Sq c8 >;-&~ ..R(zy s^Fvԇ$*cߓqrB3' }'g7t4Kf"߇ފAV_] 2H7Hk;hIf;ZX_Fڲe}NM;SIvưõ[H5Dt(?]oQ|fNL{d׀O&kNa4%d8?L_H-Ak1h fx-jWBxlB -6j>},khxd׺rXg([x?eޓϲكkS1'|^=aѱnRvPK! ѐ'theme/theme/_rels/themeManager.xml.relsM 0wooӺ&݈Э5 6?$Q ,.aic21h:qm@RN;d`o7gK(M&$R(.1r'JЊT8V"AȻHu}|$b{P8g/]QAsم(#L[PK-![Content_Types].xmlPK-!֧6 0_rels/.relsPK-!kytheme/theme/themeManager.xmlPK-!0ktheme/theme/theme1.xmlPK-! ѐ' theme/theme/_rels/themeManager.xml.relsPK]  g2 /yѺ  dMbP?_*+%,&ffffff?'ffffff?(?)?",333333?333333?&<3U} $ ?} i?} $ ?/;;,,,,,h@@ , , , , Z@,,,,,,,,,,,,,,,,@@ @ AB C DE FGH F IJ F IJ F IJ KLM N OP Q RS Q RS Q RS Q RS Q RS TUVW X YZ [ \] [ \] [ \^ [ \] [ \] [ \] [ \] [ \] [ \]W X YZ _`a [ bc [ bc [ bc [ deDl   ,!,",#,$,%,&,(,),*,,`-`.` [ bc !_`a "[ "bc #[ #bc $[ $bc %[ %de &[ &bc (f )f *f ,? -? .?(    A:??:The official logo of the IRSPicture 1The official logo of the IRS"ØPK!9^[Content_Types].xmlAN0EH%NY tA*T0'E2 JMN vi{ɖz$cȢ*%2鉣-uAg>퀳Ӷ/3[0ཻ:ũ5a8>Ҥ8Šr>O?aΫǮʰ!< `k.$c(0 a8Uⶶ/L], 9kM(m̐# tA y)IP_N!vex< ]ֳ؋dj-e%E8W*Y˒i 7pQg+.0At%xyRh#"E j.kueH10(d6"x4yAޥI8i%;!}S-螷i$xٸd5|ֲZ.T8TCJQw>,V+b/w)}[qPK!T'=drs/downrev.xmlDPn0W?X[@P_*jUz 6!3;3h ^ Mnڬ%Ow 0)Tc JEHݛfb|$T!lR}^Vg7hVZU ּpjO(\ 'j _j_e97X6\'k!ac6SWֱrGtV3ghlnGYz bA33LqwdBvg&lR.7PK-!9^[Content_Types].xmlPK-! 1_rels/.relsPK-!@Z H #Insert tester name and organizationO *Insert City, State and address or buildingggD g2 "Pq  dMbP?_*+%,&ffffff?'ffffff?(?)?",333333?333333?e &<3U} $ j} $ j} $ j",hnn,n,n,n,n;  n n @  @ @ @@@@ @ @,,,@ @@,@@@ @ , g hhhhhhhhhhhhi k llllllllllllm o ppppppppppppq "oppppppppppppq o ppppppppppppq o ppppppppppppq "rsssssssssssst .  uuuuuvw x yyyzww     {{{{{|}~    ww    w  % ; B! d@ D D % d@ ;B         w  ~      w   ~      w     +; PassAZM7%( D%2Bw   #  %   +; FailAZM7%F D%B"w  +; InfoAZM7%I D%B"w  * ; N/AAZ$w.w. uuuuuvw x yyyz {{{{{|}~       w  %  ; B! @ D D % @; B    &w   &w    "w  +;PassAZM 7%( D%2B"w  +;FailAZM7%F D%B"w  +;InfoAZM 7%I D%B"w  *;N/AAZ$w.wBX222&22&2j~~nt22TlTT`t ,!,. .!2PH 0(  >@Z     ; 0(   ;0(     ; 0(     ; 0(    ;0(      ; 0(   {+{ {+{{+{ {+{ {+{{+{ HSCAP Results ErrorzThe data input for SCAP Pass and Fail results must be a whole number. Enter the total count of Passed and Failed results. hSCAP Results ErrorzThe data input for SCAP Pass and Fail results must be a whole number. Enter the total count of Passed and Failed results. ggD g2 "qe  dMbP?_*+%,&ffffff?'ffffff?(?)?",333333?333333?z&<3U} $ } $ } $ ",     @@,@,@@,@,,,,   $ %%%%%%%%%%%%& ( ))))))))))))* "+,,,,,,,,,,,,- "+,,,,,,,,,,,,- "+,,,,,,,,,,,,- "+,,,,,,,,,,,,- "+,,,,,,,,,,,,- "+,,,,,,,,,,,,- " +,,,,,,,,,,,,- " .////////////0 " ##############                 12222222223 "4,,,,,,,,,5 "67777777778                               DR l222&&&&&&&&&2H<HHH&&H<H<HH<H<<< @!,     ! !! HPH0 0(   >@Z   ggD g2  C]  dMbP?_*+%,&ffffff?'ffffff?(?)?MSend To OneNote 2010 / odXXLetterDINU" ¬QSMTJSend To Microsoft OneNote 2010 DriverRESDLLUniresDLLPaperSizeLETTEROrientationPORTRAITResolutionDPI600ColorMode24bpp"dXX333333?333333?&<3U} } $ } } } } $4} +} I+} #} #} } m!} } I} }  @@@@ O @ ,  ,  ,  ,                               '             '               '                '            '            '            '     ~~PH@0(  >@P;0(  *Pass;0(  Info;0(  *Pass;0(  Info{+{{+{{+{{+{/  % ggD g2 ( &JmƑ(  dMbP?_*+%&ffffff?'ffffff?(?)?MSend To OneNote 2010 / odXXLetterDINU" ¬QSMTJSend To Microsoft OneNote 2010 DriverRESDLLUniresDLLPaperSizeLETTEROrientationPORTRAITResolutionDPI600ColorMode24bpp"dXX333333?333333?&43U} $ }  } } I } $} $$} '}  }  } I} } } } }  } } +} I+} } $ t t   W@@ @ @P @@.@@  @    @ @  @F@ @@k @@ @@           <  ! " " " " " " "              ?                    ?      R              ?      S              ?      T   V            ?      U   V   " #          ? !   $ % R      ' ( +        ? &   ) * W      - . 1        ? ,   / 0 Q  V   3 4 7      ? 2   5 6  X     9 : =     ? 8   ; <      ? A      ? >  @ B C       E F      ? D  @ G H       J K      ? I  @ L M       O P S       ? N   Q R Y     U V X       ? T   L W Z     Z [ ^       ? Y   \ ] [  V   ` a d        ? _   b c      f g j !       333333? e  @ h i      l m p        333333? k   n o \     r s v       333333? q   t u      x y |        333333? w  @ z {      ~          333333? }  @                 ?                    ?              )      ?      ]        (      ?      ^    !     '      ?      _   " #     &      ?      ` !  $     %      ?      a " % &     #      ?       #             ?333333?  @   D#l"                          !"@#$%&@'()*d@+,-./012` @3 45@6@7 @896@:;m @<@= >? $       "    @        !% ! ! ! ! ! ! !$ ! !  ! ! @ ! ! ! ! !! ! "& " " " " " " "* " "  " " @ " " " " "" " #' # # # # # # #+ # #  # # @ # # # # ## # $( $ $ $ $ $ $ $, $ $  $ $ @ $ $ $ $ $$ $ %) % % % % % % %- % %  % % @ % % % % %% % &* & & & & & & &. & &  & & @ & & & & && & '+ ' ' ' ' ' ' '/ ' '  ' ' @ ' ' ' ' '' ' (, ( ( ( ( ( ( (1 ( (  ( ( @ ( ( ( ( (( ( )- ) ) ) ) ) ) )0 ) )  ) ) @ ) ) ) ) )) ) *. * * * * * * *2 * *  * * @ * * * * * * +/ + + + + + + +3 + +  + + @ + + + + + + ,0 , , , , , , ,4 , ,  , , @ , , , , , , -1 - - - - - - -5 - -  - - @ - - - - - - .2 . . . .  .  .  .6 . .  . . @ . . . . .  . /3 / / / / / / /7 / /  / / @ /  / / / / / 04 0 0 0 0 0 0 08 0 0  0 0 @ 0 0 0 0 0 0 15 1' 1( 1 1 1 1 19 1 1  1 1 @1@ 1 1 1 11 1b 26 2 2 2 2 2 2! 2: 2 2  2 2 2 @2 @ 2 2 2 2 2 2c 37 3 3 3 3" 3# 3& 3; 3 3  3 3 @3ffffff @ 3 3 3$ 3%3 3 48 4 4 4 4' 4( 4+ 4< 4 4  4 4 @4333333 @ 4 4@ 4) 4*4 4d 59 5 5 5 5, 5- 50 5= 5 5  5 5 @5 @ 5 5 5. 5/5 5 6: 6) 6* 6 61 62 65 6 6 6  6 6 6 @6 @ 6 6 63 646 6e 7; 7 7 7 76 77 7> 7A 7 7  7 7 7 @7 @ 7 7@ 78 79 7 8< 8 8 8 8: 8; 8> 8G 8 8  8 8 @8ffffff@ 8 8@ 8< 8=8 8 9= 9 9 9 9? 9@ 9C 9? 9 9  9 9 @9333333@ 9 9@ 9A 9B9 9 :> : : : :D :E :H :@ : :  : : @:@ : :@ :F :G: : ;? ; ; ; ;I ;J ;M ;B ; ;  ; ; ; @;zG@ ; ;@ ;K ;L; ;f <@ < < < <N <O <R <C < <  < < @<(\@ < <@ <P <Q< < =A = = = =S =T =W =D = =  = = @= ףp= @ = =@ =U =V = >B > > > >X >Y >\ >E > >  > > @>Q @ > >@ >Z >[> > ?C ? ? ? ?] ?^ ?a ?F ? ?  ? ? @?333333 @ ? ?@ ?_ ?` ?D#l          @ AB CD@EF @G @H@IP @J@K L@M @N$ @O@P=@Q@R@S T&@UV@W@XY @Z;@[3@\@]@^n @_  @D @ @ @ @b @c @f @ @ @  @ @ @@HzG @ @ @ @d @e @ AV A A A Ah Ai Al AJ A A  A A ffffff@ Ag A A Aj Ak A BE B B B Bn Bo Br BI B B  B B ffffff@ Bm B B Bp Bq B CF C+ C, C Ct Cu Cx CH C C  C C @ Cs C C Cv CwC C DW D+ D, D Dz D{ D~ DK D D  D D @ Dy D D D| D}D Dg EG E+ E, E E E E EL E E  E E @ E E E E EE Eh FH F F F F F F FM F F  F F @ F F F F F F GI G G G G G G GN G G  G G @ G G G G G G HJ H H H H H H HO H H  H H @ H H H H H H IK I I I I I I IP I I  I I 333333@ I I I@ I II I JL J J J J J J J J J  J J  J J J@ J JJ Ji KX K K K K K K K K K  K K  K K K@ K KK Kj LM L L L L L L L L L  L L @ L L L@ L LL Lk MY M M M M M M M M M  M M @ M M M@ M M M NN N N N N N N N N N  N N N @ N N N@ N N N OO O O O O O O O O O  O O @ O O O O O O PP P P P P P P P P P  P P P @ P P P@ P P P QQ Q Q Q Q Q Q Q Q Q  Q Q @ Q Q Q Q Q Q RR R R R R R R R R R  R R ffffff@ R R R@ R RR Rl SS S S S S S S S S S  S S ffffff@ S S S@ S SS Sm TT T T T T T T T T T  T T ffffff@ T T T@ T TT Tn UU U U U U U U U U U  U U ffffff@ U U U@ U UU Uo VV V V V V V V V V V  V V @V@ V V V VV V WW W W W W W W W W W  W W @W333333@ W W@ W W W XX X- X. X X X X X X X  X X ffffff@ X X X X XX X YY Y- Y. Y Y Y Y Y Y Y  Y Y ffffff@ Y Y Y Y YY Y ZZ Z- Z. Z Z Z Z Z Z Z  Z Z ffffff@ Z Z Z@ Z Z Z [[ [ [ [ [ [ [ [ [ [  [ [ ffffff@ [ [ [ [ [[ [p \\ \- \. \ \ \ \  \ \ \  \ \ \ ffffff@ \ \ \ \ \ \ \q ]] ] ] ] ]  ]  ] ] ] ]  ] ] ffffff@ ]  ] ]@ ] ]] ] ^^ ^ ^/ ^ ^ ^ ^ ^ ^ ^  ^ ^ @^333333@ ^ ^@ ^ ^ ^ __ _ _ _ _ _ _ _ _ _  _ _ ffffff@ _ _ _ _ __ _DZ#l               `@a @b @c @d e1 @f @g hE@i@jr@k l mn@oa@p@q@r@st @u@vw @xyzx@{R@|} @~@@ `` ` ` ` ` ` `! ` ` `  ` ` ffffff@ ` ` ` ` ` ` ` aa a a0 a a# a$ a' a a a  a a ffffff@ a" a a a% a&a ar bb b b0 b b) b* b- b b b  b b ffffff@ b( b b b+ b,b bs cc c c0 c c/ c0 c3 c c c  c c ffffff@ c. c c c1 c2c ct dd d d0 d d5 d6 d8 d d d  d d ffffff@ d4 d d d1 d7d du ee e e e e: e; e= e e e  e e ffffff@ e9 e e e1 e<e ev ff f f f f? f@ fB f f f  f f ffffff@ f> f f f1 fAf fw gg g g g gD gE gG g g g  g g ffffff@ gC g g g1 gFg gs hh h h h hI h hK h h h  h h ffffff@ hH h h hJ h h ii i i i iM iN iQ i i i  i i i ffffff@ iL i i iO iP i jj j j j jS jT jW j j j = j j @ jR j j jU jVj j kk kV k k kY kZ k] k k k > k k @ kX k k k[ k\ k ll l l l l_ l` lc l l l ? l l @ l^ l l la lb l mm m m m me mf mi m m m @ m m @ md m m mg mh m nn n n n n nk n n n n A n n n @ nj n n n n n oo o o o om on oq o o o B o o @ ol o o oo op o pp p p p ps pt pw p p p C p p @ pr p p pu pv p qq q+ q3 q qy qz q} q q q D q q @ qx q q q{ q|q qx rr r+ r3 r r r r r r r  r r @ r~ r r r rr ry ss s s s s s s s s s E s s @ s s s s ss sz tt t1 t2 t t t t t t t F t t @ t t t t tt t{ uu u u4 u u u uJ u u u G u u u @ u u u uH uIu u| vv v v v v v v v v v K v v @ v v v v v v ww w5 w6 w w w w w w w L w w w @ w w w w ww w} xx x x7 x x x x x x x M x x 333333@ x x x x xx x~ yy y y7 y y y y y y y N y y y 333333@ y y y y yy y zz z8 z9 z z z z z z z U z z z 333333@ z z z@ z zz z {{ { {7 { { { { { { { T { { { 333333@ { { { { {{ { || |V | | | | | | | | O | | | @|@ | |@ | || | }} } }0 } } } } } } } P } } @}@ } } } }} } ~~ ~ ~: ~ ~ ~ ~ ~ ~ ~ S ~ ~ ~ ffffff@ ~ ~ ~ ~ ~ ~   7        R    ffffff@      D#l                 U@@@F@ @[@      ; :       Q   ffffff@         :       k  @@        :       j  @333333@               l  @@        :   n    o   @@    m   5 6       L   @333333 @       5 6       ~  @ffffff @       5 6       p   @ @  @      0       q  333333"@       Z  0       r  333333"@         0       s  333333"@         0       t  333333"@         0       u  333333"@         0       v  333333"@         0        w  333333"@          0        x  333333"@                  y  333333"@   @      :       z  333333"@         :       {  333333"@              #   |   333333"@   @ ! "      % & )   }   333333"@ $  @ ' (    :  + , /   i  ffffff"@ *   - .    :  1 2 5   h  ffffff"@ 0   3 4    :  7 2 8   g  ffffff"@ 6   3 4    :  : 2 ;   f  ffffff"@ 9   3 4    :  = > A   e  ffffff"@ <   ? @    :  C D G      ffffff"@ B   E F    0  I J M     ffffff"@ H   K L      O P S      ffffff"@ N   Q R      U V Y   [  ffffff"@ T   W X      [ \ _   d  ffffff"@ Z   ] ^      a b e   c  ffffff"@ `   c d D#l             @k @       :  g h k   b  ffffff"@ f   i j    :  m n q   a  ffffff"@ l   o p    0  s t w   `  ffffff"@ r   u v    :  y z }   _  ffffff"@ x   { |    :       ]  ffffff"@ ~        :       ^  ffffff"@                [  ffffff"@                \  ffffff"@          2  P -h(  R  C ]F! d ZR  C ]F! d ZR  C ]F! d ZR  C ]F! d ZR  C ]F! d ZR  C ]F! d ZR  C ]F! d ZR  C ]F! d ZR   C  ]F ! d ZR   C  ]F ! d ZR   C  ]F ! d ZR   C  ]F ! d >@PA     ; d  *Pass; d  Info{+{ {+{ /  % ggD@ g2    dMbP?_*+%,&ffffff?'ffffff?(?)?",333333?333333?&<3U} $ j} $ j} mT} mj} $ j ,n,,,,,,, , , , , g hh    ? }@  ? ~ ^@     82" PH`0(  >@Z ggD g2 %  dMbP?_*+%,&ffffff?'ffffff?(?)?",333333?333333?&<3U} } I} $} } m} }  $ } $ } $ %,,,,,@ @ @ , ,@@@,,,,@@@,,; g@:@, g hhhhhhhhhhhhi     o ppppppppppppq o ppppppppppppq o  ppppppppppppq "rsssssssssssst       o ppppppppppppq r sssssssssssst       o ppppppppppppq o ppppppppppppq o ppppppppppppq "rsssssssssssst       o ppppppppppppq "rsssssssssssst <====>       9 : @:@:@ ;9 :::;>0222222&22222222222&2222&"TF W!W"W#W$f $ @@+@@@X@ !$!@{@@@ @ "$"@@(@X@ @ r@ #~ #@ # ##@@ $~ $i@ $ $$ 4@@P666NPHp0(  >@P2yK  yK http://en.wikipedia.org/wiki/Red_Hat_Enterprise_LinuxyX;H,]ą'c cite_note-28 yK  yK http://en.wikipedia.org/wiki/Red_Hat_Enterprise_LinuxyX;H,]ą'c cite_note-29$$yK  yK http://en.wikipedia.org/wiki/Red_Hat_Enterprise_LinuxyX;H,]ą'c cite_note-30ggD Oh+'0@Hh Masood, Taimur [USA]Christa BatorMicrosoft Macintosh Excel@$@͘]՜.+,D՜.+,XHP X`hp x   DashboardResults InstructionsGen Test CasesRHEL6 Test Cases Change Log Appendix  Worksheetst 8@ _PID_HLINKSA,5?6http://en.wikipedia.org/wiki/Red_Hat_Enterprise_Linux cite_note-30466http://en.wikipedia.org/wiki/Red_Hat_Enterprise_Linux cite_note-29476http://en.wikipedia.org/wiki/Red_Hat_Enterprise_Linux cite_note-28  !"#$%&'()*+,-./0123456789:;<=>?@ABCDEFGHIJKLMNOPQRSTUVWXYZ[\]^_`abcdefghijklmnopqrstuvwxyz{|}~      !"#$%&'()*+,-./0123456789:;<=>?@ABCDEFGHIJKLMNOPQRSTUVWXYZ[\]^_`abcdefghijklmnopqrstuvwxyz{|}~      !"#$%&'()*+,-./0123456789:;<=>?@ABCDEFGHIJKLMNOPQRSTUVWXYZ[\]^_`abcdefghijklmnpqrstuvxyz{|}~Root Entry FWorkbookSSummaryInformation(oDocumentSummaryInformation8w