Dark Reading is part of the Informa Tech Division of Informa PLC

This site is operated by a business or businesses owned by Informa PLC and all copyright resides with them.Informa PLC's registered office is 5 Howick Place, London SW1P 1WG. Registered in England and Wales. Number 8860726.

Vulnerabilities / Threats

7/3/2019
01:00 PM
Joshua Goldfarb
Joshua Goldfarb
Commentary
Connect Directly
Twitter
RSS
E-Mail vvv
50%
50%

20 Questions to Ask During a Real (or Manufactured) Security Crisis

There are important lessons to be learned from a crisis, even the ones that are more fiction than fact.

I've heard the statement "society doesn't deal with problems until they become a crisis" many times. Unfortunately, this is often the case in information security, but it doesn't need to be this way. As security practitioners, we can't fix the ills of society. We can, however, learn how to distinguish a real security crisis from a manufactured one. Furthermore, from each crisis (real or manufactured) that we go through, we can learn how to avert them all together.

In this spirit, I offer 20 questions to ask during a real or manufactured security crisis.

Image Credit: DuMont Television/Rosen Studios. Public domain, via Wikimedia
Image Credit: DuMont Television/Rosen Studios. Public domain, via Wikimedia

1. What is the threat that the issue at hand poses? Regardless of the noise surrounding a given situation, you need to understand the actual threat you're dealing with. Conjecture and hype won't help. Rather, you need to objectively understand how the threat could manifest itself as a risk to the organization.

2. What is the organization's exposure to the threat? Once you understand the threat, you can evaluate your exposure to that threat. This needs to be done in order to fully understand the gravity of the situation.

3. What risk does this threat pose to the organization? Once you understand the organization's exposure, you can assess the risk posed to the organization. This is where you really begin to understand how seriously to consider the threat and how aggressively to respond.

4. Is the hype surrounding this threat justified? Separating fact from fiction is important. If the facts support the hype surrounding a given threat, then it needs to be dealt with as such. However, if the facts tell a different story, it's time to spin this one down.

5. Does the hype surrounding the threat translate to a real risk for the organization? If the risk is real, then it's time to respond appropriately. That includes the communication necessary to keep the right stakeholders informed.

6. When did we first become aware of the issue? Were you just made aware of this, or have you been aware of it for quite some time? The difference is important. If you knew about a significant risk to the organization and didn't act on it or escalate appropriately, that's a fairly significant lapse in security.

7. Why wasn't this raised earlier? If there is a reason, it can be addressed as part of continual process improvement. If there is no reason, it's important to understand why.

8. Could we have avoided this issue? In many cases, issues can be avoided if risk assessment were done more proactively, or if the attack surface had been reduced significantly. Not in all cases, of course, but it's good to ask the question.

9. Why didn't we avoid this issue? Once you understand how you could have avoided an issue, you need to ask why you didn't.

10. Has any damage to the organization occurred? This is, of course, the quintessential question. If no damage occurred, you need to remediate the risk, learn from your mistakes, and be thankful. If damage has occurred, then you still need to remediate the risk, learn from your mistakes, and, of course, perform incident response.

11. What are the steps required to remediate the issue? If you need to respond and remediate, the first step is to map out the steps required to do so properly. Taking a few moments to get organized and ensure all bases are covered yields a higher-quality result and saves time down the line.

12. What are the lessons learned from this issue? After any issue is dealt with, lessons need to be extracted and studied. This allows the security organization to improve and mature.

13. Can we apply those lessons to avoid a similar situation in the future? Obviously, crisis mode is a last resort. If you can apply lessons learned, you can avoid making the same mistake.

14. What other potential crises might we encounter? Post-crisis is a great time to think outside of the box and do some analysis. Understanding what other pitfalls you may encounter allows you to mitigate those risks ahead of time and improve the security posture of the organization.

15. What else can we tighten up to avoid future issues? You may have patched, tightened controls, or improved monitoring after the crisis, but what else can you do to keep from having to relive this or a similar experience?

16. How can we ensure that our remediation of the issue will be effective? Your plan may sound good on paper, but to be more certain, map the technologies and applications the issue affects, then conduct a sanity check to see whether it will achieve your desired goals.

17. Have we verified that remediation was effective? If you've already remediated, have you tested to ensure that the remediation was effective? If not, you could be exposed to a recurrence.

18. What steps have we taken to avoid a similar situation in the future? You need to ensure that whatever remediation you've done, whatever lessons you've learned, and whatever improvements you've made are lasting and not a one-time fix.

19. Have we precisely and effectively communicated actions to management and executives? Regardless of whether or not you had a real crisis, whether or not you handled it appropriately, and whether or not you've made improvements to the security organization, your actions need to be documented and communicated to management and executives. This builds confidence in the security team's ability and avoids excessive spin-up when the next issue arises.

20. Have we taken steps to avoid future damage? In the end, it all comes down to whether or not you avoid or minimize damage to the organization. This is perhaps is the hardest question to answer. But it is likely the most important.

