Image
 
linkedin_logo.png rss_logo.jpg
twitter_logo.png youtube_logo.jpg
Latest Additions
 
EH-Net Login
Welcome Guest.






Lost Password?
No account yet? Register
Who's Online
We have 23 guests online
 
Advertisement

You are here: Home arrow Ethical Hacking Discussions and Related Certificationsarrow Otherarrow Patch Management
EH-Net
May 23, 2013, 08:17:14 AM *
Welcome, Guest. Please login or register.
Did you miss your activation email?

Login with username, password and session length
News: Go back to The Ethical Hacker Network Online Magazine Home Page
 
   Home   Help Calendar Login Register  
Pages: [1]   Go Down
  Print  
Author Topic: Patch Management  (Read 6019 times)
0 Members and 1 Guest are viewing this topic.
Agoonie
Full Member
***
Offline Offline

Posts: 176



View Profile WWW
« on: January 14, 2010, 11:29:58 AM »

Hello All,

If you guys don't mind, I was wondering if people could share there advice and their experience on patch management.  How often they patch their systems, every day, week, quarter, etc?  What tools they use and their experiences with those tools?  Whether they concentrate on critical patches instead installing all patches?

Thanks in advance.
Logged

OSCE, OSCP, OSWP, CISSP, GPEN

www.agoonie.com
kennut
Newbie
*
Offline Offline

Posts: 46


CISA, C|EH, CISM


View Profile
« Reply #1 on: January 15, 2010, 03:28:38 AM »

hello,

normally we suggest them to test the patches first before applying them. It would be good if they are tested in a test server (if they have spare servers).

In addition, critical patches should be checked with the vendor first (assuming you have some applications running above the O/S, therefore, it's good to ask them before applying, otherwise, you may have problems like blue screen or some services not running etc. (Bear in mind, all IT Dept will not do the patch because they'll say, if it's not broken, why fix it, (meaning, they're scared if things goes down, so give them OT to work on the recovery.....), however, the should get the approval or rationale for patching/not patching the updates etc.

Also document the patches before/after, so you got a trail on that. and of course all patches should be approved by the management.

Thanks.
Logged

Done all 3 certs, now going for CISSP.....
unsupported
Sr. Member
****
Offline Offline

Posts: 318


Unofficial Newbie Moderator


View Profile
« Reply #2 on: January 15, 2010, 05:53:20 AM »

A certain company I may or may not be familiar with, has used various patch management tools, from rolling our own, Bladelogic, Patchlink, and SMS for OS and common applications  Before any system is deployed, there is a risk assessment done on it, part of which involves a miniumum level of patching.

We patch the week following M$ Patch Tuesday.  I believe other applications are caught in our defense in depth strategy of vulnerability scanning.  If there is a known high or medium level vulnerability with an associated patch, then it is applied.  (Unless it is a business critical application and nobody wants to take the blame for something going wrong)

It helps that there are corporate policies in place which outline that patch management must be performed on a regular basis, it's up to the individual areas to figure it out for themselves.
Logged

-Un
CISSP, GCIH, GCIA, C|EH, Sec+, Net+, MCP
dalepearson
Sr. Member
****
Offline Offline

Posts: 357


View Profile WWW
« Reply #3 on: January 21, 2010, 09:43:30 AM »

In my opinion this really depends on the environment you are working in, the type of business you conduct and the methods used.
If you can share some more information, perhaps in a generic way, you can get some more targeted responses.

Ultimately its going to come down to the risk appetite of the business, how the organisation is structured, segmentation of the infrastructure, testing capabilities and budget.

Patch management is still something that so many organisations fail to do well, but at the same time it can be very simple.

Look forward to hearing more from you.
Logged

Agoonie
Full Member
***
Offline Offline

Posts: 176



View Profile WWW
« Reply #4 on: January 22, 2010, 07:47:18 AM »

Thank you everyone for the replies.  I agree that patch management depends on the policies of the organization. I thought it was a good question to ask the community since it is such an important procedure for an organization with a security conscience. I know companies have different ways and applications of accomplishing it.  I have seen SMS, shavlik, WSUS, Altiris, BigFix, etc. I was wondering if anyone was partial to one of them and why? 

Also, I have seen people argue how often it should be done due to the testing required to install patches. Personally, I think once testing is done, you can install all tested patches.  You never know if a low priority patch can be used for a higher vulnerability. 

That is why I just wanted to see how other security minded people handled the task. Also, I think VMware is perfect for patch management because of snapshot.  It is faster than using Ghost or Clonezilla.

Again, I want to say thanks for the comments.
Logged

OSCE, OSCP, OSWP, CISSP, GPEN

www.agoonie.com
dalepearson
Sr. Member
****
Offline Offline

Posts: 357


View Profile WWW
« Reply #5 on: January 26, 2010, 08:19:44 AM »

Personally I think WSUS is a good solution if your a Windows shop, however what ever works for the organisation is a good way to proceed.
I agree a VM environment can provide an excellent platform for multiple testing, rollbacks, etc a breeze, however I have seen on the odd occasion hardware issues with patching, so there is sometimes value in hardware based testing, especially if you have adopted standard hardware and this isnt a huge amount of devices.

Security Patching is important, however many organisations still do not treat it with the attention it deserves. Keeps us in a job though Smiley
Logged

Pages: [1]   Go Up
  Print  
 
Jump to:  

Powered by MySQL Powered by PHP Powered by SMF 1.1.18 | SMF © 2013, Simple Machines
Joomla Bridge by JoomlaHacks.com
Valid XHTML 1.0! Valid CSS!
Page created in 0.06 seconds with 22 queries.
 
Exclusive Deal

sansfire13_245x90_cw90.jpg
SANSFIRE 2013
June 15 - 22

5% Off w/ Code: EHN_5

SANS Deals 4 EH-Netters
5% OFF Any SANS Course in Any Format!
Coupon Code: EHN_5 Including SANS Rocky Mountain 2013 & SANS Boston 2013
Polls
Compared to this year, 2013 will be:
 
Recent Forum Topics
EH-Net News Feeds
Latest Additions
 
         
Advertisement

© 2013 The Ethical Hacker Network
Joomla! is Free Software released under the GNU/GPL License.