Skip to main content


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

This content has been archived and is no longer being updated.

Links may not function; however, this content may be relevant to outdated versions of the product.

Pega Sales Automation for Financial Services modified rules for BAC prevention (8.3 and prior)

Updated on September 10, 2021

Broken Access control (BAC) refers to all access control issues in web applications that allow end-users to gain unauthorized access to privileged data and functionality. Open Web Application Security Project (OWASP) identifies BAC as one of the top 10 security vulnerabilities. BAC usually occurs when users can bypass access control checks by leveraging vulnerabilities such as uniform resource locator (URL)-based requests that do not verify user privileges.

In the 8.3 release, Pega Sales Automation for Financial Services has modified the rules that call secured activities in the Pega Platform. The query strings and parameters in the calls are registered so that they cannot be tampered by the end-users.

For more information about the enhancements to prevent Broken Access Control (BAC), and to see a list of rules that were modified for all Pega Sales Automation applications, see Pega Sales Automation modified rules for BAC prevention.

The following list shows the modified rules for Pega Sales Automation for Financial Services 8.5. If you have overridden any of these rules in your Pega Sales Automation for Financial Services implementation layer, you need to update them with the changed rules.

#Rule typeRule nameClass nameAvailableRuleset version
1RULE-HTML-SECTIONCRMSUBMITANDCANCELPEGSAFS-WORK-OPPORTUNITYYesPEGASAFS:08-05-01

The following list shows the modified rules for Pega Sales Automation for Financial Services 8.3. If you have overridden any of these rules in your Pega Sales Automation for Financial Services implementation layer, you need to update them with the changed rules.

#Rule typeRule nameClass nameAvailableRuleset version
1Rule-HTML-PropertySafsStageProcessButton Yes08-03-01
2Rule-Obj-ActivityGetListOfFieldValues@baseclassNo (Withdrawn)08-03-01
3Rule-Obj-ActivitypyCalendarEventDetails@baseclassYes08-03-01
4Rule-Obj-ActivityDownloadAttachedFileData-WorkAttach-FileYes08-03-01
5Rule-Obj-ActivitypyCalendarEventDetailsPegaSAFS-Work-AppointmentNo (Withdrawn)08-03-01
6Rule-Obj-ActivityOpenDefaultsPegaSAFS-Work-OpportunityYes08-03-01

 

  • Previous topic Activating and training adaptive models for artificial intelligence in Pega Sales Automation for Financial Services (8.4 and prior)

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