Chat now with support
Chat with Support

syslog-ng Store Box 5.0.3 - Administration Guide

Preface Introduction The concepts of SSB The Welcome Wizard and the first login Basic settings User management and access control Managing SSB Configuring message sources Storing messages on SSB Forwarding messages from SSB Log paths: routing and processing messages Configuring syslog-ng options Searching log messages Searching the internal messages of SSB Classifying messages with pattern databases The SSB RPC API Troubleshooting SSB Security checklist for configuring SSB About us Third-party contributions

Generating TSA certificate with Windows Certificate Authority on Windows Server 2012

To generate a TSA certificate with Windows Certificate Authority (CA) that works with SSB, generate a CSR (certificate signing request) on a computer running OpenSSL and sign it with Windows CA, then import this certificate into SSB for timestamping.


A valid configuration file for OpenSSL with the following extensions:

[ tsa_cert ]
extendedKeyUsage = critical,timeStamping


You can copy /etc/xcb/openssl-ca.cnf from SSB to the computer that will be used for signing. Rename the file to openssl-temp.cnf.

The TSA certificate is considered valid, in terms of compatibility with SSB, if the following conditions are met:

  • Must be a valid CA certificate (CA is true).

  • Key Usage: Time Stamping is required. No other key usage is permitted.

  • Extended Key Usage: Must be set to critical.

  • Optional Key Usage: If Key Usage is present, it must be digitalSignature and/or nonRepudiation. Other values are not permitted. Make sure that in Encryption, Allow key exchange without key encryption (key agreement) is selected.


    In Encryption, do NOT select Allow key exchange only with key encryption (key encipherment), because it will result in errors.

The following X509v3 extensions are supported:

  • Hard requirement:

    X509v3 Extended Key Usage must be critical, and must only contain Time Stamping.

  • Optional:

    X509v3 Key Usage, if present, must be digitalSignature and/or nonRepudiation.

  1. Create CSR using the new configuration file: openssl req -set_serial 0 -config openssl-temp.cnf -reqexts tsa_cert -new -newkey rsa:2048 -keyout timestamp.key -out timestamp.csr -nodes

  2. Complete the required fields according to your environment:

    Generating a 2048 bit RSA private key
    writing new private key to 'timestamp.key'
    You are about to be asked to enter information that will be incorporated
    into your certificate request.
    What you are about to enter is what is called a Distinguished Name or a DN.
    There are quite a few fields but you can leave some blank
    For some fields there will be a default value,
    If you enter '.', the field will be left blank.
    Country Name (2 letter code) [AU]:HU
    State or Province Name (full name) []:Budapest
    Locality Name (eg, city) []:Budapest
    Organization Name (eg, company) [Internet Widgits Pty Ltd]:BalaBit IT Security
    Organizational Unit Name (eg, section) []:Service Delivery
    Common Name (eg, YOUR name) []:scb35-1-i1.tohuvabohu.balabit
    Email Address []
  3. Create and configure a time stamping web server template in the Certificate Authority, and use that to generate the TSA certificate.

    1. Start the Certification Authority Microsoft Management Console, and select the CA server.

    2. Right-click Certificate Templates, and choose Manage.

      Figure 78: Managing certificate templates

      The Certificate Templates Console opens.

    3. Right-click the Web Server template, and choose Duplicate Template.

      Figure 79: Duplicating a Template

      The Properties of New Template window is displayed.

    4. Make the following changes to the new template:

      • On the General tab, change the Template display name to TSA.

        Figure 80: Creating the new template

      • On the Request Handling tab, enable the Allow private key to be exported option.

      • On the Extensions tab, make the following changes:

        Edit Application Policies:

        Select Application Policies and click Edit below the list of extensions.

        Figure 81: Editing Application Policies

        Remove Server Authentication:

        Select Server Authentication and click Remove.

        Figure 82: Removing Server Authentication

        Add Time Stamping:

        Click Add, select Time Stamping and click OK.

        Figure 83: Adding Time Stamping

        Make Time Stamping critical:

        Select Time Stamping and enable the Make this extension critical option, then click OK.

        Figure 84: Making Time Stamping critical

        Time Stamping and Critical extension are listed in the Description of Application Policies.

        Figure 85: Description of Application Policies

        Edit Key Usage:

        Select Key usage, click Edit. Enable the Signature is proof of origin (nonrepudiation) option.

        Select Allow key exchange without key encryption (key agreement).

        Click OK.

        Figure 86: Editing Key Usage

        The following are listed in the Description of Key Usage.

        Figure 87: Description of Key Usage

      • On the Security tab, select Authenticated Users, and set Enroll to Allowed.

        Figure 88: Configuring permissions for the template

    5. Click Apply. Click OK. The new TSA template is now displayed in the list of templates.

      Figure 89: The new TSA template is now displayed in the list of templates

    6. Close this window and return to the Certification Authority main screen, and select the Certificate Templates folder.

      Figure 90: Certificate Templates

      Right-click under the list, and choose New > Certificate Template to Issue.

      Figure 91: Certificate Template to Issue

      The Enable Certificate Templates window is displayed.

      Figure 92: Enable the new template

    7. Select the TSA certificate template, and choose OK. Close this window.

    8. Open the command line, and issue the following command:

      certreq -submit -attrib "CertificateTemplate:TSA" <CSR>

      Replace <CSR> with the full path of the CSR created earlier (in the second step).

    9. The Certification Authority List is displayed. Select the CA.

    10. The Save Certificate window is displayed. Choose an output folder.

      The certificate is generated to the specified folder.

  4. In SSB, navigate to Basic Settings > Management > SSL certificate.

  5. Click next to TSA X.509 certificate, browse for the previously generated certificate, and click Upload.

  6. Click next to TSA private key, browse for the previously generated key, and click Upload.


    If the root CA (the CA X.509 certificate field under Basic Settings > Management > SSL certificate) that is used for other certificates on SSB is different from the CA that was used to sign the TSA certificate, a warning is displayed. In this scenario, ignore this warning.

