McAfee HISCDE-AB-IA Product Guide - Page 104

Optional common s, Wildcards and variables, Use of the dependencies

Page 104 highlights

Appendix A - Writing Custom Signatures and Exceptions Rule structure • If a single subrule includes a particular user marketing\jjohns and excludes the same user marketing\jjohns, then the signature does not trigger even when the user marketing\jjohns performs an action triggers the signature. • If a subrule includes all users but excludes the particular user marketing\jjohns, then the signature triggers if the user is NOT marketing\jjohns. • If a subrule includes user marketing\* but excludes marketing\jjohns, then the signature triggers only when the user is marketing\anyone, unless the user is marketing\jjohns, in which case it does not trigger. Optional common sections A rule's optional sections and their values include the item below. For optional sections relevant to the class section that is selected, see the class section under Windows and Non-Windows custom signatures. The keywords Include and Exclude are used for both dependencies and attributes. Include means that the section works on the value indicated, and Exclude means that the section works on all values except the one indicated. Section dependencies attributes Value Description {Include/Exclude "id of a rule"} Defines dependencies between rules and prevents the triggering of dependent rules. -no_log Events from the signature are not sent to the ePO server. -not_auditable No exceptions are generated for the signature when adaptive mode is applied. -no_trusted_apps The trusted application list does not apply to this signature. -inactive The signature is disabled. Use of the dependencies section Add the optional section dependencies to prevent a more general rule from being triggering along with a more specific rule. For example, if there is one rule to monitor for a single text file in C:\test\ files { Include C:\\test\\abc.txt } as well as a rule to monitor all the text files in C:\test\ files { Include C:\\test\\*.txt } Add the section dependencies to the more specific rule, basically telling the system not to trigger the more general rule if the specific rule is triggered. files { Include C:\\test\\abc.txt } dependencies "the general rule" Wildcards and variables Wildcards, meta-symbols, and predefined variables can be used as the value in the available sections. 104 McAfee Host Intrusion Prevention 8.0 Product Guide for ePolicy Orchestrator 4.5

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
  • 113
  • 114
  • 115
  • 116
  • 117
  • 118
  • 119
  • 120
  • 121
  • 122
  • 123
  • 124
  • 125
  • 126
  • 127
  • 128
  • 129
  • 130
  • 131
  • 132
  • 133
  • 134
  • 135
  • 136
  • 137
  • 138
  • 139
  • 140
  • 141
  • 142
  • 143
  • 144
  • 145
  • 146
  • 147
  • 148
  • 149
  • 150
  • 151
  • 152
  • 153
  • 154

If a single subrule includes a particular user
marketing\jjohns
and excludes the same user
marketing\jjohns
, then the signature does not trigger even when the user
marketing\jjohns
performs an action triggers the signature.
If a subrule includes
all
users but excludes the particular user
marketing\jjohns
, then the
signature triggers if the user is NOT
marketing\jjohns
.
If a subrule includes user
marketing\*
but excludes
marketing\jjohns
, then the signature
triggers only when the user is
marketing\anyone
, unless the user is
marketing\jjohns
, in
which case it does not trigger.
Optional common sections
A rule’s optional sections and their values include the item below. For optional sections relevant
to the class section that is selected, see the class section under Windows and Non-Windows
custom signatures. The keywords
Include
and
Exclude
are used for both dependencies and
attributes. Include means that the section works on the value indicated, and Exclude means
that the section works on all values except the one indicated.
Description
Value
Section
Defines dependencies between rules and prevents
the triggering of dependent rules.
{Include/Exclude “id of a rule”}
dependencies
Events from the signature are not sent to the ePO
server.
—no_log
attributes
No exceptions are generated for the signature
when adaptive mode is applied.
—not_auditable
The trusted application list does not apply to this
signature.
—no_trusted_apps
The signature is disabled.
—inactive
Use of the dependencies section
Add the optional section dependencies to prevent a more general rule from being triggering
along with a more specific rule. For example, if there is one rule to monitor for a single text file
in C:\test\
files { Include C:\\test\\abc.txt }
as well as a rule to monitor all the text files in C:\test\
files { Include C:\\test\\*.txt }
Add the section dependencies to the more specific rule, basically telling the system not to trigger
the more general rule if the specific rule is triggered.
files { Include C:\\test\\abc.txt }
dependencies “the general rule”
Wildcards and variables
Wildcards, meta-symbols, and predefined variables can be used as the value in the available
sections.
Appendix A — Writing Custom Signatures and Exceptions
Rule structure
McAfee Host Intrusion Prevention 8.0 Product Guide for ePolicy Orchestrator 4.5
104