A
PPENDIX
D: P
ROFILE
F
ORMAT
AND
R
ULES
F
ILE
F
ORMAT
: R
ULES
AND
E
XAMPLES
266
M86 S
ECURITY
U
SER
G
UIDE
•
profile for a user with username “Public\, Joe Q.”, organi-
zational units “Users” and “Sales”, domain “qc”, DNS
suffix “.local”: Block all ports, use minimum filtering level,
use filter mode 1, use standard block page, enable all
filter options.
Group profile list format
Here is an example of a group profile entry in an ldapgroup-
profile.conf file:
CN=Sales, CN=Users, DC=qc, DC=local; Rule1, 1,
http://www.cnn.com, 0x1
NOTE
: The DN format must contain the group name—and, if
applicable—user group "CN" ("common name") attribute type,
and the domain and DNS suffix "DC" ("domain component")
attribute type. The "OU" ("organizational unit") attribute type also
can be included. Each attribute type should be followed by an
equals sign (=), and separated by a comma (,).
When translated, this string of code means:
•
profile for group with ID “Sales”, user group “Users”,
domain “qc”, DNS suffix “.local”: Bypass all categories,
use filter mode 1, use redirect URL http://www.cnn.com
in place
of the standard block page, no filter options
enabled.
Container profile list format
A container profile entry in an ldapcontainerprofile.conf file
will be similar to entries made in workstation, user, and
group profile files, however the Distinguished Name will be
slightly different, based on how containers are set up in your
organization.
