Identity security and zero trust at de Volksbank

So my name is Ben Schoenmakers. My role is a lead developer of the IdentityX Management Team. I work at the fourth largest financial institution within the Netherlands, the Volksbank. The Volksbank is a bank, so we deal with financial transactions, and I believe we currently have internal employees, which request roles on a daily basis. And we also have external employees, franchisees, as you will, which have a different kind of approach to IdentityX Management. I have been at the Volksbank for around three years now, graduated from my college, university-level bachelor position as a software developer. And basically, I wanted to do more with cybersecurity, in that way, I rolled it into bank, and they offered me this position in the IdentityX Management team. The main security concerns of banks these days are very broad. I believe you have the traditional security measures you need to have in place against DDoS attacks, ransomware attacks, phishing attacks, et cetera. Identity governance is very important for our bank, because we get all the breathing on our neck, so we need to make sure that everyone walk through the appropriate approval steps in order to gain what they can do or they are allowed to do in applications. For example, one particular person cannot authorize a loan for a bank and also approve of a particular loan. So we need to make sure that those entitlements are not matched. they are not a toxic combination. The benefits that I have seen, from my perspective as a developer for One Identity Manager is surely, the modularity that the product provides. So I can very easily create connections between applications, some of them out of the box, the one IdentityX provides using a synchronization editor. And some of them I can easily build myself as a software developer and make sure that entitlements are provisioned ad hoc, not on a paper basis that are sent only on a drive. That saves a lot of time. So I believe last week, I created some sort of password reset functionality, which saves, I believe, 400 tickets per month. If somebody asked me what part of One Identity helps us the most, I think it's providing users with the correct amount of access, nothing more, nothing less, in an automated fashion so that we know who are electees these are and what they can do and that the rest of the employees can just go about their business without worrying about [? next ?] management.