
Advisor Usage and Maintenance
161
no
vd
ocx
(e
n)
7 Ja
nua
ry 201
0
To enable exploit detection, the Sentinel Collectors must populate several variables as expected.
Collectors built by Novell populate these variables by default.
In intrusion detection systems and vulnerability Collectors, the RV31 (DeviceName) variable
in the event must be set to the value in the RV31 column in
Table 8-1
. This string is case
sensitive.
In the intrusion detection systems Collector, the DIP (Destination or Target IP) must be
populated with the IP address of the machine that is being attacked.
In the intrusion detection systems Collector, RT1 (DeviceAttackName) must be set to the attack
name or attack code for that intrusion detection system.
In the intrusion detection systems and vulnerability Collectors, RV39 (MSSPCustomerName)
value must be populated. For a standard corporation, the value can be anything. For a Managed
Security Service Provider (MSSP), the customer name should be set for the individual
customer. For either type of company, the value in the intrusion detection systems Collector
must exactly match with the value in the vulnerability Collector.
These values are used by the Mapping Service to populate the VULN field in the event. This value is
used to evaluate the incoming events to determine whether a vulnerability is exploited or not. When
the vulnerability field (VULN) equals 1, the asset or destination device is exploited. If the
vulnerability field equals 0, the asset or destination device is not exploited.
ISS RealSecure Network
IDS
XForce
ISS RealSecure Server
IDS
XForce
ISS RealSecure Guard
IDS
XForce
Sourcefire* Snort*/Phalanx
IDS
Snort
Symantec* Network Security 4.0
(ManHunt*)
IDS
ManHunt
Symantec Intruder Alert
IDS
Intruder
McAfee* IntruShield*
IDS
IntruShield
TippingPoint* IPS
TippingPoint
eEYE* Retina*
VULN
Retina
Foundstone* Foundscan*
VULN
Foundstone
ISS Database Scanner
VULN
XForce
ISS Internet Scanner
VULN
XForce
ISS System Scanner
VULN
XForce
ISS Wireless Scanner
VULN
XForce
Nessus*
VULN
Nessus
nCircle IP360*
VULN
nCircle IP360
Qualys* QualysGuard*
VULN
QualysGuard
Cisco IOS Firewall
FW
Secure
Supported Products
Device Type
RV31 Value
Содержание SENTINEL 6.1 SP2
Страница 4: ...4 Sentinel 6 1 User Guide novdocx en 7 January 2010 ...
Страница 20: ...20 Sentinel 6 1 User Guide novdocx en 7 January 2010 ...
Страница 34: ...34 Sentinel 6 1 User Guide novdocx en 7 January 2010 ...
Страница 57: ...Active Views Tab 57 novdocx en 7 January 2010 Figure 2 7 Organic View Figure 2 8 Hierarchical View ...
Страница 97: ...Incidents Tab 97 novdocx en 7 January 2010 Sort By You can set rules to sort the incidents in the display view ...
Страница 116: ...116 Sentinel 6 1 User Guide novdocx en 7 January 2010 Integer Variable String Variable ...
Страница 146: ...146 Sentinel 6 1 User Guide novdocx en 7 January 2010 ...
Страница 172: ...172 Sentinel 6 1 User Guide novdocx en 7 January 2010 ...
Страница 178: ...178 Sentinel 6 1 User Guide novdocx en 7 January 2010 ...
Страница 280: ...280 Sentinel 6 1 User Guide novdocx en 7 January 2010 ...
Страница 306: ...306 Sentinel 6 1 User Guide novdocx en 7 January 2010 ...
Страница 329: ...Quick Start 329 novdocx en 7 January 2010 ...
Страница 330: ...330 Sentinel 6 1 User Guide novdocx en 7 January 2010 ...
Страница 401: ...Sentinel Link Solution 401 novdocx en 7 January 2010 3 Select the Novell Sentinel Link Collector then click Next ...
Страница 405: ...Sentinel Link Solution 405 novdocx en 7 January 2010 6 In the Configure Connector window specify the following ...
Страница 412: ...412 Sentinel 6 1 User Guide novdocx en 7 January 2010 ...
Страница 430: ...430 Sentinel 6 1 User Guide novdocx en 7 January 2010 ...
Страница 440: ...440 Sentinel 6 1 User Guide novdocx en 7 January 2010 Figure 18 3 Reports ...
Страница 528: ...528 Sentinel 6 1 User Guide novdocx en 7 January 2010 ...