1
00:00:20,000 --> 00:00:23,200
Good morning, good afternoon, 
and good evening, to all our sap

2
00:00:23,200 --> 00:00:25,900
S400 followers. 
My name is Marvin Posh and 

3
00:00:25,900 --> 00:00:28,900
today, you are listening to the 
fifth episode of the new inside 

4
00:00:28,900 --> 00:00:31,100
as a foreigner podcast. 
We'll sit by solution 

5
00:00:31,100 --> 00:00:33,900
management. 
Through a successful 

6
00:00:33,900 --> 00:00:37,200
digitization companies, expect 
efficiency gains and cost 

7
00:00:37,200 --> 00:00:39,600
savings, important factors. 
The daily competition. 

8
00:00:39,900 --> 00:00:42,800
However, the change is 
accompanied by a continuously 

9
00:00:42,800 --> 00:00:45,900
changing threat landscape by 
evolving, cyber criminals, 

10
00:00:46,200 --> 00:00:49,200
hackers, and economic spice to 
counteract the threat. 

11
00:00:49,200 --> 00:00:51,300
Landscape Securities and 
indispensable. 

12
00:00:51,300 --> 00:00:53,400
Topic. 
That every company should value 

13
00:00:54,100 --> 00:00:55,800
today. 
I have invited my sap colleague,

14
00:00:55,800 --> 00:00:57,700
Patrick Bach to address this 
topic. 

15
00:00:57,800 --> 00:01:01,200
We are going to talk in general 
about security and the steps I 

16
00:01:01,200 --> 00:01:04,500
say p tags to ensure data. 
Section and data security for 

17
00:01:04,500 --> 00:01:07,900
sap as funnel cloud. 
Hi Patrick. 

18
00:01:08,200 --> 00:01:09,300
Hi, Marvin. 
How are you? 

19
00:01:09,700 --> 00:01:11,700
I'm really excited to have you 
as my guest today. 

20
00:01:12,300 --> 00:01:14,700
It would be great if you could 
briefly introduce yourself to 

21
00:01:14,700 --> 00:01:16,500
the audience. 
Yes. 

22
00:01:16,700 --> 00:01:20,000
Thank you for having me. 
My name is Patrick ball and I'm 

23
00:01:20,000 --> 00:01:24,800
the product manager for as far 
as security, which does not only

24
00:01:24,800 --> 00:01:29,200
cover as for Hana Cloud but also
the two other flavors so to 

25
00:01:29,200 --> 00:01:33,100
speak meaning, as far as 
on-premise and as far Hana 

26
00:01:33,100 --> 00:01:36,500
Cloud, private addition and I 
rejoined. 

27
00:01:36,500 --> 00:01:42,800
I must say sap in 2020. 
I've been with sap before from 

28
00:01:42,800 --> 00:01:49,800
2001 to 2006, so during the new 
economy time, but afterwards, I 

29
00:01:49,800 --> 00:01:55,000
went into the sap security 
space, in general and since 

30
00:01:55,000 --> 00:01:58,400
2020, as I mentioned, now 
responsible for securing, as for

31
00:01:58,400 --> 00:02:00,500
Hannah, thanks for the 
introduction. 

32
00:02:01,000 --> 00:02:02,600
The topic of data protection and
dead. 

33
00:02:02,800 --> 00:02:05,400
Privacy has gained enormous 
importance in the last few 

34
00:02:05,400 --> 00:02:07,000
years. 
We all know that there are 

35
00:02:07,000 --> 00:02:09,900
multiple reasons for that. 
For example, the introduction of

36
00:02:09,900 --> 00:02:13,300
the general data protection 
regulation in 2018 and to 

37
00:02:13,300 --> 00:02:16,200
several data breaches reported 
by bacon well-known companies. 

38
00:02:16,200 --> 00:02:19,700
Such as Microsoft or Facebook, 
what do you think is the current

39
00:02:19,700 --> 00:02:24,800
attitude towards security? 
I think it's improving from a 

40
00:02:24,800 --> 00:02:28,600
perspective of someone who is in
security or inside the security 

41
00:02:28,600 --> 00:02:31,500
to be precise. 
It wasn't that before I was 

42
00:02:31,500 --> 00:02:35,300
everyone always We thought that 
security is something where you 

43
00:02:35,300 --> 00:02:38,800
say, okay, yeah, we might have 
to do that but it's not that 

44
00:02:38,800 --> 00:02:42,500
important. 
But because of the GDP are, 

45
00:02:42,800 --> 00:02:48,200
which has heavy fines if you 
don't do proper security and 

46
00:02:48,200 --> 00:02:51,500
also because of some of the data
breaches we have heard about in 

47
00:02:51,500 --> 00:02:56,100
the past few months, and years. 
I think people take it a lot 

48
00:02:56,100 --> 00:02:58,100
more seriously than they used 
to. 

49
00:02:58,800 --> 00:03:01,100
I totally agree. 
I think you're definitely see a 

50
00:03:01,100 --> 00:03:02,600
change if you compare the 
current attitude. 

51
00:03:02,800 --> 00:03:04,500
With the one, a couple of years 
ago. 

52
00:03:05,000 --> 00:03:07,700
Do you think this is may be 
different depending on the size 

53
00:03:07,700 --> 00:03:13,300
of the company or industry? 
Unfortunately, yes, it's always 

54
00:03:13,300 --> 00:03:15,900
will not always the case but I 
think that especially bigger 

55
00:03:15,900 --> 00:03:18,500
companies, they know that 
there's an issue that they need 

56
00:03:18,500 --> 00:03:22,800
to do something, but smaller 
companies, medium-sized 

57
00:03:22,800 --> 00:03:25,500
companies. 
They sometimes, first of all, 

58
00:03:25,500 --> 00:03:28,300
it's because of a lack of 
resources. 

59
00:03:28,300 --> 00:03:32,800
So they literally don't have 
neither the people nor The 

60
00:03:32,800 --> 00:03:38,300
knowledge to do a good security.
So they are sometimes left out, 

61
00:03:38,300 --> 00:03:41,700
but sometimes it's also a little
bit of an attitude because they 

62
00:03:41,700 --> 00:03:44,800
still think they need to focus 
on their Core Business. 

63
00:03:45,200 --> 00:03:49,700
And then unfortunately, security
sometimes sort of falls behind I

