Android's identifiers shift from stable to spoofable: IMEI to MediaDrm

2FA alone isn’t enough: A newly reported Android attack allows malicious apps to quietly capture 2FA codes. At Plum Identity, we help organizations move beyond single-channel MFA by combining device attestation and continuous behavioral trust signals. The goal isn’t more friction — it’s more confidence that the person on the other side is who they say they are. Identity is the new perimeter. Let’s secure it. #IdentitySecurity #MFA #MobileSecurity #PlumIdentity https://lnkd.in/gGpRPN9H

Firefox 145 boosts fingerprinting defenses by limiting hardware and system data collection, cutting unique user tracking nearly in half. Enhanced privacy without impacting browsing performance. #FirefoxUpdate #PrivacyTech #Mozilla link: https://ift.tt/egxuACD

𝐒𝐞𝐧𝐢𝐨𝐫 𝐃𝐞𝐯𝐬: 𝐘𝐨𝐮 𝐧𝐞𝐞𝐝 𝐭𝐨 𝐫𝐞𝐚𝐝 𝐭𝐡𝐢𝐬 𝐢𝐟 𝐲𝐨𝐮 𝐡𝐚𝐧𝐝𝐥𝐞 𝐦𝐨𝐛𝐢𝐥𝐞 𝐬𝐞𝐜𝐮𝐫𝐢𝐭𝐲 We all know the drill: Security team comes knocking, asking if our 𝐑𝐨𝐨𝐭 detection is robust. We confidently point to our checks, but here’s the reality check: they are useless against runtime tools like 𝐅𝐫𝐢𝐝𝐚. 𝐅𝐫𝐢𝐝𝐚. is designed to easily bypass those simple 𝐑𝐨𝐨𝐭 checks. 𝐃𝐨 𝐲𝐨𝐮 𝐤𝐧𝐨𝐰 𝐞𝐱𝐚𝐜𝐭𝐥𝐲 𝐰𝐡𝐲 𝐨𝐮𝐫 𝐜𝐡𝐞𝐜𝐤 𝐟𝐚𝐢𝐥𝐬 ?, and how to build a defense that even the most determined attacker can't hook? I’ve documented the full technical breakdown, demonstrating the failure and introducing a powerful Native (JNI/C++) Discrepancy Check that stops Frida's root bypass in its tracks. This is the defense you need when security truly matters. Read the deep dive: https://lnkd.in/gSMKR5jD #Android #Security #Mobile #AppSec #Frida #NDK #SecurityDevelopment #SoftwareSecurity #MobileDev #AndroidNDK #FridaDefense

🚀 New Video Alert! 🚀 Ever wondered what kind of data your Android phone quietly holds—and how to extract it? 📱 In my latest video, “Android Forensics: Using ADB to Dig into Your Phone's Secrets!”, I dive into how the Android Debug Bridge (ADB) can be leveraged to uncover valuable insights during digital investigations. 🔍 What you’ll learn: How ADB works and why it’s essential in mobile forensics Key commands for data extraction and analysis Tips for safely exploring device data (without breaking anything!) Whether you’re a cybersecurity professional, digital forensics student, or just a curious tech enthusiast, this walkthrough will help you better understand the powerful tools behind Android analysis. 🎥 Watch it here: https://lnkd.in/gZV-rPGz

I think I understand why. Any country or organisation can host its own Matrix. Matrix has been around for many years, it's mature stuff. There are complexities with the federated aspects, but these are choices for TCO vs ROI. If you actually want sovereignty, ROI is your focus. WhatsApp is Meta = US company. Same protocol as Signal but that's immaterial. See also the below. Signal is solid in terms of message encryption, but it is hosted on AWS which, regardless of the hosting location, is a US company and thus subject to the US CLOUD Act. There's enough visible metadata around Signal to make it awkward if someone snoops on it (traffic analysis).

Your IAM has a mind-body problem.  Philosophers have debated the disconnect for centuries, now it's causing your biggest breaches. We call it Identity Dark Matter: the ungoverned secrets, keys, and accounts your apps hold onto despite your IAM's policies. That gap between policy intent and app execution is your biggest risk. Learn why you're blind and how to fix it here ->> https://lnkd.in/e9jHv3Tr

Your IAM has a mind-body problem.  Philosophers have debated the disconnect for centuries, now it's causing your biggest breaches. We call it Identity Dark Matter: the ungoverned secrets, keys, and accounts your apps hold onto despite your IAM's policies. That gap between policy intent and app execution is your biggest risk. Learn why you're blind and how to fix it here ->> https://lnkd.in/e9jHv3Tr

Your IAM has a mind-body problem.  Philosophers have debated the disconnect for centuries, now it's causing your biggest breaches. We call it Identity Dark Matter: the ungoverned secrets, keys, and accounts your apps hold onto despite your IAM's policies. That gap between policy intent and app execution is your biggest risk. Learn why you're blind and how to fix it here ->> https://lnkd.in/e9jHv3Tr

Think beyond external attackers. Run scenario tests for identity provider compromise, especially the one nobody likes to think about, the phish from a colleague. If an internal user gets compromised and their SSO/IDP session is abused, what can that actor reach? Privileged inboxes. App consent flows. Service principals. Tenant settings. Billing. Key vaults. Lateral moves are easier when the attacker arrives on a trusted internal channel. Config reviews have their place but in this day and age you should be simulating an internal phish leading to an IDP takeover. Measure detection, containment, and how quickly you can remove privileges and rotate keys. If you can’t revoke everything rapidly, you’ve got work to do.

🚨Security alert… Online impersonation and identity fraud is getting easier. It’s a little bit scary to be honest. Two big shifts I see coming: 1️⃣ We’re going to need smarter tools to protect ourselves online. Real tools that help us verify who we’re talking to and keep our online identity safe/authentic. 2️⃣ In-person connection is about to go up in value, big time. When everything can be faked online… real eye contact, real energy, real people are going to matter more than ever. You can’t deepfake presence (yet 🙄) The internet keeps getting smarter, faster, and more complicated. Whilst human trust becomes even more valuable.