Skip to content

CyberSecurity Institute

Security News Curated from across the world

Menu
Menu

Category: DR/Crisis Response/Crisis Management

So, what is a crisis or incident team? (Part 2 in the Crisis Team Series)

Posted on November 5, 2010December 30, 2021 by admini

Paul’s definition of a crisis response team (if we have to keep calling it that (to justify the budget)) is:

An operational capability that allows an organization to quickly initiate, track and coordinate the capabilities of multiple groups and individuals, with the single focused goal of solving an immediate business impacting event, quickly and effectively.

Business Impacting Event? Sometimes, we fail to leverage the abilities of an incident Response capability due to the fact that we view them as only useful during an IT security incident. They can be, and should be leveraged beyond that myopic vision of the role.

[Sidebar: This “pigeon holing” of security is a common problem that I have encountered in my career as a security professional. Security team can easily become isolated and out of touch of, due to the fact that the teams act as superior or independent of the rest of the organization. Misunderstanding, mistrust, “snobbishness” and general lack of communication are typical symptoms that I have encountered when called upon to fix, from everyone else’s perspective, a dysfunctional security team. Security is not a standalone capability, especially in today’s world, and needs to be integrated into the rest of the organizations.]

To create this change, we have to start at the individual level. To help create the capability, and to break down the barriers of stagnant traditional security models, I believe that a security professional needs to have a broader view of the world, encompassing not the only viruses, vulnerabilities, and hackers but also business impacting events or perspectives.

By adopting this approach, crisis response teams can provide valuable services across an organization. Crisis response teams should not be only be involved in an IT incident but they can help in situations dealing with the handling of a sensitive business events or geo-political situations. A good incident response team has the maturity and capabilities to handling these delicate situations with the aplomb required to bring about an effective resolution.

So what does the crisis response team do? To be successful in responding to these situations, requires the coordination and cooperation of multiple teams and individuals. And that is what drives how I define an incident and thats what a crisis team should be focused on as one of its primary objectives. it is driving forward to resolution with a fast ,multi-team coordinated response.

It is the last part of the sentence that really resonates with me. I almost want to change the name from crisis response to coordinated group adverse business event response team (but GABERT is a bit too long as an acronym).

I have had great success in supporting small and large organizations in many crisis situations where the capabilities and preparedness of the crisis response team have been leveraged.

So change the perceptions. It helps if people don’t view the IR team as a set of strange talking geeks, who only like IT and hacking. I can tell you that the majority of the IT security industry is very gregarious, and we don’t hide out in hidden cubicle with no light, despite how Hollywood might like to portray. Some of us even have sun tans.

So what do you think? Is this too ambitious, or outside the scope of IT security? Or could this approach add value to your organization and help expand the understanding and integration of the security team?

In the next article, we will talk about the principles goals and requirements around the culture of a crisis response team.

Read more

A new series of blog posts on Crisis Response

Posted on November 2, 2010December 30, 2021 by admini

I have been through a quite few crisis with large and small organizations and I hope that these posts will help IT teams protect their people, the world and the businesses.

Why would I write a set of blog entries about crisis response? Well to be honest, I am hoping that I can generate business opportunities, and also create a online resource of information about this very important capability. I have searched across the web and found very few sites dedicated to this subject. Yes, you can find information on disaster response but I think organizations are facing few disasters (hopefully), but probably everyone has a couple of crises a year.

So let’s start. For me, crisis response is an operational capability that needs to exercised frequently, as opposed to once a year. It goes beyond the traditional world of viruses and hack attacks. It’s something that can be leveraged to help an IT organization with it’s daily activities, not just when things are going wrong.

Hopefully, you will find this information useful.

And if you want to provide feedback, I have a forums section just for crisis response. No person is an island and it is only through sharing of knowledge and experience, that we evolve.

Now, I have become a bit of a pain when it comes to posting. I need you register and I promise not to share your email with anyone else. I will also sometimes check to see whether the person registering is really a professional. And I won’t use the email for any marketing or profiteering. If you want to talk business with me, contact me.

Thanks Paul

Read more

BIS: We Have Failed to Learn From the Nordic Crisis

Posted on August 6, 2010December 30, 2021 by admini

In the current episode, the down-leg of the financial cycle had not proceeded as far and banks were further away from the point of technical insolvency.
However, the underlying weakness in balance sheets has not been recognised as fully. All this has tended to slow down resolution. In other words, the zombie banks live on just as they have in Japan.

Principle 1: Early recognition and intervention
The nature and size of the problems should be recognised early and intervention should follow quickly. The purpose of early recognition and intervention is to avoid a hidden deterioration in conditions that could magnify the costs of the eventual resolution. A key reason why costs tend to increase as action is delayed is that economic agents operate under distorted incentives.

Principle 2: Comprehensive and in-depth intervention
Intervention and resolution should be broad-ranging and in-depth. The overriding objective is to restore lasting confidence in the financial system and its capacity to operate effectively and sustainably, without public support. Intervention includes three critical steps: (i) stabilising the financial system; (ii) restructuring balance sheets; and (iii) re-establishing the conditions for the sector’s long-term profitability.

