| Where Can I Use This? | What Do I Need? |
- Strata Cloud Manager
- Prisma Browser standalone
|
- Prisma Access with Prisma Browser bundle
license or Prisma Browser standalone license
- Superuser or Prisma Browser
role
|
To see the rules from Strata Cloud Manager, select .
All changes to policy rules are saved to a draft
configuration and do not take effect until you publish the draft. For more
information, see Manage Configuration Versions (Draft Mode).
You can use rules to specify the users, user groups, and device groups that
will be impacted by the various policies you create. These rules govern access to
web applications, security policies, and customization options. By utilizing rules
you can precisely control user access to organizational tools and components.
Each Rule is composed of different parameters and controls so that you can
create finely tuned Rules for each use case. Each Rule type has its specific
contents and requirements.
You have three available Rule types in the Prisma Browser. The
components are displayed on each tab's Policy Rules page.
For each Rule type, the Rules are evaluated according to their priority.
The first Rule that matches all the requirements creates the trigger that will be
enforced. When this happens, the browser stops looking for Rules.
Example with Access & Data Control rules:
Rule 1: Scope - Mike (a member of the General Contractors Users
group)
Web application - linkedin.com
Access to the named web application AllowedData controls - File
Download - Blocked
Rule 2: Scope -Gowri (a member of the General Contractors Users
group)
Web application - linkedin.com
Access to the named web application - AllowedData controls - File
Upload - Allowed When contains - email address.
Rule 3: Scope - Summer Interns Users Group
Web application - linkedin.com
Access to the named web application -Blocked
Rule 4: Scope - General Contractors Users Group
Web application - linkedin.com
Access to the named web application - AllowedData controls - File
Upload- Blocked
Mike will be allowed to access linkedin.com, however, he’ll be blocked when
he tries to download a file since his action matches Rule 1.
When he tries to upload a file, the Policy Engine will see that Rule 1 does
not apply. It then will move on to check the next Rule. Rule 2 does not apply due to
the Data controls. Rule 3 does not apply to Mike, as he is outside the Rule's scope.
Rule 4 will block Mike from uploading on linkedin.com.
As long as there is no matching rule, the Policy Engine will keep checking.
When it reaches the end of the list, the action will proceed according to the
default rule, as there is no other rule to apply.
| Rule | Scope | Access to linkedin.com | Download | Upload | When contains |
| 1 | Mike | Allowed | Blocked | | |
| 2 | Gowri | Allowed | | Allowed | email address |
| 3 | Summer Interns | Blocked | - - - - - - | - - - - - - | |
| 4 | General Contractors | Allowed | | Blocked | |
Mike wants to download a file from linkedin.com.
Mike wants to upload a file to linkedin.com.
Rule 1 does not apply (The rule is for downloads). Policy Engine
continues.
Rule 2 does not apply (Mike is out of scope). Policy Engine
continues.
Rule 3 applies, and the upload is Blocked. Policy Engine stops
looking for rule matches.
Gowri wants to upload a file to linkedin.com.
Rule 1 does not apply (Gowri is out of scope). Policy Engine
continues.
Rule 2 applies - but only if the upload includes an email address;
if not, Policy Engine continues.
Rule 3 does not apply (Gowri isn't a Summer Intern). Policy Engine
continues.
Rule 4 applies, and the upload is Blocked.