52 lines
4.6 KiB
HTML
52 lines
4.6 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="Wireless LAN communications" />
|
|||
|
|
<meta name="abstract" content="Some clients might use the iSeries Wireless LAN to communicate to your system without wires." />
|
|||
|
|
<meta name="description" content="Some clients might use the iSeries Wireless LAN to communicate to your system without wires." />
|
|||
|
|
<meta name="DC.Relation" scheme="URI" content="rzamvsecstation.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="reswirelesslan" />
|
|||
|
|
<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>Wireless LAN communications</title>
|
|||
|
|
</head>
|
|||
|
|
<body id="reswirelesslan"><a name="reswirelesslan"><!-- --></a>
|
|||
|
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
|||
|
|
<h1 class="topictitle1">Wireless LAN communications</h1>
|
|||
|
|
<div><p>Some clients might use the iSeries™ Wireless LAN to communicate to your system without wires.</p>
|
|||
|
|
<div class="p">The system's wireless LAN uses radio-frequency communications technology. As a security administrator, you should be aware of the following security characteristics of system wireless LAN products:<ul><li>These wireless LAN products use spread spectrum technology. This same technology has been used by the government in the past to secure radio transmissions. To someone who attempts to electronically monitor for data transmissions, the transmissions appear to be noise rather than an actual transmission.</li>
|
|||
|
|
<li>The wireless connection has three security-relevant configuration parameters:<ul><li>Data rate (two possible data rates)</li>
|
|||
|
|
<li>Frequency (five possible frequencies)</li>
|
|||
|
|
<li>System identifier (8 million possible identifiers)</li>
|
|||
|
|
</ul>
|
|||
|
|
These configuration elements combine to provide 80 million possible configurations, which makes a hacker’s likelihood of guessing the correct configuration extremely slim.</li>
|
|||
|
|
<li>Just like with other communications methods, the security of wireless communications is affected by the security of the client device. The system ID information and other configuration parameters are in a file on the client device and should be protected.</li>
|
|||
|
|
<li>If a wireless device is lost or stolen, normal server security measures, such as signon passwords and object security, provide protection when an unauthorized user attempts to use the lost or stolen unit to access your system.</li>
|
|||
|
|
<li>If a wireless client unit is lost or stolen, you should consider changing the system ID information for all users, access points, and systems. Think of this as changing the locks on your doors if a set of keys is stolen.</li>
|
|||
|
|
<li>You might want to partition your server into groups of clients that have unique system IDs. This limits the impact if a unit is lost or stolen. This method works only if you can confine a group of users to a specific portion of your installation.</li>
|
|||
|
|
<li>Unlike wired LAN technology, wireless LAN technology is proprietary. Therefore, no electronic sniffers are publicly available for these wireless LAN products. A sniffer is an electronic device that performs unauthorized monitoring of a transmission.</li>
|
|||
|
|
</ul>
|
|||
|
|
</div>
|
|||
|
|
</div>
|
|||
|
|
<div>
|
|||
|
|
<div class="familylinks">
|
|||
|
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="rzamvsecstation.htm" title="After you secure printer output, you should secure your workstations. You authorize workstations just like you authorize other objects on the system. Use the EDTOBJAUT command to give users authority to workstations.">Secure your workstations</a></div>
|
|||
|
|
</div>
|
|||
|
|
</div>
|
|||
|
|
</body>
|
|||
|
|
</html>
|