This video examines the hypothesis that SaaS data loss varies widely, ranging from large-scale incidents affecting many records to smaller issues involving fewer records.
0:00
Let's move on to our third hypothesis and theme here.
0:12
I did the pleasure of presenting a session at Salesforce's huge Dreamforce
0:17
event in September
0:19
of last year in San Francisco.
0:22
I presented with an existing customer of one companies and there was an audible
0:27
gasp from
0:27
the room when the Salesforce admin from this organization said that yes they
0:33
had lost 600,000
0:35
records from their Salesforce CRM due to an accidental error, 600,000.
0:42
The reason I mention that is because our third hypothesis was around this is
0:46
that it's a
0:46
state loss real.
0:47
It's all very well for people like me to talk about it but does it happen?
0:52
How common places it?
0:54
Well actually how varied is it because there's a sense that some of you can
0:57
think about data
0:58
losses.
0:59
Here we've lost everything but actually it varies and we wanted to understand
1:03
the extent
1:03
which it varies from large scale losses through to smaller issues involving
1:08
fewer records.
1:09
I've got a couple of slides that I'm going to share with you that talk to this.
1:12
The first one is we explored the common types of data loss and we offered the
1:19
respondents
1:20
various different options and we invited them to comment on each one.
1:25
The headline figures are on the right of the chart there where 26% of the
1:31
sample said that
1:32
they had suffered in the previous 12 months weekly delays or failures in data
1:37
synchronization.
1:38
29% said on at least a monthly basis in the previous time period they had
1:43
suffered errors
1:44
or inaccuracies in customer records.
1:47
29% occasionally saying delays or failures in data synchronization.
1:52
So is data loss real?
1:54
Well the evidence from this sample of over 500 people with responsibility for
1:59
SAS data
2:00
protection and backup recovery says yes.
2:03
Data loss absolutely is real, is prevalent and it's commonplace.
2:07
Let me take this another level forward because let's talk about the severity
2:11
and the impact
2:12
of those data losses and corruptions.
2:15
Now we asked this further question about severity and on average the leaders
2:20
using these four
2:21
SAS applications I already mentioned said that data instance did have a
2:26
moderate impact
2:27
on their organization.
2:28
Now what might those impacts be?
2:31
Well sometimes it interrupts their ability to deliver service to customers.
2:37
Sometimes it's the inability to serve future customers and manage sales
2:42
opportunities.
2:44
Sometimes it's about data management and financial reporting and so forth.
2:48
So all sorts of consequences associated with SAS data loss.
2:53
Again Andrea let me throw the microphone across to you some comments and
2:56
observations here
2:57
please.
2:58
Yeah I mean one thing I definitely would like to add here is the relevance of
3:03
ransomware
3:04
attacks right.
3:05
So unfortunately these kind of attacks are not uncommon especially these days
3:10
and you
3:10
know given the current geopolitical tension we noticed that and we're reading
3:16
on the news
3:17
that these are kind of attacks happens almost on a daily basis on large
3:22
organizations right.
3:25
And I mean from a damaged perspective apart from the pure economic aspect of it
3:30
there
3:30
is a huge brand impact and erosion of customer trust right.
3:38
So if a company is unable to protect its daytime prevent ransomware attacks of
3:43
course customers
3:44
make question its ability to safeguard their personal information and this can
3:50
definitely
3:50
lead to a damaged reputation that can take very long time to recover.
3:56
And for organizations that have a lot of intellectual property on their SAS
4:00
solutions of course
4:02
there is another aspect to consider.
4:05
So there is a whole intellectual poverty trade secret or proprietary
4:09
information you know
4:09
when it's lost you can have a very long term negative effect on the company's
4:13
competitive
4:14
advantage and innovation.
4:15
So again it's definitely there is a pure operational aspect and business
4:20
continuity
4:21
aspect to consider but you know the long term impact of a brand damage or loss
4:30
of customer
4:30
trust that is that takes very long time to recover.
4:34
So I would definitely focus on that part as well.
4:36
Yeah I don't know that makes sense.
4:38
I mentioned earlier the great pleasure I take in being able to talk to our
4:42
customers and
4:43
potential customers on a frequent basis.
4:47
And one of the conversations the recurring conversations I have there is when
4:50
we talk
4:51
about the causes of data loss and corruptions.
4:54
And some things you can seek to mitigate isn't it.
4:58
You can work hard and you put places measures in place such that you may think
5:02
you're going
5:03
to be immune from a cyber attack you know ransomware attack or such like.
5:07
You know there's maybe other factors that you can put in place that would
5:10
really minimize
5:11
the chances of any integration errors being a catalyst to a data loss or
5:17
corruption event.
5:18
But the number one reason there's an adriages highlighted is human error.
5:22
It's accidental error and it's impossible to mitigate against that and that I
5:26
think is
5:27
another added reason why it's important that we prepare for the worst and say
5:32
actually
5:33
if there is a possibility of me losing access to some or all of my data I need
5:39
to have a
5:40
protection system in place such that I can restore and recover it in the event
5:45
of such
5:45
a situation.
5:47
[ Sound Effects ]
5:51
[ Silence ]