Skip to main content

Set server defaults at an organization level

Server settings provide default configurations to new servers (and their agents) are brought on board. Organization administrators can customize these configurations and set specific defaults for each environment.

To set server defaults:

  1. Under organization settings, select Servers.

  2. Use the dropdown to choose the environment in which you want to apply the default (development, test or production). Check the box next to Set as default environment if you want to specify a default environment for future server configuration.

  3. Use the dropdown to choose the Log Level. The default log level selection is ERROR.

  4. Under Automatic server cleanup, enter the length of time that you would like servers to be offline before they are automatically cleaned up. The default value is 30 days.

    A background task runs every five minutes to check if there is an organization with automatic server cleanup enabled.

    If there are one or more servers with no activity received within the configured time frame, Contrast disables the servers automatically. They are no longer visible under Servers in the Contrast web interface.

    Contrast keeps Information on vulnerabilities and attacks related to these servers even after they're disabled. Protect licenses from disabled servers return to the pool of licenses.

  5. Under Assess, select which stacktraces should be captured (all, some or none).

  6. Select the check box to Enable sampling for higher performance.

    1. If Contrast sees the same URL being called multiple times, it analyzes the URL based on the the number of times specified in the Baseline setting.

    2. Afterwards, if Contrast continues to see the same URL, it only checks it based on the Frequency setting.

    3. Contrast retains samples for the number of seconds specified for the Window setting. After the time specified for the Window setting elapses, Contrast analyzes the URL again, according to the Baseline setting.

    Configure the following settings:

    • Baseline: The number of times that Contrast analyzes URLs to complete sampling. The default setting is 5.

    • Frequency: The number of times that Contrast analyzes URLs after the Baseline is achieved. The default setting is 10.

    • Window: The number of seconds that Contrast retains samples before reverting to the Baseline. The default setting is 180.

  7. Under Protect, use the green toggle to enable Protect.


    Turning Protect on by default requires that Protect licenses are automatically applied to servers.

    Administrators receive emails each time a server is licensed. As servers go up and down frequently, you may want to setup an email filter for any unwanted traffic.

  8. Select the check box to Enable bot blocking.

    Bot blocking blocks traffic from scrapers, attack tools and other unwanted automation.

    To view blocked bot activity, under Attacks > Attack Events, use the Automated filter option.


    You can configure bot blocking in the YAML files for Java, .NET Framework, .NET Core, Ruby, and Python.

  9. Select the checkbox to Enable output of Protect events to syslog.

  10. Enter the IP Address and Port in the given fields. Use the dropdown to chose the Facility.

  11. Click on the event severity badges, and use the dropdown to choose a message Severity level for each one. The defaults are:

    • 1 - Alert for Exploited

    • 4 - Warning for Blocked

    • 5 - Notice for Probe

  12. If allowed at a system level, you can check the box to Automatically apply licenses to new servers for Protect.

  13. Turn the toggle on (green) to enable the Retain Library Data function. When enabled library details on the last server will be retained instead of being deleted from Contrast during server cleanup.