64
00:03:49,700 --> 00:03:54,500
think for the small companies, 
especially for, if you might 

65
00:03:54,500 --> 00:03:57,600
call them startups. 
So, young company, so to speak. 

66
00:03:57,800 --> 00:04:00,400
I think they are more aware of 
the security issue. 

67
00:04:00,400 --> 00:04:02,500
Hopefully them was worth the 
security. 

68
00:04:03,900 --> 00:04:07,800
They would probably have a more 
or better attitude towards 

69
00:04:07,800 --> 00:04:12,000
security, but I think that also 
plays into the cloud business 

70
00:04:12,000 --> 00:04:15,300
and something we will discuss I 
think during the course of this 

71
00:04:15,400 --> 00:04:18,100
podcast, that's correct. 
We will talk about cloud in a 

72
00:04:18,108 --> 00:04:21,399
second but before that, I would 
like to get some insights into 

73
00:04:21,399 --> 00:04:23,900
why the topic shouldn't be 
neglected by companies. 

74
00:04:24,800 --> 00:04:28,500
You essentially mentioned it 
into your, in the main reasons 

75
00:04:28,500 --> 00:04:30,100
you mentioned in your 
introduction. 

76
00:04:30,700 --> 00:04:34,700
One of the reasons is Is, of 
course, the GDP are the data 

77
00:04:34,700 --> 00:04:38,900
protection regulation because as
I mentioned, there are heavy 

78
00:04:38,900 --> 00:04:41,200
fines. 
If you can prove that you've 

79
00:04:41,200 --> 00:04:45,500
done a proper security job or 
proper job in securing the data 

80
00:04:46,000 --> 00:04:50,300
that might actually lead to a 
fine of up to I think four 

81
00:04:50,300 --> 00:04:54,000
percent of your yearly Revenue, 
which can be really heavy on 

82
00:04:54,200 --> 00:04:56,300
especially companies with the 
low margin there. 

83
00:04:56,300 --> 00:04:59,200
But companies, in general for 
percent, that's a quite a bit 

84
00:04:59,800 --> 00:05:04,900
and then, but this is just 
Regulations on security put into

85
00:05:04,900 --> 00:05:07,700
a regulation. 
The main reason I think is just 

86
00:05:08,200 --> 00:05:12,200
the other issues, the other 
problems which you can have. 

87
00:05:12,200 --> 00:05:15,700
If you don't do proper security,
you mentioned data, breaches and

88
00:05:15,700 --> 00:05:19,800
data breaches. 
We also hear a lot about in the 

89
00:05:19,800 --> 00:05:21,800
past is something like when 
somewhere. 

90
00:05:22,200 --> 00:05:25,200
So if you don't have proper 
security, it can actually happen

91
00:05:25,200 --> 00:05:28,900
that someone would be packing, 
you would be attacking you with 

92
00:05:28,900 --> 00:05:31,500
the rent somewhere and then all 
of your data are lost and you 

93
00:05:31,600 --> 00:05:33,200
either have to buy it. 
It back. 

94
00:05:33,500 --> 00:05:36,500
But then you also have to hope 
that the attack has actually 

95
00:05:36,500 --> 00:05:38,400
also giving it back once you 
pay. 

96
00:05:39,200 --> 00:05:44,600
And even if that all of this 
works out, well then you still 

97
00:05:44,600 --> 00:05:47,600
had might have an image problem 
because you will probably have 

98
00:05:47,600 --> 00:05:52,300
to inform your customers that 
you have been breached and the 

99
00:05:52,500 --> 00:05:55,400
reputation loss of reputation 
damage. 

100
00:05:55,400 --> 00:05:58,700
It's also something that you 
need to take care of, not to 

101
00:05:58,700 --> 00:06:01,800
mention the data, which might be
a stone. 

102
00:06:02,100 --> 00:06:07,700
So, I think security is 
something which is essential to 

103
00:06:07,700 --> 00:06:11,300
any business and therefore it 
should also be treated as being 

104
00:06:11,300 --> 00:06:13,700
essential, and not something 
which you would do as an 

105
00:06:13,700 --> 00:06:18,100
afterthought which unfortunately
was the case in the past. 

106
00:06:18,100 --> 00:06:21,200
Very often. 
I know that security has always 

107
00:06:21,200 --> 00:06:23,300
been an important element for 
the Complete product life. 

108
00:06:23,300 --> 00:06:26,700
Cycle of all, I said he products
including product development 

109
00:06:26,700 --> 00:06:29,900
planning and quality assurance. 
What is in place to secure a 

110
00:06:29,907 --> 00:06:32,500
comprehensive solution like sap 
as for Hanukkah? 

111
00:06:32,600 --> 00:06:34,900
Loud. 
This is something where you 

112
00:06:34,900 --> 00:06:38,900
probably have to distinguish 
between why would see it as 

113
00:06:38,900 --> 00:06:42,400
different pillars. 
So the first pillar of course is

114
00:06:42,500 --> 00:06:45,700
the secure development of the 
software itself. 

115
00:06:45,700 --> 00:06:49,600
So how do we ensure that the 
software has as little 

116
00:06:49,600 --> 00:06:53,600
vulnerabilities is possible that
the software itself is secure 

117
00:06:54,100 --> 00:06:58,000
and therefore we have quite a 
bit or quite a few measures in 

118
00:06:58,000 --> 00:07:01,600
place actually, which if you 
start from, if you look at the 

119
00:07:01,600 --> 00:07:04,400
development lifecycle From the 
start, it starts with threat 

120
00:07:04,400 --> 00:07:06,100
modeling. 
So you know when you when you 

121
00:07:06,100 --> 00:07:11,000
actually develop the blueprint 
of your app, you need to think 

122
00:07:11,000 --> 00:07:15,100
about where is a potential 
weakness, what backdoor can an 

123
00:07:15,100 --> 00:07:19,300
attacker use in order to break 
into that software, it goes into

124
00:07:19,300 --> 00:07:22,500
the development process where of
course or developers are also 

125
00:07:22,500 --> 00:07:28,100
trained to develop securely. 
But also in our in addition to 

126
00:07:28,100 --> 00:07:31,600
that the code is scanned during 
the development process to see 

