McAfee HISCDE-AB-IA Product Guide - Page 110

Note 2, dest_file, files:rename

Get McAfee HISCDE-AB-IA - Host Intrusion Prevention PDF manuals and user guides View all McAfee HISCDE-AB-IA manuals
Add to My Manuals
Save this manual to your list of manuals

Page 110 highlights

Appendix A - Writing Custom Signatures and Exceptions Windows custom signatures files { Include "*\\abc.txt" } If the section dest_file is used, the absolute path cannot be used and a wildcard must be present in the beginning of the path to represent the drive. For example, the following are valid path representations: dest_file { Include "*\\test\\abc.txt" } dest_file { Include "*\\abc.txt" } Note 2 The directive files:rename has a different meaning when combined with section files and section dest_file. When combined with section files, it means that renaming of the file in the section files is monitored. For example, the following rule monitors renaming of file C:\test\abc.txt to any other name: Rule { tag "Sample1" Class Files Id 4001 level 4 files { Include "C:\\test\\abc.txt" } Executable { Include "*"} user_name { Include "*" } directives files:rename } Combined with section dest_file, it means that no file can be renamed to the file in the section dest_file. For example, the following rule monitors renaming of any file to C:\test\abc.txt: Rule { tag "Sample2" Class Files Id 4001 level 4 dest_file { Include "*\\test\\abc.txt" } Executable { Include "*"} user_name { Include "*" } directives files:rename } The section files is not mandatory when the section dest_file is used. If section files is used, both sections files and dest_file need to match. Note 3 To distinguish between remote file access and local file access for any directive, set the executable file path name to "SystemRemoteClient": Executable { Include -path "SystemRemoteClient" } This would prevent any directive to execute if the executable is not local. 110 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
files { Include “*\\abc.txt” }
If the section
dest_file
is used, the absolute path cannot be used and a wildcard must be present
in the beginning of the path to represent the drive. For example, the following are valid path
representations:
dest_file { Include “*\\test\\abc.txt” }
dest_file { Include “*\\abc.txt” }
Note 2
The directive
files:rename
has a different meaning when combined with section files and section
dest_file.
When combined with section files, it means that renaming of the file in the section files is
monitored. For example, the following rule monitors renaming of file C:\test\abc.txt to any
other name:
Rule {
tag "Sample1"
Class Files
Id 4001
level 4
files { Include “C:\\test\\abc.txt” }
Executable { Include “*”}
user_name { Include “*” }
directives files:rename
}
Combined with section dest_file, it means that no file can be renamed to the file in the section
dest_file. For example, the following rule monitors renaming of any file to C:\test\abc.txt:
Rule {
tag "Sample2"
Class Files
Id 4001
level 4
dest_file { Include “*\\test\\abc.txt” }
Executable { Include “*”}
user_name { Include “*” }
directives files:rename
}
The section files is not mandatory when the section dest_file is used. If section files is used,
both sections files and dest_file need to match.
Note 3
To distinguish between remote file access and local file access for any directive, set the
executable file path name to "SystemRemoteClient":
Executable { Include -path “SystemRemoteClient”
}
This would prevent any directive to execute if the executable is not local.
Appendix A — Writing Custom Signatures and Exceptions
Windows custom signatures
McAfee Host Intrusion Prevention 8.0 Product Guide for ePolicy Orchestrator 4.5
110