Security | Threat Detection | Cyberattacks | DevSecOps | Compliance

Microsoft is making a major change to the authentication experience in Microsoft Entra. The company has announced the retirement of Microsoft-provided SMS and Voice MFA, with passkeys set to become the default sign-in method. This shift reflects Microsoft's broader push toward phishing-resistant authentication as organizations face increasingly sophisticated phishing, social engineering, and AI-driven attacks.

Building a DLP strategy has two failure modes. The first is skipping the planning and going straight to deploying a tool. The second is over-planning and never actually deploying anything. These 10 Data Loss Prevention Best Practices cover the full arc. From picking the right DLP tool, setting up your program properly, and keeping it from drifting once it's live. Teams that get DLP right tend to follow roughly the same best practices.

Your data leaks in ways you don't expect. A developer pastes source code into ChatGPT. A finance employee emails a payroll spreadsheet to a personal inbox. A salesperson uploads a client list to a personal Google Drive before their last day. All of these are breaches, rather, potential breaches. That's exactly why data loss prevention (DLP) tools exist. But picking the right one? That's where it gets complicated.

A Data Subject Access Request (DSAR) gives individuals the right to ask these questions and gain greater visibility into how their personal data is being used. Under privacy laws such as India's Digital Personal Data Protection (DPDP) Act, Data Principals can request access to their information and exercise other privacy rights. Every time you shop online, sign up for a service, or submit your details on a website, organizations collect and process personal data about you.

If your organization uses a Mac, you’ve probably heard of FileVault. But what is it, exactly? And more importantly, do you actually need it? A lost Mac can become much more than an expensive replacement if you have sensitive business data in it. FileVault is one of the simplest ways to protect it. Apple provides it by default with macOS. It encrypts your startup disk, so your files stay unreadable if someone gets access to your Mac without your login.

CISA calls phishing-resistant MFA the standard every organization should be working toward. For DoD components, federal agencies, defense contractors, and other organizations operating at NIST's highest authenticator assurance level (AAL3), that guidance narrows to two paths: FIDO2/WebAuthn, or PKI-based smart cards like CAC and PIV.

If you’ve managed Jira for a while, you've probably seen permissions grow more complex over time. You might have accounts that were granted temporary access during a migration but are still retaining it today. Or maybe contractors whose access was never revoked. You can clean that up. But with hundreds of users and projects, it’s going to take forever. Things become even more complicated when you're preparing for a SOC 2, ISO 27001, or SOX access review.

Teams are connecting Claude to Jira to summarize issues, draft tickets, and answer sprint questions in seconds. The productivity gains are real, but so is the security risk. The problem is simple: a direct connection gives Claude the same permissions as the person who set it up. If that user can view confidential projects or delete issues, so can Claude. There's no business logic in between deciding what AI should and shouldn't touch. Most organizations don't want to ban AI.