5 Cybersecurity Predictions for 2024 You Should Plan For

If you want to uncover unsanctioned cloud apps, don’t begin with a policy. Start with your browser history. The cloud environment most businesses actually use rarely matches the one shown on the IT diagram. It’s built through countless small shortcuts: a “just this once” file share, a free tool that solves one problem faster, a plug-in installed to meet a deadline, or an AI feature quietly enabled inside an app you already pay for. In the moment, none of it feels like a problem. It feels efficient. Helpful. Until it isn’t. Then you realise business data is scattered across tools you didn’t formally approve, accounts you can’t easily offboard, and sharing settings that don’t reflect the actual risk. Why Unsanctioned Cloud Apps Are a 2026 Problem Unsanctioned cloud apps have always existed. What’s changed this year is the scale, the speed, and the fact that “cloud apps” now include AI features hiding in plain sight. Start with scale. Microsoft’s shadow IT guidance points out that most IT teams assume employees use “30 or 40” cloud apps, but “in reality, the average is over 1,000 separate apps.” It also notes that “80% of employees use non-sanctioned apps” that haven’t been reviewed against company policy. That’s the uncomfortable reality of unsanctioned cloud apps: the gap between what you believe is happening and what’s actually happening is often far wider than expected. Now add the 2026 twist: AI isn’t just a standalone tool employees consciously choose to use. The Cloud Security Alliance notes that AI is increasingly embedded as a feature within everyday business applications, rather than existing only as a standalone tool. In other words, you can have shadow AI risk without anyone signing up for a new AI product. It’s just… there. That creates a different kind of exposure. The same Cloud Security Alliance article cites research showing “54% of employees” admit they would use AI tools even without company authorisation. It also references an IBM finding that “20% of organisations” experienced breaches linked to unauthorised AI use, adding an average of “$670,000” to breach costs. So, this isn’t just a governance problem. It’s a measurable risk problem. And here’s the final reason 2026 feels different: the old “block it and move on” strategy no longer works. The Cloud Security Alliance has pointed out that simply blocking cloud apps isn’t an option anymore because cloud services are woven into everyday work. If you don’t provide a secure alternative, employees will find another workaround. Don’t Start with Blocking The fastest way to drive cloud app usage further underground is to treat it as a discipline problem and respond with bans. Yes, some applications do need to be blocked. But if blocking is your first move, it typically creates two unintended side effects: 1. People get better at hiding what they’re doing. 2. They switch to a different tool that’s just as risky or, sometimes, worse. Either way, you haven’t reduced the problem. You’ve just made it harder to see. A better starting point is to understand what’s happening and why. The recommendation is to evaluate cloud app risk against an “ objective yardstick ”. You should monitor what users are actually doing in those apps so you can focus on the behaviour that creates exposure, not just the name of the tool. Once you have that visibility, you can respond in a way that actually lasts. Some apps will be approved. Others may be restricted. Some will need to be replaced. And the truly high-risk ones? Those are the apps you block thoughtfully, with a clear plan, a communication message, and a secure alternative that allows people to keep doing their jobs. The Practical Workflow to Uncover Unsanctioned Cloud Apps This isn’t a one-time clean-up. It’s a workflow you can run quarterly (or continuously) to stay ahead of new tools and new habits. Discover What’s Actually in Use Start by generating a real inventory from the signals you already collect: endpoint telemetry, identity logs, network and DNS data, and browser activity. Microsoft’s shadow IT tutorial emphasises a dedicated discovery phase, because you can’t manage what you haven’t first identified. Analyse Usage Patterns Don’t stop at identifying which apps are in use. Review things like: Who is accessing cloud apps What admin activity is happening Whether data is being shared publicly or with personal accounts Access that should no longer exist, such as former employees who still have active connections Score and Prioritise Risk Not every unsanctioned app is equally dangerous. Use a simple risk lens: The sensitivity of the data involved How information is being shared The strength of identity controls The level of administrative visibility Whether AI features could be ingesting or exposing data Tag Apps Make decisions visible and repeatable by tagging apps. Microsoft explicitly calls tagging apps as sanctioned or unsanctioned an important step, because it lets you filter, track progress, and drive consistent action over time. Take Action Once an app is tagged, you can enforce the decision. Microsoft’s governance guidance outlines two practical responses: issuing user warnings, a lighter control that encourages better behaviour, or blocking access to applications that present unacceptable risk. Just keep in mind that changes aren’t always immediate. Plan for communication and a smooth transition, rather than triggering unexpected disruptions. Your New Default: Discover, Decide, Enforce Unsanctioned cloud apps aren’t disappearing in 2026. If anything, they’ll continue to multiply, especially as new AI features appear inside the tools your team already relies on. The goal isn’t to block everything. It’s to create a repeatable operating model: discover what’s in use, determine what’s acceptable, and enforce those decisions with clear guidance and secure alternatives. When you apply that consistently, cloud app sprawl stops being a surprise. It becomes another controlled, managed part of your environment.  If you’d like help building a practical cloud app governance process that fits your organisation, contact us today. We’ll help you gain visibility, reduce exposure, and put guardrails in place, without slowing productivity.

