
Inside SAP S/4HANA by Solution Management EP05: SAP's approach towards security and compliance in the cloud
Audio and video play straight from the show's own hosting. PodSubs stores and serves no media.

Audio and video play straight from the show's own hosting. PodSubs stores and serves no media.
Good morning, good afternoon, and good evening, to all our sap S400 followers. My name is Marvin Posh and today, you are listening to the fifth episode of the new inside as a foreigner podcast. We'll sit by solution management. Through a successful digitization companies, expect efficiency gains and cost savings, important factors. The daily competition. However, the change is accompanied by a continuously changing threat landscape by evolving, cyber criminals, hackers, and economic spice to counteract the threat. Landscape Securities and indispensable.
Topic. That every company should value today. I have invited my sap colleague, Patrick Bach to address this topic. We are going to talk in general about security and the steps I say p tags to ensure data. Section and data security for sap as funnel cloud. Hi Patrick. Hi, Marvin. How are you? I'm really excited to have you as my guest today. It would be great if you could briefly introduce yourself to the audience. Yes. Thank you for having me. My name is Patrick ball and I'm the product manager for as far as security, which does not only
cover as for Hana Cloud but also the two other flavors so to speak meaning, as far as on-premise and as far Hana Cloud, private addition and I rejoined. I must say sap in 2020. I've been with sap before from 2001 to 2006, so during the new economy time, but afterwards, I went into the sap security space, in general and since
2020, as I mentioned, now responsible for securing, as for Hannah, thanks for the introduction. The topic of data protection and dead. Privacy has gained enormous importance in the last few years. We all know that there are multiple reasons for that. For example, the introduction of the general data protection regulation in 2018 and to several data breaches reported by bacon well-known companies. Such as Microsoft or Facebook, what do you think is the current attitude towards security? I think it's improving from a perspective of someone who is in security or inside the security
to be precise. It wasn't that before I was everyone always We thought that security is something where you say, okay, yeah, we might have to do that but it's not that important. But because of the GDP are, which has heavy fines if you don't do proper security and also because of some of the data breaches we have heard about in the past few months, and years. I think people take it a lot more seriously than they used to.
I totally agree. I think you're definitely see a change if you compare the current attitude. With the one, a couple of years ago. Do you think this is may be different depending on the size of the company or industry? Unfortunately, yes, it's always will not always the case but I think that especially bigger companies, they know that there's an issue that they need to do something, but smaller companies, medium-sized companies. They sometimes, first of all, it's because of a lack of resources. So they literally don't have neither the people nor The
knowledge to do a good security. So they are sometimes left out, but sometimes it's also a little bit of an attitude because they still think they need to focus on their Core Business. And then unfortunately, security sometimes sort of falls behind I think for the small companies, especially for, if you might call them startups. So, young company, so to speak. I think they are more aware of the security issue. Hopefully them was worth the security.
They would probably have a more or better attitude towards security, but I think that also plays into the cloud business and something we will discuss I think during the course of this podcast, that's correct. We will talk about cloud in a second but before that, I would like to get some insights into why the topic shouldn't be neglected by companies. You essentially mentioned it into your, in the main reasons you mentioned in your introduction. One of the reasons is Is, of course, the GDP are the data
protection regulation because as I mentioned, there are heavy fines. If you can prove that you've done a proper security job or proper job in securing the data that might actually lead to a fine of up to I think four percent of your yearly Revenue, which can be really heavy on especially companies with the low margin there. But companies, in general for percent, that's a quite a bit and then, but this is just Regulations on security put into
a regulation. The main reason I think is just the other issues, the other problems which you can have. If you don't do proper security, you mentioned data, breaches and data breaches. We also hear a lot about in the past is something like when somewhere. So if you don't have proper security, it can actually happen that someone would be packing, you would be attacking you with the rent somewhere and then all of your data are lost and you either have to buy it. It back. But then you also have to hope that the attack has actually
also giving it back once you pay. And even if that all of this works out, well then you still had might have an image problem because you will probably have to inform your customers that you have been breached and the reputation loss of reputation damage. It's also something that you need to take care of, not to mention the data, which might be a stone. So, I think security is something which is essential to
any business and therefore it should also be treated as being essential, and not something which you would do as an afterthought which unfortunately was the case in the past. Very often. I know that security has always been an important element for the Complete product life. Cycle of all, I said he products including product development planning and quality assurance. What is in place to secure a comprehensive solution like sap as for Hanukkah? Loud. This is something where you probably have to distinguish between why would see it as
different pillars. So the first pillar of course is the secure development of the software itself. So how do we ensure that the software has as little vulnerabilities is possible that the software itself is secure and therefore we have quite a bit or quite a few measures in place actually, which if you start from, if you look at the development lifecycle From the start, it starts with threat modeling. So you know when you when you actually develop the blueprint of your app, you need to think
about where is a potential weakness, what backdoor can an attacker use in order to break into that software, it goes into the development process where of course or developers are also trained to develop securely. But also in our in addition to that the code is scanned during the development process to see if there's any roller. Abilities. There there's a code scan or a application scan when the application is ready to see if there's anything happening or
potentially happening in terms of vulnerabilities and that we also have internal and external security assessment. So penetration testing sore, hacking, simulation. So this we even have a bug Bounty program. So if someone wants to assist us support us in securing Isfahan, Clouds and they can sign up for the bug Bounty program and see if they will find any vulnerabilities. Because obviously, the more people were looking for something, the more they will actually be able to find it.
So that's the first pillar, the secure software development and we have basically all measures. You can think of in place to make sure that we have the security development there. Then the next pillar is the security features of the software so to speak. So, ensuring that first of all everything which is happening in the software is secure which includes things like encryption secure communication or even when you install the software that settings, which are secured
irrelevant per default, set to the secure setting, instead of an insecure setting but it also includes security features. So things like, can I check whether all of my settings are secure. Can I actually, See what's happening in my software in terms of who is logging on who might have a failed log on so I can actually identify a potential effect attack, so the security features and functions built into the software as a second pillar and the sort of to
a or second and a half pillar, you might call it is all today, the data protection features, the compliant features, which come with that. So can I lock access for just Reading data, you know, if someone could be an Insider actually is watching the or is looking at the salary information from other employees, which they shouldn't be allowed to do. I notice that at all by logging vet, or I think the most important part when it comes to data protection data, privacy, things like authorizations,
essentially, making sure that you can only do the things which are required for the job and not more the key word. Here is also very trendy keyword in the past. Do a trust. So security features and data protection privacy features. Sort of two or one pillar together and then in addition is none, that especially important. When we talk about the cloud environment, of course, is the secure equations. So how do we as sap as the cloud provider for as for Hannah? How do we make sure that the
cloud is secure and that is all on the infrastructure level? So our data centers will start with the data center so the physical All security, of course, you can enter the data center. If you're not, authorized there will be surveillance cameras. Quite literally, all equipment, which is in there has to be, certified has to be checked, has to be validated. And then, if you look at the next level, the the actual infrastructure of the data center of the network. We have Network segregation, of course, for our customers, we have tenant separation.
Terms of the databases, we have all other security Replacing the infrastructure, level things like firewall, or to prevention systems, which is actually going a little bit higher. Again, in terms of now, we're looking at the vulnerabilities of potentially, operating system, the database, where we haven't threat detection in place, which is sort of the Paulo to the secure software development. When we look at the security of sap at the cloud provider, we do
everything industry standard and even beyond that and that It's not just me saying that but that's actually certified. So we have all the certifications which you need ISO, 27001 all of the stock reports. So basically and auditing company. A testing towards the security of sap as a cloud provider. So that's so to speak, is the last pillar, the secure operations ensuring that our Cloud as a cloud provider is
actually secure. I have to admit, I didn't expect so many different aspects to be considered in terms of security. It's great to hear that sap puts all those security features in place to protect the data, what interests me as well is, if there are any differences in terms of security between the different deployment options, the main difference. If you look at it from a customer point of view, is if you have an S for Hannah system, on-premise you are fully
responsible for the security of all the settings. So that includes not only the extraña setting itself. And even though, as I mentioned, the software is developed securely, were shipping it in a way that most of the, all that most of the security relevant settings, actually set Purely. But nevertheless, you are still responsible for everything which ones in your software, which for some of the other site settings, which we might not technically be able to ship securely for
your custom coding. For example, it more importantly, you're fully responsible for the security of the infrastructure of the network of the operating system of the database that everything is patched correctly and all that kind of stuff. And you often hear the the the argument that Y is a cloud more secure than an on-premise environment. I think that would actually what comes down to when you talk about, you talk about security and a good analogy, which I found in the past is a medieval
city to City. So if you have a medieval city without a wall around it, and where everyone is responsible for the security of their own house, a an army, which would end The city, they have an easy game, right? I mean, they can just walk into any house and even if you're even if you have an archery and maybe you have a few soldiers in your house but they won't be able to get rid of all of the Tigers. Now, the different thing is if
you have a wall around it which is staffed and paid for by the city in general, but where everybody has to pay a little bit in order to have that big bucket of money Okay. So you know it's a lot easier with the wall and with soldiers on the wall to defend against the Tigers and that's the same thing when you talk about the difference between cloud and on-premise. So although of course, the cloud is a bigger Target than just your single service sitting
somewhere in your in your own data center. Nevertheless you just have more resources, more expertise and more tools to be able to defend against evil. Arch, number of Texas. So that's the basic difference between on-premise and cloud and then looking a little bit further into the different deployment options for as a PS4, Hannah and particular. You have the public Cloud which is a full software as a service. So basically we as sap as a
cloud provider, are responsible for pretty much every aspect of security. And this is something we do very well, there's still some things which you as a customer would have to do things like authorizations and access management. For example, if you look at the next option to private Cloud, there's a little bit more responsibility. Or the customer again. So they are. This is essentially it's you can compare to a platform as a service. So the application is such as one by you as a customer, which
gives you more flexibility, but also more responsibility, especially in terms of security. And last but not least. Of course, I mentioned the on-premise version where you have the full responsibility for the application down to the infrastructure level. That's a great analogy. I'll definitely use it to if I need to explain this topic to someone else. I think in one of your blog posts you wrote about external security verification for scps for Hannah. I'm sure the bug Bounty program. You mentioned earlier is part of that as well.
Can you elaborate a little bit on that? Yeah, the back Bounty program is in general maybe to start off. What is the background to program? Back on the program is, essentially, you have where you have external researchers looking at your software and see if they find any type of vulnerability or bug. And if one of these Researchers find something, they will be rewarded depending on the criticality of the vulnerability. They will be, we wanted a payout
percentage and we've done that sap. We actually been busy with establishing background to programs since I think, 2018, or 2017. Even and at first, it was a small number, but we as far as one of the core product of sap, we started our background to program. In 2019, which back then was an on-premise back Bounty program. So people could actually find and all try to find vulnerabilities in the
on-premise version. But since recently, we also expanded that to the S4 on the cloud. So now, we essentially have both and as for an on-premise systems and an F on a cloud system, where security researchers can take the look at and see if they would find any vulnerabilities and In general is back Bounty. Programs are usually done with platform. So third party providers because they basically have the task to collect all these security
researchers from around the world, signed them up, and then sell them sign a Target to them which in our case would be as for Hannah. So we're working together with the third party platform there in order to get enough researchers to actually have a meaningful bug Bounty program and it has been very successful. Peaceful, I think the, the average payout or as for Hannah in the past was something around 2,000 Euros or dollars and the vulnerabilities that they found were two, I think 73 or 74 percent to positive.
So it was actually vulnerabilities which were actually they're very often. We have also false positives where security researcher says. Okay this isn't vulnerability when in fact it's not but as I said, 75%. So three-fourth of the Vulnerabilities that were found by researchers actually turned out to be a vulnerability is, which obviously it's a big added value to us because it helps us securing a software better in the future. We've already talked about Security in general, let's be a
bit more specific and talk about data protection and data privacy. Can you tell us a little bit about that? The think the first thing to note is that the customer is still responsible for their data, of course. But we, as a cloud provider are responsible to protect the data of our customers as best as possible. And for that, there are we use several tools and measures. I mentioned the Operational part for the Isfahan. A cloud.
So basically the cloud Center the data center which were securing, I've also mentioned the secure software development and the security features and I think this is where it gets interesting for the customer, the security data protection features. So, What is data protection really about? It's about one thing data protection, which is making sure that the customer data is not reached somehow, but it's also about privacy features.
So the possibility of the consumer or customer or employee Steven to have responsibilities on their own data and also the, you know, know know where your data is and what you can actually do with that. And for that particular, The Privacy feature, we have several things inside as for Hannah and obviously also, as far as the cloud, I'd like to mention two features here, which I personally find very interesting and helpful for data. Privacy one is the information
lifecycle management because the gdpr States among other things, of course, says that you can only keep data for as long as you actually need the data or where the purpose of the data. Is required for and 42 listing information. Lifecycle management is perfect because you can essentially say, okay, take the example of a customer who's buying something with your online shop? Then you can actually say, okay, once the purchase is completed and of course, there's some
other regulations where you need to keep the order data for a specific period of time. But nevertheless all other data you can then delete from that customer and you can you know, as a consumer you can Aspartate. Can you please delete my data and with information, lifecycle management, you will be able to do that very, very easily. The other thing is, I already mentioned think is the read access logging. So in the past you could only Trace if someone actually
changed data. So someone is going into a consumer data set and maybe changing the name or something might be an exaggerated example, but that is something you could always as you were always able to track in the past with read access logging. We're even we even have the possibility to track if someone it's just looking at the data and that in itself, if you think of I mentioned, the example of salaries that is something which is helpful because obviously
just because someone has some authorization, because it's, he's in the IT department or whatever. Doesn't mean you should be able to look at your celery and when we taxes longing, that something we can effectively The prevent from happening. What about new functionalities? What kind of enhancements were shipped with the latest sap s1r Cloud release. In terms of security. Well, when the security features, a lot of the features which we ship with new releases are sort of under the hood.
So it's not something which you as a customer would actually notice. It is things like secure by default. So weird. If we were securing more of the settings in the PS4 on the cloud as well, one highlight which I like to find out because in various ways it's important for security, it's a security audit log and a security audit log is Something which has been in place in the backbone of the, what is now, as for Hannah, in general for years, it was already implemented in Zombies
to see when. So before the S400 types, and of course, it's also been available in the as far on a cloud. However, until recently as a customer, you would have to manually extract the security audit log from the system. And what we've done now is we established a pi. So basically, you now have the possibility to continuously retrieve the data from the as far on a cloud system.
And why is it important? Well, the security audit log contains information such as failed log on. So some someone is mistyping his or her passwords, so he's not be able to log on. That will be locked in the Farhana security, audit lock things, like what terminal did that user use to log on to the system? Will also be new location. Essentially, what applications what apps did he start when in the system?
So these are all information which might be security development. Not if someone does his regular job, they're not security relevant. But as soon as something out of the ordinary happens that become security element of the relevant and there's tools are solutions out there. R which are just looking for these anomalies and analyzing whether this is actually an ongoing attack and with the API we have made it possible that you don't need to but you don't have to manually retrieve the data but we can continue or the security information and event
management systems. That's the name of these Solutions. Also shortened to zeem these seem systems can continuously retrieve that information from the system and Therefore able to detect and potential attack almost in real time and these kind of security enhancements we do. Obviously, we try to do as often as possible and there will be additional things coming up a lot of or some of them actually have to do with other locks, but
you're also making available through an API. But then again, if you look at the releases in general quite a lot of security enhancements are under The hood so more to make it as far on a cloud even more secure than it already. Is we've already talked quite a bit about a functionalities and features that are already available. How does the future in terms of security look like? That is a very very good question and I think it also depends on what kind of future you looking at. I mean, one thing, which will probably be very interesting in
the coming five, to ten years, will be the rise of quantum computers. Because quantum computers are able or will be able to basically render quite a few of our encryption capabilities useless but not limited to sap that limited to the entire it world. So you know, I'm really looking forward to in a bit from security scanning that perspective, what will be happening when there will be actually in the good quantum
computer, which is useful so far the quad Computers are not yet able to do that but they will be that's for sure. And what we've done from from sap site or maybe just to eat to put the audience at ease. We've done quite a bit of research into Quantum safe cryptography. So making sure that the encryption we are using is also secure against a tech from country computer and yeah, that's that's a topic, which is sort of dear to my heart, so, to speak. If you look at the future of
security in More short term. I think we will see a lot of consolidation in terms of also security functionalities. If you I mentioned the term zero trust earlier, which essentially says, if we stay with the analogy of a medieval city in the past, you know, once once you've crossed the wall and you were inside the city, you can do pretty much anything in the city with zero. Trust that you basically are restricted even further. So even if you go into the City and you cross the Wall, you we'll still be, I don't know
what's true. That you only have that particular path and you can only go to a particular room. So very granular, authorization is one of the main Concepts on zero trust and that's funnily enough. That's something which from a technical point of view, sap has been able to do for ages literally. I mean, that that was already part of the the R3 system back in the nineties. But that's, that's picking up a little bit more. So there's a consolation of the various sort of Stages of security but again for a
short-term outlook on security and we will probably see more of a sort of incremental enhancements on security rather than sort of the big leap into something particular. But again, there's other topics which will rise in the more mid term to long term future Quantum cryptology the blockchain. Artificial intelligence will be something which will be very interesting also in security. So these are the short-term things. And of course as sap. And even as we as far as security team were keeping up
with the development here and ensuring that we will secure the Isfahan, a cloud even against more sophisticated attacks and future. This brings us to the last question of today's episode. In your opinion, what are the key? Takeaways of today's episode for someone who has not paid much attention to security, or is unsure about the security of sap as far on a cloud. If you look at as far on a cloud, I think the key takeaways are so to speak. We fault one of the key takeaways I would say is that we have a very securely developed
software. So, as far as a software is definitely secure, if you look at it more from a cloud perspective, it goes a little bit into the same direction by saying that the operations we have is not only Industry standard, but I personally think and I said I've been in the security area area for decades. Now sap is doing a really good job in securing as for Hannah clouds.
And if you look at it from a, from a cloud perspective, and then last but not least, I think the last key takeaway is that we as sap do not think of security as an afterthought, but we actually look at it from a sort of Holistic point of view so across everything starting from the software development to the operations, but even if you look at inside sap, even people who are not in security, they are also trained in security.
They have to do security trainings. Every once in a while to keep up to date. And yeah, if you would summarize that in a sentence, I would say that sap. And as IPS for Hannah adheres to and goes Ian leading industry standards and I think Commerce technology operations and even legal measures and regulations. When you talk about data privacy protection, Thanks Patrick for joining me today and providing this valuable insights. It was a real pleasure to speak with you and learn more about this complex. But highly, important topic.
Thank you for having me was the tiger. Thanks a big. Thank you to our listeners as well. Keep an eye out for our next episode. On opensap, I hope you will join me again until then as a PS4, Hannah followers, stay tuned and stay safe.
Nobody is credited on this episode yet.
Recorded live at SAP TechEd 2026 in Berlin, this episode of Inside SAP Cloud ERP gets into one of the most significant partnerships in the SAP ecosystem right now. Host Yannick speaks with Vladimir Shakhov, Strategic...
Recorded live at SAP TechEd 2026 in Berlin, this episode takes a refreshingly grounded, practitioner-first look at what AI in SAP really means in the field today. Host Fernanda speaks with Wouter Lemaire, independent...
Recorded live at SAP TechEd 2026 in Berlin, this episode of Inside SAP Cloud ERP brings something the series hasn't had yet: the perspective of an actual large enterprise customer architect, not a consultant or partner....
Recorded live at SAP TechEd, this episode of Inside SAP Cloud ERP zooms in on the dimension of SAP transformations that gets the least attention - and causes the most damage when ignored: Organizational Change...
Recorded live at SAP TechEd 2026 in Berlin, this episode of Inside SAP Cloud ERP gets to the heart of what the autonomous enterprise actually looks like when it's working. Host Yannick speaks with Sindhu Gangadharan,...