
9: Device Settings
Rule creation and
editing
Spiders come from the factory with one rule defined as an example
of the rule structure: Rule 1 allows all groups access from source IP
0.0.0.0 to 255.255.255.255. Additional rules may be entered in the
edit boxes. The
Rule Number
defines where in the evaluation
sequence this rule is to be applied. The
Starting
and
Ending IP
Addresses
define the range over which the rule applies. The
Group
defines which user group is affected by this rule. Built-in
groups include Admin, All, and Unknown (no group assigned.) As
additional groups are defined in User Management
Æ
Users
Æ
Group Management, these will appear in the pull-down. A rule can
apply to only one group at a time. The
Action
selection chooses
whether this is to be a Drop or Accept rule.
After a rule has been defined, it needs to be put in the correct place
in the list.
Append
will put the rule at the end of the list. The rule
number will be changed to reflect the last position on the list.
Insert
will put the rule in the place on the list indicated by the rule number,
renumbering and moving down the other rules to make room.
Replace
deletes the previous rule of that number, and replaces it
with the new rule.
Delete
deletes the rule of that number, and
moves the others up. Note that for a Delete the fields other than the
rule number do not need to be filled in.
Login Limitations
Enable Single
Login Limitation
If this box is checked, each username may only have one logged in
connection at a time. If unchecked, multiple instances of username
logins are allowed.
3. Click
Apply
to save settings. Click
Reset to Def
to restore system defaults.
Certificate
The Spider uses the Secure Socket Layer (SSL) protocol for any encrypted network
traffic between itself and a connected client. During the connection establishment the
Spider has to expose its identity to a client using a cryptographic certificate. Upon leaving
the factory this certificate and the underlying secret key is the same for all Spiders and
will not match the network configuration where it is installed. The certificate’s underlying
secret key is also used for securing the SSL handshake.
It is possible to generate and install a new base64 x.509 certificate that is unique for a
particular Spider. The Spider is able to generate a new cryptographic key and the
associated Certificate Signing Request (CSR) that needs to be certified by a certification
authority (CA).
To create and install a SSL certificate:
1. Select
Device Settings
Æ
Certificate
from the Main Menu. The Certificate Signing
Request window displays.
SecureLinx Spider User Guide
43