Servicenow Key management framework, high security settings, kafaka integration

 encryption key management:

additional encryption with database 

https://docs.servicenow.com/bundle/vancouver-platform-security/page/administer/key-management-framework/task/create-cryptographic-module.html

o In a short summary, ServiceNow comes with additional data encryption with its key management framework (https://docs.servicenow.com/bundle/vancouver-platform-security/page/administer/key-management-framework/concept/understanding-kmf.html). Users are allowed to create their own key cryptographic module (KCM) to encrypt scripts or tables they desire.  (https://docs.servicenow.com/bundle/vancouver-platform-security/page/administer/key-management-framework/concept/understanding-kmf.html)

o The default(free) key management only allows access to KCM with role based and create maximum of 5 KCM, and supports manual key rotations only. Customer keys are not supported (https://docs.servicenow.com/bundle/sandiego-platform-security/page/administer/encryption/reference/encryption-sku.html)

To utilize a KCM, it needs to be applied to a access policy(when to apply encryption), roles, scripts(password reset)

then you can rotate your key based on key management with default servicenow keys or customer supplied keys(audit)

High secuirty settings:

Based on https://support.servicenow.com/nav_to.do?uri=%2Fkb%3Fid%3Dkb_article_view%26sysparm_article%3DKB0745425

the required plugins are all installed on servicenow production instance by default,

High Security Settings

Kafka integration:

basic auth or Kafka SSL credentials for kafaka connectors:

https://docs.servicenow.com/bundle/vancouver-it-operations-management/page/product/event-management/task/configure-kafka-consumer-connector.html

we dont ever need to store private key there.