Notifications
Clear all
Topic starter
12/06/2026 10:15 pm
TL;DR: A new website, product packaging, Microsoft authentication support, analyst recognition, and customer feedback are tied into a momentum narrative that positions identity security around easier consumption and phishing-resistant access, according to Axiad. For practitioners, the signal is that authentication programmes are being judged on usability, partner fit, and outcome alignment, not just control strength.
NHIMG editorial — based on content published by Axiad: The Arrival of “Big Mo” at Axiad
Questions worth separating out
Q: How should IAM teams evaluate identity vendors that package controls around outcomes?
A: Treat packaging as a usability signal, not a control verdict.
Q: Why does phishing-resistant authentication still depend on ecosystem integration?
A: Because the control only holds if certificates, devices, applications, and partner systems can all support it consistently.
Q: What do analyst rankings tell security teams about identity controls?
A: They show where the market is converging, which can help with prioritisation and category selection.
Practitioner guidance
- Review how identity controls are packaged for procurement Map each purchased capability back to the underlying control objective, ownership model, and operational dependency so the buying structure does not obscure governance gaps.
- Validate phishing-resistant authentication across real user groups Test certificate-based authentication, device coverage, and application compatibility across employee, contractor, and admin populations before assuming rollout readiness.
- Check that partner integrations do not create control gaps Confirm that third-party identity and access dependencies still support policy enforcement, auditability, and lifecycle management after integration.
What's in the full article
Axiad's full blog post covers the operational detail this post intentionally leaves for the source:
- The specific product packaging and positioning changes behind the new website and brand refresh
- The Microsoft partnership details, including support for Azure Active Directory Certificate-Based Authentication
- The analyst and customer references used by Axiad to support its market positioning
- The supporting partner and alliance information that helps explain the vendor's go-to-market direction
👉 Read Axiad's blog post on momentum, partnerships, and identity packaging →
Identity security packaging and partnerships: what changes for teams?
Explore further
13/06/2026 12:53 am
Identity packaging is becoming part of the control surface. When a vendor repositions authentication and supporting services around outcomes, the buyer experience itself becomes part of governance. Clearer packaging can improve adoption, but it can also blur whether the organisation is truly simplifying access or just simplifying the sales motion. Practitioners should treat packaging changes as a signal to re-check entitlement design and control ownership.
A few things that frame the scale:
- 90% of IT leaders say properly managing NHIs is essential for a successful zero-trust implementation, according to Ultimate Guide to NHIs.
- Only 5.7% of organisations have full visibility into their service accounts, which leaves identity teams unable to validate how many non-human identities are actually in scope.
A question worth separating out:
Q: How can organisations avoid mistaking vendor momentum for security maturity?
A: By checking whether the control is actually operational across the estate. Look for consistent enforcement, clear ownership, measurable adoption, and lifecycle coverage from onboarding through offboarding. If those elements are missing, the momentum is commercial, not security-related, and the programme remains exposed despite a strong market narrative.
👉 Read our full editorial: Axiad's momentum signals tighter packaging in identity security
