Security | Threat Detection | Cyberattacks | DevSecOps | Compliance

Automated sign-ins used the vendor's Entra application identity to request Microsoft Graph tokens across consenting tenants On October 15, 2026, Sophos X-Ops researchers identified a series of service principal sign-ins in which a threat actor authenticated as the ConnectWise Cloud Backup application (formerly SkyKick) and requested app-only Microsoft Graph tokens from customer Microsoft 365 tenants.

Risk in the agentic enterprise spans people, service accounts, and AI agents. All three act with legitimate credentials, so access controls alone can’t show whether their activity is safe. A behavioral risk framework applies one model to every actor: Verify expected behavior before access goes live, observe activity once it does, analyze behavior for risk and drift, and improve detection coverage over time.

The recent disclosure of a major vulnerability in Citrix NetScaler pointed to a widespread weak point: a login page is an attack surface that can be used to compromise and access an application server. Indeed, the disclosures included an actively exploited flaw that allowed attackers to execute commands on affected gateways without signing in. As with any emergency patch, admins had to weigh cutting off or disrupting their users’ access with the risk of delaying a critical security update.

Your site loads in Chrome fine. Then a deploy script, a webhook, or integration calls the same URL and gets this: Python says certificate verify failed: unable to get local issuer certificate. Node says unable to get local issuer certificate, or unable to verify the first certificate. It’s all the same problem. It’s a misconfiguration between your certificate and a trusted root. Either the server isn’t sending it, or the client doesn’t have it.

Researchers pulled real, leaked API keys out of three LLMs using only API output. Here is how AI agents carry secrets from developer laptops into model context, and how to stop them before the model sees them.

When MSPs evaluate MDR services, the conversation usually starts in the same place: Tell me about your SOC and how quickly you respond. Those are good to know, but they don't tell you one thing that determines whether the service works: how much of your clients' environments the provider can see and act on. A SOC that's available 24/7 but only watching half the environment isn't protecting your clients. It's giving your clients a false sense of security.

A local password manager stores your credentials in an encrypted vault on your own device or server. You control your data and backups, but you also manage keys and updates yourself. That works for one person. Teams need role-based access, approvals for sensitive accounts, and logs that show who accessed what.

As AI agents spread across IT environments, organizations struggle to see what agents they have and what data those agents can access. For Cybersecurity Awareness Month, we wanted to share what Netwrix is doing to help IT and security teams improve agentic AI visibility and governance to keep their sensitive data secure. I recently sat down with Jeff Warren, our chief product officer, who has been working through this problem with customers for a while.

For years, identity governance has had a useful shorthand: Every identity needs an owner. This works reasonably well when the identity represents a person. There may be managers, application owners, entitlement owners, data owners and security teams surrounding the identity, but there is still a human being at the center. For example, Sarah in Finance has an identity. The organization determines what Sarah is permitted to access and execute, but Sarah will also be held accountable for her actions.