127
00:07:31,600 --> 00:07:33,100
if there's any roller. 
Abilities. 

128
00:07:33,100 --> 00:07:38,000
There there's a code scan or a 
application scan when the 

129
00:07:38,600 --> 00:07:43,300
application is ready to see if 
there's anything happening or 

130
00:07:43,300 --> 00:07:47,300
potentially happening in terms 
of vulnerabilities and that we 

131
00:07:47,300 --> 00:07:50,300
also have internal and external 
security assessment. 

132
00:07:50,300 --> 00:07:54,200
So penetration testing sore, 
hacking, simulation. 

133
00:07:54,200 --> 00:07:57,600
So this we even have a bug 
Bounty program. 

134
00:07:57,600 --> 00:08:02,400
So if someone wants to assist us
support us in securing Isfahan, 

135
00:08:03,000 --> 00:08:07,100
Clouds and they can sign up for 
the bug Bounty program and see 

136
00:08:07,100 --> 00:08:09,100
if they will find any 
vulnerabilities. 

137
00:08:09,100 --> 00:08:12,000
Because obviously, the more 
people were looking for 

138
00:08:12,000 --> 00:08:14,600
something, the more they will 
actually be able to find it. 

139
00:08:14,800 --> 00:08:18,500
So that's the first pillar, the 
secure software development and 

140
00:08:18,500 --> 00:08:23,500
we have basically all measures. 
You can think of in place to 

141
00:08:23,500 --> 00:08:25,800
make sure that we have the 
security development there. 

142
00:08:26,300 --> 00:08:31,200
Then the next pillar is the 
security features of the 

143
00:08:31,200 --> 00:08:34,900
software so to speak. 
So, ensuring that first of all 

144
00:08:35,000 --> 00:08:38,400
everything which is happening in
the software is secure which 

145
00:08:38,400 --> 00:08:43,900
includes things like encryption 
secure communication or even 

146
00:08:43,900 --> 00:08:48,000
when you install the software 
that settings, which are secured

147
00:08:48,000 --> 00:08:53,000
irrelevant per default, set to 
the secure setting, instead of 

148
00:08:53,000 --> 00:08:57,200
an insecure setting but it also 
includes security features. 

149
00:08:57,200 --> 00:09:01,100
So things like, can I check 
whether all of my settings are 

150
00:09:01,100 --> 00:09:03,700
secure. 
Can I actually, See what's 

151
00:09:03,700 --> 00:09:07,100
happening in my software in 
terms of who is logging on who 

152
00:09:07,100 --> 00:09:09,900
might have a failed log on so I 
can actually identify a 

153
00:09:09,900 --> 00:09:15,200
potential effect attack, so the 
security features and functions 

154
00:09:15,200 --> 00:09:20,500
built into the software as a 
second pillar and the sort of to

155
00:09:20,500 --> 00:09:24,500
a or second and a half pillar, 
you might call it is all today, 

156
00:09:24,500 --> 00:09:27,600
the data protection features, 
the compliant features, which 

157
00:09:27,700 --> 00:09:32,500
come with that. 
So can I lock access for just 

158
00:09:32,600 --> 00:09:35,600
Reading data, you know, if 
someone could be an Insider 

159
00:09:35,600 --> 00:09:38,800
actually is watching the or is 
looking at the salary 

160
00:09:38,800 --> 00:09:41,200
information from other 
employees, which they shouldn't 

161
00:09:41,200 --> 00:09:44,600
be allowed to do. 
I notice that at all by logging 

162
00:09:44,600 --> 00:09:47,900
vet, or I think the most 
important part when it comes to 

163
00:09:47,900 --> 00:09:51,200
data protection data, privacy, 
things like authorizations, 

164
00:09:51,400 --> 00:09:56,400
essentially, making sure that 
you can only do the things which

165
00:09:56,400 --> 00:09:59,700
are required for the job and not
more the key word. 

166
00:09:59,700 --> 00:10:02,500
Here is also very trendy keyword
in the past. 

167
00:10:02,600 --> 00:10:05,400
Do a trust. 
So security features and data 

168
00:10:05,400 --> 00:10:09,400
protection privacy features. 
Sort of two or one pillar 

169
00:10:09,400 --> 00:10:14,100
together and then in addition is
none, that especially important.

170
00:10:14,100 --> 00:10:16,900
When we talk about the cloud 
environment, of course, is the 

171
00:10:16,900 --> 00:10:20,600
secure equations. 
So how do we as sap as the cloud

172
00:10:20,600 --> 00:10:24,800
provider for as for Hannah? 
How do we make sure that the 

173
00:10:24,800 --> 00:10:28,500
cloud is secure and that is all 
on the infrastructure level? 

174
00:10:28,500 --> 00:10:31,900
So our data centers will start 
with the data center so the 

175
00:10:31,900 --> 00:10:35,500
physical All security, of 
course, you can enter the data 

176
00:10:35,500 --> 00:10:37,900
center. 
If you're not, authorized there 

177
00:10:37,900 --> 00:10:42,200
will be surveillance cameras. 
Quite literally, all equipment, 

178
00:10:42,200 --> 00:10:45,800
which is in there has to be, 
certified has to be checked, has

179
00:10:45,800 --> 00:10:48,400
to be validated. 
And then, if you look at the 

180
00:10:48,400 --> 00:10:51,400
next level, the the actual 
infrastructure of the data 

181
00:10:51,400 --> 00:10:54,500
center of the network. 
We have Network segregation, of 

182
00:10:54,500 --> 00:10:57,900
course, for our customers, we 
have tenant separation. 

183
00:10:57,900 --> 00:11:03,300
Terms of the databases, we have 
all other security Replacing the

184
00:11:03,300 --> 00:11:07,800
infrastructure, level things 
like firewall, or to prevention 

185
00:11:07,800 --> 00:11:11,000
systems, which is actually going
a little bit higher. 

186
00:11:11,000 --> 00:11:14,900
Again, in terms of now, we're 
looking at the vulnerabilities 

187
00:11:14,900 --> 00:11:18,200
of potentially, operating 
system, the database, where we 

188
00:11:18,200 --> 00:11:20,900
haven't threat detection in 
place, which is sort of the 

189
00:11:20,900 --> 00:11:23,300
Paulo to the secure software 
development. 