Related Content:

Black Hat USA returns to Las Vegas with hands-on technical Trainings, cutting-edge Briefings, Arsenal open-source tool demonstrations, top-tier security solutions, and service providers in the Business Hall. Click for information on the conference and to register. 

Josh (Twitter: @ananalytical) is an experienced information security leader who works with enterprises to mature and improve their enterprise security programs.  Previously, Josh served as VP, CTO - Emerging Technologies at FireEye and as Chief Security Officer for ... View Full Bio
Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
tdsan
50%
50%
tdsan,
User Rank: Ninja
7/7/2019 | 7:30:02 PM
Creating a framework to help address some of the questions brought up
NIST has a site where they provide similar questions but they revolve the questions about developing a framework. This framework is based on the Risk Management framework from NIST - Risk Assessment Framework chart.

The questions you bring up are listed in this flowchart, it addresses
  • Page 20 - Identify the threats and their severity
  • Page 24 - Mgmt, Operational, Technical Security
  • Page 31 - Risk Level Matrix with weights
  • Page 34 - Risk Mitigation Strategy
  • Page 39 - Technical Security Controls
  • Page 43 - Preventative Operational Controls
  • Page 46 - Implemented Controls and Residual Risk
  • Page 47 - Evaluation & Assessment (Good Security Practice/Keys to Success)
  • Page 48 - Sample Interview Questions (Acronym)*

* Interview questions that can assist in the assessment and risk mitigation strategy. Sample Questions listed below:
APPENDIX A: Sample Interview Questions Interview questions should be tailored based upon where the IT system assessed is in the SDLC. Sample questions to be asked during interviews with site personnel to gain an understanding of the operational characteristics of an organization may include the following:
  • Who are valid users?
  • What is the mission of the user organization?
  • What is the purpose of the system in relation to the mission?
  • How important is the system to the user organization's mission?
  • What is the system-availability requirement?
  • What information (both incoming and outgoing) is required by the organization?
  • What information is generated by, consumed by, processed on, stored in, and retrieved by the system?
  • How important is the information to the user organization's mission?
  • What are the paths of information flow?
  • What types of information are processed by and stored on the system (e.g., financial, personnel, research and development, medical, command and control)?
  • What is the sensitivity (or classification) level of the information?
  • What information handled by or about the system should not be disclosed and to whom?
  • Where specifically is the information processed and stored?
  • What are the types of information storage?
  • What is the potential impact on the organization if the information is disclosed to unauthorized personnel?
  • What are the requirements for information availability and integrity?
  • What is the effect on the organization's mission if the system or information is not reliable?
  • How much system downtime can the organization tolerate?
  • How does this downtime compare with the mean repair/recovery time?
  • What other processing or communications options can the user access?
  • Could a system or security malfunction or unavailability result in injury or death?

Todd
Navigating Security in the Cloud
Diya Jolly, Chief Product Officer, Okta,  12/4/2019
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Write a Caption, Win a Starbucks Card! Click Here
Latest Comment: "The security team seem to be taking SiegeWare seriously" 
Current Issue
Navigating the Deluge of Security Data
In this Tech Digest, Dark Reading shares the experiences of some top security practitioners as they navigate volumes of security data. We examine some examples of how enterprises can cull this data to find the clues they need.
Flash Poll
Rethinking Enterprise Data Defense
Rethinking Enterprise Data Defense
Frustrated with recurring intrusions and breaches, cybersecurity professionals are questioning some of the industrys conventional wisdom. Heres a look at what theyre thinking about.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2019-5098
PUBLISHED: 2019-12-05
An exploitable out-of-bounds read vulnerability exists in AMD ATIDXX64.DLL driver, version 26.20.13001.29010. A specially crafted pixel shader can cause out-of-bounds memory read. An attacker can provide a specially crafted shader file to trigger this vulnerability. This vulnerability can be trigger...
CVE-2012-1104
PUBLISHED: 2019-12-05
A Security Bypass vulnerability exists in the phpCAS 1.2.2 library from the jasig project due to the way proxying of services are managed.
CVE-2019-17387
PUBLISHED: 2019-12-05
An authentication flaw in the AVPNC_RP service in Aviatrix VPN Client through 2.2.10 allows an attacker to gain elevated privileges through arbitrary code execution on Windows, Linux, and macOS.
CVE-2019-17388
PUBLISHED: 2019-12-05
Weak file permissions applied to the Aviatrix VPN Client through 2.2.10 installation directory on Windows and Linux allow a local attacker to execute arbitrary code by gaining elevated privileges through file modifications.
CVE-2019-18381
PUBLISHED: 2019-12-05
Norton Password Manager, prior to 6.6.2.5, may be susceptible to a cross origin resource sharing (CORS) vulnerability, which is a type of issue that allows restricted resources on a web page to be requested from another domain outside the domain from which the first resource was served.