Customer feedback

With Silk Central 20.0 or later, you can join the Silk Central Improvement Program and help us improve your test management experience. If you choose to participate, Silk Central will collect information on how users of an instance use our software and services to identify trends and usage patterns.

We will not:
  • Collect your name, address, or any other personally identifiable information.
  • Collect any content-related data.
  • Collect your scripts, passwords, or any other data files.
  • Prompt you with additional messages that might distract you from your work.

Security enhancements - Restriction to localhost

To prevent access from remote with Silk Central 20.0 or later, the JMX access for Front-end-, Application, and Chart-services is by default restricted to the loopback address of the machine

As the Application- and Chart-services are usually only used by the local Front-end-service, these are also restricted to the loopback address for new installations.

Security enhancements - Secure execution server communication

With Silk Central 20.0 or later, the Silk Central execution server setup enables you to specify a secure communication during installation. When checking Enable secure communication in the Silk Central execution server setup, you have to specify a keystore file that you can download from your Silk Central site. The keystore file is created with your Silk Central database and contains the certificate of the application service as well as a private key for the execution services. When the execution service starts up, it will only allow the corresponding application service, which is having a matching private key, to connect to the execution service.

An execution server setup with secure communication enabled will only open the Windows Firewall for the secure port 19125. The JMX service of the execution server on port 19144 is no longer available.