190
00:11:23,500 --> 00:11:28,400
When we look at the security of 
sap at the cloud provider, we do

191
00:11:28,400 --> 00:11:32,600
everything industry standard and
even beyond that and that It's 

192
00:11:32,600 --> 00:11:35,300
not just me saying that but 
that's actually certified. 

193
00:11:35,300 --> 00:11:38,100
So we have all the 
certifications which you need 

194
00:11:38,100 --> 00:11:42,400
ISO, 27001 all of the stock 
reports. 

195
00:11:42,500 --> 00:11:44,900
So basically and auditing 
company. 

196
00:11:44,900 --> 00:11:49,300
A testing towards the security 
of sap as a cloud provider. 

197
00:11:49,500 --> 00:11:54,500
So that's so to speak, is the 
last pillar, the secure 

198
00:11:54,500 --> 00:11:59,400
operations ensuring that our 
Cloud as a cloud provider is 

199
00:11:59,400 --> 00:12:03,400
actually secure. 
I have to admit, I didn't expect

200
00:12:03,400 --> 00:12:06,600
so many different aspects to be 
considered in terms of security.

201
00:12:07,200 --> 00:12:09,900
It's great to hear that sap puts
all those security features in 

202
00:12:09,908 --> 00:12:13,700
place to protect the data, what 
interests me as well is, if 

203
00:12:13,700 --> 00:12:16,700
there are any differences in 
terms of security between the 

204
00:12:16,700 --> 00:12:20,100
different deployment options, 
the main difference. 

205
00:12:20,100 --> 00:12:23,600
If you look at it from a 
customer point of view, is if 

206
00:12:23,600 --> 00:12:29,400
you have an S for Hannah system,
on-premise you are fully 

207
00:12:29,400 --> 00:12:32,600
responsible for the security of 
all the settings. 

208
00:12:32,600 --> 00:12:36,100
So that includes not only the 
extraña setting itself. 

209
00:12:36,400 --> 00:12:40,100
And even though, as I mentioned,
the software is developed 

210
00:12:40,100 --> 00:12:44,400
securely, were shipping it in a 
way that most of the, all that 

211
00:12:44,800 --> 00:12:49,500
most of the security relevant 
settings, actually set Purely. 

212
00:12:49,900 --> 00:12:54,400
But nevertheless, you are still 
responsible for everything which

213
00:12:54,400 --> 00:12:58,000
ones in your software, which for
some of the other site settings,

214
00:12:58,000 --> 00:13:01,500
which we might not technically 
be able to ship securely for 

215
00:13:01,500 --> 00:13:04,000
your custom coding. 
For example, it more 

216
00:13:04,000 --> 00:13:08,100
importantly, you're fully 
responsible for the security of 

217
00:13:08,100 --> 00:13:12,000
the infrastructure of the 
network of the operating system 

218
00:13:12,000 --> 00:13:14,900
of the database that everything 
is patched correctly and all 

219
00:13:14,900 --> 00:13:19,600
that kind of stuff. 
And you often hear the the the 

220
00:13:19,600 --> 00:13:23,700
argument that Y is a cloud more 
secure than an on-premise 

221
00:13:23,700 --> 00:13:26,300
environment. 
I think that would actually what

222
00:13:26,700 --> 00:13:29,400
comes down to when you talk 
about, you talk about security 

223
00:13:29,800 --> 00:13:34,800
and a good analogy, which I 
found in the past is a medieval 

224
00:13:34,800 --> 00:13:38,700
city to City. 
So if you have a medieval city 

225
00:13:38,700 --> 00:13:43,800
without a wall around it, and 
where everyone is responsible 

226
00:13:43,800 --> 00:13:48,500
for the security of their own 
house, a an army, which would 

227
00:13:48,500 --> 00:13:50,800
end The city, they have an easy 
game, right? 

228
00:13:50,800 --> 00:13:54,400
I mean, they can just walk into 
any house and even if you're 

229
00:13:55,400 --> 00:13:59,500
even if you have an archery and 
maybe you have a few soldiers in

230
00:13:59,500 --> 00:14:02,900
your house but they won't be 
able to get rid of all of the 

231
00:14:02,900 --> 00:14:05,900
Tigers. 
Now, the different thing is if 

232
00:14:05,900 --> 00:14:11,700
you have a wall around it which 
is staffed and paid for by the 

233
00:14:11,700 --> 00:14:15,000
city in general, but where 
everybody has to pay a little 

234
00:14:15,000 --> 00:14:18,900
bit in order to have that big 
bucket of money Okay. 

235
00:14:19,300 --> 00:14:23,500
So you know it's a lot easier 
with the wall and with soldiers 

236
00:14:23,500 --> 00:14:26,800
on the wall to defend against 
the Tigers and that's the same 

237
00:14:26,800 --> 00:14:31,100
thing when you talk about the 
difference between cloud and 

238
00:14:31,100 --> 00:14:35,100
on-premise. 
So although of course, the cloud

239
00:14:35,100 --> 00:14:38,100
is a bigger Target than just 
your single service sitting 

240
00:14:38,100 --> 00:14:40,200
somewhere in your in your own 
data center. 

241
00:14:40,800 --> 00:14:44,700
Nevertheless you just have more 
resources, more expertise and 

242
00:14:44,700 --> 00:14:48,700
more tools to be able to defend 
against evil. 

243
00:14:48,900 --> 00:14:52,300
Arch, number of Texas. 
So that's the basic difference 

244
00:14:52,300 --> 00:14:55,700
between on-premise and cloud and
then looking a little bit 

245
00:14:55,700 --> 00:14:59,400
further into the different 
deployment options for as a PS4,

246
00:14:59,400 --> 00:15:04,300
Hannah and particular. 
You have the public Cloud which 

247
00:15:04,300 --> 00:15:09,800
is a full software as a service.
So basically we as sap as a 

248
00:15:09,808 --> 00:15:13,500
cloud provider, are responsible 
for pretty much every aspect of 

249
00:15:13,508 --> 00:15:16,900
security. 
And this is something we do very

250
00:15:16,900 --> 00:15:20,600
well, there's still some things 
which you as a customer would 

251
00:15:20,600 --> 00:15:24,200
have to do things like 
authorizations and access 

252
00:15:24,200 --> 00:15:26,400
management. 
For example, if you look at the 

