LexisNexis Risk Solutions: real AI capability starts with real people. AI is already reshaping the workplace. The question is: how do organisations respond in a way that actually lasts? At LexisNexis Risk Solutions, the answer starts with learning. Last week, Makers launched a new AI partnership with LexisNexis Risk Solutions, supporting 28 learners through a practical programme designed to build confidence, adaptability, and real-world AI capability across the organisation. The programme officially kicked off with an in-person activation day focused not just on AI tools, but on how teams can use them with purpose. Because in the AI age, the organisations that thrive won't simply be the ones experimenting with technology. They'll be the ones building cultures that can keep learning as technology evolves. AI capability starts with learning capability Opening the launch day, Makers CEO Claudia Harris OBE spoke about Learning Quotient (LQ): the ability to learn, adapt, and evolve as work changes around Makers Academy Limited. "The future belongs to those who are willing and able to adapt." Claudia Harris OBE, CEO at Makers Sessions moved learners beyond AI hype and into practical application; identifying where AI could genuinely improve the way they work, and building the confidence to act on it. Practical AI. Human-first thinking. The launch workshop was led by Yusuf Kissi, AI Coach at Makers. Rather than treating AI as a one-size-fits-all solution, Yusuf's sessions encouraged learners to reflect on their own workflows, identify repetitive or low-value tasks, and explore where automation could create meaningful impact - helping people move from passive AI users to confident AI champions. "AI doesn't replace you. It amplifies you." Yusuf Kissi, AI Coach at Makers Building confidence alongside capability Learners also took part in workshops focused on emotional intelligence, wellbeing, and learner support, because successful AI adoption isn't just a technology challenge. It's a human one. The organisations that succeed through AI won't be the ones with access to the most tools. They'll be the ones most willing to learn, and most committed to building that capability in their people. LexisNexis Risk Solutions is doing exactly that. Want to do the same? Thinking about what this could look like for your organisation? Makers Academy Limited'd love to help you figure it out. The Makers team is dedicated to transforming lives by building inclusive pathways into tech careers. With a mission to align their success with their students' success, Makers challenges traditional education models by integrating training with employment support, helping aspiring developers find roles where they can thrive.

Third-Party data breach: the LexisNexis lesson every Australian business ignores. * May 11 2026 * Neil Frick When LexisNexis confirmed a major cloud breach in March 2026 exposing legal and government client data, it exposed something every Australian business should already know: your cyber security is only as strong as the weakest vendor connected to your systems. A third-party data breach does not need to touch your infrastructure at all. It just needs to touch someone who touches you. From the OracleCMS breach that hit Victorian councils, to the Pareto Phone incident that leaked charity donor data, to MOVEit, Blackbaud, and now LexisNexis, the pattern is identical. If you are not actively managing your vendors, you are not managing your cyber risk. Why third-party data breach incidents dominate the headlines. The Office of the Australian Information Commissioner has repeatedly flagged third-party and supply-chain incidents as one of the fastest-growing breach categories. In the first half of 2025 alone, more than 30% of notifiable breaches in Australia involved a vendor, service provider, or contractor. Recent high-profile Australian examples include: * LexisNexis (2026) - legal and government client data exposed * Booking.com (2026) - third-party compromise enabled targeted phishing * OracleCMS (2024) - after-hours call centre breach impacting multiple councils * ZircoDATA (2024) - document storage breach affecting Monash Health * Finsure (2024) - nearly 300,000 customer emails leaked via a data partner What exactly is a third-party data breach? A third-party data breach occurs when an organisation suffers loss, exposure, or compromise of data through a vendor, supplier, contractor, SaaS provider, or any other external party with access to the organisation's systems or information. This includes: * Cloud software providers storing customer data * Outsourced IT or help-desk services * Marketing agencies with email-list access * Accounting firms with financial data access * Document-storage and records-management vendors The five vendor questions every Australian SMB must ask. Before you sign any contract that involves a vendor touching your data, your staff, or your systems, you need clear answers to these five questions: * Where is its data stored and who has access? Ask for specifics, not marketing language. * Are you aligned to Essential Eight, ISO 27001, or SOC 2? If the answer is a blank stare, reconsider. * What is your incident response process and how quickly will Netlogyxit be notified? Under the Privacy Act, you may only have days. * Do you carry cyber insurance and what are the limits? You do not want to discover this after an incident. * Will you allow an annual security review or audit? Good vendors welcome this. Bad vendors refuse. Contract clauses that actually protect you. Most Australian SMB contracts with vendors contain generic boilerplate security language that does not survive a real breach. Stronger clauses include: * Mandatory breach notification within 24 or 48 hours * Rights to audit and test security controls * Named sub-processors list and notification before changes * Data return or destruction obligations on termination * Liability caps that genuinely reflect breach risk Do You Know Which Vendor Will Cause Your Next Breach? Third-party data breach incidents now account for a growing share of Australian notifications. You cannot delegate your risk. * Build a prioritised vendor risk register * Review existing contracts for breach notification clauses Frequently asked questions. Q: Am I legally responsible if a vendor causes a third-party data breach? A: In most cases, yes. Under the Privacy Act, the organisation that collected the personal information usually remains accountable, even if the breach occurred at a processor or vendor. Q: How often should I review my vendors? A: At minimum annually. For vendors handling sensitive data or with privileged access, a six-month review cycle is strongly recommended. Q: What is the first vendor I should review? A: Any vendor with access to your email environment, your customer database, your payroll system, or your financial records. These are your crown jewels. The LexisNexis breach, the OracleCMS incident, and every other third-party data breach on the Australian record share one common feature: the victim organisations trusted their vendors without verification. Trust is not a control. Verification is. (Netlogyxit is not looking to replace your current provider, just offering an alternative perspective)

LexisNexis data breach: security safeguards failed. MagazineCoverage LexisNexis' breach reveals systemic failures beyond a contained incident, exposing deep weaknesses in cloud security and governance. The exploitation of an unpatched React2Shell vulnerability highlights a critical lapse in patch management despite known public exploits. Identity and access controls failed, with excessive permissions allowing a single role to access all secrets, violating least-privilege principles. Poor secrets hygiene amplified risk, including unrotated credentials, weak encryption practices, and plaintext passwords in support systems. Network segmentation gaps enabled front-end systems to directly access databases, increasing lateral movement risk across environments. Data protection controls were ineffective, as large-scale data exfiltration occurred without triggering alerts, indicating weak DLP enforcement. More critically, exposed AI pipeline credentials introduce risks of model theft, poisoning, and supply chain compromise, demanding urgent architectural overhaul. START - UP Tweets from @varindiamag. Nothing to see here - yet. When they Tweet, their Tweets will show up here.