Loading module...
Loading module...
GSA-06
Identify malicious links and QR codes, understand public Wi-Fi risks, and practice secure habits that prevent shadow IT from creating vulnerabilities.
General Security Awareness Training
Estimated Time: 15 minutes
By the end of this module, you will be able to:
Phishing emails (covered in depth in Module 2) are the most common delivery mechanism for malicious links, but they're far from the only one. Malicious links can arrive through text messages, Slack DMs, social media posts, search engine ads, and even legitimate websites that have been compromised. The destination is usually one of two things: a credential-harvesting page designed to look like a real login screen, or a site that delivers malware to your device.
On desktop, hover first. Before clicking any link, hover your mouse over it. The actual destination URL will appear in the bottom-left corner of your browser or in a tooltip. If the display text says "Sign in to Microsoft 365" but the URL points to something like microsoft365-verify.sketchy-domain.com, don't click.
On mobile, long-press. Touch and hold the link to preview the URL without opening it. Mobile browsers make this harder than desktop browsers, which is exactly why attackers increasingly target mobile users.
Check the domain, not just the page. Attackers register domains that look almost right: amaz0n.com (zero instead of 'o'), microsoft-support.net (plausible but not real), or yourcompany-hr.com (close enough to pass a quick glance). Read the domain carefully, character by character, when something feels off.
Be skeptical of shortened URLs. Services like bit.ly and t.ly hide the actual destination. If you receive a shortened URL in a context where you weren't expecting one, don't click it. Ask the sender for the full link, or use a URL preview service to check the destination.
Watch for HTTPS, but don't rely on it. The padlock icon means the connection is encrypted, not that the site is legitimate. Attackers can and do obtain SSL certificates for phishing sites. HTTPS is necessary but not sufficient.
Module 2 introduced quishing as a phishing variant. This section goes deeper into the mechanics, because QR code attacks exploit a specific gap in how most people think about security: we've been trained to evaluate links, but QR codes bypass that habit entirely.
A QR code is just a link encoded as an image. When you scan it, your phone opens the encoded URL in your browser. The problem is that you can't read a QR code with your eyes. Unlike a URL you can hover over and inspect, a QR code is completely opaque until after you've scanned it. This makes it a near-perfect delivery mechanism for phishing sites.
Where malicious QR codes show up:
QR code phishing attacks jumped 25% year over year in 2025, and research found that 26% of all malicious links in phishing campaigns were delivered via QR code. The FBI issued a formal warning about quishing targeting both consumers and organizations.
How to protect yourself:
Working from coffee shops, airports, hotels, and co-working spaces is a normal part of modern work. But the networks in these locations come with risks that your office network doesn't.
Public Wi-Fi networks are, by definition, shared with strangers. On an unsecured network (one that doesn't require a password, or one where everyone uses the same password), an attacker on the same network can potentially intercept your traffic, see which sites you're visiting, and in some cases capture data you're transmitting. More sophisticated attacks involve setting up a fake Wi-Fi network with a plausible name ("Starbucks_Free_WiFi" or "Airport_Guest") that routes all your traffic through the attacker's device.
Use your company's VPN. A virtual private network encrypts all traffic between your device and your company's network, making it unreadable to anyone on the local Wi-Fi. If your company provides a VPN, use it whenever you're on a network you don't control. If your company doesn't provide one, ask IT whether they recommend one.
Verify the network name. Before connecting, confirm the exact network name with staff at the location. Attackers create networks with names that are close to but not identical to the legitimate one ("Hotel_Lobby" vs. "Hotel_Lobby_Free").
Avoid accessing sensitive systems without a VPN. If you can't connect to a VPN, avoid logging into financial accounts, customer data systems, or internal tools. Email and general browsing on HTTPS sites carry lower risk but are not risk-free.
Use your phone's hotspot as an alternative. Tethering to your phone's cellular connection is generally safer than using public Wi-Fi because the connection isn't shared with strangers. If you need to do sensitive work and don't have a VPN, a hotspot is a reasonable fallback.
Forget the network when you're done. Remove public networks from your saved connections so your device doesn't automatically reconnect the next time you're in range.
Your laptop, phone, and tablet are the physical entry points to every system and account you have access to. Losing a device or leaving it unsecured, even briefly, can be as damaging as having your password stolen.
Lock your screen. Every time. When you step away from your computer, even for 30 seconds, lock it. On Mac: Ctrl+Command+Q. On Windows: Windows+L. On your phone, set auto-lock to the shortest interval you can tolerate (one minute or less). An unlocked device in a coffee shop, a conference room, or even your own office is an open invitation.
Enable full-disk encryption. This ensures that if your device is lost or stolen, the data on it can't be read without your password. Most modern operating systems have this built in (FileVault on Mac, BitLocker on Windows). Your company likely requires it. If you're not sure whether it's enabled, ask IT.
Keep software updated. Operating system updates, browser updates, and app updates frequently include security patches for vulnerabilities that attackers are actively exploiting. Delaying updates doesn't just mean missing new features. It means running software with known holes. Enable automatic updates wherever possible.
Don't install unapproved software. Every application you install is an application that could contain malware, exfiltrate data, or create a vulnerability. Stick to software approved by your company. If you need something that isn't on the approved list, go through the request process rather than installing it on your own.
Be cautious with USB devices. USB drives are a known malware delivery vector. Don't plug in USB drives you find in parking lots, conference rooms, or anywhere else. If you receive a USB drive from a vendor or at an event, hand it to IT for scanning before plugging it into your work machine.
Shadow IT refers to any software, cloud service, or hardware that employees use for work without the knowledge or approval of the IT and security teams. It's not usually malicious. It's usually someone trying to get work done faster by signing up for a tool that seems helpful, without realizing the security implications.
The numbers are striking. Research consistently shows that roughly 65% of SaaS applications in use at a typical company are unsanctioned, meaning IT doesn't know they exist. The average enterprise has hundreds of cloud services in active use, and IT is aware of a fraction of them.
Each unapproved tool represents a potential gap in your company's security and compliance posture:
Data leaves the perimeter. When you paste customer data into an unapproved tool, that data is now stored on a server your security team can't monitor, audit, or protect. If that tool is breached, your company may not even know its data was involved.
Access control breaks down. Unapproved tools don't integrate with your company's SSO or identity management systems. That means no centralized access logging, no automatic deprovisioning when someone leaves, and no visibility into who has access to what.
Compliance evidence disappears. SOC 2 auditors expect to see that data is handled through approved, controlled channels. Shadow IT creates gaps in the evidence chain that are difficult to explain during an audit.
Ask before you adopt. If you find a tool that would help your work, bring it to IT or your manager before signing up. There may already be an approved alternative, or IT may be able to evaluate and approve the tool quickly.
Use approved tools for their intended purpose. Your company chose specific tools for communication, file sharing, project management, and other functions. Use them, even if they feel slightly less convenient than an alternative. The convenience gap is almost never worth the security gap.
Don't use personal accounts for work data. Your personal email, personal cloud storage, and personal messaging apps are not subject to your company's security controls. Work data should stay on work systems.
Security isn't a single decision. It's a set of habits you practice every day. The good news is that most of the habits that matter are simple and fast. Here's the shortlist:
None of these habits require technical expertise. All of them reduce the likelihood that your account, your device, or your data becomes the starting point for an incident.
Next up: Module 7, Vendor & Third-Party Risk, where we'll cover how the apps and services you connect to your work accounts create supply chain risk, and how to evaluate tools before adopting them.
Module Version: 1.0
Last Updated: March 2026
Framework References: NIST Cybersecurity Framework 2.0 (Protect, Identify), SOC 2 Trust Services Criteria (CC 6.1, CC 6.6, CC 6.8)
Data Sources: FBI Internet Crime Complaint Center (IC3) 2025, Hoxhunt 2025 Phishing Trends Report, Keepnet Labs 2025 QR Code Phishing Statistics, IBM/Ponemon Cost of a Data Breach Report 2025