Topic starter
09/06/2026 11:40 pm
TL;DR: Stronger security, compliance, and efficiency are the focus of Netwrix’s customer webinar on Strongpoint for Salesforce 6.0, with user license analysis used to uncover cost-saving opportunities and automation used to free teams for more strategic work. The practical takeaway is that Salesforce governance now has to connect access oversight, compliance evidence, and spend control in one operating model.
Editorial analysis by NHI Mgmt Group, based on content published by Netwrix: “What's New in Netwrix Strongpoint for Salesforce 6.0”.
Key questions
Q: How should teams govern Salesforce licences and access together?
A: Treat licence assignment, access certification, and business ownership as one governance motion.
Q: Why do unused Salesforce licences matter beyond cost?
A: Unused licences often indicate more than overspend.
Practitioner guidance
- Map Salesforce entitlements to business owners Define who is accountable for each Salesforce profile, permission set, and licence class so recertification has a clear decision owner.
- Use license utilisation data in access reviews Combine licence usage evidence with entitlement reviews to identify stale users, over-assigned roles, and licences that no longer match current job needs.
- Automate routine governance evidence collection Shift repetitive checks, report assembly, and audit evidence gathering out of manual workflows so analysts can focus on exceptions and policy decisions.
Bottom line: Salesforce governance now spans security, compliance, and licence efficiency, so teams need one control model rather than disconnected reviews.
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
This topic was modified 3 days ago by NHI Mgmt Group
10/06/2026 2:05 am
Salesforce governance is now an identity problem, not just an application admin problem. When security, compliance, and licence optimisation are managed together, the organisation gets a clearer view of entitlement sprawl and stale access. That is the real governance boundary here, because the same workflow that trims cost can also reveal over-assignment and weak review discipline. Practitioners should treat application governance as part of the identity control plane.
A few things that frame the scale:
- The average organisation believes more than 1 in 5 of their non-human identities are insufficiently secured, according to The 2024 ESG Report: Managing Non-Human Identities.
- 72% of organisations have experienced or suspect they have experienced a breach of non-human identities, with 46% confirmed and 26% suspected.
A question worth separating out:
Q: How can IAM and compliance teams work together on Salesforce governance?
A: They should use one governance view for licences, access reviews, configuration drift, and evidence collection. That allows cost, security, and compliance teams to work from the same entitlement reality rather than separate reports. The result is faster remediation and fewer blind spots in audit preparation.
👉 Read our full editorial: Netwrix Strongpoint 6.0 shifts Salesforce governance and cost control
11/06/2026 1:10 am
Salesforce governance is now an identity problem, not just an application admin problem. When security, compliance, and licence optimisation are managed together, the organisation gets a clearer view of entitlement sprawl and stale access. That is the real governance boundary here, because the same workflow that trims cost can also reveal over-assignment and weak review discipline. Practitioners should treat application governance as part of the identity control plane.
A few things that frame the scale:
- The average organisation believes more than 1 in 5 of their non-human identities are insufficiently secured, according to The 2024 ESG Report: Managing Non-Human Identities.
- 72% of organisations have experienced or suspect they have experienced a breach of non-human identities, with 46% confirmed and 26% suspected.
A question worth separating out:
Q: How can IAM and compliance teams work together on Salesforce governance?
A: They should use one governance view for licences, access reviews, configuration drift, and evidence collection. That allows cost, security, and compliance teams to work from the same entitlement reality rather than separate reports. The result is faster remediation and fewer blind spots in audit preparation.
👉 Read our full editorial: Netwrix Strongpoint 6.0 shifts Salesforce governance and cost control
12/06/2026 2:44 am
Salesforce governance is becoming a convergence point for access control and cost discipline. The most useful takeaway from this webinar is not the feature set itself, but the governance model it implies. In SaaS platforms, access sprawl and licence waste often surface together because both are symptoms of weak entitlement hygiene. That makes Salesforce one of the clearest examples of why identity governance has to track both security posture and spend efficiency.
A question worth separating out:
Q: Should Salesforce governance be owned by security, IAM, or application teams?
A: It needs shared ownership. Security teams define the control intent, IAM or IGA teams operationalise access oversight, and application owners validate business need and role context. If one team owns it alone, licence optimisation, access hygiene, and audit evidence tend to fragment.
👉 Read our full editorial: Netwrix Strongpoint 6.0 shifts Salesforce governance and cost control
This post was modified 3 days ago by NHI Mgmt Group