Skip to main content

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

Defining the security model and product operational structure

Updated on April 20, 2021
Product Designer for Financial Services

Security planning involves defining authorization and authentication strategies for your application.

  • Authentication: proves to the application that you are who you say you are. Pega applications support several authentication protocols.
  • Authorization: tells the application which functions you may perform. Pega applications define this using access group and role configurations.

Pega security planning additionally involves configuring the application’s operational structure and operator. attributes

Pega applications provide organization the ability to fine-tune security control through using access settings and denial rules in the application. Many integration rules also incorporate authentication.

Defining the security model includes these tasks:

  • Supported authentication schemes
  • Defining an authentication scheme
  • Configuring the authorization scheme in the application
  • Defining theproduct operational structure
  • Defining the operator attributes

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