RedMax EXtreme EX-LRT Guía para resolver problemas Pagina 65

  • Descarga
  • Añadir a mis manuales
  • Imprimir
  • Pagina
    / 142
  • Tabla de contenidos
  • SOLUCIÓN DE PROBLEMAS
  • MARCADORES
  • Valorado. / 5. Basado en revisión del cliente
Vista de pagina 64
Oracle SBC Security Guide
Some customers have asked about using the “reject” action in HMRs to send a “677 Rogue” response
rather than routing to a dummy session agent. However, the “reject” action is evaluated immediately, and
therefore is not affected by the sip-interface dropResponse parameter so the attacker will receive many
more responses than you intend.
Configuration for C-series (Net-Net 3000, 4000, and 6000 series)
Inbound SIP Manipulation Rule
An inbound SIP Manipulation Rule needs to be created to modify any messages that contain a User-
Agent header that is known (or suspected) to be fraudulent. The manipulation rule will add a Route
header that directs the message to a “dummy” Session Agent.
Two rule examples are given. The first one identifies fraudulent User-Agent values, and the second
whitelists only the desired User-Agent values and denies all others.
NOTES
The list of User-Agents in the match-value shown in the example should be entered without
spaces between the pipe symbols. There is an extra space for formatting.
Release S-CX6.2.0 and greater allows you to log attack messages to the /ramdrv/logs/matched.log
file if you wish. Simply change the store action in the isScanner rule to log.
If you already have inbound sip-manipulations the header rules identified in the examples below
can be added to them.
WARNING
If you have valid users of Counterpath Eyebeam in your environment then you should delete the
final “|eyeBeam” string from the match-value below.
Identifying fraudulent User-Agent values
In this HMR, the first header-rule uses a logical OR and performs a regular expression match on multiple
known User-Agent values. If any of these partial matches is found then the value is stored. The second
rule checks to see if the first rule stored a value, and inserts the Route header if it did.
sip-manipulation
name AddRoutHdr
description
split-headers
join-headers
header-rule
name isScanner
header-name User-Agent
action store
comparison-type pattern-rule
msg-type any
methods
match-value friendly|sundayddr|SIPScan|
smap|sipsak|sipcli|sipv|
VaxIPUserAgent|eyeBeam
new-value
header-rule
name addNullRoute
header-name Route
Vista de pagina 64
1 2 ... 60 61 62 63 64 65 66 67 68 69 70 ... 141 142

Comentarios a estos manuales

Sin comentarios