Newsletters Welcome, Guest Log In | Register

Join the Community

Exchange

Get full access to our community's expertise and resources.

Register Now >

Identifying Security Threats

19 Replies Last post: Nov 14, 2009 10:27 AM by MikeBailey   1 2 Previous Next
Ralph DeFrangesco   54 posts since
Oct 3, 2008
Reply

Dec 16, 2009 1:32 PM

Identifying Security Threats

"Is it worth going through the exercise to identify every threat in an organization? Why or why not?"

JeffGoldman   10 posts since
Nov 3, 2009
1. Nov 10, 2009 9:13 PM in response to: Ralph DeFrangesco
Re: Identifying Security Threats

When assessing risk there is an unlimited amount of possible threats that could jeopardize a successful initiative or mission. It is worth compiling an extensive list, within reason, to identify all possible threats. This does not mean you should mention ridiculous ideas like key personnel being abducted my aliens, but it may be worth mentioning a key individual quiting or disappearing if that is what is deemed critical to the mission. This process will be handled in cooperation with business and resource owners, and by engaging others as to what their concerns are and looking at all possibilities a threat specific to a business may have otherwise been overlooked.

 

Different threats and requirements may need to be identified that are related to environmental factores or specific business processes and by creating an extensive list solutions can be addressed. The result is really twofold: On one hand, by identifying all risks you can confidently select those risks that need to be addressed individually from those that can be dealt with together from those that can be excluded all together. Those grouped together will fall somewhere in the High, Medium, Low categories where they can be considered and addressed methodically; and on the other hand, at the very least, identifying all the threats demonstrates due diligence on behalf of the business.

 

Identifying threats can be a lengthy task depending on the client or requirements and determining which are pertinent may be an arduous task, but even though many will fall below the line of concern and not targeted directly, many will automatically fall within the boundaries of the business's overall continuity plan.

WarrickStJean   28 posts since
May 11, 2009
2. Nov 10, 2009 10:27 PM in response to: Ralph DeFrangesco
Re: Identifying Security Threats

The question being posed is both utilitarian and philosophical. From a philosophical perspective the answer is NO, simply because organizations "don't know what they don't know" and thus only known threats could ever be considered. From a utilitarian perspective the answer is also a resounding NO, because it is simply not economically feasible to attempt to quantify ALL risks. The excercise becomes exponentially more complex and expensive as more and more factors are considered.

 

Businesses are in the business of taking calculated risks in order to make prudent/informed decisions that materialize as profits. Businesses leaders are faced with the challenge of  perpetual decision making and ultimate responsibility for outcomes both known and unknown. All efforts to quantify threats/risk serve only the purpose of reducing the potential for lo$$ and are not conducted for the purpose of achieving mathematical precision.

 

One of the key challenges facing leaders is the prioritization of tasks & resources, this is difficult to do without having a complete list. At best any single excercise to identify and perform threat/risk analysis is a point-in-time snapshot. Since resources are limited analysis should be performed only up to the break even point, beyond which exists the point of diminishing returns. This is the point at which further analysis will yield information of diminishng value and ultimately lead to the escalation of opportunity costs. In order for business organizations to obtain maximum value from any  threat/risk analysis a clear scope must be outlined along with reasonable parameters.

 

Businesses, industries, technology, processes and practices are constantly evolving. As organizations adapt to keep pace with clients, competitors and regulations so do the threats and risks. The organization will derive greater value from generating a clear focused list of well defined and relevant threats assessed and weighed over time. Ultimately, just like with physical excercise threat/risk analysis is a process NOT an event!

JeffGoldman   10 posts since
Nov 3, 2009
3. Nov 11, 2009 8:29 AM in response to: WarrickStJean
Re: Identifying Security Threats

Mr. StJean, once again I am impressed at your selection of words and aptitude for the subject; however, the question posed was should we "identify" all risks not necessarily "quantify". If I misunderstood then please forgive my banter.

 

You are correct, businesses are challenged with identifying and calculating risk, but I am speaking from the view that this is the first assessment being performed and the list of threats are being established for the first time, along with the obvious threats being templated and submitted by the Risk Assessment professional (me).

 

Not being privy to an environment's particular processes and/or business would lead me to be required to interview those that are familiar. Their concerns, once listed, can then be included or excluded. Again, I reiterate, this is to all be performed within reason. The possibilty of a Tsunami happening in Nebraska should not even be considered. This, to me, does not entail quantifying risk on every possible threat for it would be a complete waste of time and not be required in this scenerio, but the result will be a focused outline of pertinent threats that can be recycled for the next assessment, even though the next assessment should be given the same critical evaluation so not to overlook a specific risk.

 

