You can edit custom YARA rules, for example, to enable the rule, update the tags, or to reanalyze files.


To get familiar with YARA rule parameters, see YARA Rule Parameters.

For a list of the YARA tags that have predefined meanings, see YARA Rule Tags.

To get familiar with YARA CBEP attributes, see YARA CBEP Attributes.

Important: In general, consider YARA rules to be completely case-sensitive.
  • Rule identifiers can differ only by case, for example, "ABC" and "abc" can identify completely different rules.
  • Operators such as == and contains use case-sensitive semantics and may return counter-intuitive results. For example, hash.sha1(0, filesize) == "7193B6EDF651EAC1AB437F64B2FD6F203F8B702F" will never return true because YARA hashes use lower case hexadecimal digits. There are no modifiers or workarounds available for this.
  • Regular expressions can be used as workarounds for case-sensitivity. For example, == returns false for hashes with differing case. However, the required results can be obtained by using a case insensitive regular expression: (cbep.analysis.file.signature.codesigning_chain[0].cert[0].sha1_thumbprint matches /^09A5C5E9AF1B96091B22F92E0356B1C33A410420$/is. For information on regular expressions, see
  • The Windows Agent generally ignores the case of YARA tags, however, it is recommended always to use lower case when using predefined tags. Tags in the Classification namespace are always treated case-insensitively, for example, QUARANTINE becomes quarantine. However, some of the predefined tags in the IsInteresting namespace must be lower case for them to be recognized. These tags are: archive, dep_incompatible, executable, filetype, installer, invalid, script, and script_interpreter.
For more information, see
Warning: The quarantine tag will cause a file to be deleted if tagged with it.
Important: YARA rules are powerful and can have far-reaching, unexpected consequences. It is strongly recommended that you test a rule before you enable it for your endpoints. Ensure you are familiar with the instructions in Test a YARA Rule.


  1. On the console menu, navigate to the Rules > Software Rules page.
    Tip: Before you edit a YARA rule, consider the following testing and editing scenario that may save you some time.
    1. Suppose you have a rule named AbsoluteGuardian that you want to edit. To test your changes, create a rule named AbsoluteGuardian_temporary which is a copy of AbsoluteGuardian.
    2. Modify AbsoluteGuardian_temporary and test it.
    3. If AbsoluteGuardian_temporary works as expected, copy its content to AbsoluteGuardian and delete AbsoluteGuardian_temporary.
  2. Click the YARA tab and locate the YARA rule that you want to modify in the table.
  3. Click the View Details icon on the left of the specific rule.
    The Edit YARA Rule page appears.
  4. Edit the rule.
    Note: For the agent to apply any tags set by one or more rules where the namespace is specified as IsInteresting, the final tag applied to a file must be filetype. The agent will only treat a file as interesting if either the executable tag or the script tag was applied before the filetype tag. The archive tag and the installer tag can also be used, although they do not determine the interesting status.
    Warning: Ensure tags are used in only one namespace. For example, do not use the same tag in a rule in the Classification namespace and subsequently in a rule in the IsInteresting namespace. Otherwise, tags might not be removed from an analysis when a YARA rule is edited or deleted.
    Note: For rules in the IsInteresting namespace, CBEP attributes are not available. The file has not been hashed yet and will have not have an associated AB.
  5. Before you save the rule for global use, it is strongly recommended to test it by following some or all of the steps in Test a YARA Rule.
  6. When you are satisfied with the rule, click Save & Exit.


The modified rule appears in the YARA rules table.

The agent must sync with the server and download the new rule for it to become effective.

If the YARA rule is enabled and the Namespace is defined as Classification, all new or modified files will be scanned and the rule tags will be assigned if the rule criteria is met. If you chose to rescan known files, they are rescanned immediately or the rescan will begin during the time range you selected.

If the YARA rule is enabled and the Namespace is defined as IsInteresting, all new or modified files will be scanned and the rule tags will be assigned if the rule criteria is met. If you chose to perform a full system scan, it is performed immediately or will begin during the time range you selected.