Security | Threat Detection | Cyberattacks | DevSecOps | Compliance

Safeguard 9.0 by One Identity is now available, built around three things privileged access teams care about most: less infrastructure to manage, a stronger case to bring to auditors, and coverage that reaches further into the systems your teams already rely on. Here's what's new.

Non-human identities (NHIs) are not new. We have run service accounts, scripts and machine credentials for years. What changed is the population. Every automation project and every AI investment adds more of them, and they now sit in the foreground of the security conversation, versus the background. You have probably seen the ratios in every deck on the topic. One hundred NHIs per human. Two hundred to one. Pick a number. The point in this session was that the exact ratio does not matter much anymore.

Every year, higher education hits the same beats. New students show up in the fall, ready to begin their undergraduate career. Staff and faculty come and go on their own timelines, some tenured for decades and others moving on after a single semester. Every spring, graduates ring in a new chapter, crossing the stage after years of hard-won achievements. Then there’s visiting researchers and affiliated partners, collaborating all throughout the academic year.

Identities in the modern enterprise are increasingly less human and more autonomous, powered by the rise in AI agents, APIs and other non-human identities (NHIs). The result is often an entitlement sprawl, where operations take place without human oversight and with privileged access. This non-linear evolution has meant many businesses have had to respond using bolted-on tools, rather than one unified, enterprise-grade platform.

Over 300 million people rely on Microsoft Teams to get their work done every day. That’s a lot of messages, meetings and “you’re on mute” moments happening every day. Teams makes it easy to collaborate. Too easy, sometimes. Anyone can create a new channel, add users and start sharing files in minutes. That’s great for getting work done, but it’s also how things get out of control. If you manage Teams, you’ve probably seen this happen.

ServiceNow is core to many modern businesses. The platform is cloud-based, AI-first and centralized. As the operational center of the enterprise, ServiceNow offers IT leaders automation opportunities that help optimize workflows, track requests and enforce processes. Naturally, managing so many actions within one ecosystem calls for advanced identity governance and administration (IGA).

Modernize and protect your Active Directory (AD) using Active Roles by One Identity Active Roles version 8.5 provides several highly requested features to fortify and enrich the integration capabilities of Active Roles. These new features bring unmatched flexibility and security to Active Directory environments, supporting customers where they are today and where they want to go in the future.

The end of an era is upon us, as SAP has announced the end of life for their identity governance and administration (IGA) platform — a platform that supported several SAP products. Without this pivotal identity management tool, where are customers to go to protect the digital identities of their organization? And how can they know that any new platform will be trustworthy? SAP hasn’t left their customers in a lurch.

Most identity governance and administration (IGA) programs do a good job answering one question: who should have access to what. The platform provisions accounts, runs certifications, enforces segregation of duties and feeds compliance reporting. After the request has been approved and the account exists in Active Directory, the IGA tool typically stops looking. What happens inside the directory after that is somebody else’s problem.

You can stand up a vault in two weeks. The team at One Identity says that’s about how long it takes to get the basics running, from discovery scans to approval workflows. Two to four weeks of work, and a respectable PAM foundation is in place. That’s not the hard part. The hard part starts the next morning, when actual users start working around the system.