
Oracle SBC Security Guide
NN 6300 724k CAM 16G memory – copper single GigE
access-control-trust-level
untrusted-signal-threshold
access-control-trust-level
untrusted-signal-threshold
Observations/Limitations
The settings outlined in this appendix are beneficial when facing malicious attacks from any unknown
sources; this is a typical concern when deploying peering traffic on the public Internet. Setting access-
control-trust-level to “high” in both peer realm and an ACL (access-control) will yield an
implicit deny scenario where traffic from unknown source IP addresses will be silently discarded at the
hardware level in order to protect both the SBC’s host CPU and core devices from being attacked. The
design of this configuration is not to prevent cases where malicious attacks are generated behind the
trusted source IP within peer’s network, since all traffic from peer is consider as “trusted”. Therefore, the
SBC will forward all traffic from trusted sources to the core network as allowed by the system’s hardware
or software capabilities. There is no demotion event when access-control-trust-level at realm
is set “high” as packets from trusted peer endpoint are always allocated the trusted queue for processing.
An alternative DDoS prevention practice in peering is to set access-control-trust-level to
“medium”, but this type of configuration requires settings of “max-untrusted-signaling”,
“min-untrusted-signaling” and “maximum-signal-threshold”, which vary greatly
Komentáře k této Příručce