McAfee HISCDE-AB-IA Product Guide - Page 30

Methods for delivery of IPS protection, Enveloping and shielding, System call interception

Page 30 highlights

Configuring IPS Policies Overview of IPS policies Methods for delivery of IPS protection Shielding and enveloping, system call interception, and installation of specific engines and drivers are the methods used to deliver IPS protection. Enveloping and shielding Host Intrusion Prevention uses enveloping and shielding signatures to protect against attacks. The enveloping strategy works to prevent applications from accessing files, data, registry settings, and services outside their own application envelope. The shielding strategy works to prevent application files, data, registry settings, and services from being the accessed by an exploit from outside their own application envelope. System call interception Host Intrusion Prevention monitors all system and API calls and blocks malicious activity. It determines which process is using a call, the security context in which the process runs, and the resource being accessed. A Host Intrusion Prevention kernel-level driver, which receives redirected entries in the user-level system call table, monitors the system call chain. When calls are made, the driver compares the call request against a database of combined signatures and behavioral rules to determine whether to allow, block, or log an action. User-level programs use the functionality provided by the kernel to access disk drives, network connections, and shared memory. Because the processor prevents direct access to kernel-level functions, user-level programs use system calls, which permit communication between user and kernel modes. System calls expose all kernel functionality that user-level programs require and are implemented inside the operating system using a system call table. Host Intrusion Prevention inserts itself into the system call chain by installing a kernel-level driver and redirecting the entries in the system call table. When an application requests a file, it is directed to the Host Intrusion Prevention driver, which checks the request against its set of signatures and behavioral rules to determine whether to allow or block the request. HTTP engine for web servers Host Intrusion Prevention gives protection against attacks directed at web applications and systems with its HTTP protection engine. It protects by parsing the HTTP stream coming in to an application and matching patterns on incoming HTTP requests. The HTTP Protection engine installs between the web server's SSL decryption and decoding element that turns requests into plain text and the web server's engine. This guarantees that the Host Intrusion Prevention engine sees requests in plain text and blocks malicious requests before they are processed. HTTP signatures prevent directory traversal and Unicode attacks, web defacement, data theft, and server hacking. SQL engine for SQL servers Host Intrusion Prevention protects against attacks on database servers with its SQL inspection engine, which installs between database network libraries and the database engine. It examines all SQL requests and blocks any that could trigger an event. SQL protection rules, which differentiate on user, query origination location, query validity, and other parameters. SQL database signatures build on the core protection provided by standard signatures and add specific database interception and protection rules. The Host IPS SQL engine intercepts incoming database queries before they are processed by the database engine. Each query is examined to see whether it matches any known attack signatures, if it is well formed, and if there are tell-tale signs of SQL injection. 30 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

Methods for delivery of IPS protection
Shielding and enveloping, system call interception, and installation of specific engines and
drivers are the methods used to deliver IPS protection.
Enveloping and shielding
Host Intrusion Prevention uses enveloping and shielding signatures to protect against attacks.
The enveloping strategy works to prevent applications from accessing files, data, registry
settings, and services outside their own application envelope. The shielding strategy works to
prevent application files, data, registry settings, and services from being the accessed by an
exploit from outside their own application envelope.
System call interception
Host Intrusion Prevention monitors all system and API calls and blocks malicious activity. It
determines which process is using a call, the security context in which the process runs, and
the resource being accessed. A Host Intrusion Prevention kernel-level driver, which receives
redirected entries in the user-level system call table, monitors the system call chain. When calls
are made, the driver compares the call request against a database of combined signatures and
behavioral rules to determine whether to allow, block, or log an action.
User-level programs use the functionality provided by the kernel to access disk drives, network
connections, and shared memory. Because the processor prevents direct access to kernel-level
functions, user-level programs use system calls, which permit communication between user
and kernel modes. System calls expose all kernel functionality that user-level programs require
and are implemented inside the operating system using a system call table. Host Intrusion
Prevention inserts itself into the system call chain by installing a kernel-level driver and redirecting
the entries in the system call table. When an application requests a file, it is directed to the
Host Intrusion Prevention driver, which checks the request against its set of signatures and
behavioral rules to determine whether to allow or block the request.
HTTP engine for web servers
Host Intrusion Prevention gives protection against attacks directed at web applications and
systems with its HTTP protection engine. It protects by parsing the HTTP stream coming in to
an application and matching patterns on incoming HTTP requests. The HTTP Protection engine
installs between the web server's SSL decryption and decoding element that turns requests into
plain text and the web server's engine. This guarantees that the Host Intrusion Prevention
engine sees requests in plain text and blocks malicious requests before they are processed.
HTTP signatures prevent directory traversal and Unicode attacks, web defacement, data theft,
and server hacking.
SQL engine for SQL servers
Host Intrusion Prevention protects against attacks on database servers with its SQL inspection
engine, which installs between database network libraries and the database engine. It examines
all SQL requests and blocks any that could trigger an event. SQL protection rules, which
differentiate on user, query origination location, query validity, and other parameters.
SQL database signatures build on the core protection provided by standard signatures and add
specific database interception and protection rules. The Host IPS SQL engine intercepts incoming
database queries before they are processed by the database engine. Each query is examined
to see whether it matches any known attack signatures, if it is well formed, and if there are
tell-tale signs of SQL injection.
Configuring IPS Policies
Overview of IPS policies
McAfee Host Intrusion Prevention 8.0 Product Guide for ePolicy Orchestrator 4.5
30