Tip #5 — Ask, Assess, and Analyze Before Using New Technology
The Goose rolled in a new Smart Toaster for Toast Time — the campus tradition of bread, toppings, and toasters bringing the community together.
The Big Banana cheers, “Check it out — it remembers preferences, personalizes browning, and even suggests toppings with AI!” Curious, Banana leans in to try it. The toaster buzzes and flashes a message on its tiny screen: “Face not detected — unable to personalize.”
Conrad cautions with concern, “Wait… that toaster’s creating more than crumbs — it’s scooping up personal information too! Did you get an Information Risk Assessment (IRA) and Privacy Impact Assessment (PIA) before rolling it in? Smart devices can have cameras, sensors, or other hidden risks.”
The Goose admits sheepishly, “Uh… no. I just bought it with my Purchasing Card (P-card).”
“Doesn’t matter if it’s bought through procurement, P-card, or built-in-house — you still need an IRA and PIA,” AHSSIE advises firmly. “Skipping them is like skipping a health checkup: it may seem fine at first, but it opens the door to bigger problems — privacy violations, compliance gaps, reputation damage, or even new entry points into the network.”
Porcellino remarks knowingly, with a grin, “Rubbing my nose might bring luck — but security needs more than luck. It requires expert checks.”
Cobalt adjusts their googles and points out, “Exactly. Technology is moving faster than regulators can keep up. That means we carry more responsibility to stay cautious, ask questions, and consult experts before jumping in.”
“And it’s not just toasters,” Pinky cautions. “Many third-party cloud Software-as-a-Service (SaaS) platforms now use integrated AI to automate decisions or generate content — often using your data to train their models without clear notice. They carry inherent risks like bias, errors, and hallucinations, and are susceptible to data poisoning. All the while, it is expanding the attack surface."
Reni the Moose chuckles, “Expanded attack surface might sound like more room for me — but in security, it just means more ways for attackers to get in.”
“Attackers take advantage of that expanded surface,” King Warrior declares. “With AI, they can automate scans and even leverage Large Language Models (LLMs) like ChatGPT or Gemini to generate exploits. It is like cutting corners in a game. What once took skill and practice, now takes almost none. That’s why we must stay disciplined and ready to defend.”
The Tool stresses, “LLMs aren’t just handy for attackers — we use them in daily tasks too. That means we need to be careful: don’t put anything in an AI tool you wouldn’t post publicly and always follow IST’s guidelines on responsible use of AI tools with university data.”
Jerome warns with a wince: “Like a thorn in the paw, one careless paste of non-public data into an LLM can hurt. And once it’s in, you can’t pull it back out — it may leak or get absorbed into training where you lose control.”
Toasty exclaims, “That’s right — little mistakes can cause big problems. Cybersecurity is participatory — everyone has a role. Stay informed, complete your training, and help protect our community.”
The Goose concludes, “Cybersecurity is about people first — our habits, choices, and awareness — not just the technology we use.”
Key Takeaways
- Understand emerging risks: New devices and AI features expand the attack surface and can introduce privacy or compliance gaps.
- Do the checks: complete IRAs/PIAs before using new tech.
- Think before you paste: Only share public information into AI tools. When in doubt, refer to the IST’s guidance on information confidentiality classification to determine whether data is public, confidential, restricted, or highly restricted. Anything beyond public must stay out of LLMs. To learn more about generative AI on campus, visit the GenAI Hub.
- Complete your training:
- Faculty & Staff: Register for annual cyber awareness training in LEARN.
- Students: Create an account with Cyber Security Ontario to access their free Learning Modules.
- Stay informed: Sign up for Information Security Services’ Cyber Awareness newsletter and keep up with threats through Get Cyber Safe and the Canadian Centre for Cyber Security.
- Play your part: Report suspicious emails, odd logins, or unusual activity to the SOC, soc@uwaterloo.ca.
Securing IoT Devices at UW
- Change default passwords: set strong, unique credentials. Keep firmware updated: apply updates regularly.
- Limit access: restrict which accounts, devices, or networks can connect.
- Avoid direct exposure: keep devices behind secure networks/firewalls.
- Turn off extras: disable unused features (mics, Bluetooth, remote access).
- Plan ahead: replace devices when vendor support ends.
- UW standards: see IST’s security standards for network peripheral devices.
Don’t be a silly Goose: cybersecurity is everyone’s job — it starts with you. Play your part, and together, curiosity with caution, will keep Waterloo secure.
Campaign feedback
Have thoughts on Goose & Friends? Share your feedback on Cyber Awareness Month.
Top #4 - Layer your defenses: Qualys Agent scans for weaknesses, SentinelOne Agent stops active threats
The Goose had just upgraded their laptop from Windows 10 to Windows 11 and leaned back, satisfied. Windows 10 support ended on October 14, 2025, which means no more security patches or fixes resulting in more openings attackers can use to break in. With a long device password and Waterloo’s security software, SentinelOne Agent for Endpoint Detection and Response (EDR) tool for threat detection and response and Qualys Agent for vulnerability scanning, installed, The Goose’s laptop was well protected.

