Video: Securing Access: Best Practices for Multi-Factor Authentication on IBM i | Duration: 3612s | Summary: Securing Access: Best Practices for Multi-Factor Authentication on IBM i | Chapters: Introduction and Welcome (24.67s), Regulatory Themes Overview (173.15001s), Regulatory Compliance Mandate (302.335s), Rising Threat Landscape (431.97s), Compliance Summary 2026 (596.63s), Compliance Changes 2026 (668.38995s), Regulatory Compliance Framework (789.665s), Choosing MFA Solutions (949.205s), Assure MFA Advantages (1181.58s), Q&A Session (1474.485s), MFA Implementation Strategy (1698.505s), Closing and Resources (1755.855s)
Transcript for "Securing Access: Best Practices for Multi-Factor Authentication on IBM i":
Alright. Hi, everyone. Thank you for joining us today. We really appreciate you taking the time out for this. My name is Haley. I'm on the product marketing team here at Precisely, and I'm joined by my colleague, Geeta, from the product management team. Today, we're going to walk you through what we think is one of the most important topics in IBM I security right now, making sure the right people are getting on your system and the wrong people are not. And the best way to do that in 2026 is multifactor authentication. Before we dive in, just a few housekeeping notes. This session is being recorded, so you will receive a link for the recording and the slide deck in your inbox. So feel free to share that with your colleagues who couldn't make it today. We are also coming to you live. So if you're having any technical difficulties with the audio or the visuals, please feel free to use the q and a box on your screen, and someone from our team will be in touch with you. You can also use that q and a box to send in questions anytime during the presentation. We do have time at the end for answering some questions, if time permits. But if we don't get to your question, please be sure that we will reach out to you via email. Dita and I will get to as many as we can at the end, and then we'll just follow-up via email for the rest. But with that, here's what we are going to cover today. We start with what's happening in the broader regulatory landscape because a lot of what's driving MFA adoption right now is coming from outside organizations, not inside it. Then we'll get specific on some compliance changes that are happening in 2026 and that we really need to know about. And from there, we'll get more practical. So if you are evaluating an MFA solution for your IVMI, what should you actually be looking for? We'll we'll get to that. And then we'll leave time at the end for q and a. So without much delay, let's get into it. Let's start with the big picture. Right? What is going on in the regulatory landscape right now, and why does it matter for our IBM I security strategy? I want to give you six themes to keep it tight. These six themes are what we see, what we've been seeing come up across every analyst, every vendor, every regulator, and then we look at some of the leading voices in the industry, what they're actually saying about 2026 specifically. So when I look across everything that's being written and said about cybersecurity regulation right now, six themes keep coming up over and over and over again. We walk we walk you through them super quick. First, regulate the uncertainty. This one is super real. The geopolitical landscape is shifting, rules are changing, and frankly, nobody is 100% sure what the compliance environment looks like in twelve months. And the thing is that this uncertainty is not a reason to wait. If anything, it's a reason to make sure that our foundation is solid now because whatever comes next, MFA is going to be a part of it. Next is cybersecurity mesh. This is about moving away from a bunch of disconnected silo security tools that don't talk to each other toward a more integrated coordinated approach. Your MFA solution needs to fit into that picture and not sit outside of it. Third is audit reporting. This is becoming a really, really big deal. Regulators and internal audit teams, they want detailed evidence that controls are in fact working. Not just, yes, we have MFA and, yes, like, we have this. It's not a checkbox anymore. They want logs, reports, and crew to go with it. For AI and machine learning, we'll we can say agentic AI specifically here. This is reshaping risk on both sides. Attackers are using it, and defenders need to use it, and regulators are starting to write rules around it. So it's kind of in the whole, in the whole life cycle. Data protection, encryption, access control, recovery strategies, these used to be best practices, but now in 2026, they're mandated requirements across multiple regulations. We'll get into these specifics in a few slides. And finally, zero trust. The idea that just because someone got through the front door doesn't mean they should have access to everything. Every user, every device, every access request gets verified. This is now being required by regulators and, interesting enough, by cyber insurers as well. We'll come back to this, we'll come back to this also. So let's look a little at what the analysts and industry bodies are actually saying. Starting with Gartner, the same global security spending is projected to hit $244,000,000,000 this year, and that's a 13% jump over last year, which is one of the biggest single year increases on record. So security software is the fastest growing piece of that, which is being driven by the move to cloud. So organizations are definitely spending. The question is whether they're spending on the right things. On the health care side, we have folks from different industries. On this call, I know, but this one is worth paying attention to regardless of your sector because it signals where things are heading broadly. The, HIPAA security rule is getting its biggest overhaul since 2013. The final rule is expected in May 2026, and it eliminates what were called addressable safeguards. Meaning encryption and MFA are no longer optional. They are mandatory for any system that touches patient data. And separately, the health care cybersecurity and resiliency act just passed out of the senate committee 22 to one in February. That is a strong bipartisan signal that this is coming into law. It mandates MFA encryption and NIST alignment across all HIPAA regulate regulated entities. And Forrester is making a point that we know is really important. Right? The accountability for security failures is shifting. It's no longer just an IT team problem. Executives are being held personally liable. So if you're on this call and you're thinking about how to make the case internally for investing in MFA, this this is your argument right here. So continuing on the idea of data, the Splunk CISO report from February surveyed around six fifty secondurity leaders globally, and numbers are pretty striking. 95% of CSIOs say that the growing sophistication of threats is their number one risk. 92% say that AI is helping them review more events and detect faster, move faster. But the one thing that really stood out was that 78% of these people are worried about personal liability for security incidents. This is up 56% last year, and this is a massive shift in how security leadership thinks about their own exposure. This goes to say what we saw on the last slide. On cyber insurance, and this this one is directly relevant to everyone here. MFA is now the number one reason companies get denied cyber insurance. Not just flagged, not just penalized, but denied. Insurers want verified proof that controls are actually in place and that they actually work. Documentation alone does not cut it anymore. And if you have partial MFA coverage, many insurance are treat many insurers are treating it the same as having none at all. So that's something we we need to, keep in mind. Checkpoints 2026 report. This one shows that organizations are facing nearly 2,000 cyberattacks per week on an average, and this is a striking 70% increase since 2023. Ransomware as a service group grew 50% year over year, and AI is now embedded across the entire attack lifecycle. It's not just being used for defense. Again, something that we saw in the sixteenth. And from cybercrime magazines, ransomware damage costs are projected to reach $74,000,000,000 this year alone. And the attack frequency, we wanna make sure this land. The attack frequency, ransomware is now hitting every two seconds. When, we did a similar webinar to this in 2025, At that time, there was a prediction that this was a prediction for 2031, but it's actually happening now in the span of one year. The average incident costs over $5,000,000, and we have a global workforce gap of 4,800,000 unfair cybersecurity positions. So the threat is accelerating and the people to fight it on there. That's just the environment that we're operating in. So to kind of give you a summary, if we pull it all together, compliance in 2026 is not something that we are able to treat as a checkbox exercise anymore. It's not something that the IT team handles quietly in the background. It is now a core business function. The cost of not being compliant, which is the fines, the lawsuits, the insurance denials, the deputational damage not to mention, these are now genuinely outweighing the cost of getting ahead of it. But the good news is that MFA is one of the clearest, most concrete steps that we can take right now. It's it's able to directly address what regulators are asking for, what insurers are requiring, and what the threat data tells us is the number one attack window. So with that, I'm going to hand it over to Geeta who's going to walk us through some of the specific, compliance changes for 2026 and then get into what this means for your IVMI specifically. Geeta, all yours. Thank you, Hailey. So, yes, I'll be speaking about the compliance changes for 2026. So it's important to note that NFA is evolving quite a bit in 2026. So now that it's a nonnegotiable security measure for business and individuals, it significantly reduces the risk of unauthorized access, making it a critical component of cybersecurity strategy. So we can expect to see a surge in adoption as organizations prioritize safeguarding and sensitive data. So in 2026, MFA has been evolving significantly, and that's towards a more adaptive and user friendly approach. There is a strong focus on integrating data, advanced technologies like AI and biometrics and utilizing contextual awareness to prompt verification only when necessary and potentially becoming mandatory across various platforms. And so this was a requirement back in March 2025, and, there are a few other requirements as well that are coming up. One of those is PCI DSS. So, version four dot o dot one in 2026 is the current requirement. So the PCI standard is, something that defines the security requirements for merchants and other businesses to handle credit card information in a secure manner that helps reduce likelihood that cardholders would have sunset financial account information stolen. And so the new requirements require mandatory multifactor authentication systems. They also require network security and firewalls, data protection, also known as encryption, continuous monitoring and testing, secure systems development, and third party management, must have a third party risk management program to ensure vendors are also compliant and has some different things for different levels of merchants. So looking at that, some of the keys that we want to remember for 2026 is that, the MFA system cannot be susceptible to replay attacks, and MFA systems cannot be bypassed by any users unless specifically documented and authorized by management on an exception basis for a limited time. At least two different types of authentication factors are used, and success of all authentication factors is required before access is granted. So looking at Azure MFA, we can help with achieving regulatory compliance by utilizing a one time token, which cannot be reused in replay attacks, and all users are configured to use, Assur MFA must authenticate with additional factors. Assur MFA relies on radius as one type, to comply with two different types of authentication and also has TOTP support and which qualifies for ODA implementation as well. Assurant MFA ensures that rejected authentication requests do not grant access to the system. DORA is another regulation. So the Digital Operations Resiliency Act is an EU regulation aimed at enhancing operational resilience in the financial sector. It focuses on managing IT risks and incidences incidents and harmonizes existing roles across EU member states. So this is having an interesting impact on financial institutions as, there's a much more increased regulatory burden. So extensive documentation and reporting requirements as well as the need for robust governance and oversight. There's, enhanced cybersecurity that's required to strengthen our focus on cybersecurity measures and incidence response, operational resilience, improved ability to withstand disruptions and recover quickly, as well as innovation opportunities, the potential to drive innovation and digital technologies and risk management. So some of the key requirements are for IT risk management, implementing robust risk management framework and setting clear risk tolerance levels and ensuring business continuity and disaster recovery plans. Third party risk management implement due diligence and oversight of third party service providers, digital operations resilience testing, conducts regular testing to assess resilience capabilities, and include cybersecurity aspects in testing programs. So now I can hand this over to Hailey to talk about choosing an NFA solution for I IBM I. Thanks, Geeta. Yeah. So now that we've covered the regulatory drivers and what some of these compliances and rules mean in practice, let's get into the more practical questions. So if you're sitting here today thinking, okay. We need MFA or or IVMI. How do we make the right choice? That's what we're going to walk you through now. So the first question is why is MFA required? Right? The short answer is that it's showing up everywhere. So PCI, DSS, if you're taking credit cards, this applies to you. The NYCRR, that's in New York State's, cybersecurity regulation relevant for financial services. The GLBA, FFIEC for financial institutions, and then in a broader set of regulations, the GDPR, HIPAA, Swift Alliance Access, DSOX, and now DORA. MFA is either explicitly required or strongly implied. So the point that we're trying to make here by listing all of these down is that, this is no longer a decision that lives within the IBM I team alone. MFA is becoming a corporate mandate driven by the compliance team, the legal team, the CSIO, and the cyber insurance provider. There's multiple stakeholders here. The IDMI needs to fit into whatever MFA framework your organization decides on. So you're not so if you're not already in that conversation, now is definitely the time to be. And that last line on the slide, comprehensive MFA coverage is now the standard. Caution implementation isn't enough. So if you've got nothing on some systems but not others, insurers and auditors are increasingly treating that as a huge gap. So once we've seen why MFA is required, the natural next step the natural next question is why MFA specifically? So on the next slide, we see this because because total credentials are now the number one entry point for ransomware attacks. Non sophisticated zero day exploits, just someone getting hold of a username and password. Password alone give you no real protection against that. What MFA does is it adds that layer that makes stolen credentials useless on their own. Something you know, your password, something you have, so the device or token, and something you are, a biometric. An attacker needs all of those but and not just one. And the stat that I always come back to is that MFA blocks 99.9% of automated attacks. It is not bulletproof. Nothing really is. But it is by far the most effective single thing you can do to protect access to your systems. And it's worth saying that this is no longer just a recommendation. Regulators require it. Cyber insurance requires it, And in press security mandates are requiring it. We're just reiterating the same requirements. So if we if there's anything that, you know, you wanna take back from today, it's this. The MFA on your own on your IDMI is not optional anymore. The question is just which one you choose, and that's what we're going to do next. So I'm gonna hand it over to Geeta to show you how precisely addresses this. Thank you, Hailey. So we're continuing to enhance Assure MFA. So, first, as part of the PCI DSS, a point for our requirements, we have the time based one time password, which we'll get into a little bit more. But it's an authentication option which became generally available in March 2026, and this allows for security administrators to utilize one time password solutions across their organization and for IBM I logins to be prompted to input a one time password when logging in to each IBM I account so that there's an additional layer of security which is added to the authentication process. So this has already come out, and then the next few enhancements are coming up. And so as we look to the future, we're working on the ability to integrate IDMI MFA solutions with other authentication identity management solutions in order to standardize with corporate standards and streamline user management. So we're going to be having a an MFA device authorization flow support that's coming up. So we're working on big identity providers integration such as Okta. And so this will, also be along with the integrating of the MFA user synchronization, so allowing, for an automated solution to synchronize user definitions for MFA efficiently through an integration such as Okta. And so that, administrators can avoid the cumbersome and error prone manual process as well as, and that they use their life cycle management coming up with identity providers such as Okta, where administrators can have an automated, sorry, can, also have automated, solutions to synchronize user definitions through this. In the future, we're also looking into AI as well as model context protocols. And if y'all are interested in that, please reach out to products and talk. We'd love to hear what you think about that. So IBM did come out with 7.6, which is the m which is their MFA offering, which really highlights the growing industry adoption of MFA, and it's a timely move as corporations seek robust security solutions. But note that Precisely has been focused on MFA for years. We have deep expertise and a track record of continuous innovation. We've helped many customers implement MFA solution, and we offer a more comprehensive solution. So AdiM's MFA solution has potential notable limitations that we'll get into in a minute, and Assure MFA can address these gaps. So when you're choosing a MFA solution for IBM I for your IBM I, you wanna note a few different things. So IBM solution is limited to TOTP only, whereas Assure MFA has a much more user friendly authentication. Support we support multiple authentication methods, including push notifications and on demand authentication, which are more user friendly, and then we also have this UTP solution. Azure MFA utilizes centralized radius servers as one option, making it easier to manage. IBM's implementation requires users to create and configure keys for each system, which can be a really complex process. Assurant MFA supports integration with various I'm identity and access management pro platforms such as Okta, Duo, Microsoft Intra, which is previously known as Azure Active Directory, as well as others, which provides flexibility and ease of use. Azure MFA also offers a phased approach to defining users and applications. This allows for better productivity and gradual testing, whereas IBM's MFA requires all applications to be MFA protected at once for selected users. Our MFA integration with SAM offers enhanced ransomware protection, taking MFA to the next level and contributing to your zero trust strategy with our ransomware protection. We have flexible control as we provide the ability to define controls at the individual user group or group level, offering more flexibility and implementation. We also support older OS versions below 7.6, ensuring that customers with older systems are not off behind. So Assure MFA offers a complete and holistic solution. And with that, we can move on to questions. Awesome. Thanks, Geeta. I did see a few questions come into the chat, so we'll just go in order. The first one is related to compliance. So it says, IBM's MFA in v 7.6 doesn't meet the PCI requirements, and is that enough? Thanks, Hailey. I can take this. So IBM's inclusion of MFA in 7.6 is a positive step and does align with PCI DSS four point o at a basic level. However, there are some notable limitations worth considering. First, IBM solution is limited to TOTP, time based onetime passwords only, Whereas a more complete solution should support multiple authentication methods, including push notifications and on demand authentication. Second, IBM's implementation requires users to create and configure keys individually for each system, which adds complexity at scale. Third, and most importantly, it requires both IBM I version 7.6 and Power 10 hardware. So if you're not on the latest operating system hardware, it simply isn't available to you. And finally, IBM's MFA applies on an all or nothing basis for Slack users. There's no phase or incremental rollout option. Assurant MFA addresses all of these gaps and supports older operating system versions and gives you the flexibility to roll out gradually and manage centrally. Okay. Makes sense. Thanks, Geeta. Second question that I will do is, we already have high availability. Does that cover us from a security and compliance standpoint? Okay. That that is a good question, and that comes up pretty more often than you think it might. So this is important to address. So high availability is definitely something that you should have in place. It's one of the core competencies along with security when you think about, like, a holistic, security end to end life cycle. It protects you again. System downtime, hardware pager ensures that your data remains accessible even if the even if your systems go down. Right? So their and security, they're solving two different problems. Do they need to work together? So does not protect you against a bad actor that's trying to get on your system. Right? If someone gains unauthorized access to your IDMI and deploys a ransomware, that attack will replicate across your across your environment just like legitimate data does. So, and MFA, they're not either or. They need to work together. So, ideally, you do wanna have a MFA setup along with your solution so that, we're securing who gets into the system in first place, and then your is able to operate at the layer, which is keeping your systems up and running and being able to give you that always on capability. So, it's kind of complementing each other, but it's not a replacement for for the other. But good question. We do know one more question. The question is with so many regulations calling out MFA, where should we start if we haven't implemented it yet? That's a good one. Martha, do you wanna take that one? Sure. Yeah. I can take it. So I know it can be kind of, overwhelming if you haven't started with MFA yet, but there's some good news. You don't have to do everything at once. So first, you just have to understand which regulations actually apply to your organization. So for example, like p PCI, DSS, if you're processing card payments, HIPAA, if you're in health care, Dora, if you're financial institution operating in the EU, etcetera. And so once you know your compliance obligations, you can prioritize accordingly. From an implementation standpoint, we'd recommend starting with your highest risk access points, so like remote access, privileged accounts, and administrative users, and expanding from there. Assure MFA is specifically designed to support this kind of phased approach, allowing you to define MFA roles by user, group, job type, or application so you can test, validate, and roll out gradually without disrupting your entire user base on day one. Great. Thanks, Deepa. That makes sense. That was the bulk of the questions that we had in the chat, and it kind of duplicated. So I think we've got majority of it. If we didn't get your question, please be rest assured that we'll reach out via email. To close out, we do have a couple notes for you. So if you are wanting to get started and, wanna have conversations broader than MFA just with your security posture, we do have a free risk assessment that you can take. You can head over to the Azure Security web page and find the button right at the top. There's a super simple short form that you can fill out and, and an expert will get in touch with you. And there's another note that I'm gonna let Deepa share with you. Oh, hi. If you're interested in getting in touch with us, we're always looking to improve our products based on real customer needs, and your feedback plays a direct role in shaping your webinar. So if you'd be open to it, please reach out to our product team for a short, focused conversation to gather insights, all day ideas, or discuss potential enhancement. Participation is completely optional, and there's no obligation. Your input simply helps guide future improvement. So please click the link and get in touch with the Azure product team. Thank you. Awesome. And with that, that's all we had for today. Once again, thank you for taking out the time and being a great audience. We will catch you on the next one. Hope you have a great rest of your day.