Either way, I see where you are coming from and agree with you on many points.

Dawit   8 posts since
Nov 5, 2009
4. Nov 11, 2009 9:44 PM in response to: Ralph DeFrangesco
Re: Identifying Security Threats

Identifying risk as early stage will be benefit for the all lover cost effectiveness and successfulness of the risk management. Identifying risk also helps to determine the boundaries in which the risk assessment will be done or particularly concerned on.

If we don’t carefully identify the risk at beginning of the risk assessment result that we have later don’t have complete set of documentation due diligence of the organization. More over risks that we identify on the process might not be as bad as risk we thought and the risk we left out without notice might jeopardize the entire accomplishment of the project .Finally the whole point of identifying the risk is to be cost effective on our risk management project .

Dawit   8 posts since
Nov 5, 2009
5. Nov 11, 2009 9:55 PM in response to: WarrickStJean
Re: Identifying Security Threats

i realy like what you wrote and once again you selection words (jeff is right)

but i was wondering the Q was pose on why.but to get back on your points

you are 100 % right what the organztion "dont know why thye dont know"

what we come in to play and identifying the all the existing  threats  by perfoming some process or function.becuase the business owner could know all  the threats,to be exact on my point every level of the organztion can help us to identifying the threats that exist within the organztion;that might the senior dont even know it's exist so i will say its good to take time and use the available tools to identify all risks before jumping to cost and controls

John.Kimmel   8 posts since
Nov 5, 2009
6. Nov 12, 2009 12:57 PM in response to: Ralph DeFrangesco
Re: Identifying Security Threats

  Risk Assessment is defined as analyzing all risk pertaining to the company. When analyzing risk we can go to one of two extremes. Another more practical solution is to analyze the validity of the risk and determine if it should be reported on.

 

One extreme would be to analyzing every risk. We could document and attempt to mitigate all risks. These would include not only risks with potential, but those with little probability of occurring. An example of such risk would be a typhoon in Kansas. While anything is possible, this has little to no chance of occurring. With this method we risk inundating the reader with information which may not need to be addressed and mitigated.

 

The other extreme would be to only categorize those risks that only have a high probability of occurring. This may seem like a good idea because we leave the reader with only risk that needs to be addressed and how to mitigate the threat. However, leaving such pertinent information out may make our superiors think we were lax in our risk assessment and lead to lawsuit for lack of due diligence.

 

A balance between the two would the best way to report risk. Discretion needs to be used when deciding what to report. We should list all risks and rank their probability of occurring. With this list we can choose a cut off line, then report and attempt to mitigate only those risks we deem worthy. The risks we choose not to report on can be listed in a separate section with their listed probability. The person constructing the risk analysis needs to judge what risk is probable and ensure that risk is brought to the attention of management.

 

We can see the danger of being too far in one direction or the other. As in the case of most issues, a balance between the two is the best solution. It provides the reader only with pertinent information, but also demonstrates due diligence, because we listed all risks in a separate section with probability.

MaribelLeon   8 posts since
Nov 4, 2009
7. Nov 12, 2009 5:09 PM in response to: Ralph DeFrangesco
Re: Identifying Security Threats

Yes, during risk assessment it is important to identify every threat to an organization, regardless of the likehood of it happening or not. Any circumstance or event that can harm a company asset or business objective should be examined. Most importantly, the source of the threat must be examined before it is dismissed to determine if it presents a risk to the organization. Circumstances where the possibility of human threats exist, whether deliberate or unintentional, should be thoroughly investigated and identified. Subsequently, during the risk level process, threats that have little or no possibility of occuring can be eliminated.

Royce"The-Go-to-Guy"Richards   9 posts since
Nov 5, 2009
8. Nov 12, 2009 5:10 PM in response to: Ralph DeFrangesco
Re: Identifying Security Threats

It is important to go through the exercise of attempting to identify every reasonable risk that may affect an organization.   Given that risk assessments are subjective by nature, it is impossible to identify “EVERY” threat.  Also, whether or not something is truly a threat is up for interpretation by the parties involved. 

One could theoretically come up with an infinite number of threats, but most organizations can’t afford to waste time thinking up an endless list of “what if’s”.  Instead, it makes sense for stake holders and other members involved in the assessment process to do their due diligence and generate an exhaustive list of possible threats that not only may have a real impact on the organization, but a list of threats that could be realized in the foreseeable future based on historical events or prophetic insight.

