Funding rounds, leadership changes, incidents, new capabilities and announcements across the vendors in this catalog — collected automatically from vendors' own public feeds. Product release versions are on their own page, so the landing feed here never reads as one vendor's changelog.Where this comes fromEvery item links to the vendor's own published source: a GitHub release feed, a changelog, a status page, an SEC filing or a company blog. Nothing here is written or editorially reviewed by 0-Doubt, and nothing is a recommendation — it is machine-collected public record, labelled the same way as all other baseline content on the platform. Coverage is uneven by design: a vendor that publishes no public feed will not appear, and that absence is not a judgement about the vendor.
83 matching stories — in Customer Identity and Access Management (CIAM) — showing up to 3 per vendorPer-vendor capWhile browsing, no single vendor may fill more than three slots on any one page, so a vendor with a chatty release cadence cannot buy the page you are looking at. That means a page can render fewer stories than the count above. Searching a headline or naming a vendor turns the cap off, because then you have asked to see everything that matches.
As major banks move to restrict AI assistants from accessing customer accounts, they face a difficult question: How do you protect customers from untrusted agents without preventing them from using the next generation of digital banking? For decades, banks have invested billions of dollars making it easier for customers to manage their money digitally. They […]
AI agents and machine identities now authenticate, hold access, and act on their own. Each one is an identity you own, and one most security tools weren’t built to watch. So they run with standing permissions to sensitive resources, and no one reviews what they do with them. Simeio runs the identity work ITDR depends […] The post ITDR in the Age of AI and Agentic AI appeared first on Simeio.
James Robinson never planned a cybersecurity career — seven companies and one deputy CISO role later, he leads security at Netskope. The post CISO Conversations: James Robinson – Many Jobs, One Journey to Netskope CISO appeared first on SecurityWeek.
A customer asks their AI assistant to pay a utility bill from their bank account. The assistant logs in, navigates to bill pay, fills in the form, and gets blocked. Ten minutes later, a credential-stuffing script tuned to look human walks straight through the same defenses. This is happening today, at banks and retailers that […]
Every identity vendor now has an agent story: register your AI agent, give it a client ID, issue it a short-lived, narrowly scoped token, and log what it does. The story comes with clean diagrams, sensible standards and good demos. There is just one problem: the whole model assumes the agent knocks on the front […]
In early June 2026, an AI-driven operator tracked as JadePuffer (Microsoft: Storm-3168) used two compromised Azure service principals to map a tenant, then made 100+ storage account deletion attempts in about seven minutes. Most succeeded. There was no malware and no exploit inside Azure. Every action was a normal Azure Resource Manager call, allowed by roles the identities already held. We walk the full chain — the 16-hour recon window, the inherited RBAC that gave it the blast radius, and the
AI agents are moving into production faster than security teams can govern them. They are connecting to apps, handling data, calling APIs, and acting across business systems—often without the same controls applied to human users. According to Okta’s Global CISO Insights 2026 report, only 47% of CISOs are confident they can identify every AI agent in their environment. Even among those who feel
Concerns over agentic risks are rising, and identity and access management (IAM) giant Okta believes it’s making the moves of a would-be leader in this emerging cyber market. “Identity is the primary control plane for securing AI,” said Okta CEO and co-founder Todd McKinnon in an earnings call in late August, telling investment analysts that the company’s customers see Okta as well-positioned to secure this agentic future. “And so we’re going after that on all fronts.” “We think that being the s
While zero trust is widely adopted in principle, it is unevenly implemented in practice, with most deployments stopping at the boundary. That gap is increasingly where risk concentrates.Identity, endpoint, network, and cloud controls have transformed how organizations secure access. They help answer essential questions like who is requesting access, what device or workload is acting, what application is mediating the request, and what policy applies within context.
A user access review is the process by which an organization periodically confirms that every user's access is still appropriate — and that access no longer needed has been removed. In manufacturing, these reviews cover SAP roles, directory groups, plant applications, contractor accounts, and privileged access across a complex multi-system estate.
Key Takeaways SAP Segregation of Duties is a critical control for manufacturing compliance, but it covers only part of what auditors test. A complete manufacturing compliance program requires identity governance across SAP and every connected system, not just within the SAP boundary. Finding an SoD conflict is only step one. Auditors require evidence of what happened after the conflict was found: who reviewed it, what was decided, and what was done about it. Manufacturing does not have an access
Okta used early access to GPT 5.5 Cyber Preview and Anthropic's Mythos Preview to hunt vulnerabilities in our own codebase. The big lesson: agents alone generate noisy leads, but pairing them with human experts who steer investigations produces real, high-confidence findings, plus a reusable pipeline architecture for future AI-driven security work.
The threat model for customer identity changed faster in the last eighteen months than in the decade before it. Two things moved... The post AI is reshaping identity threats: why home-grown SSO cannot keep up appeared first on Ubisecure Digital Identity Management.
Key Takeaways An SoD rule names a toxic access combination; a control is the operating process that prevents, detects, remediates, and evidences it. Auditors test operating effectiveness — proof the rules did something — not the existence of a list. Preventive enforcement at the request layer produces the strongest evidence: a conflict that never existed. Exceptions count as evidence only when documented with owner, rationale, compensating control, and review date. A well-built SoD rule set is t
Automated user onboarding and instant access revocation across IdPs protect against orphaned accounts and accelerate compliance delivery for high-growth B2B platforms.
New architecture integrates cutting-edge OAuth 2.1 protocols - including PAR and RAR - to eliminate transaction fraud while maintaining frictionless checkout conversion rates.