--- title: "aaa authorization access-groups rules rule" slug: "aaa-authorization-access-groups-rules-rule" tags: ["Reference", "CMS 11.x", "EX 11.x", "HX 10.x", "FX 11.x", "AX 11.x", "NX 11.x", "IVX 11.x", "Customer", "Network Security"] updated: 2026-08-04T17:22:07Z published: 2026-08-04T17:22:07Z canonical: "docs.trellix.com/aaa-authorization-access-groups-rules-rule" stale: true --- > ## Documentation Index > Fetch the complete documentation index at: https://docs.trellix.com/llms.txt > Use this file to discover all available pages before exploring further. # aaa authorization access-groups rules rule Creates or modifies an authorization rule defining matching criteria that is applied to a login request, and specifies the access group to which the matched user will be granted access. > [!NOTE] > Note > > For more information about authorization rules and usage, see the "Configuring Access Groups for Alerts" chapter of the *Trellix* *System Security Guide*. ### Syntax `aaa authorization access-groups rules rule <operation> <match option 1> [<match option 2>...] grant-access-group <access group name> [comment "<comment>"]` `no aaa authorization access-groups rules rule <rule number> <match option>` `no aaa authorization access-groups rules rule <rule number>` `no aaa authorization access-groups rules all` `no aaa authorization access-groups rules rule <rule number> comment` ### Parameters `no` The `no` forms of this command remove the specified match option, the specified authorization rule, all authorization rules, or a comment from an authorization rule. `operation` The operation used to define the position of a rule in the rule list, modify a rule, or delete duplicate rules. | `append tail` | Inserts the new rule after the highest-numbered rule, or at position 1 if there are no existing rules. | | --- | --- | | `insert <rule number>` | Inserts the new rule at the specified position. If there is already a rule in this position, that rule and all other rules are moved up by one position. | | `set <rule number>` | Creates a new rule at the specified position. If there is already a rule in this position, it is replaced by the new rule. | | `modify <rule number>` | Creates or modifies a rule at the specified position. If there is already a rule in this position, the old values are retained unless they are modified by new values specified by this command. | | `dup-delete` | Deletes rules that are the same as the specified rule. (Rules that are the same except for their comments are not deleted.) | `match option` The match criteria that will be applied to login requests. You can include multiple match options, but not more than one of the same type. If a rule includes more than one match option, all statements must be true to achieve a match. | `match-auth-method <method>` | Match the specified authentication method (local, radius, tacacs+, or ldap). | | --- | --- | | `match-not-auth-method <method>` | Do not match the specified authentication method. | | `match-remote-username <name>` | Match the specified remote user name. | | `match-not-remote-username <name>` | Do not match the specified remote user name. | | `match-mapped-local-username <name>` | Match the specified local user name. | | `match-not-mapped-local-username <name>` | Do not match the specified local user name. | | `match-ldap-group <group DN>` | Match the specified LDAP group Distinguished Name (DN). | | `match-not-ldap-group <group DN>` | Do not match the specified LDAP group DN. | | `match-ldap-search-filter <string>` | Match the specified LDAP search filter. | | `match-x509-cert-subject <string>` | Match the specified subject field in the client X.509 certificate. The subject field contains the Distinguished Name (DN). | | `match-x509-cert-san-email <string>` | Match the specified email address in the Subject Alternate Name (SAN) field in the X.509 client certificate. | | `match-x509-cert-san-email-username <string>` | Match the specified user name portion of the email address in the X.509 client certificate. | | `match-x509-cert-san-upn <string>` | Match the specified User Principal Name (UPN) attribute from the SAN/Other Name field in the X.509 client certificate. | | `match-x509-cert-san-upn-username <string>` | Match the user name from the UPN attribute in the X.509 client certificate. | | `match-x509-cert-subject-cn <string>` | Match the specified Common Name (CN) entry from the DN attribute in the X.509 client certificate. | | `match-oidc-preferred-username <string>` | Match the specified preferred-username field in the OIDC identity token. | | `match-oidc-email <string>` | Match the specified email field in the OIDC identity token. | | `match-oidc-email-username <string>` | Match the specified username portion of the email address in the OIDC identity token. | | `match-saml-attribute <string>` | Match the specified attribute element from the SAML assertion. | | `match-saml-nameid <string>` | Match the specified name ID element from the SAML assertion. | `access group` The name of the access group to which the rule applies. To apply the rule to multiple access groups, you can add a separate `grant-access-group <access group>` option for each group, or use one option with a comma-separated list of groups as the `<access group>` parameter. `comment` An optional comment. Enclose the comment in double-quotation marks if it includes more than one word. ### Examples The following example creates a rule that grants users in the infosec LDAP group access to the alerts defined for the nx-alerts access group. ```plaintext cm-03 (config) # aaa authorization access-groups rules rule append tail match-ldap-group infosec grant-access-group nx-alerts ``` ```plaintext cm-03 (config) # show aaa authorization access-groups rules #      AAA Authorization Access-groups Rules : Enabled ----------------------------------------------------------- # Rule        Statements ----------------------------------------------------------- #1           Match LDAP Group          : infosec              Grant Access Groups       : nx-alerts ``` The following example removes the `match-mapped-local-username analyst2` match option from rule 2. ```plaintext cm-05 (config) # no aaa authorization access-groups rules rule 2 match-mapped-local-username ``` The following example adds the user "analyst_a" to the "special-analysts" access group on the nx-03 appliance for YARA rules access. ```plaintext nx-03 (config) # aaa authorization access-groups rules rule append tail grant-access-group special_analysts match-mapped-local-username analyst_a ``` ```plaintext nx-03 (config) # show aaa authorization access-groups rules ``` ```plaintext -------------------------------------------------------------- #         AAA Authorization Access-groups Rules : Enabled -------------------------------------------------------------- # Rule          Statements       -------------------------------------------------------------- # 1 Match Map Local Users              : analyst_a Grant Access Groups                : special_analysts ``` ### User role Admin ### Command mode Configuration ### Supported appliances This command is supported on the following appliances running the specified releases or later: - **Central Management System****:** Release 8.2.0. New authorization rules were added to match against the name ID and attribute fields in the SAML assertion in Release 8.7.1. - **Network Security****:** New option was added to match YARA rules access in Release 9.1.0.