Vendor Lock-In

Video Activity
Join over 3 million cybersecurity professionals advancing their career
Sign up with
Required fields are marked with an *
or

Already have an account? Sign In »

Time
12 hours 57 minutes
Difficulty
Intermediate
CEU/CPE
13
Video Transcription
00:00
>> All right, now we're going to
00:00
>> talk about vendor lock-in.
00:00
>> I know this has come up a few times at this point,
00:00
but there are a number of components of
00:00
vendor lock in that we haven't discussed yet,
00:00
and it is an incredibly important risk
00:00
when using Cloud deployments.
00:00
Our learning objectives for
00:00
this lesson are really to talk
00:00
about the common issues that result in vendor lock-in,
00:00
talk about the primary methods for
00:00
avoiding the factors that lead a vendor lock-in,
00:00
and really how to prioritize and
00:00
mitigate major risks for vendor lock-in.
00:00
As we said before,
00:00
vendor lock-in is when you are unable
00:00
to remove your data from a Cloud provider.
00:00
We call this the lack of data portability.
00:00
This is often caused by data
00:00
being stored in the Cloud and proprietary formats
00:00
that may be useful to the Cloud provider
00:00
in terms of storage or processing data,
00:00
but they pose a huge risk to a business.
00:00
Vendor lock-in can result in
00:00
a business paying more than they should for
00:00
Cloud provider services over time because they are
00:00
unable to move their data to a cheaper alternative.
00:00
The best way to mitigate vendor lock-in is to really
00:00
consider how data can
00:00
be removed before signing a contract,
00:00
before putting data in the Cloud.
00:00
Now, I have done many vendor reviews in my time,
00:00
and I know this is
00:00
a very difficult thing in terms of human psychology.
00:00
You've purchased to Cloud vendor,
00:00
you've signed a contract,
00:00
you've fallen in love.
00:00
You don't necessarily want to think about breaking up.
00:00
You don't necessarily want to think about,
00:00
are we creating a dependency by using this Cloud vendor?
00:00
Did we really investigate whether we
00:00
can easily remove our data?
00:00
It's very hard for people,
00:00
but it is an essential thing to be considered in
00:00
the planning process when migrating to a Cloud vendor.
00:00
One of the other considerations are
00:00
physical and technical limitations
00:00
to moving from the Cloud.
00:00
The more data you put in the Cloud,
00:00
the harder it is to actually remove
00:00
that data in terms of sending it over the Internet.
00:00
There are just throughput and bandwidth limitations
00:00
that make it really difficult to move data.
00:00
If you've used a Cloud provider for
00:00
many years for business continuity,
00:00
you could have terabytes and terabytes,
00:00
potentially even petabytes of data in
00:00
the Cloud that could take months
00:00
or years to potentially
00:00
move over a standard Internet connection.
00:00
Even fiber optic connection might be difficult.
00:00
Now some Cloud providers,
00:00
they have solutions for this.
00:00
The solutions are usually aimed at moving
00:00
data to the Cloud in an effective manner,
00:00
but they can be used in the reverse.
00:00
AWS has a device they call the Snowball,
00:00
that can be taken to
00:00
an on-premise datacenter and you can
00:00
load petabytes of data onto the snowball,
00:00
which then can be physically taken to
00:00
an AWS datacenter and upload it into the Cloud.
00:00
Quiz question. A medical imaging software company is
00:00
dissatisfied with the service level
00:00
at its current hosting provider.
00:00
The company would like to move,
00:00
but the volume of imaging data
00:00
stored in their current provider
00:00
would take months to move
00:00
given the current providers capabilities.
00:00
This is an example of which lock-in risk?
00:00
Is it, one, proprietary data format, two,
00:00
regulatory constraints or
00:00
three, physical/technical limitations?
00:00
In this case, it definitely
00:00
is the physical/technical limitations.
00:00
Now if the company could potentially avoided this by
00:00
analyzing how much data
00:00
they've been starting to store in the Cloud,
00:00
as well as reading the Cloud contracts very carefully and
00:00
using effective risk management strategies
00:00
when figuring out their Cloud migration.
00:00
All right, in this video, we talked
00:00
about the main factors
00:00
associated with the risk of vendor lock-in,
00:00
namely proprietary data formats and
00:00
technical and physical limitations
00:00
on moving data in and out of the Cloud.
00:00
We talked about the primary methods
00:00
for addressing these factors.
00:00
Really just reading
00:00
the Cloud services contract carefully,
00:00
doing effective risk management and
00:00
business continuity scenarios before migrating to
00:00
the Cloud and identifying
00:00
mitigation strategies or having this data in the Cloud.
00:00
Perhaps you'd use multiple Clouds and not just one.
00:00
Anyway, this can really save you a lot of
00:00
time and headache in migrating to a Cloud environment.
00:00
I'll see you in the next lesson
Up Next