Oracle SBC Security Guide
become trusted through SIP registration. The untrusted-signal-threshold value should be confirmed by
collecting and analyzing a packet capture from the targeted network deployment. In many cases a
registration will be two or three messages, but endpoint behavior and requirements vary. When this
threshold is exceeded, the endpoint will be placed on the denied list for the amount of time defined in the
deny-period. This period should be determined based on your individual needs. Setting the deny period to
a long duration may cause problems for endpoints that simply entered an incorrect password or had a
connection issue with some packet loss.
The following parameters should also be customized to your needs based on expected call flows.
realm-config
identifier access
description Serving all access endpoints
.
.
.
access-control-trust-level low
invalid-signal-threshold 1
maximum-signal-threshold 4000
untrusted-signal-threshold 5
nat-trust-threshold 0
deny-period 120
Configure the media-manager settings per the recommendations in the DDoS prevention appendix that is
applicable for your architecture. The max-untrusted-signaling parameter will limit the amount of
untrusted traffic the SBC will process.
If any media-manager settings are changed you MUST save, activate, and reboot the SBC so they will
take effect.
Peering Environments
As noted earlier, this appendix does not focus on scanning attacks in SIP Peering environments. In these
environments it is recommended to create static ACLs with a trust level appropriate for the peer. It is
recommended when peering over a trusted network, such as an MPLS connection delivered from a
service provider, that a “high” trust level should be used. If your trust in the peer is not assured, it may be
appropriate to set trust level to “medium” or “low” so they will be limited or blacklisted for abuse. Keep
in mind that signaling thresholds will then need to be set on the realm.
The realm-config, access-control-trust-level should match the trust-level of the ACL so that all traffic
from any endpoint that does not have an ACL will be denied. Always make sure that the realm-id, source-
address, destination-address, and application-protocol are specified.
realm-config
identifier peer
description
addr-prefix 172.16.101.6
.
.
.
access-control-trust-level high
Comentarios a estos manuales