Skip to main content

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

Security Checklist

Updated on July 1, 2021

The Security Checklist provides Pega's leading practices for securely deploying applications. To assist you in tracking the completion of the tasks in the Security Checklist, Pega Platform™ shows the overall completion on the Dev Studio Home page, and built-in ways to track the status of each task.

Pega takes application and system security extremely seriously. Security is a shared responsibility between Pega and our clients.

Each successive release of Pega Platform augments the security features and capabilities available to harden applications and systems against improper access and to protect the data that those applications manage.

The Security Checklist is the key feature of Pega Platform that assists clients in hardening their applications and systems. The Security Checklist does the following:

  • Provides Pega's leading practices for securely deploying applications.
  • Helps protect the confidentiality, integrity, and availability of your application in production.
  • Identifies when each task should be performed: at or near the beginning of development, on an ongoing basis, or just before deployment.
  • Helps avoid expensive rework late in your development process.

To assist you in tracking the completion of the tasks in the Security Checklist, Pega Platform automatically installs an application guideline rule instance that includes the tasks in the Security Checklist for each version of your application.

For more information, see Assessing your application using the Security Checklist.

Note: If you are using Deployment Manager, starting in Pega Platform 8.5, completing the Security Checklist is required to move an application into production.

Security is critical

Inadequate security can prevent your application from being deployed in two ways:

  • Most clients need approval from the IT security group who review the application’s security before the project team can put the application into production.
  • If a client is building their application with Deployment Manager, the application will be blocked if the Security Checklist has not been completed.

Your responsibility as an administrator, senior system architect, or lead system architect is to ensure the confidentiality, integrity, and availability of your application. Unauthorized individuals should not be able to access or modify the application or the data it creates and stores. Further, users should only have access to those application functions and data that are necessary to perform their jobs.

Prepare to complete the Security Checklist

At the beginning of application development, determine who is responsible for verifying the completion of the tasks in the Security Checklist, and assign clear responsibility for each task to the Security Administrator.

Determine who is responsible for the Security Checklist
  • Create a Security Administrator work queue.
  • Add operators who are responsible for verifying the completion of the Security Checklist tasks to this work queue.
  • Click the option on each task to create a corresponding user story, give it a high priority, and assign to this work queue.

    For more information, see:

Independent security assessment

An independent assessment of your application’s security, and sign-off of that assessment, is always recommended and is required by most organizations’ IT Security groups.

Guardrail compliance: the basis of a secure application

The most important security requirement for all Pega Platform applications is to maintain guardrail compliance. Pega Platform security features cannot always be successfully enforced in custom code.

Use the built-in security configuration features in Pega Platform to protect your application, and do not rely on custom code built by developers who are not security experts.

Review the Application Guardrails landing page weekly and make changes to keep your application rules in compliance.

Do not wait until deploying your application to eliminate non-compliant rules, because applying changes is costlier after deployment.

For more information, see Improving your compliance score.

If your application includes custom Java or custom HTML written by your project team, you must perform special tasks to secure that code.

For more information, see:

Not all security tasks are required for all applications or releases

It’s important to understand the nature of the application and how it will be deployed when reviewing the Security Checklist tasks – these tasks are not required for all applications:

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. is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us