Learn how to create, view, list, update, archive, and unarchive custom rules in
Prisma AIRS AI Model Security.
| Where Can I Use This? | What Do I Need? |
- Prisma AIRS (AI Model Security)
|
- Prisma AIRS AI Model Security License
|
Custom rules let you define your own security checks in addition to the built-in
managed rules. A custom rule is a tenant-wide rule that evaluates a model scan's
labels and the pass/fail results of managed rules, combined with AND/OR logic, and
produces a violation message and remediation steps that you define when its
condition matches.
A custom rule is defined at the tenant level and then assigned to one or more
security groups, where each assignment is blocking, allowing (non-blocking), or
disabled. A custom rule can only be assigned to a security group whose source type
is in the rule's compatible sources.
The rule_action field controls the polarity of the check.
FAIL (default) produces a violation when the condition matches.
PASS produces a violation when the condition does not
match.
When you create or update a custom rule, its condition is validated. A request is
rejected with a 422 error if it references a managed rule that does
not exist, if the condition is unsatisfiable (an AND group that can never be true),
is a tautology (an OR group that is always true), or exceeds the depth or leaf-node
limits.
Custom rules follow these limits:
| Property | Limit |
| Active custom rules per tenant | 100 |
| Custom rule assignments per security group | 25 |
| Condition nesting depth | 25 levels |
| Condition leaf nodes (total per rule) | 100 |