User Guide

Planning for security 17
Breeze web server
Breeze comes with its own built-in, high-performance, secure web server. This web server is based
in part on Macromedia JRun Enterprise Server and has been designed specifically to serve
dynamic content for Breeze, including Breeze Meetings, Breeze Presentations, Breeze Seminars,
and other rich media content. Because of Breeze’s special requirements, no other web servers (such
as Apache) can be used with Breeze.
Database server security
Whether or not you are hosting your database on the same server as Breeze, you must make sure
that your database is secure. Computers hosting a database should be in a physically secure
location. Additional precautions include the following:
• Install the database in the secure zone of your organization’s intranet.
• Never connect the database directly to the Internet.
• Back up all data regularly and store copies in a secure off-site location.
The Microsoft security website contains information that applies to both securing SQL
Server 2000 and the embedded database engine: www.microsoft.com/sql/techinfo/
administration/2000/security/.
The following link provides a good starting point to making sure that your database is secure:
www.microsoft.com/sql/techinfo/administration/2000/security/securingsqlserver.asp.
Note: Macromedia Breeze supports SQL authentication only. You must install SQL Server with
mixed-mode authentication. Breeze does not support Windows Authentication Mode.
If you are running the embedded database engine, the database uses breeze as the password by
default. You should change this password after you install Breeze and verify that all its applications
are functioning. To change the password, type the following at the command line:
osql -E -Q "sp_password @new = 'new_password', @loginame = 'sa'"
where {new_password} is a strong password.
Solutions for a secure infrastructure
Most Breeze configurations fall into one of two configurations:
• A single-server configuration
• A multiple-server configuration (a cluster)
This section discusses both configurations and provides examples on how to secure
these environments.