Feeling confident, the Goose settled in to browse for teaching resources. The Goose found what looked like a free textbook online. Excited, they downloaded it and ran the file, and malware slipped onto the device.
At first, nothing seemed wrong, the screen looked normal, the laptop ran as usual. Then, in the corner of the screen, a pop-up flashed: “SentinelOne Agent has detected and quarantined a threat.”
The Goose exhaled in relief, “Wow… that was lucky.”
Porcellino, tapping their nose knowingly, said, “It wasn’t luck that saved you — it was the SentinelOne Agent. Its behavioural AI detected suspicious processes and quarantined the threat before any data could be stolen. Without it, you might never have known — the malware could have changed settings, installed backdoors, or even spread across the network."
The Goose was about to learn what happens when protection is missing, and luck is all that’s left.
A sponsored research server under The Goose’s responsibility was breached by ransomware. Waterloo’s Security Operations Center (SOC)’s investigation revealed that neither Qualys Agent nor SentinelOne Agent had been installed, leaving sensitive research data at risk.
The research contract required “reasonable security controls” to be in place. Qualys Agent would have shown whether the system was patched and hardened against known flaws, and SentinelOne Agent would have provided real-time detection and response to stop ransomware before it spread. By skipping both, The Goose had no way to argue that safeguards had been followed.
The incident had to be reported to the sponsor, with no certainty that attackers wouldn’t return or release stolen data. That lapse carried consequences far beyond The Goose’s desk: legal and contractual issues surfaced, Waterloo’s reputation suffered, and sponsors began to question whether the university could be trusted with future projects. One neglected responsibility threatened the work of the entire community.
That’s when Pinky the Tie spoke, their voice steady from years of experience, “I’ve been sabotaged and stolen before — that’s why the Tie Guard was created, to keep me safe. Qualys Agent and SentinelOne Agent are our University’s device guards."
"Qualys Agent finds the cracks the attackers exploit, and SentinelOne Agent stops intruders in their tracks. But guards can’t protect you if you ignore them, or worse, never call on them at all. Device protection isn’t optional. Just as the Tie Guard shields me, these agents shield you, your colleagues, and the entire University.”
The Goose's Pro Tips
- Mobile devices (smartphones, tablets) carry email, contacts, files, and 2FA codes -- keep them updated, secure, and locked.
- Report lost or stolen devices to your mobile carrier or local IT if UW-owned.
Key Takeaways
University-owned devices
- Install security agents: Ensure SentinelOne Agent and Qualys Agent are active.
- Back up University data: Use Microsoft 365 (OneDrive, SharePoint, Teams) to store University data. For centrally managed servers, workstations, or laptops, departments and system administrators can use the IST Backup Service — a high-performance, encrypted, on-campus backup solution with retention policies and recovery options.
- Monitor and patch: Watch for emails from your local IT team or SOC regarding security instructions or vulnerability alerts and apply patches promptly.
- Follow UW standards: Learn and adhere to Waterloo’s security standards for desktops and laptops.
- Lost or stolen devices: Contact your local IT team immediately if a university device is lost or stolen.
- Report suspicious activity: If a device is infected, behaving unusually, or you suspect a security incident, report it to the SOC: soc@uwaterloo.ca.
Personal devices
- Install antivirus: Use a trusted solution such as Windows Defender, macOS built-in protections, or another recommended option.
- Back up your data: Use cloud storage (Microsoft 365, Google, Apple) for important files and maintain separate local backups for extra resiliency.
All devices
- Protect access: Password-protect devices and lock screens when away.
- Remove unused apps: Delete apps you no longer use to reduce the attack surface and potential vulnerabilities.
- Apply updates promptly: Keep operating systems and applications up to date.
- Windows 10 support has ended: Windows 10 support ends on October 14, 2025. Devices still running it are vulnerable to unpatched exploits. Upgrade to Windows 11.
- Track support and EOL: Ensure operating systems and applications are actively supported. Know their End-of-Life (EOL) dates, typically published by the vendor. A useful resource: endoflife.date.
Don’t be a silly Goose — deploy the agents, your digital guards against threats.
Tip #3 - The Goose and the Midnight Buzz: The 2FA Fatigue Trap
It was the middle of the night when The Goose’s phone buzzed.
Duo Push Request… Duo Push request… Duo Push request.
At first, The Goose denied them. By the tenth request, The Goose was groggy and frustrated. Wanting the notifications to stop, they tapped Approve.
What The Goose didn’t realize was that this attack could only happen because their password had already been compromised. Attackers entered it into the login page, which triggered the 2FA requests. Without that first line of defense falling, the attackers would have had no way in.
Accepting the push request gave attackers access to The Goose’s Waterloo email account. By morning, messages were blasting across campus and beyond: ‘Work at Waterloo! Easy job, high pay, no experience needed.’ Each included a malicious link.
The scam didn’t just hit campus. It also reached The Goose’s personal contacts — and one friend, thrilled at the idea of working at Waterloo alongside The Goose, clicked the link without thinking, which installed malware on their device. Goose felt awful, realizing their slip had pulled someone else into the mess.
King Warrior was one of the recipients. He didn’t click right away. Instead, he studied the email — and knowing The Goose, there was no way they were recruiting for jobs at Waterloo. At that moment, Warrior identified the email as suspicious: this was a phishing attempt. Acting fast, he forwarded the message as an attachment to the Security Operations Centre (SOC). Thanks to his quick thinking, SOC locked The Goose’s account, cutting off the attackers before the scam could spread further.
But that wasn’t the only damage. With the same access, attackers also signed in to The Goose’s Workday account. There, they quietly changed Goose’s direct deposit information to their own account. When payday came, The Goose’s pay cheque went straight to the attackers instead. The Goose was devastated — not only had their account been used to phish the entire campus, but there was the added stress of working with Human Resources to recover their missing pay.
King Warrior spots The Goose and shakes his head. “You really are a silly Goose — accepting Duo push notifications you didn’t initiate. That’s how the attackers got in.”
The Goose looks down, embarrassed. “I thought I was safe — I’ve got a strong passphrase, I use a password manager, and I even had 2FA. But I just wanted the buzzing to stop so I could sleep…”
Cobalt the Dinosaur overhears and adjusts their goggles. “Let me explain the science, Two-Factor Authentication (2FA), sometimes called Multi-Factor Authentication (MFA) — means you need more than just a password to log in. It adds a second check, like something on your phone or a device you carry with you."
Authenticator apps and push notifications both add a second step beyond your password, but they can still be misused if attackers trick you into sharing a code or approving a request you didn’t start. Hardware tokens go further — they’re phishing-resistant and prove you’re physically present. Not everyone needs a hardware token day to day, but they’re a smart choice for protecting high-value or high-risk accounts. Text messages and email codes are weaker, but still better than no 2FA at all.
The Goose asks: “So here at Waterloo, what should I be using?”

