HashiCorp Vault now available as an external credential store in ServiceNow

[sremerson]

When it comes to agentless discovery and automating workflows to third-party systems from ServiceNow, having access to the right credentials is critical for success. Oftentimes, organizational security policies prevent the storage of credentials inside specific applications and require the use of a centralized credential management system. To solve this challenge, ServiceNow includes an out of the box framework to support external credential resolvers.

HashiCorp recently announced an integration for using HashiCorp Vault as an external credential resolver in ServiceNow. HashiCorp Vault is an identity-based security solution that leverages trusted sources of identity to keep credentials and application data secure. Joint customers are now able to use HashiCorp Vault to securely retrieve credentials necessary for agentless Discovery and Service Mapping to ensure complete visibility of their estate. Additionally, credentials from HashiCorp Vault can be utilized in automating workflows to third-party systems. Example workflows include:

• Automate-remediate service issues with AIOps (ex. service restart)
• Self Service Password Reset (ex. Active Directory)
• Automate Citrix session & virtual application resets

“HashiCorp has been a tremendous partner to ServiceNow by making it easy for our joint customers to connect the workflow automation power of the Now Platform with the infrastructure workflow capabilities of Terraform Enterprise,” said Brian Emerson, Vice President of Product Management, ITOM at ServiceNow. “Now, practitioners, teams, and global businesses can easily scale critical ServiceNow workflows in a way that strengthens their security posture.”

How do external credential resolvers work in ServiceNow?
The ServiceNow MID Server is directly integrated with an external credential store by installing JAR files and APIs on the MID Server. This allows the MID Server to retrieve credentials from the external store using a credential ID. A ServiceNow administrator enters credential IDs which are stored in the ServiceNow instance database. When the MID server needs a credential, it sends a request over the TLS connection to the ServiceNow instance, which
retrieves and returns the corresponding credential ID. The MID server then uses
this credential ID to retrieve the credential from the external credential store.

For a demonstration of how to setup HashiCorp Vault as a credential resolver in ServiceNow, watch this video.

Availability
Joint customers can install the HashiCorp Vault Credential Resolver application in their ServiceNow instance and begin resolving credentials with HashiCorp Vault today.

Learn More
To learn more about this new integration, please join our joint webinar on October 26th at 1 PM Eastern.

Read the HashiCorp Vault blog here.