Technically U

Technically U
  • 3,0 (2)
  • Технологии
  • Еженедельно

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

  1. -6 ч

    The AI Criminal Playbook: How Cybercrime Changed Forever in 2026

    The next generation of cybercrime may not come from a hacker typing code in a dark room.It may come from someone using AI to generate phishing emails, clone voices, create fake identities, manipulate video calls, automate scams, and launch attacks at a scale human attackers could never match.In this episode of Technically U, we break down how AI is changing the economics of cybercrime — not just making elite attackers more dangerous, but making average attackers far more capable.We explore why AI-powered cybercrime is becoming a serious threat for businesses, consumers, IT teams, and security leaders.You’ll learn how AI is being used to create more convincing phishing campaigns, how deepfake voice and video fraud are changing identity verification, why AI agents are becoming a new enterprise attack surface, and why traditional trust-based security is no longer enough.We also discuss the growing shift toward AI-powered defense, Zero Trust, stronger identity verification, passkeys, conditional access, and security processes designed for a world where seeing and hearing are no longer proof of identity.Topics covered in this episode:• AI-generated phishing and social engineering• Deepfake fraud and voice cloning• Business email compromise in the AI era• Prompt injection and AI agent security• Why AI tools are lowering the barrier to cybercrime• The end of trust-based verification• Zero Trust and identity-first security• AI-powered defense and the future of cybersecurityThe key question is no longer whether AI can be used for cybercrime.It already is.The real question is whether businesses and consumers are prepared to defend against attacks that are faster, cheaper, more convincing, and easier to scale than ever before.Technically U — Tech made simple. One concept at a time.Subscribe for more deep dives into cybersecurity, emerging technology, AI risks, and the systems shaping how we work, connect, and defend.Question for viewers:How prepared do you think most businesses are for AI-powered cybercrime?

    The AI Criminal Playbook: How Cybercrime Changed Forever in 2026

  2. -4 дн.

    RiskRecon Explained: The Cybersecurity Credit Score Companies Use to Judge You

    What if a company you've never heard of is already influencing whether customers do business with you?In this episode of Technically U, we break down RiskRecon, the cybersecurity risk-rating platform owned by Mastercard that helps organizations evaluate the security posture of vendors, suppliers, partners, and even themselves.Often described as a "credit score for cybersecurity," RiskRecon continuously analyzes an organization's internet-facing assets, looking for vulnerabilities, misconfigurations, outdated software, weak encryption, email security issues, and other indicators of cyber risk.But how does it work? Who uses it? And why can a poor cybersecurity rating impact sales, vendor approvals, mergers and acquisitions, and third-party risk management programs?In this episode, you'll learn:✅ What RiskRecon is and how it works✅ How cybersecurity ratings are calculated✅ The role of third-party risk management (TPRM)✅ Why procurement and security teams use cyber ratings✅ How RiskRecon differs from BitSight and SecurityScorecard✅ What information RiskRecon can and cannot see✅ Why sales engineers and business leaders should care✅ The limitations of cybersecurity risk ratings✅ How external attack surface monitoring affects your organizationWhether you're an IT professional, cybersecurity analyst, network engineer, compliance specialist, business leader, or someone interested in how organizations measure cyber risk, this episode will help you understand one of the most important trends in modern cybersecurity.Tech made simple. One packet at a time.#RiskRecon #Cybersecurity #ThirdPartyRiskManagement #TPRM #VendorRiskManagement #CyberRisk #CyberSecurityRatings #SecurityScorecard #BitSight #AttackSurfaceManagement #InformationSecurity #RiskManagement #CyberAwareness #NetworkSecurity #TechnicallyU

    RiskRecon Explained: The Cybersecurity Credit Score Companies Use to Judge You

  3. 12 июл.

    Vulnerability Management Explained: Find, Prioritize & Patch Before Hackers Strike

    Right now, there may be vulnerabilities sitting inside your organization’s systems — and attackers may already be looking for them.In this episode of Technically U, we break down Vulnerability Management in a way that makes sense for security teams, IT leaders, business executives, and anyone responsible for reducing cyber risk.Most major cyberattacks do not come from brand-new, never-before-seen techniques. Many come from known vulnerabilities — weaknesses that already have patches available but were not fixed in time. That delay between discovery, patching, and exploitation is where breaches happen.In this episode, we explain what Vulnerability Management really is, why it matters, and why it should be treated as a continuous security program — not just a quarterly scan or compliance checkbox.You’ll learn how a strong Vulnerability Management program helps organizations gain visibility into their assets, prioritize the vulnerabilities that matter most, reduce their attack surface, improve compliance, and respond faster when new threats appear.We also cover what happens when organizations do not have a mature program in place: alert fatigue, reactive firefighting, regulatory exposure, increased breach risk, reputational damage, and major financial impact.Then we walk through how to choose the right Vulnerability Management platform, including what to look for in asset discovery, risk-based prioritization, remediation workflows, executive reporting, scalability, integrations, and threat intelligence quality.Finally, we explain how to build a mature program over time — starting with discovery and baseline scanning, then moving into prioritization, process, automation, measurement, and continuous improvement.Whether you are a CISO, CTO, security analyst, IT manager, business leader, or student learning cybersecurity, this episode will help you understand why vulnerability management is one of the most important foundations of modern cyber defense.In this episode:00:00 – Why vulnerabilities are being hunted right now01:02 – What Vulnerability Management is and why it matters01:59 – The business benefits of a mature program03:08 – Risk-based prioritization using CVSS, EPSS, and threat intelligence04:14 – Compliance, audit readiness, and attack surface reduction05:36 – The cost of not managing vulnerabilities08:50 – How to choose the right Vulnerability Management platform13:56 – Building a mature Vulnerability Management program16:54 – Key takeaways for security and business leadersVulnerability Management is not just about finding weaknesses. It is about finding the right weaknesses, fixing them fast, and proving your organization’s risk is going down over time.Tech made simple. One packet at a time.

    Vulnerability Management Explained: Find, Prioritize & Patch Before Hackers Strike

  4. 3 июл.

    HSTS: The Invisible Security Header Protecting Billions

    Every time you visit your bank, check your email, log into a shopping site, or open a secure web app, there’s an invisible browser protection working behind the scenes: HSTS — HTTP Strict Transport Security.In this episode of Technically U, we break down how HSTS protects billions of web sessions from one of the most elegant and dangerous network attacks ever demonstrated: SSL stripping.Back in 2009, security researcher Moxie Marlinspike showed how attackers could intercept users on public Wi-Fi, downgrade HTTPS connections to plain HTTP, and steal usernames, passwords, cookies, and sensitive data without triggering obvious browser warnings.HSTS was created to stop that.You’ll learn how a simple security header tells your browser to never connect to a website over insecure HTTP again, why this matters for banking sites, how the HSTS preload list protects users even on their first visit, and why misconfiguring HSTS can accidentally break websites or lock users out of legacy systems.We’ll also cover the risks of public Wi-Fi, protocol downgrade attacks, browser security, HTTPS enforcement, and why HSTS remains critical even as modern browsers move toward HTTPS by default.If you work in cybersecurity, web development, IT infrastructure, networking, or cloud security, this episode gives you a clear, practical understanding of one of the most important web security technologies most people never notice.In this episode:Why your first web request can be vulnerableWhat SSL stripping is and why it was so dangerousHow HSTS protects browsers from HTTP downgrade attacksWhy the HSTS preload list mattersReal-world HSTS adoption by banks, governments, and tech companiesCommon HSTS implementation mistakesWhy HSTS is still critical for modern web securityHSTS may be invisible, but without it, the modern web would be far less secure.Tech made simple. One packet at a time.

    HSTS: The Invisible Security Header Protecting Billions

  5. 20 июн.

    The DNS Encryption War: Why Privacy Tools and Security Teams Are Fighting Over DoH

    DNS over HTTPS (DoH) encrypts the internet's phonebook—and it's breaking traditional network security. Here's what IT professionals need to know about DoH in 2026, why enterprises are concerned, and how to adapt.🔐 WHAT IS DNS OVER HTTPS:THE PROBLEM DoH SOLVES:- Traditional DNS = plaintext on port 53 (unencrypted since 1983)- ISPs, network operators, anyone on WiFi can see every domain you visit- DNS queries reveal: Health research, job hunting, political views, all browsing activity- Government censorship via DNS blocking- DNS hijacking attacks on public WiFiHOW DoH WORKS:- Wraps DNS queries inside HTTPS connections (port 443)- Encrypted with TLS (same as secure websites)- Network observers see encrypted HTTPS traffic, can't tell it's DNS- RFC 8484 standard (2018)DoH vs DoT (DNS over TLS):- DoT: Dedicated port 853, easier for networks to identify/block- DoH: Port 443 (standard HTTPS), indistinguishable from web traffic- Both: Same encryption strength (TLS)- DoH: Better privacy, harder to block- DoT: Easier for enterprises to monitor/control⚠️ WHY ENTERPRISES ARE CONCERNED:BROWSER-LEVEL DoH BYPASSES CORPORATE DNS:- Firefox enables DoH by default (85%+ US users in 2026)- Chrome auto-upgrades when available- Bypasses network security tools completelyWHAT GETS BROKEN:1. Malware blocking (can't filter queries to C2 servers)2. Content filtering (parental controls, workplace policies)3. Threat detection (can't log DNS queries to identify infections)4. Data loss prevention (can't block file-sharing, personal email)5. Incident response (DNS logs don't exist for forensics)6. Compliance (regulatory requirements to monitor traffic)REAL ATTACKS USING DoH:- Godlua DDoS worm (2019): Used DoH to hide C2 communications- ShadowPad backdoor (2024): Encrypted DNS tunneling- 87% of organizations experienced DNS attacks in 2026- Malware increasingly adopting encrypted DNS to evade detectionNSA WARNING (January 2021, still relevant 2026):"Enterprises should avoid external DoH resolvers. Deploy internal DoH/DoT resolvers and block external endpoints."🛠️ HOW ENTERPRISES ARE ADAPTING:SOLUTION 1: Deploy Internal DoH/DoT Resolvers- Windows Server 2025: DoH support added February 2026- Run corporate DoH server with threat intelligence/filtering- Configure devices via MDM/group policy- Result: Encrypted DNS + enterprise security controlsSOLUTION 2: Block External DoH Providers- Block Cloudflare 1.1.1.1, Google 8.8.8.8, Quad9, etc.- Configure browser enterprise policies to disable DoH- Challenge: 931+ active DoH resolvers globally (can't block all)SOLUTION 3: Firefox Canary Domains- Firefox checks "use-application-dns.net" before enabling DoH- Corporate DNS returns specific response = Firefox disables DoH- Limitation: Only Firefox (Chrome doesn't use canary domains)SOLUTION 4: Roaming Client Agents- Deploy agents on devices (Cloudflare Gateway, Cisco Umbrella, DNSFilter)- Route DoH through corporate resolver- Works on BYOD and remote workers- Identity-aware policies even when encryptedSOLUTION 5: Shift to Endpoint Security- Network visibility lost → endpoint visibility gained- EDR (Endpoint Detection and Response) monitors device processes- TLS certificate monitoring, IP reputation, traffic patterns- Complement, don't replace, DNS security📊 CURRENT STATE (2026):ADOPTION RATES:- Firefox: 85%+ US users on DoH- Chrome: Auto-enabled since 2020- iOS/Android: "Private DNS" in system settings- Windows 11: DoH configuration built-in- Windows Server 2025: DoH server support (Feb 2026)JANUARY 2025 US EXECUTIVE ORDER:- Mandated DNS encryption for federal systems- Accelerated enterprise adoption- Government agencies deploying internal DoH/DoT resolvers

    The DNS Encryption War: Why Privacy Tools and Security Teams Are Fighting Over DoH

  6. 14 июн.

    Container Security Explained: Kubernetes, Docker & Cloud Native Threats

    🔐 Are your containers actually secure… or just assumed to be?In this episode of Technically U, we take a deep, structured dive into Container Security, breaking down how modern environments built on Docker and Kubernetes are secured—and more importantly, how they’re attacked.Containers have revolutionized application deployment, but they’ve also introduced an entirely new security model. Unlike traditional virtual machines, containers share a kernel, are highly dynamic, and require a completely different approach to security.🎯 In this episode, you’ll learn:Why containers are NOT virtual machines (and why that matters for security)How container isolation actually works:NamespacescgroupsCapabilitiesSeccompThe real risks of container escape attacks and shared kernel vulnerabilitiesWhy misconfiguration is the #1 cause of container breachesThe dangers of privileged containers and over-permissioningA full breakdown of the container security lifecycle:Build (image security, scanning, secrets management)Registry (supply chain risks, image signing)Orchestration (Kubernetes security, RBAC, etcd protection)Runtime (monitoring, anomaly detection, threat prevention)The most common Kubernetes attack vectors:Exposed dashboardsWeak RBAC policiesFlat networking (lack of segmentation)Secrets exposureResource exhaustion attacksHow to implement Network Policies and microsegmentationTools used in real-world environments: Falco, Trivy, Sysdig, OPA, VaultA practical container security checklist you can apply immediately🚨 Key Insight:Containers are not inherently insecure—but they require a completely different security mindset. Most breaches aren’t caused by sophisticated attacks… they’re caused by simple misconfigurations.💡 Who this episode is for:Network EngineersCybersecurity ProfessionalsDevOps EngineersCloud ArchitectsAnyone working with Kubernetes or containerized applications🎧 Technically U – Tech made simple. One concept at a time.👉 Whether you're running a single Docker container or managing a large Kubernetes cluster, understanding these security principles is critical to protecting modern cloud-native environments.

    Container Security Explained: Kubernetes, Docker & Cloud Native Threats

  7. 28 мая

    Your Device Has a Secret Fingerprint — And Websites Know It

    Have you ever logged into your bank account and seen the message: “We don’t recognize this device”?That message may be powered by one of the most important cybersecurity tools most people have never heard of: device fingerprinting. In this episode of Technically U, we break down how websites, banks, apps, payment platforms, and security systems can recognize your device based on clues like your browser, operating system, screen size, location, time zone, IP address, graphics behavior, and even how your device renders web content. Device fingerprinting can help protect you from fraud, account takeover, bots, credential stuffing, and suspicious logins — but it also raises serious privacy concerns because it can be used to track users even when cookies are deleted or blocked. We explain it in a way that everyday users can understand, while also covering technical details for cybersecurity professionals, including browser signals, WebGL fingerprinting, canvas fingerprinting, behavioral analytics, bot detection, session protection, and risk-based authentication. Device fingerprinting is one of the hidden cybersecurity functions working behind the scenes every day. It helps protect your accounts — but it also shows how much your device may reveal without you realizing it. 📢 Your support means the world to us! Every subscriber motivates our team to create even better educational and awareness videos. Hit that subscribe button and be part of our journey! Technically UTech made simple. One packet at a time.

    Your Device Has a Secret Fingerprint — And Websites Know It

  8. 28 мая

    DTLS: Why VoIP Calls and Video Conferences Need Different Encryption Than HTTPS

    Your Zoom call, WebEx meeting, VoIP phone conversation, and WebRTC video chat may all be encrypted — but they are not using HTTPS. Why? Because HTTPS relies on TLS over TCP, while real-time communications usually run on UDP. In this episode of Technically U, we break down DTLS — Datagram Transport Layer Security — the encryption protocol that makes secure real-time communication possible. DTLS gives voice, video, gaming, IoT, VPNs, and live streaming the security benefits of TLS while still supporting the speed and flexibility of UDP. You’ll learn why traditional TLS works well for websites, APIs, and file downloads, but creates problems for real-time traffic where delays, retransmissions, and packet ordering can ruin the user experience. We also explain how DTLS handles packet loss, out-of-order delivery, replay protection, handshake reliability, and secure key exchange. Topics covered include: What DTLS is Why TLS does not work well over UDP TCP vs UDP for real-time communications How DTLS secures VoIP and video conferencing DTLS-SRTP and WebRTC encryption How DTLS is used in IoT, VPNs, gaming, and live streaming DTLS 1.2 vs DTLS 1.3 Common DTLS security mistakes Why certificate validation still matters How DTLS protects real-time traffic without breaking performance DTLS is the unsung hero behind secure real-time communications. Every VoIP call, browser-based video meeting, WebRTC session, and many IoT communications rely on encryption that can survive packet loss, jitter, and unreliable networks. We are Technically U, and our motto is: Tech made simple. Subscribe for more clear breakdowns on networking, cybersecurity, encryption, protocols, enterprise technology, and the systems that power modern communication.

    DTLS: Why VoIP Calls and Video Conferences Need Different Encryption Than HTTPS
См. все (263)

Оценки и отзывы

3
из 5
Оценок: 2

Об этом подкасте

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

Информация

  • Автор
    Technically U
  • Годы выхода
    2025 - 2026
  • Выпуски
    263
  • Ограничения
    Без ненормативной лексики
  • Авторские права
    © Technically U
  • Сайт подкаста
    Technically U