McAfee HISCDE-AB-IA Product Guide - Page 102

Common s, Windows custom signatures, Include

Page 102 highlights

Appendix A - Writing Custom Signatures and Exceptions Rule structure method { Include GET } time { Include * } Executable { Include * } user_name { Include * } directives isapi:request } See Windows custom signatures and Non-Windows custom signatures for an explanation of the various sections and values. Common sections A rule's most common sections and their values include the items below. For sections relevant to the selected class section, see the class section under Windows or Non-Windows custom signatures. The keywords Include and Exclude are used for all sections except for tag, Id, level, and directives. Include means that the section works on the value indicated, and Exclude means that the section works on all values except the one indicated. NOTE: All section names on all platforms are case-sensitive. Values for sections are case-sensitive on non-Windows platforms only. Section Class tag Id level Value Description Depends on operating system. See Windows custom signatures or Non-Windows Indicates the class this rule custom signatures. applies to. Name of the rule in quotes "..." Name of the subrule. 4000 - 5999 The unique ID number of the signature. The numbers are the ones available for custom rules. 0 The severity level of the signature: 1 0=Disabled 2 1=Log 3 2=Low 4 3= Medium 4= High user_name {Include/Exclude user's name or The users to whom the rule applies. Specify system account} particular users or all users. Remarks for Windows: • For local user: use /. • For domain user: use /. • For local system: use Local/System. • Some remotely initiated actions do not report the ID of the remote user, but use the local service and its user context instead. You need to plan accordingly when developing rules. When a process occurs in the context of a Null Session, the user and domain are 'Anonymous'. If a rule applies to all users, use *. On UNIX, this section is case sensitive. 102 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

method { Include GET }
time { Include * }
Executable { Include * }
user_name { Include * }
directives isapi:request
}
See
Windows custom signatures
and
Non-Windows custom signatures
for an explanation of
the various sections and values.
Common sections
A rule’s most common sections and their values include the items below. For sections relevant
to the selected class section, see the class section under Windows or Non-Windows custom
signatures. The keywords
Include
and
Exclude
are used for all sections except for tag, Id, level,
and directives. Include means that the section works on the value indicated, and Exclude means
that the section works on all values except the one indicated.
NOTE:
All section names on all platforms are case-sensitive. Values for sections are case-sensitive
on non-Windows platforms only.
Description
Value
Section
See
Windows custom signatures
or
Non-Windows
custom signatures
.
Depends on operating system.
Indicates the class this rule
applies to.
Class
Name of the subrule.
Name of the rule in quotes "..."
tag
The unique ID number of the signature. The
numbers are the ones available for custom rules.
4000 - 5999
Id
The severity level of the signature:
0=Disabled
0
1
level
1=Log
2
2=Low
3
3= Medium
4
4= High
The users to whom the rule applies. Specify
particular users or all users.
{Include/Exclude user's name or
system account}
user_name
Remarks for Windows:
For local user: use <machine name>/<local
user name>.
For domain user: use <domain
name>/<domain user name>.
For local system: use Local/System.
Some remotely initiated actions do not
report the ID of the remote user, but use
the local service and its user context
instead. You need to plan accordingly when
developing rules. When a process occurs in
the context of a Null Session, the user and
domain are ‘Anonymous’. If a rule applies
to all users, use *. On UNIX, this section is
case sensitive.
Appendix A — Writing Custom Signatures and Exceptions
Rule structure
McAfee Host Intrusion Prevention 8.0 Product Guide for ePolicy Orchestrator 4.5
102