Skip to main content


Using Access Control Checks

Suggest edit Updated on June 30, 2021

Use Access Control Checks to identify broken custom code that must be fixed. During development, it is easy to introduce risks into your application by implementing custom code. By using Access Control Checks, you help proactively fix your code by identifying potential issues.

If you do not fix broken access controls, when you enable security protections and the application goes into hardening, the broken features may stop working or will not work properly.

  1. In the header of Dev Studio, click ConfigurationOrg and SecurityToolsSecurityAccess Control Check.

  2. Optional:

    On the Search Criteria tab, select from the following check boxes:

      1. Select an Application check box to define the application on which you will run the Access Control Check. Note: The current application is selected by default. If you have multiple applications configured, you can run tests on the applications at the same time.Note: Running tests for multiple applications at the same time will take longer to process the request. The more applications that you check, the longer the Access Control Check will take.
      2. Select the Rulesets check box to define the rulesets on which you want to run the Access Control Check. By default, all rulesets are selected. However, to only run checks on certain rulesets, clear the Ruleset check box to manually indicate which rulesets you want to run the check on.Note: When you make small changes to a ruleset that you want to verify, it is more effective to run the Access Control Check on just the rulesets that you change, to ensure that they do not cause any unintended issues.
  3. Optional:

    To select whether to display and run the Access Control Check on rules that call custom code in custom calls, or on a Standard API, select one of the following radio buttons:

    Custom calls in custom code
    Runs the rules in your applications that call custom code from custom calls.
    Standard API calls in custom code
    Runs the rules in your applications that call custom code from Standard API.
  4. Click List Rules for mitigation button.

  5. Open each rule to refactor and address its issues.

Result: The system will display a table of Access Control alerts that you need to mitigate.
Did you find this content helpful? YesNo

0% found this useful

Have a question? Get answers now.

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

Ready to crush complexity?

Experience the benefits of Pega Community when you log in.

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