Rich Polanco

Student web-design projects are unknowingly fueling the phishing ecosystem. Here, we uncover how tutorial sites and free hosting can turn innocent “clone” pages into credential traps. Read more: https://lnkd.in/eEq4Hm7k #BrandProtection #Phishing #ThreatIntel

6

In this episode of The Hitchhiker's Guide to the GRC Technology Galaxy Podcast, guide researcher and intergalactic GRC hitchhiker Michael Rasmussen speaks with David Fisher, President of TDI Solutions, about something that often gets lost in the noise of modern GRC—Intelligence. They begin by exploring what makes TDI Solutions different in a crowded landscape. While many platforms lead with automation and AI, TDI starts with intelligence (human expertise, investigative depth, geopolitical awareness, and regulatory context) and then uses AI to enhance, scale, and accelerate that foundation. The conversation dives into TDI’s due diligence capabilities, what distinguishes their approach, and how intelligence-led analysis improves executive decision-making across jurisdictions and value chains. From there, they unpack how TDI’s technology platforms, including third-party monitoring and regulatory navigation, are built to support and operationalize that intelligence, not replace it. They also discuss why clients typically engage TDI, the caliber of analysts behind the work, and how the firm balances SaaS scalability with advisory depth. The episode closes with a look ahead at how TDI sees its intelligence-driven model evolving over the next several years. In a galaxy increasingly powered by algorithms, AI may be fast but intelligence still comes first.

1

👋 Issue 84 of The OSINT Newsletter is live, and it's another issue focused on helping beginner OSINT investigators improve their skills. This week, we're teaching you about Username OSINT that goes beyond tools. We'll be covering: - Username search tools - Username variations - Pivoting - Case study - Key takeaways Check it out here: https://lnkd.in/etdEK4tE

35

Credential stuffing isn't loud. Each request looks like a legitimate failed login. Correct content type, realistic user agent, proper headers. The credentials are real. They're just from a different breach. The tell is in the aggregate. Login failures across unrelated accounts, concentrated in a short window, from IPs with no prior session history, with no upstream page navigation before the POST. That cross-request pattern is where detection lives. And it's exactly what a WAF evaluates alone, per request, with no session context. What changes when they share the same path: you're evaluating cross-account velocity and session history while the request is still being processed. The evidence and the decision are in the same place. We broke it down in detail 👉 https://lnkd.in/g8YiFrvj

18