Notifications
Clear all
Topic starter
30/07/2026 10:48 pm
TL;DR: Microsoft’s Security Store is designed to simplify discovery, billing, deployment, and integration of security solutions and AI agents, while Linx says its participation helps shape that experience for identity and governance customers. The real story is that procurement is becoming part of the identity control plane, not just a buying motion.
NHIMG editorial — based on content published by Linx Security: Linx's participation in the Microsoft Security Store Partner Ecosystem
By the numbers:
- Lack of credential rotation is cited as the top cause of NHI-related attacks by 45% of organisations, followed by inadequate monitoring and logging and over-privileged accounts at 37% each.
Questions worth separating out
Q: How should security teams govern tools deployed through a security marketplace?
A: Security teams should treat marketplace deployment as part of identity governance, not just procurement.
Q: Why do curated security ecosystems still create identity risk?
A: Curated ecosystems reduce friction, but they can also accelerate adoption faster than governance can track.
Q: What breaks when marketplace tools are not added to recertification?
A: Unreviewed marketplace tools create entitlement drift.
Practitioner guidance
- Map marketplace intake to identity governance review Add security marketplace sourcing to third-party risk and access approval workflows.
- Inventory every marketplace-deployed integration Track each certified app, agent, and connector in the same register used for service accounts and privileged access.
- Tie recertification to operational use Recertify marketplace-delivered capabilities alongside other entitlements, with evidence of actual usage and business need.
What's in the full article
Linx Security's full company news post covers the operational detail this post intentionally leaves for the source:
- The stated scope of Linx's participation in the Microsoft Security Store Partner Ecosystem and how the collaboration is framed.
- The marketplace model for discovery, billing, and guided deployment of security solutions and AI agents.
- The vendor's positioning on certified integrations and the operational experience it expects security and IT teams to have.
- The surrounding company update and webinar promotion that provide context for the announcement.
👉 Read Linx Security's update on joining the Microsoft Security Store Partner Ecosystem →
Microsoft Security Store partner ecosystem: what changes for IAM teams?
Explore further
30/07/2026 10:55 pm
Security marketplaces are becoming an upstream identity governance control point. When organisations buy, deploy, and operationalise security tools through a curated store, the trust decision shifts earlier in the lifecycle. That does not remove governance burden, it relocates it to approval, verification, and integration review. Practitioners should treat the marketplace as a policy surface, not a convenience layer.
A few things that frame the scale:
- 85% of organisations lack full visibility into third-party vendors connected via OAuth apps, with 38% reporting no or low visibility and 47% only partial visibility, according to The State of Non-Human Identity Security.
- The same research found that 1 in 4 organisations are already investing in dedicated NHI security capabilities, with an additional 60% planning to do so within the next twelve months.
A question worth separating out:
Q: Who is accountable when a marketplace-delivered integration overreaches?
A: Accountability should sit with the system owner, the approving security team, and the identity governance function together. The marketplace is the distribution channel, not the control owner. Organisations should define who approves scope, who reviews ongoing use, and who must revoke access when the integration no longer fits the business need.
👉 Read our full editorial: Microsoft Security Store partner ecosystem shifts identity procurement
