1) Is your SQL DB available to the world, or only to select users? IIS can configure each website to accept/reject a packet based on the IP address or IP domain name. This can provide a firewall-like capability, *IN ADDITION* to an existing firewall.
2) Are your web users known ahead of time, and have (or could have) NT logon accounts? Then you can configure IIS to require authentication before allowing access to a website. This would require the NT username/password.
In IIS right click on the website, select properties, select directory security tab, press the "edit" button for anonymous access..... Challenge/response is the most secure, but only works with MS IE.
3) If you can use NT authentication on your website, thenyou can also configure SQL 7.0 to accept the NT authentication from the website. Once the user is authenticated by the website, her credentials can be used to satisfy access controls within SQL.
Good luck,
Jerry