What ACSC's New AI Defence Guidance Actually Means for Your Business

97% of organisations that suffered a data breach in 2024 had no AI access controls in place. That number comes from IBM and Ponemon's 2025 global breach study. It should stop you cold.​‌‌​​​​‌‍​‌‌​​​‌‌‍​‌‌‌​​‌‌‍​‌‌​​​‌‌‍​​‌​‌‌​‌‍​‌‌​​​​‌‍​‌‌​‌​​‌‍​​‌​‌‌​‌‍​‌‌​​‌​​‍​‌‌​​‌​‌‍​‌‌​​‌‌​‍​‌‌​​‌​‌‍​‌‌​‌‌‌​‍​‌‌​​​‌‌‍​‌‌​​‌​‌‍​​‌​‌‌​‌‍​‌‌​​‌‌‌‍​‌‌‌​‌​‌‍​‌‌​‌​​‌‍​‌‌​​‌​​‍​‌‌​​​​‌‍​‌‌​‌‌‌​‍​‌‌​​​‌‌‍​‌‌​​‌​‌‍​​‌​‌‌​‌‍​‌‌‌​​‌‌‍​‌‌​‌‌​‌‍​‌‌​​​‌​‍​​‌​‌‌​‌‍​‌‌​​‌‌‌‍​‌‌‌​‌​‌‍​‌‌​‌​​‌‍​‌‌​​‌​​‍​‌‌​​‌​‌

The Australian Cyber Security Centre (ACSC) published "Opportunities for AI in Cyber Defence" on 27 May 2026. It is a dense government document. We read it so you do not have to. Here is the short version, written for business owners who need to act, not study.

TL;DR

AI can strengthen your cyber defence. It helps you prioritise alerts, detect threats faster, and respond under pressure. But AI is not a substitute for basics like patching, access controls, and staff training. The ACSC is clear: adopt AI to support your people, not replace them.​‌‌​​​​‌‍​‌‌​​​‌‌‍​‌‌‌​​‌‌‍​‌‌​​​‌‌‍​​‌​‌‌​‌‍​‌‌​​​​‌‍​‌‌​‌​​‌‍​​‌​‌‌​‌‍​‌‌​​‌​​‍​‌‌​​‌​‌‍​‌‌​​‌‌​‍​‌‌​​‌​‌‍​‌‌​‌‌‌​‍​‌‌​​​‌‌‍​‌‌​​‌​‌‍​​‌​‌‌​‌‍​‌‌​​‌‌‌‍​‌‌‌​‌​‌‍​‌‌​‌​​‌‍​‌‌​​‌​​‍​‌‌​​​​‌‍​‌‌​‌‌‌​‍​‌‌​​​‌‌‍​‌‌​​‌​‌‍​​‌​‌‌​‌‍​‌‌‌​​‌‌‍​‌‌​‌‌​‌‍​‌‌​​​‌​‍​​‌​‌‌​‌‍​‌‌​​‌‌‌‍​‌‌‌​‌​‌‍​‌‌​‌​​‌‍​‌‌​​‌​​‍​‌‌​​‌​‌

Meanwhile, attackers are already using AI against you. Phishing emails that used to take 16 hours to craft now take 5 minutes (IBM X-Force 2025). The first documented AI-assisted zero-day exploit has been confirmed (Google GTIG 2025-26). APT45 fired off thousands of AI prompts to recursively analyse vulnerabilities and build working proof-of-concept exploits.

The gap between attackers and defenders is widening. The ACSC guidance is your map for closing it.

The threat is real and it is accelerating

Let us talk numbers.

The average cost of a data breach globally hit $4.44 million in 2025, according to IBM and Ponemon. Thirteen percent of firms surveyed experienced a breach. For a small business, a single incident can be existential.

Phishing remains the number one entry point. Verizon's 2025 DBIR found 36% of breaches involve phishing, with a median click time of just 21 seconds. Your staff have less than half a minute to spot a trap.

Now layer AI on top of that. KnowBe4 and VIPRE reported in 2025 that 82.6% of phishing emails are now AI-generated. Harvard Business Review published research showing AI spear phishing achieves a 54% click-through rate, compared to 12% for human-written messages.

