Technically U

About Technically U

One podcast keeps IT pros ahead of career-ending surprises. You're in cybersecurity, networking, or IT leadership. You know the feeling—scrambling to explain a breach, outage, or AI disruption you should have seen coming. TechnicallyU give you a 20-minute or more weekly briefing that makes you the smartest person in every meeting. What we actually cover: Why your MFA isn't protecting you like you think AI tools that will replace jobs vs. ones that will save them Cloud architecture mistakes costing companies millions Your competitors are already listening. New episodes every Thursday

Publisher

Technically U

Category

technology

Language

en

Explicit

No

First episode

15 Mar 2025

Latest episode

12 Sept 2026

Latest episodes

269 episodes in the feed.

1. 

   12 Sept 2026

   Pass-ta-Key Attacks: Is Passwordless Security Still Safe?

   Apple, Google, Microsoft, and the security industry have spent years telling us that passkeys are the future of authentication. No passwords. Less phishing.No reusable credentials for attackers to steal. But researchers have now demonstrated something important :Attackers may not need to break the passkey itself. They can attack everything around it. Windows. Browsers. Extensions. Password managers. Cloud synchronization. Authentication workflows. Welcome to the world of Pass-ta-Key attacks. In this episode of the Technically U Podcast, we break down how researchers demonstrated more than 20 techniques targeting weaknesses in the passkey ecosystem—and what that means for consumers, enterprises, and the future of passwordless authentication. 🔍 THE BIG DISTINCTIONPass-ta-Key attacks do not necessarily break FIDO2 cryptography.Instead, they target implementation weaknesses surrounding authentication, including:• Windows event logging• Server-side WebAuthn validation• Malicious browser extensions• Synced passkey architectures• Endpoint memory• Recovery and registration workflowsThe cryptography can remain strong while the surrounding environment creates another path for attackers.🎯 ATTACK VECTOR 1: WINDOWS EVENT LOGGINGResearchers identified a Windows vulnerability, CVE-2026-34348, involving WebAuthn authentication information appearing in Windows Event Logs.In the demonstrated attack chain:An attacker first compromises the endpointMalware accesses Windows Event LogsWebAuthn authentication material is extractedThe attacker attempts to replay itWeak validation can allow unauthorized accessMicrosoft released a Windows update addressing the issue in July 2026.🌐 ATTACK VECTOR 2: MALICIOUS BROWSER EXTENSIONSResearchers also demonstrated how a malicious Chrome or Edge extension could interfere with passkey creation.Instead of stealing an existing private key, the extension attacks the registration process itself.If successful, an attacker-controlled credential may be registered while everything appears normal to the user.The lesson:If the browser is compromised, strong authentication alone may not save you.🔑 ATTACK VECTOR 3: SYNCED PASSKEYSSynced passkeys provide enormous convenience because credentials can follow users across devices.But synchronization also creates additional attack surface.Research involving Google Password Manager examined techniques targeting sensitive information available during the synchronization and decryption process.A sufficiently capable attacker with endpoint access may attempt to steal information protecting multiple synced passkeys rather than attacking accounts one at a time.⚠️ SO... ARE PASSKEYS BROKEN?No.Passkeys still provide major security improvements over traditional passwords, especially against:• Credential phishing• Password reuse• Weak passwords• Stolen password databasesBut “phishing-resistant” should not be interpreted as attack-proof.Passkeys still depend on secure operating systems, browsers, identity providers, endpoints, synchronization systems, and proper implementation.That means defense in depth still matters.🏢 WHAT ENTERPRISES SHOULD DOA passkey can be a strong authentication factor.It should not automatically become the entire security strategy.🎙️ Technically U PodcastMaking complex cybersecurity, networking, cloud, AI, and emerging technology easier to understand.Subscribe and join the conversation.#Passkeys #FIDO2 #Cybersecurity #WebAuthn #Passwordless #MFA #IdentitySecurity #ZeroTrust #BrowserSecurity #MicrosoftSecurity #CyberSecurity #TechnicallyU

2. 

   5 Sept 2026

   SaaS Bloodbath: Why Your Trusted Apps Are Now the Attack Surface

   Your company may not get hacked through the firewall. It may get breached through the SaaS app everyone trusts. In this episode of Technically U, we break down the growing SaaS security crisis and why trusted cloud applications like Salesforce, Slack, Workday, Google Workspace, Microsoft 365, and third-party integrations have become prime targets for attackers. Modern breaches are no longer just about breaking into networks. Attackers are stealing credentials, abusing OAuth permissions, compromising SaaS vendors, and using trusted integrations to move directly into business-critical systems. We discuss how SaaS breaches can happen in minutes, why stolen credentials are cheaper and easier to obtain than ever, and how third-party SaaS platforms can become the weak link in an organization’s security strategy. In this episode, we cover: ✅ Why SaaS breaches are increasing ✅ How stolen credentials and infostealer malware fuel attacks ✅ Why identity is now the new security perimeter ✅ How OAuth integrations can create hidden risk ✅ Why third-party SaaS vendors can expose customer data ✅ What recent SaaS-related incidents reveal about modern cyber threats ✅ Why traditional firewalls and endpoint tools are not enough ✅ How poor SaaS logging delays breach detection ✅ What organizations should do to improve SaaS security ✅ Why SaaS security is now a frontline cybersecurity issue If your organization uses SaaS applications, this episode is for you. Whether you work in cybersecurity, IT, networking, compliance, risk management, sales engineering, or business leadership, understanding SaaS risk is now essential. Tech made simple. One packet at a time. #SaaSSecurity #Cybersecurity #CloudSecurity #IdentitySecurity #OAuth #Infostealer #ThirdPartyRisk #VendorRiskManagement #TPRM #SalesforceSecurity #SlackSecurity #WorkdaySecurity #CyberRisk #ZeroTrust #TechnicallyU