MaribelLeon   8 posts since
Nov 4, 2009
9. Nov 12, 2009 5:24 PM in response to: Dawit
Re: Identifying Security Threats

Dawit, I completely agree with you. If all threats are not considered, then due diligence fails and the process cannot be documented accurately or properly. It is best to consider all possible scenarios and then weed out those that have no likehood of occurring. And as you said it is most cost effective than realizing it after the fact, when the process would have to be revisited and the wheel would have to be reinvented. It's also important to remember that the scope statement may include assumptions that a risk assessment has been performed on the supporting infrastructure and the proper controls have been implemented.

Royce"The-Go-to-Guy"Richards   9 posts since
Nov 5, 2009
10. Nov 12, 2009 5:31 PM in response to: MaribelLeon
Re: Identifying Security Threats

You made a great point when you said, “Circumstances where the possibility of human threats exist, whether deliberate or unintentional, should be thoroughly investigated and identified.”  I don’t think some people realize how big a threat the people in the organization really are.

Maybe hasty decision making and selfish acts should be on the list of threats to identify.  Failing to invest the necessary amount of time and money into a complete and thorough risk assessment might be another risk to consider.  The human factor in my humble opinion probably generates the largest window of risk possibilities that could have a real and regular impact on the company’s public image and bottom line.  Someone has probably already written a book on the pitfalls of having humans manage an organization.  Don’t get me wrong though.  The human factor isn’t all bad… is it?

Millie   8 posts since
Nov 3, 2009
11. Nov 12, 2009 7:27 PM in response to: Ralph DeFrangesco
Re: Identifying Security Threats

The rewards for identifying threats in an organization are worth the time and efforts.  The success of a business depends on everyone’s cooperation and input.  Observation and patience are attributes that can be valuable to any business because natural, human and environmental threats are carefully being considered prior to incidents occurring.  The process of identifying threats allows individuals to express various points of views and a since of team effort which is recognizable.

WarrickStJean   28 posts since
May 11, 2009
12. Nov 12, 2009 7:34 PM in response to: JeffGoldman
Re: Identifying Security Threats

Jeff,

      I believe that our points of view reflect more similarities than differences. For example I agree that "...This does not mean you should mention ridiculous ideas like key personnel being abducted my aliens".

 

       From my perspective, there would be little business value in spending an inordinate amount of time listing risks only to end up complicating the process of prioritizing and quantifying. The process of determining value cannot be considered in a vacuum. I choose to focus on the feasibility of compiling a "complete" list and determining the value that such a list would bring to the process. In thinking through the overall risk assessment project one phase affects the other.I believe that although risk identification and risk quantification can be mutually exclusive, one is a pre-requisite to the other. In order to prioritize and choose which risks to consider a fairly comprehensive list of relevant threats must be compiled. Fairly comprehensive is a long way from "complete", and the key word would be "relevant".

 

     Risks and Threats are circumstantial and relational the eventual list could be exponentially large due to permutations and combinations applied in "what if" scenarios. In order to avoid having to hire or retain an actuary, businesses should keep it simple. I honestly do not believe that a truly complete list can ever be compiled so I arrived at the conclusion that it was best to narrow the focus to the most obvious and relevant threats in order to cover as much ground as possible.

JeffGoldman   10 posts since
Nov 3, 2009
13. Nov 12, 2009 7:42 PM in response to: WarrickStJean
Re: Identifying Security Threats

Sounds good.

Millie   8 posts since
Nov 3, 2009
14. Nov 12, 2009 8:07 PM in response to: Dawit
Re: Identifying Security Threats

The idea of being cost effective is definitely a major reason for identifying threats.  The assets of any business should be protected in order to accomplish the expected goals and tasks.  For this reason it is important to take the time to identify threats to avoid unnessary spending.

Identifying Security Threats

Go to original post 1 2 Previous Next

The IT Service Catalog Management Toolkit

Bridge the IT-business gap once and for all! A well documented IT services catalog is the conduit for IT services to the rest of the company.

Learn more >

Janco's 2010 IT Salary Survey

This survey from Janco Associates, Inc., draws on data collected by extensive surveys of businesses throughout the United States and Canada.

Learn more >

Application Server Choices: Important Considerations in Selecting an Application Server

This white paper examines the role of the application server, reviews some of the more notable offerings available, and suggests which criteria and considerations are most important in the selection process.

Preventing Data Corruption in the Event of an Extended Power Outage

This white paper discusses various power management software configurations, and presents best practices aimed at ensuring system uptime.