13.07.2015 Views

Administering Websense Databases, v7.6.x and 7.7.x

Administering Websense Databases, v7.6.x and 7.7.x

Administering Websense Databases, v7.6.x and 7.7.x

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

<strong>Administering</strong> <strong>Websense</strong> <strong>Databases</strong>Email Security sizing factorsHybrid serviceThe <strong>Websense</strong> Email Security Gateway hybrid service drops email that comes fromknown bad (blacklisted) sources <strong>and</strong> blocks email with a very high spam score in thecloud before it ever reaches the Email Security Gateway appliance. This reduces theamount of data stored in the Email Security Log Database for reporting by 30 MB peruser per month.Above average email traffic: recipients, quarantined messages, orspamThe sizing guidelines above are based on the following assumptions about the emailtraffic h<strong>and</strong>led by Email Security Gateway. These assumptions are derived from theaverage email traffic pattern of <strong>Websense</strong> customers over time.There are an average of 5 recipients for each email message.When hybrid service is not enabled, the ratio among spam messages, infectedmessages, <strong>and</strong> clean messages is 85-to-1-to-14.The hybrid service scans only inbound email traffic, <strong>and</strong> it can block 25 percent ofspam.All outbound <strong>and</strong> internal email messages are clean.Note that Email Security counts the number of recipients for each message rather thanthe number of messages sent. Each recipient is counted as a transaction.If the pattern of email traffic in your organization exceeds these averages, your storagecapacity will vary.Data Security sizing factorsNumber of discovery incidents<strong>Websense</strong> Data Security limits the number of discovery incidents that can be stored inthe Data Security Incident <strong>and</strong> Configuration Database in order to prevent improperlyconfigured discovery policies from flooding the database. By default this limit is set to1 million incidents. If you are using SQL Server Express, you should reduce thisnumber to 250 thous<strong>and</strong>.To do this:1. Log onto TRITON Console.2. Select the Data Security tab.3. Select Settings > General > System.4. Select the Reporting option from the System pane.5. Select the Discovery tab.6. Adjust the Maximum Discovery Incidents field.<strong>Administering</strong> <strong>Websense</strong> <strong>Databases</strong> 19

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!