253
00:15:26,400 --> 00:15:30,500
next option to private Cloud, 
there's a little bit more 

254
00:15:30,500 --> 00:15:33,500
responsibility. 
Or the customer again. 

255
00:15:33,500 --> 00:15:37,300
So they are. 
This is essentially it's you can

256
00:15:37,300 --> 00:15:39,100
compare to a platform as a 
service. 

257
00:15:39,100 --> 00:15:42,500
So the application is such as 
one by you as a customer, which 

258
00:15:42,500 --> 00:15:45,600
gives you more flexibility, but 
also more responsibility, 

259
00:15:45,600 --> 00:15:48,800
especially in terms of security.
And last but not least. 

260
00:15:48,800 --> 00:15:52,300
Of course, I mentioned the 
on-premise version where you 

261
00:15:52,300 --> 00:15:57,300
have the full responsibility for
the application down to the 

262
00:15:57,300 --> 00:16:00,600
infrastructure level. 
That's a great analogy. 

263
00:16:00,800 --> 00:16:03,500
I'll definitely use it to if I 
need to explain this topic to 

264
00:16:03,500 --> 00:16:06,700
someone else. 
I think in one of your blog 

265
00:16:06,700 --> 00:16:10,000
posts you wrote about external 
security verification for scps 

266
00:16:10,000 --> 00:16:12,200
for Hannah. 
I'm sure the bug Bounty program.

267
00:16:12,200 --> 00:16:14,200
You mentioned earlier is part of
that as well. 

268
00:16:14,500 --> 00:16:16,500
Can you elaborate a little bit 
on that? 

269
00:16:17,300 --> 00:16:21,300
Yeah, the back Bounty program is
in general maybe to start off. 

270
00:16:21,300 --> 00:16:23,100
What is the background to 
program? 

271
00:16:23,400 --> 00:16:26,400
Back on the program is, 
essentially, you have where you 

272
00:16:26,400 --> 00:16:30,700
have external researchers 
looking at your software and see

273
00:16:30,700 --> 00:16:33,700
if they find any type of 
vulnerability or bug. 

274
00:16:34,000 --> 00:16:37,800
And if one of these Researchers 
find something, they will be 

275
00:16:37,800 --> 00:16:41,000
rewarded depending on the 
criticality of the 

276
00:16:41,000 --> 00:16:44,700
vulnerability. 
They will be, we wanted a payout

277
00:16:44,700 --> 00:16:48,200
percentage and we've done that 
sap. 

278
00:16:48,200 --> 00:16:51,100
We actually been busy with 
establishing background to 

279
00:16:51,100 --> 00:16:55,000
programs since I think, 2018, or
2017. 

280
00:16:55,000 --> 00:17:00,800
Even and at first, it was a 
small number, but we as far as 

281
00:17:00,800 --> 00:17:04,700
one of the core product of sap, 
we started our background to 

282
00:17:04,700 --> 00:17:09,500
program. 
In 2019, which back then was an 

283
00:17:09,500 --> 00:17:13,700
on-premise back Bounty program. 
So people could actually find 

284
00:17:13,700 --> 00:17:16,700
and all try to find 
vulnerabilities in the 

285
00:17:16,700 --> 00:17:20,300
on-premise version. 
But since recently, we also 

286
00:17:20,300 --> 00:17:22,900
expanded that to the S4 on the 
cloud. 

287
00:17:22,900 --> 00:17:26,500
So now, we essentially have both
and as for an on-premise systems

288
00:17:26,500 --> 00:17:31,000
and an F on a cloud system, 
where security researchers can 

289
00:17:31,000 --> 00:17:34,600
take the look at and see if they
would find any vulnerabilities 

290
00:17:34,900 --> 00:17:39,000
and In general is back Bounty. 
Programs are usually done with 

291
00:17:39,000 --> 00:17:41,300
platform. 
So third party providers because

292
00:17:41,300 --> 00:17:47,100
they basically have the task to 
collect all these security 

293
00:17:47,100 --> 00:17:50,200
researchers from around the 
world, signed them up, and then 

294
00:17:50,500 --> 00:17:54,500
sell them sign a Target to them 
which in our case would be as 

295
00:17:54,500 --> 00:17:56,500
for Hannah. 
So we're working together with 

296
00:17:56,500 --> 00:17:59,500
the third party platform there 
in order to get enough 

297
00:17:59,500 --> 00:18:03,400
researchers to actually have a 
meaningful bug Bounty program 

298
00:18:03,700 --> 00:18:06,600
and it has been very successful.
Peaceful, I think the, the 

299
00:18:06,600 --> 00:18:10,200
average payout or as for Hannah 
in the past was something around

300
00:18:10,200 --> 00:18:15,900
2,000 Euros or dollars and the 
vulnerabilities that they found 

301
00:18:15,900 --> 00:18:20,500
were two, I think 73 or 74 
percent to positive. 

302
00:18:20,500 --> 00:18:22,900
So it was actually 
vulnerabilities which were 

303
00:18:22,900 --> 00:18:26,400
actually they're very often. 
We have also false positives 

304
00:18:26,400 --> 00:18:30,100
where security researcher says. 
Okay this isn't vulnerability 

305
00:18:30,100 --> 00:18:33,200
when in fact it's not but as I 
said, 75%. 

306
00:18:33,200 --> 00:18:37,000
So three-fourth of the 
Vulnerabilities that were found 

307
00:18:37,000 --> 00:18:40,400
by researchers actually turned 
out to be a vulnerability is, 

308
00:18:40,400 --> 00:18:44,300
which obviously it's a big added
value to us because it helps us 

309
00:18:44,500 --> 00:18:47,000
securing a software better in 
the future. 

310
00:18:48,200 --> 00:18:50,900
We've already talked about 
Security in general, let's be a 

311
00:18:50,900 --> 00:18:53,600
bit more specific and talk about
data protection and data 

312
00:18:53,600 --> 00:18:55,600
privacy. 
Can you tell us a little bit 

313
00:18:55,600 --> 00:18:58,700
about that? 
The think the first thing to 

314
00:18:58,700 --> 00:19:04,300
note is that the customer is 
still responsible for their 

315
00:19:04,300 --> 00:19:07,100
data, of course. 
But we, as a cloud provider are 

