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 49 guests online
 
Advertisement

You are here: Home arrow Ethical Hacking Discussions and Related Certificationsarrow Otherarrow Security Risk Management Program
EH-Net
May 24, 2013, 08:05:06 PM *
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: Security Risk Management Program  (Read 2758 times)
0 Members and 1 Guest are viewing this topic.
T_Bone
Full Member
***
Offline Offline

Posts: 199


View Profile
« on: June 20, 2010, 11:14:59 AM »

The aim of a security risk management program is to "Reduce the number of vulnerabilities and reduce the severity of the bugs you miss."

SDL is good but that’s only for new projects that are being developed, how about the hundreds of implemented systems and applications already in production. Is penetration testing every system every year the best way to do this?

What do you think the best approach to "Reduce the number of vulnerabilities and reduce the severity of the bugs you miss."
Logged
vekarman
Newbie
*
Offline Offline

Posts: 28



View Profile
« Reply #1 on: June 21, 2010, 09:24:34 AM »

Security Risk Management Program is lengthy and time consuming when you are doing it for the first time. Later on, based on Risk Analysis, you must have various controls in place. So, later on, you have to just monitor performance and activity will be marginal and less time consuming.

Penetration testing is more relevant with technology, where as Risk Management covers all 3, people, process and technology. For technology part, to ensure that nothing has bypassed the technical security controls, penetration testing is the best option which is generally conducted bi-annually.
Logged

CISSP
sil
Hero Member
*****
Offline Offline

Posts: 549



View Profile WWW
« Reply #2 on: June 21, 2010, 01:26:52 PM »

The response to this would be enough to write a book, in fact many books have already been written on this subject... If you're focused on performing a penetration test to immediately assess your risk you will fail. Your first focus when it comes to this type of "risk assessment" is to determine what your risks are. After you've concluded what those risks are, you begin at the 50k foot view and determine the weights of those risks. After all the paper pushing and math is done, then you'd perform a penetration test where it's needed.

Imagine for a moment you have 3 networks (/24's). One is production, one is devel and one is internal. What is your first priority here? Obviously the forward facing network (production) is most important. Allocate your priorities. The risk of having a vulnerable version of IIS on an internal server is far lower than having it on the outside.

You calculate your risks based on your business objectives. What do you need to do, how do you need to do it, what's defensible, what comes secondhand. Performing a full blown penetration test in my example network would be overkill. I'd perform a focused technical (non social engineering) test on my external network and go from there. Using something like GFI + OSSIM on the internal and development network would give me great results I could act on. Lowering the costs (time) to perform a full blown test. With the monies save, I could use it where its needed.

If I had to reduce vulnerabilities, my first goal would be my entrypoint. I'd focus most of my resources there and use compensating controls (GFI + OSSIM maybe even metasploit (using autopwn)) internally. However, focusing my resources means focusing on the systems that matter. (Bread and butter)
Logged

T_Bone
Full Member
***
Offline Offline

Posts: 199


View Profile
« Reply #3 on: June 22, 2010, 01:46:49 AM »

This question is very BROAD in a sense because realistically there are a lot of elements that need to be covered within a risk management program as verkarman says (people, process and technology). I guess as a company you have to determine what is your priority, is it likely that a more technical company will have a bigger insider threat due to knowledge and curiosity as opposed to a company of recruitment consultants? This is one that i think considers serious thought!

Just to give you an insight i am an entry level penetration tester with only a few months experience and is something i have thought about.....
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.073 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.