Principle 3: Balancing systemic costs with moral hazard P3: Intervention should strike a balance between limiting the adverse impact on the real economy and containing moral hazard.

http://seekingalpha.com/article/219124-bis-we-have-failed-to-learn-from-the-nordic-crisis

Read more

Disaster Planning Is Critical, but Pick a Reasonable Disaster

Posted on July 27, 2007December 30, 2021 by admini

Disaster planning is critically important for individuals, families, organizations large and small, and governments.

For the individual, it can be as simple as spending a few minutes thinking about how he or she would respond to a disaster. For example, I’ve spent a lot of time thinking about what I would do if I lost the use of my computer, whether by equipment failure, theft or government seizure. As I a result, I have a pretty complex backup and encryption system, ensuring that 1) I’d still have access to my data, and 2) no one else would. On the other hand, I haven’t given any serious thought to family disaster planning, although others have.

For an organization, disaster planning can be much more complex. What would it do in the case of fire, flood, earthquake and so on? The resultant disaster plan might include backup data centers, temporary staffing contracts, planned degradation of services and a host of other products and service — and consultants to tell you how to use it all.

And anyone who does this kind of thing knows that planning isn’t enough: Testing your disaster plan is critical. Far too often the backup software fails when it has to do an actual restore, or the diesel-powered emergency generator fails to kick in. That’s also the flaw with the emergency kit suggestions I linked to above; if you don’t know how to use a compass or first-aid kit, having one in your car won’t do you much good.

But testing isn’t just valuable because it reveals practical problems with a plan. It also has enormous ancillary benefits for your organization in terms of communication and team building. There’s nothing like a good crisis to get people to rely on each other. Sometimes I think companies should forget about those team building exercises that involve climbing trees and building fires, and instead pretend that a flood has taken out the primary data center. It really doesn’t matter what disaster scenario you’re testing.

The real disaster won’t be like the test, regardless of what you do, so just pick one and go. Whether you’re an individual trying to recover from a simulated virus attack, or an organization testing its response to a hypothetical shooter in the building, you’ll learn a lot about yourselves and your organization, as well as your plan. There is a sweet spot, though, in disaster preparedness. Some disasters are too small or too common to worry about. It makes no sense to plan for total annihilation of the continent, whether by nuclear or meteor strike: That’s obvious.

But depending on the size of the planner, many other disasters are also too large to plan for. People can stockpile food and water to prepare for a hurricane that knocks out services for a few days, but not for a Katrina-like flood that knocks out services for months. Organizations can prepare for losing a data center due to a flood, fire or hurricane, but not for a Black-Death-scale epidemic that would wipe out a third of the population. No one can fault bond trading firm Cantor Fitzgerald, which lost two thirds of its employees in the 9/11 attack on the World Trade Center, for not having a plan in place to deal with that possibility.

If your corporate headquarters burns down, it’s actually a bigger problem for you than a citywide disaster that does much more damage. If the whole San Francisco Bay Area were taken out by an earthquake, customers of affected companies would be far more likely to forgive lapses in service, or would go the extra mile to help out. Think of the nationwide response to 9/11; the human “just deal with it” social structures kicked in, and we all muddled through.

A blogger commented on what I said in one article: Schneier is using what I would call the nuclear war argument for doing nothing.

Bird flu, pandemics and disasters in general — whether man-made like 9/11, natural like bird flu or a combination like Katrina — are definitely things we should worry about.

http://www.wired.com/politics/security/commentary/securitymatters/2007/07/securitymatters_0726

Read more

Six sensible steps to keep disaster recovery real

Posted on September 11, 2006December 30, 2021 by admini

On this topic IBM aims continuous data backup software at SMBs One in five firms has no disaster recovery plan MessageLabs launches e-mail archival service Protecting Remote Office Data: D2D Backup/Recovery Solutions Protecting Microsoft Exchange: The Need for Disaster Prevention and Optimization Best Practices for Disaster Recovery Across the WAN Costs and Consequences: Securing sensitive data at the edge of the network and beyond Data Protection – A Top Priority: Reduce the Risk of Costly Data Breaches A Guide to Reducing the Risks of Costly Data Breaches security.itworld.com.

Ultimately IT is there to serve business, and disaster recovery planning should be no different. Well, most IT shops still don’t get it, according to EMC Canada consultant Iain Anderson. People are still making technology decisions, and not business decisions.

According to Paul Saxton, lead consultant in business resiliency at IMB Canada Ltd., recovery capabilities have to be matched to the business requirements. “Understand that disaster recovery and business continuity are part of overall risk management,” he says.

“One of the challenges I see all the time is that business continuity and disaster recovery fall back to the responsibility of IT, and IT’s normal response is to throw technology at it,” says Anderson, client director at EMC Corp. of Canada. Anderson says IT has a responsibility to understand how business workflow ties in to business applications, and how those applications in turn are supported by infrastructure. “We tend not to spend enough time communicating out there with the business units and understanding what their business problems are,” he says.

