How do I customize the bundled PostgreSQL server configuration in MetaDefender Core?
This article applies to all MetaDefender Core releases deployed on Windows and Linux systems.
Overview
This article describes how to customize the PostgreSQL configuration for the bundled PostgreSQL server that comes with MetaDefender Core.
For example, one goal of making such configurations is to meet requirements in the CIS benchmark for PostgreSQL server.
Steps to Configure
To resolve the issues and achieve CIS benchmark compliance without affecting MetaDefender Core operations, follow these steps:
Do not modify the bundled postgresql.conf
located at OPSWAT\MetaDefender Core\data\pg_data\postgresql.conf
because it is controlled by MetaDefender Core and resets on service restart.
Instead, create and edit a new configuration file, which overrides the default configuration, and changes made here will persist after restarts:
- Windows:
<installation directory>\OPSWAT\MetaDefender Core\postgres\postgresql.conf
- Linux:
/usr/lib/ometascan/postgres/postgresql.conf
- Windows:
Add any configuration parameters needed, such as
ssl_ciphers
, and save the file.Restart the MetaDefender Core service (which also restarts the bundled PostgreSQL server).
Note: if SSL configuration for PostgreSQL server needs to be made, such as enabling SSL connection, please refer to SSL connection for PostgreSQL communication.
Verify the Change
After the service restarts, check and verify that the custom parameters have overridden the default ones.
If you’re making these configurations according to CIS benchmarks, refer to the relevant CIS documentation for the audit steps to verify that PostgreSQL is using the recommended settings.

If Further Assistance is required, please proceed to log a support case or chat with our support engineer.