3. 

   29 Aug 2026

   The AI Data Disaster: What ChatGPT, Claude, and Gemini Really Do With Your Secrets

   143,000 ChatGPT, Claude, and Copilot conversations are publicly accessible right now. Here's what was exposed—and why your AI isn't as private as you think. 🚨 THE HEADLINE: 143,000 user conversations with ChatGPT, Claude, Copilot, and other AI tools are publicly accessible on Archive.org. Anyone with internet access can read them. WHAT'S IN THEM: - Medical histories and diagnoses - Financial accounts and credit card numbers - Source code from major companies - Internal company documents - Social Security numbers - Passwords and API keys - Legal contracts and NDAs ---💀 REAL INCIDENTS (2024-2026): CASE 1: Samsung's Proprietary Chip Design Leaked- Samsung engineer pasted confidential code into ChatGPT- Wanted optimization help- Code was for a secret chip design project- Code ended up in OpenAI's training data- Samsung immediately banned ChatGPT company-wide CASE 2: 143,000 Conversations Made Public (2025-2026)- Security researcher found shareable conversation links- Many linked from forums, Reddit, social media- Archive.org captured 143,000+ conversations- Indexed and searchable- Included medical data, financial info, source code- Most users had no idea conversations were public CASE 3: Mexican Government Breach (Dec 2025 - Feb 2026)- Single attacker used Claude Code and ChatGPT- Breached 9 government agencies- Stole data on 195 MILLION Mexican citizens- Claude Code executed 75% of all attack commands- 1,088 prompts = 5,317 AI-executed commands- Built tools to forge tax certificates in real-time CASE 4: ChatGPT Data Leakage Vulnerability (Feb 2026)- Researchers discovered vulnerability in ChatGPT- Allowed silent data exfiltration via DNS queries- Data leaked without user knowledge or consent- Attackers could command model to extract specific data- Could enable remote command execution- Fixed by OpenAI, but proven the attack surface exists CASE 5: API Keys and Secrets Exposed- 23.8 million "secrets" (passwords, keys) leaked via AI tools in 2024- 25% increase year-over-year- A single screenshot with exposed API key → data in ChatGPT logs- If OpenAI logs are breached, attackers get production access--- 🔴 WHAT YOU SHOULD NEVER SHARE: CATEGORY 1: Passwords, API Keys, Credentials ❌ Pasting code with API keys visible ❌ Database connection strings ❌ SSH keys ❌ AWS access tokens ❌ Private encryption keys Why: 23.8M secrets leaked via AI in 2024. If logs are breached, attackers have direct infrastructure access. CATEGORY 2: Health Information (PHI) ❌ Medical diagnoses ❌ Medications and dosages ❌ Lab results ❌ Mental health concerns ❌ Sexual health questions Why: HIPAA doesn't protect consumer AI. Data in training datasets. Breaches expose health records. Insurance companies could deny coverage. CATEGORY 3: Financial Information ❌ Bank account numbers ❌ Credit card numbers ❌ Social Security numbers ❌ Tax returns ❌ Investment account details ❌ Mortgage documents Why: Complete identity theft package if exposed. Perfect for fraud. CATEGORY 4: Proprietary Source Code ❌ Company software ❌ Technical architecture ❌ Algorithms ❌ Frameworks specific to your business ❌ Configuration files with secrets Why: 11% of ChatGPT inputs from workers contained confidential code. May be in training data. Rivals could see it. CATEGORY 5: Personal Identifying Information (PII) ❌ Full names with context ❌ Addresses ❌ Phone numbers ❌ Email addresses (specific to you) ❌ Driver's license numbers Why: Combined with other data = phishing/identity theft profile. CATEGORY 6: Legal Documents & NDAs ❌ Contracts ❌ Non-Disclosure Agreements ❌ Partnership agreements ❌ Internal legal opinions ❌ Litigation records Why: Pasting an NDA-covered document into a third party may violate the NDA itself. Sensitive terms exposed to competitors. CATEGORY 7: Regulated Data (HIPAA, PCI, GDPR, FERPA, SOX) ❌ Healthcare records ❌ Credit card data ❌ EU resident personal data ❌ Student education records ❌ Financial reporting data

Reach and audience

Public platform figures. Ratings count people who left a rating, not total listeners.

YouTube views

224,637

Score snapshot 15 Sept 2025

Apple Podcasts (US)

3.0 / 5

2 ratings

Spotify

2.3 / 5

3 ratings

Podcast Authority Score: 73 / 100

A composite of feed quality, social presence, YouTube performance and engagement. Read the methodology.

Quality

96

Social presence

0

YouTube

93

Engagement

32

Contact Technically U

Guest appearances

Books guests

Based on episode analysis; this does not confirm that the show is currently accepting guests.

Questions about Technically U