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

  • 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 27
Oracle SBC Security Guide
authorization response. If TACACS+ grants authorization, the pending command is executed; if
authorization is not granted, the SBC does not execute the ACLI command, and displays an appropriate
error message.
All management stations used for SSH access should have a permit ACL configured. An ACL should also
be configured to allow TACACS+ traffic to the Network Access Server. TACACS+ is disabled by
default.
Refer to “TACACS+ AAA” in Section 2 Getting Started” of the ACLI Configuration Guide.
Configuring Signaling & Media Interface Security
Securing the service interfaces is perhaps the most important consideration as they are typically deployed
in public unsecure networks and these interfaces are usually the demarcation or access point to the core
network infrastructure.
Signaling/Media Management Functions
The phy-card is intended for signaling and media traffic only. The SBC disables ICMP, telnet, SNMP and
FTP on signaling/media interfaces by default. It is not recommended that any of these protocols be
enabled on a service interface for any length of time beyond that required for troubleshooting purposes.
Configuration is detailed in Section 3 “System Configuration” of the ACLI Configuration Guide.
SIP Interface Security
As well as the layer3 ACLs described earlier, the SBC provides layer5 SIP protection to its signaling
interfaces. By default, the SBC sip-interface > sip-port parameter will allow and route signaling from any
device.
For Access/untrusted networks, the sip-interface > sip-port > allow-anonymous setting should be
configured to one of the following values:
registered: This is the most widely deployed setting, only allowing non-REGISTER SIP requests
from either a defined session-agent or a previously registered device. (All REGISTER requests
are processed.)
realm-prefix: Allows SIP requests only from defined session-agents or previously registered
endpoints. Only REGISTER requests from endpoints within the configured realm-prefix (subnet)
are allowed.
Although this feature will deny service to a malicious user, the SIP daemon and hence the core CPU is
utilized to parse and process each and every request; therefore, this feature is recommended to be
deployed in conjunction with the Net-SAFE architecture.
SIP-interfaces communicating with non-registering devices (e.g. peering partner SBCs or core devices
such as softswitches) should have the allow-anonymous setting configured for agents-only.
An Enforcement Profile should be configured with the list of allowable SIP methods. It is recommended
that only the minimum set of SIP methods necessary for the customer application be configured.
Furthermore in S-C6.1.0, added protection is configurable in Access scenarios where SIP endpoints are
sending SUBSCRIBE dialogs. The rate of these messages can be limited per user.
Vista de pagina 27
1 2 ... 23 24 25 26 27 28 29 30 31 32 33 ... 141 142

Comentarios a estos manuales

Sin comentarios