316
00:19:07,100 --> 00:19:11,300
responsible to protect the data 
of our customers as best as 

317
00:19:11,300 --> 00:19:15,100
possible. 
And for that, there are we use 

318
00:19:15,100 --> 00:19:19,000
several tools and measures. 
I mentioned the Operational part

319
00:19:19,000 --> 00:19:21,700
for the Isfahan. 
A cloud. 

320
00:19:21,700 --> 00:19:26,000
So basically the cloud Center 
the data center which were 

321
00:19:26,000 --> 00:19:30,200
securing, I've also mentioned 
the secure software development 

322
00:19:30,200 --> 00:19:33,400
and the security features and I 
think this is where it gets 

323
00:19:33,400 --> 00:19:36,200
interesting for the customer, 
the security data protection 

324
00:19:36,200 --> 00:19:40,900
features. 
So, What is data protection 

325
00:19:41,200 --> 00:19:43,600
really about? 
It's about one thing data 

326
00:19:43,600 --> 00:19:48,300
protection, which is making sure
that the customer data is not 

327
00:19:48,300 --> 00:19:51,900
reached somehow, but it's also 
about privacy features. 

328
00:19:51,900 --> 00:19:57,200
So the possibility of the 
consumer or customer or employee

329
00:19:57,200 --> 00:20:02,900
Steven to have responsibilities 
on their own data and also the, 

330
00:20:02,900 --> 00:20:05,700
you know, know know where your 
data is and what you can 

331
00:20:05,700 --> 00:20:09,100
actually do with that. 
And for that particular, The 

332
00:20:09,100 --> 00:20:14,100
Privacy feature, we have several
things inside as for Hannah and 

333
00:20:14,200 --> 00:20:17,900
obviously also, as far as the 
cloud, I'd like to mention two 

334
00:20:18,200 --> 00:20:21,600
features here, which I 
personally find very interesting

335
00:20:21,600 --> 00:20:24,700
and helpful for data. 
Privacy one is the information 

336
00:20:24,700 --> 00:20:29,500
lifecycle management because the
gdpr States among other things, 

337
00:20:29,500 --> 00:20:35,200
of course, says that you can 
only keep data for as long as 

338
00:20:35,200 --> 00:20:38,800
you actually need the data or 
where the purpose of the data. 

339
00:20:38,900 --> 00:20:42,500
Is required for and 42 listing 
information. 

340
00:20:42,500 --> 00:20:45,100
Lifecycle management is perfect 
because you can essentially say,

341
00:20:45,100 --> 00:20:48,500
okay, take the example of a 
customer who's buying something 

342
00:20:48,500 --> 00:20:51,300
with your online shop? 
Then you can actually say, okay,

343
00:20:51,300 --> 00:20:56,100
once the purchase is completed 
and of course, there's some 

344
00:20:56,100 --> 00:21:00,200
other regulations where you need
to keep the order data for a 

345
00:21:00,300 --> 00:21:03,300
specific period of time. 
But nevertheless all other data 

346
00:21:03,300 --> 00:21:07,200
you can then delete from that 
customer and you can you know, 

347
00:21:07,200 --> 00:21:11,300
as a consumer you can Aspartate.
Can you please delete my data 

348
00:21:11,500 --> 00:21:14,200
and with information, lifecycle 
management, you will be able to 

349
00:21:14,200 --> 00:21:18,300
do that very, very easily. 
The other thing is, I already 

350
00:21:18,300 --> 00:21:20,500
mentioned think is the read 
access logging. 

351
00:21:20,700 --> 00:21:26,600
So in the past you could only 
Trace if someone actually 

352
00:21:26,600 --> 00:21:30,100
changed data. 
So someone is going into a 

353
00:21:31,400 --> 00:21:34,900
consumer data set and maybe 
changing the name or something 

354
00:21:35,100 --> 00:21:38,300
might be an exaggerated example,
but that is something you could 

355
00:21:38,300 --> 00:21:41,800
always as you were always able 
to track in the past with read 

356
00:21:41,800 --> 00:21:44,500
access logging. 
We're even we even have the 

357
00:21:44,500 --> 00:21:47,700
possibility to track if someone 
it's just looking at the data 

358
00:21:48,100 --> 00:21:51,800
and that in itself, if you think
of I mentioned, the example of 

359
00:21:52,600 --> 00:21:56,800
salaries that is something which
is helpful because obviously 

360
00:21:57,000 --> 00:22:00,500
just because someone has some 
authorization, because it's, 

361
00:22:00,500 --> 00:22:02,500
he's in the IT department or 
whatever. 

362
00:22:03,000 --> 00:22:05,900
Doesn't mean you should be able 
to look at your celery and when 

363
00:22:06,100 --> 00:22:10,100
we taxes longing, that something
we can effectively The prevent 

364
00:22:10,200 --> 00:22:13,500
from happening. 
What about new functionalities? 

365
00:22:13,700 --> 00:22:16,700
What kind of enhancements were 
shipped with the latest sap s1r 

366
00:22:16,700 --> 00:22:18,600
Cloud release. 
In terms of security. 

367
00:22:19,800 --> 00:22:23,500
Well, when the security 
features, a lot of the features 

368
00:22:23,500 --> 00:22:27,700
which we ship with new releases 
are sort of under the hood. 

369
00:22:27,700 --> 00:22:31,400
So it's not something which you 
as a customer would actually 

370
00:22:31,400 --> 00:22:34,000
notice. 
It is things like secure by 

371
00:22:34,000 --> 00:22:34,700
default. 
So weird. 

372
00:22:34,700 --> 00:22:39,100
If we were securing more of the 
settings in the PS4 on the cloud

373
00:22:39,100 --> 00:22:43,300
as well, one highlight which I 
like to find out because in 

374
00:22:43,300 --> 00:22:47,300
various ways it's important for 
security, it's a security audit 

375
00:22:47,300 --> 00:22:50,700
log and a security audit log is 
Something which has been in 

376
00:22:50,700 --> 00:22:55,700
place in the backbone of the, 
what is now, as for Hannah, in 

377
00:22:55,700 --> 00:23:01,100
general for years, it was 
already implemented in Zombies 

378
00:23:01,100 --> 00:23:05,300
to see when. 
So before the S400 types, and of