That is a four-and-a-half-fold increase in effectiveness.

Voice phishing (vishing) attacks surged 442% in the second half of 2024 alone, per CrowdStrike's 2025 threat report. Attackers clone voices, impersonate executives, and pressure staff into transferring funds.

At the top end of the threat spectrum, researchers at the University of Illinois Urbana-Champaign demonstrated that GPT-4 can autonomously exploit known vulnerabilities at an 87% success rate. Google's Threat Intelligence Group documented the first zero-day exploit developed with AI assistance. This is no longer theoretical.

Gartner projects global information security spending will reach $246.2 billion in 2026, up 13.3% year over year. Yet enterprises are spending 17 times more on AI tools than on securing the AI itself. Only about 6% of organisations have an advanced AI security strategy in place (BigID 2025).

The attackers have AI. Most defenders do not. That is the problem the ACSC is trying to fix.

What the ACSC actually said

The ACSC maps AI capabilities across six functions from the Information Security Manual (ISM). Think of these as the six things every business needs to get right, regardless of size.

Govern

This is about decision making at the top. AI can help you evaluate risk, interpret security policies, and manage your Software Bill of Materials (SBOM). For SMBs, this means using AI tools to understand what software is running in your environment and where the gaps are. You cannot protect what you cannot see.

Identify

AI excels at asset discovery and patch prioritisation. It can also chain vulnerabilities together, showing how a weakness in one system can cascade into a breach of another. If you have ever wondered which of your 47 unpatched systems matters most, this is where AI earns its keep.

Protect

AI can recommend hardening actions, evaluate your architecture, and scan code for vulnerabilities before it goes live. This is your preventative layer. Think of it as a second pair of eyes on every configuration change and every line of code.

Detect

This is where AI shines brightest. Event detection, telemetry analysis, behaviour baselining. The ACSC specifically references MITRE ATLAS, a framework for understanding adversarial attacks against AI systems. AI tools can learn what normal looks like on your network and flag what does not fit. For SMBs without a 24/7 security operations centre, this capability is a lifeline.

Respond

When an incident hits, AI can correlate alerts, suggest response sequences, and even draft incident updates for your team and stakeholders. The ACSC highlights AI's ability to augment surge capacity. In plain English: when everything is on fire, AI helps your small team punch above its weight.

Recover

AI can analyse restore pathways, trigger automated recovery processes, and validate that systems have been properly restored. It can also help you roll back AI models that have been tampered with. Recovery is where most incident response plans fall apart. AI gives you a structured path back to operational.

Here is the important part. The ACSC places these functions on a spectrum. On one end, you have AI embedded in security tools you already use. In the middle, general-purpose large language models (LLMs) like ChatGPT or Claude. On the far end, frontier AI models and agentic AI. Those are systems that can independently plan, decide, and take actions without human intervention.

Agentic AI introduces additional risk. The ACSC is explicit about this. Systems that act on their own need more guardrails, not fewer.

The adoption principles you need to follow

The ACSC lays out seven principles for adopting AI securely. We translated each one into what it means for your business.

Human oversight

AI should support your people, not replace them. Every AI-generated alert, recommendation, or action should be reviewable by a human before it is executed. This is especially true for agentic AI systems. If a tool claims to "autonomously remediate threats," ask who approves the remediation before it runs.

System protection

Run AI tools in sandboxed environments with minimal privileges. Do not give your AI security tool access to everything on day one. Segment it. Contain it. Treat it like any other privileged account.

Secure system integration

How does the AI tool connect to your existing stack? Does it use APIs with proper authentication? Does it store data locally or in the cloud? Does it phone home? Map the data flows before you plug anything in.

Governance

You need policies for how AI is used in your security operations. Who can deploy AI tools? Who reviews their output? What happens when the AI gets it wrong? Write it down. Enforce it.

Supply chain

This is where AIBOMs come in. An AI Bill of Materials is like an SBOM but for AI models. It documents what data the model was trained on, what version it is, and what its known limitations are. Ask your vendors for both SBOMs and AIBOMs. If they cannot provide them, that is a red flag.

Testing and assurance

Test AI tools before you deploy them. Run them in a staging environment. Feed them known inputs and verify the outputs. The ACSC recommends continuous testing, not just a one-time check at deployment.

