Stronger Security in vScope: Support for SAML SSO and Kerberos

Single Sign-On (SSO) with SAML 2.0 – Centralized and Secure Access

In the latest update of vScope, we’ve expanded vScope’s existing SSO support by adding the option to connect identity management through SAML 2.0. As before, you can use Microsoft Entra ID as an identity provider (IdP). That integration is based on OpenID Connect, however, and does not allow for a generic IdP setup.

With the latest update, vScope integrates even better into your Single Sign-On strategy. vScope now supports SSO with any IdP that complies with SAML 2.0 – including Microsoft Entra ID (Azure AD), ADFS, Okta, OneLogin, Mobile Connect, and more. You’ll find the setting under Settings > Single Sign-On.

Benefits of SSO in vScope

• Simplified login and fewer passwords: Users log in to vScope with their regular company accounts – no extra password required.
• Stronger security: Take advantage of your IdP’s features such as MFA, conditional access, and security policies for vScope as well.
• Centralized access control: Add or remove a user in the IdP, and vScope follows automatically.
• Compatibility: SAML 2.0 is an industry standard with broad support – you’re not locked to a single vendor.

Want to learn more about SSO in vScope? Check out our support article on Single Sign-On.

Kerberos Authentication – Stronger Protection in Windows Environments

Alongside SAML, we’re also introducing support for Kerberos, a robust authentication protocol standard in many Windows-based networks. Kerberos ensures that users and services verify each other using tickets instead of passwords, making communication significantly more secure.

In vScope, Kerberos is primarily used when scanning systems and integrating with Active Directory (AD) or other Windows-based data sources. You decide whether to use Kerberos or the traditional username and password. By default, Kerberos is not configured. If Kerberos is not required in your environment, vScope will continue to use username + password authentication. However, if your environment requires Kerberos, you’ll need to configure it. Admins can find these settings under Settings > Kerberos.

Read more about how to set up Kerberos in our support article.

Benefits of Kerberos in vScope

• Stronger security: vScope no longer needs to store or send passwords when communicating with other systems and data sources.
• Policy compliance: Many organizations require Kerberos instead of simpler methods like NTLM.
• Access to more data sources: Some systems and databases require Kerberos – now vScope can scan these as well.

Why This Matters

SAML and Kerberos are the latest additions to the growing set of security features in vScope – designed to give you the flexibility to choose the settings that best match your environment and security policies. You can rest assured that vScope helps you meet the security requirements your organization sets for IT inventory and asset registers.

Together with Just Enough Administration, GMSA, Local Administrator, On-Prem Discovery, proxies, and more, you have a wide range of technologies and protocols to choose from – so you can find what best fits your needs.

With support for both SAML and Kerberos, you get:

• Increased security – access to vScope is protected by established authentication methods.
• Simplified administration – accounts and permissions are managed centrally.
• Better compliance – vScope works in environments with strict security requirements.

Update to the latest version to take advantage of these new features – and feel free to reach out to us if you’d like to discuss how vScope can help strengthen the security of your IT environment.