Cobalt nods. “Most University systems use Single Sign-On (SSO) with Duo 2FA — that’s your foundation. Some systems outside SSO still offer 2FA in other ways. But a few don’t support 2FA at all, and those need extra care. If you run into one, contact your local IT team or Information Security Services, so the risks can be assessed and safeguards put in place.”
Warrior steps in again, pointing at The Goose. “And don’t forget — your personal accounts matter, too. Protect them with 2FA, where possible. Duo works with many other apps, and you can also secure your logins with sign-in partners like Google, Apple, or Microsoft. Just make sure you’ve turned 2FA on everywhere.”
Key Takeaways
- Secure every account: Turn on 2FA for campus and personal accounts wherever it’s offered.
-
Choose the most secure 2FA option available:
-
Hardware Security Keys – best, phishing-resistant. More advanced than most people need day-to-day, but ideal for high-risk accounts.
-
Authenticator apps or push notifications – good, convenient, widely supported, but can still be phished or misused if you share codes or approve a login you didn’t start.
-
SMS or email codes – weakest, use only if there is no other choice.
-
-
Don’t give in to fatigue: Deny any 2FA request you didn’t start, no matter how many times it pops up.
-
Never share codes: They’re like temporary passwords — giving them away hands attackers the keys.
-
Spot the phish: If it seems too good to be true, it almost always is. Phishing scams often dangle easy money, prizes, or offers that feel urgent or irresistible. Pause, think, and verify before you click. Learn how to Defend against phishing at Waterloo.
-
Assess the risks: Ensure all systems, including research and departmental tools, go through an Information Risk Assessment to identify authentication risks and the most secure 2FA option is applied.
-
Report suspicious activity: Always deny Duo requests you didn’t initiate and report them to the SOC: soc@uwaterloo.ca
Don’t be a silly Goose — deny unexpected pushes and secure your accounts with 2FA.
Tip #2 – Use strong, unique passphrases and store them securely with a password manager
The Goose and the Great Password Panic
The Goose believed they were safe with an 8-character password they thought was very complex — numbers, letters, even a symbol. But attackers cracked it in just three hours.
Because The Goose reused that same password everywhere — email, banking, shopping, and social media — the fallout came fast.
Before The Goose knew what was happening, their inbox flooded with hundreds of spam emails. Annoyed, The Goose just deleted them. Then came the embarrassment, a friend messaged, “Why are you spamming me with Bitcoin scams on Instagram?” And finally, the heartbreak — The Goose’s grandma wired money to an attacker, after receiving a desperate plea from The Goose’s hacked Facebook account.
Starting to panic, The Goose went back to those “spam” messages for another look. Buried in the pile was an Amazon confirmation, proof of a purchase worth thousands of dollars. The rest of the emails weren’t random at all, they were junk deliberately sent by attackers to bury the real alerts, hoping The Goose would ignore the evidence of fraud.
Realizing this was more than just annoying spam, The Goose finally remembered what they’d been told: if you think your account has been compromised, contact the Security Operations Centre (SOC).
Luckily, SOC confirmed that The Goose’s WatIAM account was safe; Duo 2FA had stopped attackers from breaking in. Still, SOC instructed The Goose to change their password immediately and began an investigation to see whether the compromised password had been used on any other University services which were not protected by Duo.
And then came the final blow. As SOC investigated the suspicious activity tied to Goose’s locked account, they uncovered signs that the same compromised credentials had been used in a research application. And because the system had been set up without a formal risk assessment, 2FA hadn’t been enabled.
The consequences were severe. The project’s funding sponsor and the Privacy Commissioner had to be notified. Ethics violations and fines were on the table. The university’s ability to continue working with the sponsor could be jeopardized — not to mention the reputational damage to researchers and the institution.
Later that day, feeling defeated, The Goose turned to their friends for help. Luckily, their friends had some great advice.
The Tool gleamed, “Attackers will hammer away at your password — so make sure it’s as solid as me. Attackers can snap weak ones in seconds, but a long passphrase — real words forged together — stands firm. Try something like ILovePastaWith7KindsOfCheese! It’s simple for you, brutal for them.”
Big Banana warned, “Reuse is good for the planet and sustainable, but not for passwords.”
The Tool Bearers piped in, “The Tool was kidnapped once, by the folks at the University of Toronto. Now we the Bearers protect the Tool at all times. That’s what a password manager can do for you — it safeguards every password, keeps them organized, and ensures no one can take them from you.”
“Skipping an Information Risk Assessment is like dumping waste into a river,” The Big Banana added. Even research systems need a proper review so security protections like 2FA don’t get left out. Otherwise, the whole campus ecosystem gets polluted.”
The Goose’s Pro Tips
- Check Yourself: Use haveibeenpwned.com or your password manager’s alerts to see if your passwords have been exposed. Change them immediately if they have.
- Curious how strong your password really is? Try Bitwarden’s trusted password strength checker and see how long it would take to crack. (Spoiler: short ones don’t last long.)
- Security Questions: Treat them like extra passwords. Don’t use real answers. Save made-up ones in your manager. Example: What is your father’s name? → DarthVader2025!
Features of a Password Manager
- Encrypts and stores all your passwords in one protected vault.
- Creates strong, unique passwords for every account—you only need to remember one master password.
- Syncs across devices, so you’re never locked out.
- Monitors breaches and alerts you if any of your credentials appear in a data leak.
- Blocks phishing by only auto filling credentials on the exact website they were saved for (it won’t autofill on a fake login page). Learn more to Defend against phishing at Waterloo.
At Waterloo, Bitwarden and 1Password have been risk-assessed by Information Security Services. Either are recommended.
Don’t be a silly Goose — use a password manager to keep every account secure!
Key Takeaways
- Build strong, unique, long password: Minimum 15 characters. Review Waterloo’ s Password standards to ensure your password meets requirements.
- Never reuse passwords: One password should only ever unlock one account.
- Manage them securely: Use a reputable password manager.
- Never share your password with anyone, including family, friends, and IT help.
- Protect your WatIAM account: Learn how to manage your account, username, and password.
- Engage in an Information Risk Assessment: ensure that any system handling University data, including research systems, goes through review so critical safeguards like 2FA are in place.
- Report suspicious activity: If you think your account has been compromised, contact the SOC: soc@uwaterloo.ca
Tip #1 – Be mindful and limit your digital footprint
The Goose and the Terrible, Horrible, No Good, Very Bad Day
The Goose was juggling too much: budget cuts at work, a looming term paper, texts from home, and doom-scrolling the news. Distracted and stressed, they moved too fast, and mistakes piled up.
It began the night before. The Goose was venting online in a heated moment and posted a harmful comment about a classmate in a public forum. To cool off, they took a few “fun” online quizzes. The quizzes asked for personal information like a first pet’s name, which seemed harmless at the time.
The next morning, The Goose started going through their Waterloo inbox. A message from their Associate Dean had arrived notifying them of a Policy 71 charge for disruptive or aggressive behaviour by electronic means. The late-night post had been reported. The Goose felt the sharp sting of regret for last night’s online venting.
Shaken, The Goose skimmed past another message, a shared document from a classmate. Distracted, they clicked the link. The page asked for a login even though The Goose was already signed in. The Goose knew this was a red flag, but their brain took a shortcut. Twice they entered their Waterloo credentials before giving up. The attacker now had The Goose’s WatIAM password.
And the attackers were not done. Those “fun” quizzes had given away perfect answers to security questions on The Goose’s Canada Revenue Agency (CRA) account. Combined with the stolen Waterloo credentials that The Goose foolishly reused for CRA, this was enough to reset recovery settings and begin filing fraudulent tax returns, setting the stage for identity theft.
Overwhelmed by the cascade of blunders, The Goose turned to their friends for advice on how to dig out of the mess.
Jerome growls, “Venting feels good in the moment, but like a thorn in your paw, it leaves a digital scar that lingers.”
Conrad chimes in, “Every time you go online, you leave digital crumbs behind. Even small interactions — like answering a quiz, posting a comment, or sharing a favourite memory — add to your footprint. On their own they seem harmless, but together those crumbs can be pieced into a profile attackers may exploit.”
AHSSIE explains with care, “Attackers count on us being rushed and running on autopilot. Mindfulness isn’t just healthy practice to calm your mind and be present — it’s also one of the best cyber defences. Small slips can create big problems. By slowing down, acting with intention, and noticing when something feels off, you give yourself the chance to avoid another terrible, horrible, no good, very bad day.”
Key Takeaways
- Slow down under pressure. A calm mind is your best defense.
- Observe, describe, and participate. Notice what is on your screen, identify the red flags, and act with intention. Do not run on autopilot.
- Hover over links to see where they go before you click. The link text does not have to match the destination.
- Check the sender. A display name does not have to match the email address.
- Think before you type. Legitimate services will never ask you to enter your username or password in a Google Form or directly in an email.
- What goes online, stays online. Deleting a post doesn’t erase screenshots, shares, or archives — once it’s out there, assume it’s permanent.
- Block third-party cookies and use an ad blocker. Do not “accept all” without checking.
- Report suspicious activity. Contact the Security Operations Centre (SOC) at soc@uwaterloo.ca if you think your account has been compromised.
Don’t be a silly Goose—pause, double-check, and act with intention before you leave a digital footprint.
Stay Cyber Aware All Year
Cybersecurity doesn’t stop after October.
Sign up for Waterloo’s Cyber Awareness Newsletter to stay informed year-round about the latest threats on campus and in the news. Each issue shares practical tips to help you avoid pitfalls, protect your accounts, and keep our Waterloo community secure.