AI Secure by Demand

This is procurement language. When you buy security tools, demand that AI features are secure by design. Do not accept "we added AI" as a feature. Ask how the AI was built, how it is protected, and how you can verify its behaviour.

What to ask your vendors

The ACSC guidance includes a set of questions in Appendix A designed for procurement. Here are the ones that matter most for SMBs.

  • How does your AI model make decisions? Can you explain its outputs in plain language?
  • What data was used to train the model? Was any of it customer data?
  • How do you protect the model from adversarial attacks or tampering?
  • Can you provide an AIBOM and SBOM for this product?
  • What human oversight controls are built into the system?
  • How is the AI model updated, and how are updates validated?
  • Where is my data processed and stored when using this tool?
  • What happens if the AI produces a false positive or false negative?
  • Can I configure the level of autonomy the AI has in my environment?
  • How do you handle incident response when the AI itself is the attack vector?

If a vendor cannot answer these questions clearly, walk away. You are a small business. You cannot afford to inherit someone else's AI risk.

The bottom line

The threat landscape has changed. Attackers are using AI to work faster, smarter, and at greater scale. The 5-minute phishing email is here. The autonomous vulnerability exploit is here. The 442% surge in voice phishing is here.

But so is the defence. The ACSC has given Australian businesses a clear framework for adopting AI in security operations. The six ISM functions give you structure. The seven adoption principles give you guardrails. The procurement questions give you leverage with vendors.

You do not need to be an enterprise with a $10 million security budget to act on this. You need to start with the basics. Patch your systems. Train your staff. Enable multi-factor authentication. Then layer in AI-powered tools that support your people, not replace them.

The firms that got breached last year were not unlucky. They were unprepared. Ninety-seven percent of them had no AI access controls. Do not be one of them.

Read the full ACSC guidance at cyber.gov.au. And if you need help translating it into an action plan for your business, that is what we do.

Sources: ACSC "Opportunities for AI in Cyber Defence" (27 May 2026), IBM/Ponemon 2025 Cost of a Data Breach Report, Google GTIG 2025-26, IBM X-Force Threat Intelligence Index 2025, Verizon DBIR 2025, CrowdStrike 2025 Global Threat Report, KnowBe4/VIPRE 2025 Phishing Threat Intelligence Report, Harvard Business Review 2024 AI Phishing Study, Gartner 2026 Security Spending Forecast, University of Illinois Urbana-Champaign 2024 Autonomous CVE Exploitation Study, BigID 2025 AI Security Survey.

TL;DR

Bad actors are sneaking dangerous code into trusted software libraries—like swapping real books on a library shelf with trick copies that spy on whoever reads them. The campaign is called GlassWorm, and businesses can protect themselves by checking their software ingredients and locking down developer accounts.


What Is GlassWorm? (The Library Bookshelf Analogy)

Imagine your favourite library. You trust every book on the shelves because the librarians picked them out. Now imagine someone steals a librarian's ID badge, walks in after hours, and swaps a popular book with a fake copy that looks identical on the outside. When you borrow that book, a hidden camera inside starts watching everything you do at home.

That's basically what GlassWorm does to software [1][2]. Programmers build apps using shared code libraries—think of them as bookshelves full of useful tools hosted on sites like npm and PyPI. GlassWorm's operators stole the credentials of real "librarians" (package maintainers) and pushed out poisoned updates that developers pulled in without suspecting a thing [3][9].

How Does GlassWorm Hide Its Secret Instructions?

Here's the clever part. When the fake book needs to phone home for new orders, it doesn't call a regular phone number that could be disconnected. Instead, it checks a public bulletin board that nobody can erase—the Solana blockchain [1]. The attacker writes a tiny note inside a blockchain transaction, and the malware reads it to learn where to send stolen data. Because blockchain entries are permanent, defenders can't simply delete the note the way they'd take down a website [2].

What Does GlassWorm Actually Do Once It's Inside?

The attack happens in stages—like chapters in that trick book. First, it settles in quietly. Then it starts copying your saved passwords, cryptocurrency wallets, and information about your computer [1][2]. In the final stage, it installs a remote control tool (called a RAT) that lets the attacker see your screen, record your keystrokes, and even trick you into handing over hardware wallet codes for devices like Ledger and Trezor [1]. It also adds a fake Chrome extension pretending to be "Google Docs Offline" that watches almost everything you do in your browser—cookies, bookmarks, screenshots, and thousands of history entries [2][7].

