Skip to main content


         This documentation site is for previous versions. Visit our new documentation site for current releases.      
 

Implementing security guidelines for test environments

Updated on March 15, 2022

As a best practice, configure the application server in your test environment so it mirrors a production environment configuration.

Use the following guidelines to minimize security vulnerabilities on the server side in your application:

  • Prevent the application server from serving files to unauthorized users.
  • Disable application-server directory traversals. For example, eliminate the ability to insert ../ or ..\ into directory paths.
  • Disable directory listings on the application server.
  • Verify that no extraneous ports are open on the application server or on the firewall that protects the application server.
  • Disable HTTP methods that your application does not use, including HEAD, TRACE, and TRACK. By default, Pega Platform uses POST and GET.
  • Remove the web server banner from the Server field in the HTTP response header. This ensures that you do not share the type and version of your application server with users.
  • Disable sample applications, their supporting files, and permissions when they are no longer used. This prevents users from logging in to your system with sample application credentials.

Have a question? Get answers now.

Visit the Support Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best.

Pega.com is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us