Picture a finance officer who gets a voice message from the CEO asking for an urgent payment. The voice is right. The tone is right. The request is plausible. It’s also fake.
AI is now a part of everyday work. Microsoft Copilot, ChatGPT, Claude and Gemini (to name a few) are helping people draft content, analyse information and get through routine tasks faster than ever. The same technology is making cyber threats quicker to produce and harder to detect, and it’s creating new risks inside businesses that haven’t set rules for it.
So, are your policies, systems and people keeping up with how AI is actually used?
What AI changes about cyber risk
Phishing, impersonation, social engineering and data leakage are old problems. AI makes them cheaper to run and harder to spot. Phishing emails used to give themselves away through clumsy wording, spelling mistakes or requests that didn’t add up.
Now AI can write a polished message in your organisation’s tone, mention a real project, and appear to come from a senior leader, colleague or supplier. Deepfake audio, video and images take impersonation further. An urgent request can look and sound completely legitimate, which makes pausing to verify more important than it has ever been.
That’s the message of this year’s Cyber Smart Week: threats are getting more sophisticated, but people remain one of your best defences. An employee who feels able to question an odd request, check it through another channel and report it quickly can stop a convincing attempt becoming a costly incident.
The risk inside your business
Not every AI risk starts with a criminal. Often, it starts with someone trying to finish a task.
An employee pastes source code, customer data, financial figures or meeting notes into a public AI tool without knowing how that information might be stored or used. Another trusts an AI-generated answer without checking whether it’s accurate or secure. Most of the time this isn’t carelessness. Nobody has told them where the line is.
The National Cyber Security Centre’s guidance on engaging with artificial intelligence sets out an informed, secure and responsible approach. It identifies threats to AI systems and offers mitigations for organisations using self-hosted and third-party tools.
Informal AI use is still AI use. If you don’t know how your people are using these tools, you can’t manage the risk.
Your existing policies might not cover this
Most organisations already have policies on acceptable technology use, privacy, information security and data handling. Many were written before generative AI became part of daily work. A blanket ban isn’t the answer either, because it tends to push AI use onto personal accounts and unapproved tools, where you can’t see it.
A usable AI policy answers these questions:
- Which AI tools are approved?
- What information can go into them?
- How do privacy, confidentiality and intellectual property requirements apply?
- When does an output need human review?
- Who approves new use cases, receives incident reports and owns AI governance?
It also has to change over time. Microsoft’s article on responsible AI in 2026 argues for adaptive governance, ongoing risk management and controls such as permissions, monitoring and employee training. That matters more as AI tools start to retain information, access data and take action on a user’s behalf. A policy written once and filed away won’t cover that.
Technology won’t catch everything
Access controls, monitoring and approved platforms matter, but they can’t see every decision an employee makes. Your people are both where things can go wrong and your strongest protection.
Digital literacy now includes using AI securely, questioning what it produces, and recognising when something is misleading or malicious. In practice, employees need to be able to spot unusually convincing phishing, verify unexpected requests for payments, information or system access, and judge what is safe to put into an AI tool. They also need to question realistic-looking audio, video and images and check AI outputs before acting on them. Just as important, they need to be able to report a mistake straight away without worrying about blame. People who fear blame tend to hide mistakes.
Training should fit the role. A developer using AI to write or review code faces different risks from a finance analyst working with company figures or a leader summarising a confidential strategy paper. The closer training is to the decisions people actually make, the more of it sticks.
Five questions to ask before you add more AI tools
Here’s where I would start.
1. How are your people already using AI?
Look past the approved systems. Anonymous surveys and open team conversations will show where staff are using personal accounts or unapproved platforms. Treat it as research, not an investigation. You want to see how work really gets done so you can offer better tools and clearer limits.
2. Do your people know what safe AI use looks like?
Test whether they know what must never go into a public AI tool, when to verify an unexpected request, and who to ask when they’re unsure. Cyber Smart Week’s advice is simple: think twice before putting information into an AI tool, and if in doubt, leave it out.
3. Who is responsible?
Name who approves tools, owns AI governance, monitors risk and responds when something goes wrong. Your technology team will be involved, but accountability needs to reach senior leadership and the wider business.
4. Where are the capability gaps?
Check your depth across cyber security, data governance, privacy, cloud security, architecture, technology risk and responsible AI.
5. Does your workforce plan match your AI strategy?
Decide which skills you can build internally and where you need specialists, whether permanent, contract or project-based. Powerful new tools are wasted if you don’t have people who can introduce and govern them securely.
Closing the capability gap
Last year we looked at the pressure New Zealand organisations face in finding specialist cyber talent, in our blog on navigating New Zealand’s cyber security talent gap. It covered workforce planning, retention, training and flexible resourcing. AI adds another layer.
Some employers will focus on upskilling existing teams and lifting digital literacy across the business. Others will need specialists in AI governance, cyber security, cloud security, data, architecture or technology risk. A permanent hire isn’t always the answer. Contract or project-based specialists can cover a particular implementation, assessment or uplift programme, while permanent staff hold the organisational knowledge that keeps AI well managed over the long term.
Find the gap before it becomes an emergency.
Where to start
AI adoption is as much a people and governance question as a technology one. The organisations that get the most from it will be the ones whose people know the rules, have training that fits their role, and work under governance that changes as the technology does.
If you’re preparing for AI adoption or assessing whether your team has the skills to use it securely, give me a call or get in touch. I can help you understand the talent market, identify capability gaps and plan the permanent or contract hires you need.