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.
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 this Checklist
- Create a Security Administrator work queue.
- Add operators to this work queue who are responsible for verifying the completion of checklist tasks.
- 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:
- Security Checklist core tasks are critical and should be performed for every application.
- Security Checklist additional tasks may be required, depending on what Platform features your application uses, how much you customize a Pega application, the amount of sensitive data created and stored within the application, and other factors.
- Special considerations apply for public-facing applications, where not all
users are your employees.
For more information, see Basic requirements for deploying public-facing applications.
- Your choice of deployment environment also determines which tasks you need
to complete. Pega Cloud configures most deployment environment security for
For more information, see:
- Security Checklist core tasks
- Security Checklist additional tasks
- Security Checklist when deploying on Pega Cloud
- Security Checklist when not deploying on Pega Cloud
- Assessing your application using the Security Checklist
- Adding the Security Checklist to an application created before 7.3.1
- Implementing security guidelines for test environments