It usually starts small. Someone uses an AI tool to refine a difficult email. Someone enables an AI add-on inside a SaaS app because it promises to save an hour a week. Someone pastes a paragraph into a chatbot to “make it sound better.” Then it becomes routine. And once it’s routine, it stops being a simple tool decision and becomes a data governance issue: what’s being shared, where it’s going, and whether you could prove what happened if something goes wrong. That’s the core of shadow AI security. The goal isn’t to block AI entirely. It’s to prevent sensitive data from being exposed in the process. Shadow AI Security in 2026 Shadow AI is the unsanctioned use of AI tools without IT approval or oversight, often driven by speed and convenience. The challenge is that the “helpful shortcut” can become a blind spot when IT can’t see what’s being used, by whom, or with what data. Shadow AI security matters in 2026 because AI isn’t just a standalone tool employees choose to use. It’s increasingly embedded directly into the applications you already rely on. At the same time, it’s expanding through plug-ins, extensions, and third-party copilots that can tap into business data with very little friction. And there’s a human reality in it: 38% of employees admit they’ve shared sensitive work information with AI tools without permission. It’s people trying to work faster, but making risky decisions as they go. That’s why Microsoft sees the issue as a data leak problem, not a productivity problem. In its guidance on preventing data leaks to shadow AI, the core risk is simple: employees can use AI tools without proper oversight, and sensitive data can end up outside the controls you rely on for governance and compliance. And here’s what many teams overlook: the risk isn’t just which tool someone used. It’s what that tool continues to do with the data over time. This is known as “ purpose creep ”, when data begins to be used in ways that no longer align with its original purpose, disclosures, or agreements. But shadow AI isn’t limited to one obvious chatbot . It shows up in workflows across marketing, HR, support, and engineering, often through browser-based tools and integrations that are easy to adopt and hard to track. The Two Ways Shadow AI Security Fails 1.) You don’t know what tools are in use or what data is being shared Shadow AI isn’t always a shiny new app someone signs up for. It can be an AI add-on enabled inside an existing platform, a browser extension, or a feature that only shows up for certain users. That makes it easy for AI usage to spread without a clear “moment” where IT would normally review or approve it. It’s best to treat this as a visibility problem first: if you can’t reliably discover where AI is being used, you can’t apply consistent controls to prevent data leakage. 2.) You have visibility, but no meaningful way to manage or limit it Even when you can name the tools, shadow AI security still fails if you can’t enforce consistent behaviour. That typically happens when AI activity lives outside your managed identity systems, bypasses normal logging, or isn’t governed by a clear policy defining what’s acceptable. You’re left with “known unknowns”: people assume it’s happening, but no one can document it, standardise it, or rein it in. This can quickly turn into a governance issue . This happens when the organisation loses confidence in where data flows and how it’s being used across workflows and third parties. How to Conduct a Shadow AI Audit A shadow AI audit should feel like routine maintenance, not a crackdown. The goal is to gain clarity quickly, reduce the most significant risks first, and keep the team moving without disruption. Step 1: Discover Usage Without Disruption Start by reviewing the signals you already have before sending a company-wide email. Practical places to look: Identity logs: who is signing in, to which tools, and whether the account is managed or personal Browser and endpoint telemetry on managed devices SaaS admin settings and enabled AI features A brief, non-judgmental self-report prompt, such as: “What AI tools or features are helping you save time right now?” Shadow AI is often adopted for productivity first , not because people are trying to bypass security. You’ll get better answers when you approach discovery as “help us support this safely.” Step 2: Map the Workflows Don’t obsess over tool names. Map where AI touches real work. Build a simple view: Workflow AI touchpoint Input type Output use Owner Step 3: Classify What data is Being Put into AI This is where shadow AI security becomes practical. Use simple buckets that your team can apply without legal translation: Public Internal Confidential Regulated (if relevant) Step 4: Triage Risk Quickly You’re not aiming to create a perfect inventory. You’re focused on identifying the highest risks right now. A simple scoring model can help you move quickly: Sensitivity of the data involved Whether access occurs through a personal account or a managed/SSO account Clarity around retention and training settings Ability to share or export the data Availability of audit logging If you keep this step lightweight, you’ll avoid the trap of analysing everything and fixing nothing. Step 5: Decide on Outcomes Make decisions that are easy to follow and easy to enforce: Approved: Permitted for defined use cases, with managed identity and logging wherever possible Restricted: Allowed only for low-risk inputs, with no sensitive data Replaced: Transition the workflow to an approved alternative Blocked: Poses unacceptable risk or lacks workable controls. Stop Guessing and Start Governing Shadow AI security isn’t about shutting down innovation. It’s about making sure sensitive data doesn’t flow into tools you can’t monitor, govern, or defend. A structured shadow AI audit gives you a repeatable process: identify what’s in use, understand where it intersects with real workflows, define clear data boundaries, prioritise the biggest risks, and make decisions that hold. Do it once, and you reduce risk right away. Make it a quarterly discipline and shadow AI stops being a surprise.  If you’d like help building a practical shadow AI audit for your organisation, contact us today. We’ll help you gain visibility, reduce exposure, and put guardrails in place without slowing your team down.