Part 5 - Outsourcing Considerations

Video Activity

This lesson covers considerations for outsourcing an incident response team: · Current and future quality of work · Division of responsibilities · Sensitive information revealed to contractor · Lack of organization specific knowledge · Lack of correlation · Handling of incidents at multiple locations · Maintaining incident response skills in house

Join over 3 million cybersecurity professionals advancing their career
Sign up with

Already have an account? Sign In »

7 hours 26 minutes
Video Description

This lesson covers considerations for outsourcing an incident response team: · Current and future quality of work · Division of responsibilities · Sensitive information revealed to contractor · Lack of organization specific knowledge · Lack of correlation · Handling of incidents at multiple locations · Maintaining incident response skills in house

Video Transcription
some of the gun. We're gonna talk about outsourcing considerations. So one of the first considerations to look at is the current and future quality of work
performed by these teams. So organizations should consider not only the current quality at the breadth and depth of the outsourcers work, but also efforts to ensure the quality of future work
for example, minimizing turnover and burn out. Providing a solid training program for new employees
Organization should think about how they could objectively assess the quality of the outsourcers work.
So again it's kind of similar to if you're going to want to look at your
internal incident response team, you would also want to look at a way of how you can evaluate that outside team or that outside source to know if you're getting your money's worth,
so you don't so one look at the division of Responsibilities, so organizations are often unwilling to give an outsourcer authority to make operational decisions for the environment. You see that lot with the United States government, government boys have the ability to essentially make decisions and
contract with the government, and then you have the government contractors who sexually
do the workers is required and contracting but can't really make any decisions or commit the government
to certain actions of spending. Money
in this example could be essentially disconnecting a Web server. So it's really important to document what type of responsibilities that you want to have outside organizations to do and to have certain types of decision points to allow them
the ability to know when they should or could
take certain actions. For example, one particularly outsourced model addresses this issue by having the outsourcer provide incident data to the organization's internal team, along with recommendations for further handling of the incident.
Then the internal team ultimately makes the operation operational. Decisions with the outsourcer can continue to arrive the support as needed.
Another consideration that you might have this sensitive information revealed to the contractor,
so dividing incident response responsibilities and restricting access to sensitive information could live in this. For example, a contractor may determine what you what user I d would use an incident. So, for example, the user i d. 123456
but not know what person is associated with the user, I d.
So boys can then take over the investigation.
Non disclosure agreements are one possible option for protecting the disclosure of sensitive information,
but it's likely in your organization you may have essentially compartment, and we're not. Everyone in the organization even knows what other apartments they're doing, so that's very common. But you just want to be able to have a way to work with or work through some of those considerations. If you do have
our do work with the lie of sensitive information,
Some other outsourcing considerations are the lack of organization specific knowledge, so accurate analysis and prioritization of incidents are dependent on specific knowledge of the organization's environment.
So the organization should provide the outsourcer regularly updated documents that define what incidents it is concerned about. Which resource is air critical. A lot level of response should be under various circumstances. The organization should also report all changes and updates made to its I T infrastructure
network configuration systems to that outside contractor.
Otherwise, the contractor has to make the best gas how each incident should be handled, inevitably leading to a mishandled incident and frustration on both sides. So communication is going to be very key doing this if you've ever responded to an incident, particularly even within your own organisation.
Often times you may have ah, diagram of your your server room
or I T room, and even within your own organisation, it's not up to date.
Ideally, you would be able to figure out how that works. But if you're outside are going in the organization, that's even harder. So it's It's important to have good communication between your contractors, so lack of organization specific knowledge can also be a problem when incident response is not outsourced.
If communications air Week among teams or organization simply does not collect the necessary information,
the next consideration is going to be a lack of correlation. So correlation among multiple data sources is going to be very important
if your intrusion detection system records and attempted attack against a Web server. But the outsourcer has no access to the servers log, it may be unable to determine whether the attack was successful, so to be efficient, the out searcher will require administrative privileges to critical systems
and security device logs remotely over secure channel.
This will increase your admin cost and it probably introduce additional access entry points and increase the risk of unauthorized disclosure of sensitive information. So those were just some some things to be aware of so often times. If you're trying to provide that extra information to the outsourcer,
you may be opening yourself up to
additional kind of vulnerabilities.
So the next consideration is going to be handling incidents at multiple locations. So as we talked about earlier line of large enterprises are spread out. Of course, the United States across globally so effective incident response were often requires physical presence at the organization's facilities.
So if the outsourcer it's offside, consider whether the officer consider where the outsourcers located,
how quickly it can respond to that incident or haven't answered response team at that facility, and how much will that cost?
So consider on site visits. Per perhaps there are certain facilities are areas where the outsourcer should not be permitted to work well. So again, if you've got one of those
secure facilities are working in a government skiff, you may not want to have that outsourcer that outsourced or may not be permitted to work in that area due to security constraints.
And then the next consideration is maintaining incident response skills in house. So organizations that completely outsource incident response should strive to maintain basic incident response skills inside and situations may arise in which the outsources unavailable
up, which could be Maybe you have a contract dispute
are they go out of business. So the organization should be prepared to perform all of its own incident handling, or at least have someone there who's knowledgeable about incident. Handling on that also goes kind of hand in hand with being able to evaluate that outsourcing. As long as you have someone within the organization you have some knowledge
of incident response.
You are protecting yourself.
Up Next
Incident Response and Advanced Forensics

In this course, you will gain an introduction to Incident Response, learn how to develop three important protection plans, perform advanced forensics on the incident, deep dive into insider and malware threats, and commence incident recovery.

Instructed By