109 lines
7.4 KiB
HTML
109 lines
7.4 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 physical security for system documentation and storage media" />
|
||
|
|
<meta name="abstract" content="This topic describes the importance of securing important system documentation and storage media. Emphasis placed on storing these items in two locations, both on-site and offsite." />
|
||
|
|
<meta name="description" content="This topic describes the importance of securing important system documentation and storage media. Emphasis placed on storing these items in two locations, both on-site and offsite." />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzamvplanphysec.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzamvplanphysecsysunit.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzamvplanphystationsec.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="planphysecsysdoc" />
|
||
|
|
<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 physical security for system documentation and storage media</title>
|
||
|
|
</head>
|
||
|
|
<body id="planphysecsysdoc"><a name="planphysecsysdoc"><!-- --></a>
|
||
|
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
||
|
|
<h1 class="topictitle1">Plan physical security for system documentation and storage media</h1>
|
||
|
|
<div><p>This topic describes the importance of securing important
|
||
|
|
system documentation and storage media. Emphasis placed on storing these items
|
||
|
|
in two locations, both on-site and offsite. </p>
|
||
|
|
<p>System documentation includes information that IBM<sup>®</sup> sends with the system, password information,
|
||
|
|
your planning forms, and any reports that the system generates. Depending
|
||
|
|
on your system, backup media can include tapes, CD-ROMs, diskettes, or DVD
|
||
|
|
storage. You should store both system documentation and backup media at your
|
||
|
|
business location as well as at another remote location. In case of a disaster,
|
||
|
|
you will need this information to recover your system.</p>
|
||
|
|
<p><strong>Storing system documentation securely</strong></p>
|
||
|
|
<p>Service tools and security officer passwords are critical to the operation
|
||
|
|
of your system. You should write these passwords down and store them in a
|
||
|
|
safe, confidential location. In addition, keep a copy of these passwords at
|
||
|
|
an offsite location to help you recover from a disaster.</p>
|
||
|
|
<p>Consider storing other important system documentation, such configuration
|
||
|
|
settings and your main application libraries, away from your business location
|
||
|
|
to help you recover from a disaster.</p>
|
||
|
|
<p><strong>Storing your storage media securely</strong></p>
|
||
|
|
<p>When you install your system, make plans for regularly saving all the information
|
||
|
|
on the system to tape or other storage media. These backups allow you to recover
|
||
|
|
your system if necessary. You should keep these backups in a secure location
|
||
|
|
offsite as well.</p>
|
||
|
|
<p><strong>Risks related to backup media and password information</strong></p>
|
||
|
|
<ul><li>Damage to backup media: If a disaster or vandals destroyed your system
|
||
|
|
backup media, you could not recover the information that was on your system,
|
||
|
|
except from printed reports.</li>
|
||
|
|
<li>Theft of backup media or passwords: You may have confidential business
|
||
|
|
information saved on your backup media. A knowledgeable person might be able
|
||
|
|
to restore this information to another computer and print or process it.</li>
|
||
|
|
</ul>
|
||
|
|
<p><strong>What to do to keep your storage media and passwords secure</strong></p>
|
||
|
|
<p>The following information suggests ways to store your system documentation
|
||
|
|
and storage media. After you have decided on your method, record your choices
|
||
|
|
on the Backup Media and Documentation section of the <a href="rzamvphysecplanworksheet.htm#physecplanworksheet">Physical
|
||
|
|
Security Planning worksheet</a>:</p>
|
||
|
|
<ul><li>Store all passwords and backup media in a locked, fireproof cabinet.</li>
|
||
|
|
<li>Take copies of your backup media to a secure, offsite location on a regular
|
||
|
|
basis, for example, at least weekly.</li>
|
||
|
|
</ul>
|
||
|
|
<div class="section" id="planphysecsysdoc__backupmedia_example"><a name="planphysecsysdoc__backupmedia_example"><!-- --></a><h4 class="sectiontitle">Example: Physical security planning
|
||
|
|
form—backup media and documentation</h4>
|
||
|
|
<div class="tablenoborder"><table cellpadding="4" cellspacing="0" summary="" width="100%" frame="border" border="1" rules="all"><caption>Table 1. Physical Security Planning Form: Backup Media and Documentation</caption><thead align="left"><tr><th colspan="2" valign="top" id="d0e61">Backup Media and Documentation</th>
|
||
|
|
</tr>
|
||
|
|
</thead>
|
||
|
|
<tbody><tr><td valign="top" headers="d0e61 ">Where are backup tapes stored at your business location?</td>
|
||
|
|
<td valign="top" headers="d0e61 "><kbd class="userinput">In a fireproof safe.</kbd></td>
|
||
|
|
</tr>
|
||
|
|
<tr><td valign="top" headers="d0e61 ">Where are backup tapes stored away from your business
|
||
|
|
location?</td>
|
||
|
|
<td valign="top" headers="d0e61 "><kbd class="userinput">In a fireproof safe at the office of our
|
||
|
|
company's accountant.</kbd></td>
|
||
|
|
</tr>
|
||
|
|
<tr><td valign="top" headers="d0e61 ">Where are the security officer, service, and DST passwords
|
||
|
|
kept?</td>
|
||
|
|
<td valign="top" headers="d0e61 "><kbd class="userinput">In the manager's office.</kbd></td>
|
||
|
|
</tr>
|
||
|
|
<tr><td valign="top" headers="d0e61 ">Where is important system documentation, such as the
|
||
|
|
serial number and the configuration, kept?</td>
|
||
|
|
<td valign="top" headers="d0e61 "><kbd class="userinput">In a fireproof safe at the office of our
|
||
|
|
company's accountant.</kbd></td>
|
||
|
|
</tr>
|
||
|
|
</tbody>
|
||
|
|
</table>
|
||
|
|
</div>
|
||
|
|
<p>After you plan your storage and documentation security, you can
|
||
|
|
plan physical security for your workstations.</p>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
<div>
|
||
|
|
<div class="familylinks">
|
||
|
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="rzamvplanphysec.htm" title="This topic describes physical security, the key tasks for planning physical security, and explains why these tasks are important.">Plan physical security</a></div>
|
||
|
|
<div class="previouslink"><strong>Previous topic:</strong> <a href="rzamvplanphysecsysunit.htm" title="This topic discusses the importance of securing certain aspects of the system unit, such as the physical location, the control panel and keylock, and the Service Tools user ID and password.">Plan physical security for the system unit</a></div>
|
||
|
|
<div class="nextlink"><strong>Next topic:</strong> <a href="rzamvplanphystationsec.htm" title="This topic describes the security risks and recommendations for workstations.">Plan physical workstation security</a></div>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
</body>
|
||
|
|
</html>
|