There are many files that are placed in the Bugzilla directory area that should not be accessible from the web. Because of the way Bugzilla is currently layed out, the list of what should and should not be accessible is rather complicated. A quick way is to run testserver.pl to check if your web server serves Bugzilla files as expected. If not, you may want to follow the few steps below.
In the main Bugzilla directory, you should:
Block: *.pl, *localconfig*, runtests.sh
But allow: localconfig.js, localconfig.rdf
But allow: duplicates.rdf
If you use a remote webdot server:
But allow *.dot only for the remote webdot server
Otherwise, if you use a local GraphViz:
But allow: *.png, *.gif, *.jpg, *.map
And if you don't use any dot:
Be sure to test that data that should not be accessed remotely is properly blocked. Of particular interest is the localconfig file which contains your database password. Also, be aware that many editors create temporary and backup files in the working directory and that those should also not be accessible. For more information, see bug 186383 or Bugtraq ID 6501. To test, simply run testserver.pl, as said above.
Be sure to check Section 2.2.4 for instructions specific to the web server you use.
This section only applies to people who have chosen the Apache webserver. It may be possible to do similar things with other webservers. Consult the documentation that came with your webserver to find out.
It is possible for a user, by mistake or on purpose, to access the database many times in a row which can result in very slow access speeds for other users (effectively, a DOS attack). If your Bugzilla installation is experiencing this problem, you may install the Apache module mod_throttle which can limit connections by IP address. You may download this module at http://www.snert.com/Software/mod_throttle/. Follow the instructions to install into your Apache install. The command you need is ThrottleClientIP. See the documentation for more information.