How Can Businesses Stay Safe?

The good news: you don't need a massive security team to protect yourself. Think of it as better library hygiene [4][6][10]:

  • Check the books before shelving them. Use tools that scan your software dependencies for known bad packages [3][5].
  • Protect the librarian badges. Turn on multi-factor authentication for every developer account so attackers can't steal credentials easily [4][10].
  • Keep a list of every book on the shelf. Maintaining a Software Bill of Materials (SBOM) means you can quickly find and remove a bad package when one is discovered [6].
  • Lock the browser extension shelf. Only allow approved Chrome extensions through your organization's policy [7].

Taking these steps isn't about being scared—it's about running a tighter ship so you can focus on building great products with confidence [8].


FAQ

A supply chain attack is when bad actors sneak malicious code into trusted software libraries or tools that developers use to build applications. Instead of attacking your business directly, they compromise the building blocks your software depends on [4][9].

Yes. If any software your business uses was built with compromised packages from npm or PyPI, it could carry GlassWorm's malicious payload. This is why maintaining a Software Bill of Materials (SBOM) matters—so you know exactly what ingredients are in the software you rely on [3][6].

GlassWorm writes its command-and-control instructions into Solana blockchain transaction memos. Because blockchain entries are permanent and decentralised, security teams cannot simply take down a website or block a domain to cut the malware's communication line [1][2].

Start with three steps: enable multi-factor authentication on all developer and admin accounts, use dependency scanning tools to check software packages before deploying them, and restrict Chrome extension installations to an approved list only [4][6][10].


Want help checking your software supply chain? Schedule a free consultation.


References

[1] I. Makari, "GlassWorm: Chrome Extension RAT Using Solana Dead Drops," Aikido Security Blog, Mar. 2026. [Online]. Available: https://www.aikido.dev/blog/glassworm-chrome-extension-rat

[2] R. Lakshmanan, "GlassWorm Malware Uses Solana Dead Drops to Deliver RAT and Steal Browser, Crypto Data," The Hacker News, Mar. 25, 2026. [Online]. Available: https://thehackernews.com/2026/03/glassworm-malware-uses-solana-dead.html

[3] Sonatype, "State of the Software Supply Chain Report 2025," Sonatype, 2025. [Online]. Available: https://www.sonatype.com/state-of-the-software-supply-chain

[4] CISA, "Defending Against Software Supply Chain Attacks," Cybersecurity and Infrastructure Security Agency, Apr. 2023. [Online]. Available: https://www.cisa.gov/sites/default/files/publications/defending_against_software_supply_chain_attacks_508_1.pdf

[5] Synopsys, "Open Source Security and Risk Analysis Report 2025," Synopsys, 2025. [Online]. Available: https://www.synopsys.com/software-integrity/resources/analyst-reports/open-source-security-risk-analysis.html

[6] NIST, "Software Supply Chain Security Guidance," NIST SP 800-218, Feb. 2022. [Online]. Available: https://csrc.nist.gov/publications/detail/sp/800-218/final

[7] Google, "App-Bound Encryption for Chrome Cookies," Google Security Blog, 2024. [Online]. Available: https://security.googleblog.com/2024/07/improving-security-of-chrome-cookies.html

[8] IBM Security, "Cost of a Data Breach Report 2025," IBM, 2025. [Online]. Available: https://www.ibm.com/reports/data-breach

[9] European Union Agency for Cybersecurity (ENISA), "Threat Landscape for Supply Chain Attacks," ENISA, 2021. [Online]. Available: https://www.enisa.europa.eu/publications/threat-landscape-for-supply-chain-attacks

[10] OpenSSF, "Package Repository Security Best Practices," Open Source Security Foundation, 2024. [Online]. Available: https://openssf.org/blog/package-repository-security/

Ready to strengthen your security?

Talk to lilMONSTER. We assess your risks, build the tools, and stay with you after the engagement ends. No clipboard-and-leave consulting.

Get a Free Consultation