The three families of AI risk at work
Think of AI at work like a new kitchen helper. They might leak the secret family recipe (privacy), they might treat some customers unfairly without noticing (bias), or someone might trick them into opening the back door (security and misuse). Knowing the three kinds of trouble helps you look in the right places.
- The Canadian Centre for Cyber Security (guidance ITSAP.00.041) names these generative AI risks, among others:
- Privacy of data: users may unknowingly enter sensitive company data or personal information into prompts.
- Biased content: training data from the open internet and unbalanced representation can make output prejudiced.
- Misinformation and disinformation: AI content that isn't clearly labelled can spread false information.
- Phishing: attackers can write more frequent, automated and convincing spear-phishing messages.
- Malicious code and buggy code: attackers can create malware, and developers can introduce insecure code.
- Poisoned datasets: malicious content in training data can weaken output quality and raise supply-chain risk.
- Loss of intellectual property: AI can help attackers steal company data more easily.
- This course groups them in three families:
| Family | The question it asks | Example at work |
|---|---|---|
| Privacy | Whose information is going in or coming out? | A support agent pastes a customer's full file into a chat |
| Bias | Could the result treat some people unfairly? | AI ranks job applicants and favours one group |
| Security and misuse | Could someone trick or abuse the tool? | A web page hides instructions for an AI agent |
- The Cyber Centre's advice to organizations includes setting policies on how AI is used, choosing vendors carefully, being careful about what information goes in, using MFA, applying updates, and training employees.
- Write down every way your team already uses AI (writing, summaries, search, spreadsheets, customer replies). Include tools people use on their own.
- For each use, write the kind of information that goes in: public, internal, or personal.
- Label each use with one family that worries you most: Privacy, Bias, or Security and misuse.
- Circle any use that touches personal information or decisions about people.
- Put the circled uses at the top. These are the ones you will examine first in the next lessons.
- Check: every use has an information type and a family label, and at least one is circled or you can explain why none is.
Videos by other creators on YouTube, for reference. They are not made by or affiliated with The Future Market.
Read the video script
[Host] "AI at work can go wrong in three ways. Learn them and you know where to look."
[Text on screen: 1. Privacy] "One: privacy. Someone pastes in information that should not leave the building."
[Text on screen: 2. Bias] "Two: bias. The result treats some people unfairly, and nobody notices."
[Text on screen: 3. Security and misuse] "Three: security. Someone tricks the tool, or uses it to trick you."
[Host] "Name the family first. Then you can fix the right thing."
Make a one-page list of your team's AI uses with the information type and family for each, and circle the top three to review.
ClaudeStuck? Copy a ready-made prompt for Claude
Copy this, open Claude, paste it, and Claude will walk you through the lesson step by step.
For a grown-up: Claude is for adults (18+). Copy this, paste it into Claude, and use the answer to explain the lesson to your child.
I'm learning "AI Risk at Work: privacy, bias and misuse in practice" on The Future Market. Lesson 1: "The three families of AI risk at work". What the lesson teaches: - The Canadian Centre for Cyber Security (guidance ITSAP.00.041) names these generative AI risks, among others: - Privacy of data: users may unknowingly enter sensitive company data or personal information into prompts. - Biased content: training data from the open internet and unbalanced representation can make output prejudiced. - Misinformation and disinformation: AI content that isn't clearly labelled can spread false information. - Phishing: attackers can write more frequent, automated and convincing spear-phishing messages. - Malicious code and buggy code: attackers can create malware, and developers can introduce insecure code. - Poisoned datasets: malicious content in training data can weaken output quality and raise supply-chain risk. The exercise I'm working on: Make a one-page list of your team's AI uses with the information type and family for each, and circle the top three to review. I'm stuck. Please: 1. Explain the main idea in plain, simple words with one everyday example. 2. Walk me through the exercise one small step at a time. Ask me what I've done so far before giving the next step. 3. Don't just give me the final answer. Help me do it myself, and check my work when I share it.
I'm a parent helping my child (about 8 years old) with a lesson called "The three families of AI risk at work" from the course "AI Risk at Work: privacy, bias and misuse in practice". Here's what the lesson says: Think of AI at work like a new kitchen helper. They might leak the secret family recipe (privacy), they might treat some customers unfairly without noticing (bias), or someone might trick them into opening the back door (security and misuse). Knowing the three kinds of trouble helps you look in the right places. The activity: Make a one-page list of your team's AI uses with the information type and family for each, and circle the top three to review. Please explain this so an 8-year-old understands: short sentences, a fun everyday example, and no hard words. Then give me 3 simple questions I can ask my child to check they understood, and a way to do the activity together, one tiny step at a time.
Sources
- Canadian Centre for Cyber Security, Generative artificial intelligence (AI) (ITSAP.00.041): www.cyber.gc.ca/en/guidance/generative-artificial-intelligence-ai-itsa
Privacy at work: what regulators expect
This lesson is part of full access: every course and every level for one payment.
When something leaks: privacy breaches
This lesson is part of full access: every course and every level for one payment.
Bias in practice: decisions about people
This lesson is part of full access: every course and every level for one payment.
Security and misuse: tricks, scams and bad code
This lesson is part of full access: every course and every level for one payment.
A simple AI risk check
This lesson is part of full access: every course and every level for one payment.
Do and don't rules for your team
This lesson is part of full access: every course and every level for one payment.
Final project
This lesson is part of full access: every course and every level for one payment.
Quiz
Name the three risk families used in this course.
Privacy, bias, and security or misuse.
According to good-practice AI guidelines, when should personal information go into a prompt?
Only when authorized and necessary; use de-identified data where personal information is not required.
Under Anthropic's commercial terms, who is the data controller and who is the processor?
The customer is the controller; Anthropic acts as the processor.
When should an organization report a breach to the regulator and notify people?
When there is a real risk of significant harm; check your own country's rules and deadlines.
What two things does a real risk of significant harm depend on?
How sensitive the information is and how likely it is to be misused.
What should you do with records of data breaches?
Keep a record of every breach, whether or not it reached the harm threshold, for as long as your country's rules require.
Many countries set short deadlines to notify the regulator of a breach. What should you do?
Learn your country's deadline in advance and report inside quickly.
Who must make the final decision when AI helps with hiring or grading?
A named person, not the AI.
What is prompt injection?
Hidden adversarial instructions in content that an AI processes, which can hijack its behavior.
What is a safe starting rule for an AI tool that can take actions?
Start read-only and require human approval before it sends, deletes, pays or publishes.
Final exam
This lesson is part of full access: every course and every level for one payment.
Certificate
This lesson is part of full access: every course and every level for one payment.