Guide to Creating a DigiCert Certificate Inventory in ServiceNow

[Selva Arun]

Guide to Creating a DigiCert Certificate Inventory in ServiceNow

Introduction

In this article, I will outline the steps to create a DigiCert Certificate Inventory in ServiceNow. This inventory will help organizations manage their digital certificates effectively, ensuring security and compliance.

Prerequisites

• Access to ServiceNow with appropriate permissions
• DigiCert account credentials
• Basic knowledge of ServiceNow and certificate management

Step 1: Create a Credential Alias for Digicert

1. Navigate to Credentials Alias from the Application Navigator:

2. Search for Digicert and open the record:

3. Click on New under the related items of credentials tab and create an entry by providing the CA Type as Digicert and API key.

Step 2: Create a Discovery Schedule

1. Navigate to Discovery Schedules:
   • Click on new, Discover: Certificates.
2. Select Certificate Discovery Type:
   • Choose CA Trust Discovery and link the newly created Credential alias.
3. MID Server Selection:
   • Select the MID Server selection method: Auto Select or Specific MID Server.
4. Fill Out Necessary Fields:
   • Complete any additional required fields.
5. Save the Schedule:
   • Click Save.

Step 4: Add CA Patterns

6. Select the Serverless Execution Pattern Tab:
   • Click on the Serverless Execution Pattern tab.
7. Create a New Pattern:
   • Select New to add a DigiCert- Certificate Management as needed.
8. Enable Certificate Status Option:
   • If you enable the Include cert status option, specify multiple certificate statuses by separating them with commas.
9. Submit the Pattern:
   • Click Submit to finalize the process.

• Add the newly created credential alias name in the credential Alias parameter to avoid the error below and save the record.

Step 5: Run the Discovery Schedule by clicking on Discover now.

Conclusion

Following these steps will help you set up a DigiCert Certificate Inventory in ServiceNow efficiently. Ensure that all entries are accurate to maintain effective certificate management.

For more info, please check: Run Certificate Discovery via Certificate Authority query (servicenow.com)

[David_Casper]

Thanks for this post!!! The SNOW documentation left out the part of adding the credential alias value under the Discovery Pattern Launcher Parameters. 

[Selva Arun]

Thank you for your feedback, please mark this article as helpful if it has helped you in any ways.

Selva

[SK Chand Basha]

Very Helpful!!

[Selva Arun]

Thank you so much for your feedback.

If you believe the solution provided has adequately addressed your query, could you please **mark it as 'Helpful'**. This will help other community members who might have the same question find the answer more easily.

Thank you for your consideration.

Selva

[Thomas Buecker]

Hi,
is there a way to achieve it with ACC-V?
I can't find any documentation and the community post: https://www.servicenow.com/community/itom-forum/certificate-discovery-with-acc-v-agents/m-p/2895329 has also no answer

Kind Regards
Thomas

[Christopher Hub]

With ACC-V you could create a custom check that functions like the TLS port probe used in Discovery, but it feels like just using the TLS port probe itself might be a better approach.  You wouldn't usually care about this for end user devices, which are a common use-case for ACC-V agents.  If you are scanning on non-EUC devices, which use TLS certificates, then they need to be IP accessible to function.  TLS certificate discovery doesn't actually require a credential since it's accessing an open port, so the benefit of using an agent to discover it is small comapred to the additional complexity.  Do you have a specific reason for wanting to do this with ACC-V rather than Certificate Discovery?

[SK Chand Basha]

Hi @Thomas Buecker 

In zurich release you will get TLS certificates from ACC. 

Please find link below

https://www.servicenow.com/docs/bundle/zurich-release-notes/page/release-notes/it-operations-managem...