88 lines
8.9 KiB
HTML
88 lines
8.9 KiB
HTML
|
<?xml version="1.0" encoding="UTF-8"?>
|
||
|
|
<!DOCTYPE html
|
||
|
|
PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
|
||
|
|
<html lang="en-us" xml:lang="en-us">
|
||
|
|
<head>
|
||
|
|
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
|
||
|
|
<meta name="security" content="public" />
|
||
|
|
<meta name="Robots" content="index,follow" />
|
||
|
|
<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' />
|
||
|
|
<meta name="DC.Type" content="concept" />
|
||
|
|
<meta name="DC.Title" content="Plan network security" />
|
||
|
|
<meta name="abstract" content="When connecting to an untrusted network, your security policy must describe a comprehensive security scheme, including the security measures that you will implement at the network level." />
|
||
|
|
<meta name="description" content="When connecting to an untrusted network, your security policy must describe a comprehensive security scheme, including the security measures that you will implement at the network level." />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzamvplansecstrat.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzamvplannetattributes.htm" />
|
||
|
|
<meta name="copyright" content="(C) Copyright IBM Corporation 2006" />
|
||
|
|
<meta name="DC.Rights.Owner" content="(C) Copyright IBM Corporation 2006" />
|
||
|
|
<meta name="DC.Format" content="XHTML" />
|
||
|
|
<meta name="DC.Identifier" content="plannetsec" />
|
||
|
|
<meta name="DC.Language" content="en-us" />
|
||
|
|
<!-- All rights reserved. Licensed Materials Property of IBM -->
|
||
|
|
<!-- US Government Users Restricted Rights -->
|
||
|
|
<!-- Use, duplication or disclosure restricted by -->
|
||
|
|
<!-- GSA ADP Schedule Contract with IBM Corp. -->
|
||
|
|
<link rel="stylesheet" type="text/css" href="./ibmdita.css" />
|
||
|
|
<link rel="stylesheet" type="text/css" href="./ic.css" />
|
||
|
|
<title>Plan network security</title>
|
||
|
|
</head>
|
||
|
|
<body id="plannetsec"><a name="plannetsec"><!-- --></a>
|
||
|
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
||
|
|
<h1 class="topictitle1">Plan network security</h1>
|
||
|
|
<div><p>When connecting to an untrusted network, your security policy must describe a comprehensive security scheme, including the security measures that you will implement at the network level.</p>
|
||
|
|
<p>Installing a firewall is one of the best means of deploying a comprehensive set of network security measures. Also, your Internet Service Provider (ISP) can and should provide an important element in your network security plan. Your network security scheme should outline what security measures your Internet Service Provider (ISP) will provide, such as filtering rules for the ISP router connection and public Domain Name Service (DNS) precautions. Continue to check with your ISP periodically to ensure they are continually upgrading their security measures, this will also help you keep your security plans current.</p>
|
||
|
|
<p>Although a firewall certainly represents one of your main lines of defense in your total security plan, it should not be your only line of defense. Because Internet security risks occur at a variety of levels, you need to set up security measures that provide multiple layers of defense against these risks.</p>
|
||
|
|
<p>While a firewall provides a tremendous amount of protection from certain kinds of attack, a firewall is only part of your total security solution. For instance, a firewall cannot necessarily protect data that you send over the Internet through applications such as SMTP mail, FTP, and TELNET. Unless you choose to encrypt this data, anyone on the Internet can access it as it travels to its destination.</p>
|
||
|
|
<p><span class="uicontrol">Choosing network security options</span></p>
|
||
|
|
<p> Network security solutions that guard against unauthorized access generally rely on firewall technologies to provide the protection. To protect your system, you can choose to use a full-capability firewall product or you can choose to put into effect specific network security technologies as part of the i5/OS™ TCP/IP implementation. This implementation consists of the Packet rules feature, which includes IP filtering and NAT, and the HTTP for iSeries™ proxy server feature.</p>
|
||
|
|
<p>Choosing to use either the Packet rules feature or a firewall depends on your network environment, access requirements, and security needs. You should strongly consider using a firewall product as your main line of defense whenever you connect your system or your internal network to the Internet or other untrusted network. </p>
|
||
|
|
<p>A firewall is preferable in this case because a firewall typically is a dedicated hardware and software device with a limited number of interfaces for external access. When you use the i5/OS TCP/IP technologies for Internet access protection you are using a general purpose computing platform with a myriad number of interfaces and applications open to external access.</p>
|
||
|
|
<p>The difference is important for a number of reasons. For example, a dedicated firewall product does not provide any other functions or applications beyond those that comprise the firewall itself. Consequently, if an attacker successfully circumvents the firewall and gains access to the system, the attacker can not do much. Whereas, if an attacker circumvents the TCP/IP security functions on your system, the attacker potentially could have access to a variety of useful applications, services, and data. The attacker can then use these to wreck havoc on the system itself or to gain access to other systems in your internal network.</p>
|
||
|
|
<div class="p">So, is it ever acceptable to use the TCP/IP security features? As with all the security choices that you make, you must base your decision on the cost versus benefit trade-offs that you are willing to make. You must analyze your business goals and decide what risks you are willing to accept versus the cost of how you provide security to minimize these risks. The following table provides information about when it is appropriate to use TCP/IP security features versus a fully functional firewall device. You can use this table to determine whether you should use a firewall, TCP/IP security features, or a combination of both to provide your network and system protection.
|
||
|
|
<div class="tablenoborder"><table cellpadding="4" cellspacing="0" summary="" frame="border" border="1" rules="all"><thead align="left"><tr valign="bottom"><th valign="bottom" id="d0e47">Security technology</th>
|
||
|
|
<th valign="bottom" id="d0e49">Best use of i5/OS TCP/IP technology</th>
|
||
|
|
<th valign="bottom" id="d0e54">Best use of a fully functional firewall</th>
|
||
|
|
</tr>
|
||
|
|
</thead>
|
||
|
|
<tbody><tr><td valign="top" headers="d0e47 ">IP packet filtering</td>
|
||
|
|
<td valign="top" headers="d0e49 "><ul><li>To provide additional protection for a single system, such as a public web server or an intranet system with sensitive data.</li>
|
||
|
|
<li>To protect a subnetwork of a corporate intranet when the system is acting as a gateway (casual router) to the rest of the network.</li>
|
||
|
|
<li>To control communication with a somewhat trusted partner over a private network or extranet where the system is acting as a gateway.</li>
|
||
|
|
</ul>
|
||
|
|
</td>
|
||
|
|
<td valign="top" headers="d0e54 "><ul><li>To protect an entire corporate network from the Internet or other untrusted network to which your network is connected.</li>
|
||
|
|
<li>To protect a large subnetwork with heavy traffic from the remainder of a corporate network. </li>
|
||
|
|
</ul>
|
||
|
|
</td>
|
||
|
|
</tr>
|
||
|
|
<tr><td valign="top" headers="d0e47 ">Network Address Translation (NAT) </td>
|
||
|
|
<td valign="top" headers="d0e49 "><ul><li>To enable the connection of two private networks with incompatible addressing structures. </li>
|
||
|
|
<li>To hide addresses in a subnetwork from a less trusted network. </li>
|
||
|
|
</ul>
|
||
|
|
</td>
|
||
|
|
<td valign="top" headers="d0e54 "><ul><li>To hide addresses of clients accessing the Internet or other untrusted network. To use as an alternative to Proxy and SOCKS servers.</li>
|
||
|
|
<li>To make services of a system in a private network available to clients on the Internet.</li>
|
||
|
|
</ul>
|
||
|
|
</td>
|
||
|
|
</tr>
|
||
|
|
<tr><td valign="top" headers="d0e47 ">Proxy server </td>
|
||
|
|
<td valign="top" headers="d0e49 ">To proxy at remote locations in a corporate network when a central firewall provides access to the Internet.</td>
|
||
|
|
<td valign="top" headers="d0e54 ">To proxy an entire corporate network when accessing the Internet.</td>
|
||
|
|
</tr>
|
||
|
|
</tbody>
|
||
|
|
</table>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
<div>
|
||
|
|
<ul class="ullinks">
|
||
|
|
<li class="ulchildlink"><strong><a href="rzamvplannetattributes.htm">Plan network attributes</a></strong><br />
|
||
|
|
If you have primarily NetWare servers on your network, you can simplify working with those servers by changing default values on a system-wide basis.</li>
|
||
|
|
</ul>
|
||
|
|
|
||
|
|
<div class="familylinks">
|
||
|
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="rzamvplansecstrat.htm" title="This topic describes various aspects of planning a security strategy.">Plan your security strategy</a></div>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
</body>
|
||
|
|
</html>
|