379
00:23:05,300 --> 00:23:10,200
course, it's also been available
in the as far on a cloud. 

380
00:23:10,300 --> 00:23:14,800
However, until recently as a 
customer, you would have to 

381
00:23:14,800 --> 00:23:19,000
manually extract the security 
audit log from the system. 

382
00:23:19,600 --> 00:23:23,400
And what we've done now is we 
established a pi. 

383
00:23:23,600 --> 00:23:29,200
So basically, you now have the 
possibility to continuously 

384
00:23:29,200 --> 00:23:33,100
retrieve the data from the as 
far on a cloud system. 

385
00:23:33,100 --> 00:23:37,700
And why is it important? 
Well, the security audit log 

386
00:23:37,700 --> 00:23:40,600
contains information such as 
failed log on. 

387
00:23:40,600 --> 00:23:45,800
So some someone is mistyping his
or her passwords, so he's not be

388
00:23:45,800 --> 00:23:49,000
able to log on. 
That will be locked in the 

389
00:23:49,600 --> 00:23:53,800
Farhana security, audit lock 
things, like what terminal did 

390
00:23:54,000 --> 00:23:57,100
that user use to log on to the 
system? 

391
00:23:57,200 --> 00:24:00,900
Will also be new location. 
Essentially, what applications 

392
00:24:00,900 --> 00:24:03,900
what apps did he start when in 
the system? 

393
00:24:03,900 --> 00:24:07,500
So these are all information 
which might be security 

394
00:24:07,500 --> 00:24:10,400
development. 
Not if someone does his regular 

395
00:24:10,400 --> 00:24:12,000
job, they're not security 
relevant. 

396
00:24:12,000 --> 00:24:15,200
But as soon as something out of 
the ordinary happens that become

397
00:24:15,200 --> 00:24:19,000
security element of the relevant
and there's tools are solutions 

398
00:24:19,000 --> 00:24:20,800
out there. 
R which are just looking for 

399
00:24:20,800 --> 00:24:26,600
these anomalies and analyzing 
whether this is actually an 

400
00:24:26,800 --> 00:24:30,300
ongoing attack and with the API 
we have made it possible that 

401
00:24:30,300 --> 00:24:33,200
you don't need to but you don't 
have to manually retrieve the 

402
00:24:33,200 --> 00:24:38,200
data but we can continue or the 
security information and event 

403
00:24:38,200 --> 00:24:40,300
management systems. 
That's the name of these 

404
00:24:40,300 --> 00:24:43,800
Solutions. 
Also shortened to zeem these 

405
00:24:43,800 --> 00:24:48,100
seem systems can continuously 
retrieve that information from 

406
00:24:48,100 --> 00:24:54,700
the system and Therefore able to
detect and potential attack 

407
00:24:54,900 --> 00:24:58,900
almost in real time and these 
kind of security enhancements we

408
00:24:58,900 --> 00:25:01,500
do. 
Obviously, we try to do as often

409
00:25:01,500 --> 00:25:06,400
as possible and there will be 
additional things coming up a 

410
00:25:06,400 --> 00:25:09,700
lot of or some of them actually 
have to do with other locks, but

411
00:25:09,700 --> 00:25:12,800
you're also making available 
through an API. 

412
00:25:13,100 --> 00:25:16,900
But then again, if you look at 
the releases in general quite a 

413
00:25:16,908 --> 00:25:22,000
lot of security enhancements are
under The hood so more to make 

414
00:25:22,000 --> 00:25:24,400
it as far on a cloud even more 
secure than it already. 

415
00:25:24,400 --> 00:25:28,000
Is we've already talked quite a 
bit about a functionalities and 

416
00:25:28,000 --> 00:25:29,600
features that are already 
available. 

417
00:25:30,100 --> 00:25:32,600
How does the future in terms of 
security look like? 

418
00:25:33,400 --> 00:25:37,500
That is a very very good 
question and I think it also 

419
00:25:37,500 --> 00:25:39,500
depends on what kind of future 
you looking at. 

420
00:25:39,500 --> 00:25:44,500
I mean, one thing, which will 
probably be very interesting in 

421
00:25:44,500 --> 00:25:48,900
the coming five, to ten years, 
will be the rise of quantum 

422
00:25:48,900 --> 00:25:52,600
computers. 
Because quantum computers are 

423
00:25:52,600 --> 00:25:58,100
able or will be able to 
basically render quite a few of 

424
00:25:58,100 --> 00:26:03,900
our encryption capabilities 
useless but not limited to sap 

425
00:26:03,900 --> 00:26:07,000
that limited to the entire it 
world. 

426
00:26:07,100 --> 00:26:10,400
So you know, I'm really looking 
forward to in a bit from 

427
00:26:10,400 --> 00:26:13,200
security scanning that 
perspective, what will be 

428
00:26:13,200 --> 00:26:16,800
happening when there will be 
actually in the good quantum 

429
00:26:16,800 --> 00:26:21,900
computer, which is useful so far
the quad Computers are not yet 

430
00:26:21,900 --> 00:26:24,200
able to do that but they will be
that's for sure. 

431
00:26:24,500 --> 00:26:27,800
And what we've done from from 
sap site or maybe just to eat to

432
00:26:27,800 --> 00:26:31,300
put the audience at ease. 
We've done quite a bit of 

433
00:26:31,300 --> 00:26:34,200
research into Quantum safe 
cryptography. 

434
00:26:34,200 --> 00:26:37,300
So making sure that the 
encryption we are using is also 

435
00:26:37,600 --> 00:26:42,300
secure against a tech from 
country computer and yeah, 

436
00:26:42,300 --> 00:26:45,100
that's that's a topic, which is 
sort of dear to my heart, so, to

437
00:26:45,100 --> 00:26:48,600
speak. 
If you look at the future of 

438
00:26:48,600 --> 00:26:52,400
security in More short term. 
I think we will see a lot of 

439
00:26:52,500 --> 00:26:57,100
consolidation in terms of also 
security functionalities. 

440
00:26:57,100 --> 00:27:01,200
If you I mentioned the term zero
trust earlier, which essentially

441
00:27:01,200 --> 00:27:05,700
says, if we stay with the 
analogy of a medieval city in 

442
00:27:05,700 --> 00:27:08,600
the past, you know, once once 
you've crossed the wall and you 

