---
sourceDocument: Australia Platform security
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/de-DE/platform-security

 Release :

    - australia

ft:locale :

    - de-DE

ft:publication_title :

    - Australia Platform security

ft:clusterId :

    - psec

bundleId :

    - psec

workflow :

    - Platform


---

# JDBC Signing

# Sign the JDBC data source records in the protected instance {#ariaid-title1}

* Freigeben Version: Australia
* 
* Aktualisiert 12. März 2026
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 2 Minuten Lesedauer

Use update sets to sign and validate the JDBC data sources by enabling the code
signing in protected and trusted instances.
* Establish Circle of Trust between the protected and trusted instances.
* Role required: security_admin

{#cs-jdbc__ul_twx_t3f4_spb}  
Hinweis:  
* MID Server doesn't handle the file data sources and hence, these data sources are not code signed.
* LDAP data sources can't be code signed.
{#cs-jdbc__ul_bg4_g1v_5pb}

## Sign existing data sources of the JDBC type {#ariaid-title2}

Use update sets to bring mass signing jobs to the protected instance.

### Vorbereitungen

Role required: security_admin

### Prozedur

1. In the trusted instance, configure the KMF signing job to sign the data sources.
   1. Navigate to System SecuritySecurity JobsAll.
   2. Click New.
   3. On the form, fill these values.  
      {#jdbc-datasource__table_jpp_cwp_spb__entry__2}

      | Field | Description |
      |-|-|
      | Name | Name to identify the record. |
      | Type | Type of the encryption job. Select Mass Sign Records. |
      | Table | Table from which the records should be signed. Select Data Source. |
      [ ]

      {#jdbc-datasource__table_jpp_cwp_spb}
   4. Click Export Code Signing job to production.  
      A confirmation message is displayed that the update set is signed.
   5. Export the generated update set to an XML file.
2. In the protected instance, import and commit the update set to retrieve the mass signed jobs from trusted instance.
   1. Navigate to System SecuritySecurity JobsAll.
   2. Open the update set exported from the trusted instance.
   3. Click Start.  
      A confirmation message is displayed that the records are signed.
   {#jdbc-datasource__substeps_x5w_mlp_5pb}

## Sign new data sources of the JDBC type {#ariaid-title3}

Use update sets to bring the signed update set to the protected instance.

### Vorbereitungen

Role required: sn_kmf.cryptographic_manager

### Prozedur

1. In the trusted instance, start an update set.  
2. In the trusted instance, create the required data sources.  
   The data sources are added to the update set.
3. In the trusted instance, change the state of the update set to Complete and click Update.  
4. In the trusted instance, sign the update set by creating an encryption job.
   1. Navigate to System SecuritySecurity JobsAll.
   2. Click New.
   3. On the form, fill these values.  
      {#cs-jdbc-new__table_jpp_cwp_spb__entry__2}

      | Field | Description |
      |-|-|
      | Name | Name to identify the record. |
      | Type | Type of the encryption job. Select Sign Update Set. |
      | Table | Update set from which the records should be signed. |
      [ ]

      {#cs-jdbc-new__table_jpp_cwp_spb}
   4. Click Submit.
   5. Click Start to sign the update set.  
      * Summary is updated that the records are signed.
      * The update set is updated and includes the signature.
      {#cs-jdbc-new__ul_vpg_x4p_5pb}
   {#cs-jdbc-new__substeps_lnr_knp_5pb}
5. In the trusted instance, open the signed update set record and export it to an XML.
6. In the protected instance, import the signed update set.
   1. Navigate to System Update SetsRetrieved Update Sets.
   2. Click the Import Update Set from XML related link to import the update set that is exported from the trusted instance.  
      For more information, see Import and commit the quick-start update set.  
      The update set is committed successfully.
   {#cs-jdbc-new__substeps_wln_npp_5pb}