Appendix A: Glossary
issuer keyring | The keyring used by the SG appliance to sign emulated certificates. The keyring is |
| configured on the appliance and managed through policy. |
L |
|
licensable component (LC) | (Software) A subcomponent of a license; it is an option that enables or disables a |
| specific feature. |
license | Provides both the right and the ability to use certain software functions within an AV |
| (or SG) appliance. The license key defines and controls the license, which is owned |
| by an account. |
listener | The service that is listening on a specific port. A listener can be identified by any |
| destination IP/subnet and port range. Multiple listeners can be added to each |
| service. |
live content | Also called live broadcast. Used in streaming, it indicates that the content is being |
| delivered fresh. |
LKF | License key file. |
load balancing | A way to share traffic requests among multiple upstream systems or multiple IP |
| addresses on a single host. |
local bypass list | A list you create and maintain on your network. You can use a local bypass list alone |
| or in conjunction with a central bypass list. See bypass list. |
local policy file | Written by enterprises (as opposed to the central policy file written by Blue Coat); |
| used to create company- and |
| Blue Coat Policy Language (CPL). |
log facility | A separate log that contains a single logical file and supports a single log format. It |
| also contains the file’s configuration and upload schedule information as well as |
| other configurable information such as how often to rotate (switch to a new log) the |
| logs at the destination, any passwords needed, and the point at which the facility can |
| be uploaded. |
log format | The type of log that is used: NCSA/Common, SQUID, ELFF, SurfControl, or |
| Websense. |
| The proprietary log types each have a corresponding |
| been set up to produce exactly that type of log (these logs cannot be edited). In |
| addition, a number of other ELFF type log formats are also |
| p2p, ssl, streaming). These can be edited, but they start out with a useful set of log |
| fields for logging particular protocols understood by the SG appliance. It is also |
| possible to create new log formats of type ELFF or Custom which can contain any |
| desired combination of log fields. |
log tail | The access log tail shows the log entries as they get logged. With high traffic on the |
| SG appliance, not all access log entries are necessarily displayed. However, you can |
| view all access log information after uploading the log. |
M |
|
MACH5 | SGOS 5 MACH5 Edition. |
97