22.12.2012 Views

Front cover - IBM Redbooks

Front cover - IBM Redbooks

Front cover - IBM Redbooks

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.

5.7 Summary<br />

186 Lotus Security Handbook<br />

name, resulting in processing overhead on the server. Unless there are security<br />

or logging reasons for doing so, this option should generally be turned off.<br />

Log and monitor your proxy<br />

Proxy servers are generally deployed in external zones, which leaves them open<br />

to an increased level of attack from would-be hackers. Therefore, you should<br />

regularly log and monitor your proxy systems.<br />

Keep up with the latest system patches<br />

While we understand internal deployment complexities and timing issues, having<br />

a security product installed at anything less than the latest available patch/level is<br />

an open invitation to get in trouble. There is no point in spending money<br />

maintaining sub-standard security. While you can use it to prevent certain<br />

mistakes, there is no such thing as half-secure. Malicious hackers have access<br />

to the same information about known vulnerabilities that the rest of us have, and<br />

they are quick to exploit them.<br />

In this chapter, we have introduced the concept of proxy servers, and described<br />

the various types of proxies utilized in current computing infrastructures. We then<br />

focused on the reverse proxy concepts, as reverse proxies provide a key building<br />

block for creating multi-zoned secure environments. Various considerations and<br />

hints were then provided for implementing reverse proxies with <strong>IBM</strong> and Lotus<br />

technologies.<br />

The reverse proxy concept is used later in this redbook, in Part 4, “A secure<br />

scenario” on page 579, to help build a secure environment for a fictitious<br />

company.

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

Saved successfully!

Ooh no, something went wrong!