Creating hostlist policies

SSB can use a list of host and network addresses at a number of places, for example for limiting the client that can send log messages to a log source, or the hosts that can access shared logspaces.

Creating hostlists


To create a new hostlist, complete the following steps.

  1. Navigate to Policies > Hostlists and select .

  2. Enter a name for the hostlist (for example servers).

    Figure 93: Policies > Hostlists — Creating hostlists

  3. Enter the IP address of the permitted host into the Match > Address field. You can also enter a network address in the IP address/netmask format (for example To add more addresses, click and repeat this step.

  4. To add hosts that are excluded from the list, enter the IP address of the denied host into the Ignore > Address field.


    To add every address except for a few specific hosts or networks to the list, add the network to the Match list, and the denied hosts or networks to the Ignore list.

  5. Click Commit.


    If you modify a hostlist, navigate to Basic Settings > System > Service control > Syslog traffic, indexing & search: and select Restart syslog-ng for the changes to take effect.

Importing hostlists from files


To import hostlists from a text file, complete the following steps.

  1. Create a plain text file containing the hostlist policies and IP addresses to import. Every line of the file will add an IP address or network to a policy. Use the following format:



    ignore;IP address

    For example, a policy that ignores the IP address and another one that matches on the subnet, use:


    To add multiple addresses or subnets to the same policy, list every address or subnet in a separate line, for example:

  2. Navigate to Policies > Hostlists > Import from file > Browse and select the text file containing the hostlist policies to import.

    Figure 94: Policies > Hostlists — Importing hostlists

  3. If you are updating existing policies and want to add new addresses to them, select Append.

    If you are updating existing policies and want to replace the existing addresses with the ones in the text file, select Replace.

  4. Click Upload, then Commit.


    If you modify a hostlist, navigate to Basic Settings > System > Service control > Syslog traffic, indexing & search: and select Restart syslog-ng for the changes to take effect.

Related Documents