Using Access Control Checks
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 may not work properly.
In the header of Dev Studio, click.
On the Search Criteria tab, select from the following check boxes:
- Select an Application check box to define
the application on which you will run the accessa control check.
The current application is selected by default. If you have multiple applications configured, you can run tests on the applications at the same time.Running tests for multiple applications at the same time takes longer to process the request. The more applications that you check, the longer the Access Control Check will take.
- 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.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.
- Select an Application check box to define the application on which you will run the accessa control check.
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.
Click List Rules for mitigation button.
Open each rule to refactor and address its issues.