443
00:27:08,600 --> 00:27:12,000
were inside the city, you can do
pretty much anything in the city

444
00:27:12,500 --> 00:27:15,000
with zero. 
Trust that you basically are 

445
00:27:15,000 --> 00:27:17,700
restricted even further. 
So even if you go into the City 

446
00:27:17,700 --> 00:27:20,800
and you cross the Wall, you 
we'll still be, I don't know 

447
00:27:20,800 --> 00:27:23,100
what's true. 
That you only have that 

448
00:27:23,100 --> 00:27:25,900
particular path and you can only
go to a particular room. 

449
00:27:26,100 --> 00:27:31,000
So very granular, authorization 
is one of the main Concepts on 

450
00:27:31,000 --> 00:27:32,900
zero trust and that's funnily 
enough. 

451
00:27:32,900 --> 00:27:36,200
That's something which from a 
technical point of view, sap has

452
00:27:36,200 --> 00:27:38,500
been able to do for ages 
literally. 

453
00:27:38,800 --> 00:27:42,900
I mean, that that was already 
part of the the R3 system back 

454
00:27:42,900 --> 00:27:45,600
in the nineties. 
But that's, that's picking up a 

455
00:27:45,608 --> 00:27:48,500
little bit more. 
So there's a consolation of the 

456
00:27:48,500 --> 00:27:53,900
various sort of Stages of 
security but again for a 

457
00:27:53,900 --> 00:27:58,300
short-term outlook on security 
and we will probably see more of

458
00:27:58,300 --> 00:28:01,800
a sort of incremental 
enhancements on security rather 

459
00:28:01,800 --> 00:28:05,000
than sort of the big leap into 
something particular. 

460
00:28:05,000 --> 00:28:09,100
But again, there's other topics 
which will rise in the more mid 

461
00:28:09,100 --> 00:28:12,900
term to long term future Quantum
cryptology the blockchain. 

462
00:28:12,900 --> 00:28:16,300
Artificial intelligence will be 
something which will be very 

463
00:28:16,300 --> 00:28:19,200
interesting also in security. 
So these are the short-term 

464
00:28:19,200 --> 00:28:21,300
things. 
And of course as sap. 

465
00:28:21,300 --> 00:28:25,400
And even as we as far as 
security team were keeping up 

466
00:28:25,400 --> 00:28:29,300
with the development here and 
ensuring that we will secure the

467
00:28:29,300 --> 00:28:32,400
Isfahan, a cloud even against 
more sophisticated attacks and 

468
00:28:32,400 --> 00:28:34,700
future. 
This brings us to the last 

469
00:28:34,700 --> 00:28:38,200
question of today's episode. 
In your opinion, what are the 

470
00:28:38,200 --> 00:28:40,100
key? 
Takeaways of today's episode for

471
00:28:40,100 --> 00:28:43,500
someone who has not paid much 
attention to security, or is 

472
00:28:43,500 --> 00:28:46,300
unsure about the security of sap
as far on a cloud. 

473
00:28:47,400 --> 00:28:50,900
If you look at as far on a 
cloud, I think the key takeaways

474
00:28:51,100 --> 00:28:54,000
are so to speak. 
We fault one of the key 

475
00:28:54,000 --> 00:28:59,600
takeaways I would say is that we
have a very securely developed 

476
00:28:59,600 --> 00:29:03,400
software. 
So, as far as a software is 

477
00:29:03,500 --> 00:29:08,300
definitely secure, if you look 
at it more from a cloud 

478
00:29:08,300 --> 00:29:13,000
perspective, it goes a little 
bit into the same direction by 

479
00:29:13,000 --> 00:29:17,600
saying that the operations we 
have is not only Industry 

480
00:29:17,600 --> 00:29:21,800
standard, but I personally think
and I said I've been in the 

481
00:29:21,808 --> 00:29:26,300
security area area for decades. 
Now sap is doing a really good 

482
00:29:26,300 --> 00:29:30,500
job in securing as for Hannah 
clouds. 

483
00:29:30,500 --> 00:29:33,800
And if you look at it from a, 
from a cloud perspective, and 

484
00:29:33,800 --> 00:29:39,800
then last but not least, I think
the last key takeaway is that we

485
00:29:39,800 --> 00:29:44,800
as sap do not think of security 
as an afterthought, but we 

486
00:29:44,800 --> 00:29:49,100
actually look at it from a sort 
of Holistic point of view so 

487
00:29:49,100 --> 00:29:53,400
across everything starting from 
the software development to the 

488
00:29:53,900 --> 00:29:58,600
operations, but even if you look
at inside sap, even people who 

489
00:29:58,600 --> 00:30:04,800
are not in security, they are 
also trained in security. 

490
00:30:05,100 --> 00:30:06,800
They have to do security 
trainings. 

491
00:30:06,800 --> 00:30:09,000
Every once in a while to keep up
to date. 

492
00:30:09,200 --> 00:30:12,600
And yeah, if you would summarize
that in a sentence, I would say 

493
00:30:12,600 --> 00:30:16,300
that sap. 
And as IPS for Hannah adheres to

494
00:30:16,300 --> 00:30:20,800
and goes Ian leading industry 
standards and I think Commerce 

495
00:30:21,200 --> 00:30:25,000
technology operations and even 
legal measures and regulations. 

496
00:30:25,000 --> 00:30:29,100
When you talk about data privacy
protection, Thanks Patrick for 

497
00:30:29,100 --> 00:30:31,600
joining me today and providing 
this valuable insights. 

498
00:30:31,700 --> 00:30:34,100
It was a real pleasure to speak 
with you and learn more about 

499
00:30:34,100 --> 00:30:36,200
this complex. 
But highly, important topic. 

500
00:30:36,800 --> 00:30:38,200
Thank you for having me was the 
tiger. 

501
00:30:38,400 --> 00:30:41,300
Thanks a big. 
Thank you to our listeners as 

502
00:30:41,300 --> 00:30:43,300
well. 
Keep an eye out for our next 

503
00:30:43,300 --> 00:30:45,900
episode. 
On opensap, I hope you will join

504
00:30:45,900 --> 00:30:50,400
me again until then as a PS4, 
Hannah followers, stay tuned and

505
00:30:50,400 --> 00:30:51,300
stay safe.