As a type of insurance policy, it’s helpful to know what threats and vulnerabilities you’re likely to come up against. Unless you’re in a tornado area, on a fault line or flood plane, you probably won’t be building a mirror site of your entire IT infrastructure. But going through that vulnerability and risk assessment can be a heated debate, says George Kerns, president and CEO of Fusepoint Managed Services Inc.

The budget for a recovery plan is large compared to the operating budget, and if the chance of a disaster occurring isn’t high, how do you avoid spending too much? “I think this has to come down to a rational conversation between the CIO and the CEO,” says Kerns. He says most business units believe their IT systems can be back up within hours, while IT will estimate a couple of days and an actual assessment of the technology will reveal a further gap.

“This is a big area where more testing needs to be done, with a more rigorous, more integrated approach and a stronger level of governance around it,” he says. And don’t test to pass; you have to test to fail, says Anderson.

Read more

Disaster Recovery at the Macro Level

Posted on June 13, 2006December 30, 2021 by admini

DRP and its partner Business Continuity Planning (BCP) are board level initiatives and should be treated as such. If you don’t have someone within your organization with the right expertise, go find someone who specializes. Put someone in your organization solely and fully in charge of the effort with board level authority.

If you never got to the point of testing your existing plan, the right consultant will help you develop a program that requires the least amount of investment initially. In disaster recovery planning, you have to do the right things in the right order and there are no shortcuts. This will require your patience, but not a huge chunk immediately out of your pocketbook. However, this is where testing mistakes can have huge negative impact on the business.

Pick a smaller application and test recovery outside of the production environment. After each recovery test exercise, an honest review of the successes and failures is not a step to be taken lightly. This is your opportunity to refine, refine, and refine.

Documenting procedures is not for the faint of heart.

http://www.bankinfosecurity.com/articles.php?art_id=150&PHPSESSID=180fe654b2a330ff0b5cdba0e36eec9f

Read more

Recent Posts

  • AI/ML News – 2024-04-14
  • Incident Response and Security Operations -2024-04-14
  • CSO News – 2024-04-15
  • IT Security News – 2023-09-25
  • IT Security News – 2023-09-20

Archives

  • April 2024
  • September 2023
  • August 2023
  • July 2023
  • June 2023
  • April 2023
  • March 2023
  • February 2022
  • January 2022
  • December 2021
  • September 2020
  • October 2019
  • August 2019
  • July 2019
  • December 2018
  • April 2018
  • December 2016
  • September 2016
  • August 2016
  • July 2016
  • April 2015
  • March 2015
  • August 2014
  • March 2014
  • August 2013
  • July 2013
  • June 2013
  • May 2013
  • April 2013
  • March 2013
  • February 2013
  • January 2013
  • October 2012
  • September 2012
  • August 2012
  • February 2012
  • October 2011
  • August 2011
  • June 2011
  • May 2011
  • April 2011
  • February 2011
  • January 2011
  • December 2010
  • November 2010
  • October 2010
  • August 2010
  • July 2010
  • June 2010
  • May 2010
  • April 2010
  • March 2010
  • February 2010
  • January 2010
  • December 2009
  • November 2009
  • October 2009
  • September 2009
  • June 2009
  • May 2009
  • March 2009
  • February 2009
  • January 2009
  • December 2008
  • November 2008
  • October 2008
  • September 2008
  • August 2008
  • July 2008
  • June 2008
  • May 2008
  • April 2008
  • March 2008
  • February 2008
  • January 2008
  • December 2007
  • November 2007
  • October 2007
  • September 2007
  • August 2007
  • July 2007
  • June 2007
  • May 2007
  • April 2007
  • March 2007
  • February 2007
  • January 2007
  • December 2006
  • November 2006
  • October 2006
  • September 2006
  • August 2006
  • July 2006
  • June 2006
  • May 2006
  • April 2006
  • March 2006
  • February 2006
  • January 2006
  • December 2005
  • November 2005
  • October 2005
  • September 2005
  • August 2005
  • July 2005
  • June 2005
  • May 2005
  • April 2005
  • March 2005
  • February 2005
  • January 2005
  • December 2004
  • November 2004
  • October 2004
  • September 2004
  • August 2004
  • July 2004
  • June 2004
  • May 2004
  • April 2004
  • March 2004
  • February 2004
  • January 2004
  • December 2003
  • November 2003
  • October 2003
  • September 2003

Categories

  • AI-ML
  • Augment / Virtual Reality
  • Blogging
  • Cloud
  • DR/Crisis Response/Crisis Management
  • Editorial
  • Financial
  • Make You Smile
  • Malware
  • Mobility
  • Motor Industry
  • News
  • OTT Video
  • Pending Review
  • Personal
  • Product
  • Regulations
  • Secure
  • Security Industry News
  • Security Operations
  • Statistics
  • Threat Intel
  • Trends
  • Uncategorized
  • Warnings
  • WebSite News
  • Zero Trust

Meta

  • Log in
  • Entries feed
  • Comments feed
  • WordPress.org
© 2025 CyberSecurity Institute | Powered by Superbs Personal Blog theme