SAM Pro SaaS Visibility Using Netskope Service Graph Connector

[meganfisher]

Hello everyone,

I'm looking to connect with anyone who has experience using the Service Graph Connector for Netskope in conjunction with ServiceNow SAM Pro, specifically for identifying and managing SaaS applications.

Our organization is currently evaluating options for improving SaaS visibility within SAM Pro. We have reviewed the standard "Integrate with SSO providers" capability, but unfortunately it is not a viable solution for us because we utilize PingFederate as our identity provider and the current SAM Pro integrations only support Azure AD and Okta. 

While researching alternatives, I reviewed the documentation for the Service Graph Connector for Netskope, which indicates that it can import hardware and software inventory data from Netskope into ServiceNow. The documentation references importing software inventory information into CMDB-related tables.

I'm hoping to hear from any SAM practitioners who have deployed this connector and can share:

• Are you using the Netskope connector as a source of SaaS application discovery for SAM Pro?
• What types of SaaS products or usage data are you able to identify through the integration?
• Are the imported software records successfully normalized through Content Service / Normalization processes?
• How effective has the solution been for identifying shadow IT or applications not captured through traditional endpoint discovery tools?
• Have you experienced any data quality, normalization, or maintenance challenges with the integration?
• If you evaluated it and decided not to use it for SaaS discovery, what limitations did you encounter?

I'm particularly interested in understanding whether others have used Netskope as a practical alternative for SaaS visibility when the native SAM Pro SSO integrations are not an option.

Any lessons learned, architecture diagrams, screenshots, or implementation recommendations would be greatly appreciated.

Thank you!