69 lines
4.2 KiB
HTML
69 lines
4.2 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="reference" />
|
||
|
|
<meta name="DC.Title" content="Auditing" />
|
||
|
|
<meta name="abstract" content="DB2 UDB for iSeries is designed to comply with the U.S. government C2 security level. A key feature of that level is the ability to audit actions on the system." />
|
||
|
|
<meta name="description" content="DB2 UDB for iSeries is designed to comply with the U.S. government C2 security level. A key feature of that level is the ability to audit actions on the system." />
|
||
|
|
<meta name="DC.subject" content="auditing, C2 security" />
|
||
|
|
<meta name="keywords" content="auditing, C2 security" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rbafysecurity.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="../books/sc415302.pdf" />
|
||
|
|
<meta name="copyright" content="(C) Copyright IBM Corporation 1998, 2006" />
|
||
|
|
<meta name="DC.Rights.Owner" content="(C) Copyright IBM Corporation 1998, 2006" />
|
||
|
|
<meta name="DC.Format" content="XHTML" />
|
||
|
|
<meta name="DC.Identifier" content="rbafyaudit" />
|
||
|
|
<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>Auditing</title>
|
||
|
|
</head>
|
||
|
|
<body id="rbafyaudit"><a name="rbafyaudit"><!-- --></a>
|
||
|
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
||
|
|
<h1 class="topictitle1">Auditing</h1>
|
||
|
|
<div><p><span class="keyword">DB2<sup>®</sup> UDB for iSeries™</span> is designed
|
||
|
|
to comply with the U.S. government C2 security level. A key feature of that
|
||
|
|
level is the ability to audit actions on the system. </p>
|
||
|
|
<div class="section"><p><span class="keyword">DB2 UDB for iSeries</span> uses the
|
||
|
|
audit facilities managed by the system security function. Auditing can be
|
||
|
|
performed on an object level, user, or system level. The system value QAUDCTL
|
||
|
|
controls whether auditing is performed at the object or user level. The Change
|
||
|
|
User Audit (CHGUSRAUD) command and Change Object Audit (CHGOBJAUD) command
|
||
|
|
specify which users and objects are audited. The system value QAUDLVL controls
|
||
|
|
what types of actions are audited (for example, authorization failures, creates,
|
||
|
|
deletes, grants, revokes, and so on.) </p>
|
||
|
|
</div>
|
||
|
|
<div class="section"><p><span class="keyword">DB2 UDB for iSeries</span> can also
|
||
|
|
audit row changes by using the <span class="keyword">DB2 UDB for iSeries</span> journal
|
||
|
|
support.</p>
|
||
|
|
</div>
|
||
|
|
<div class="section"><p>In some cases, entries in the auditing journal will not be in
|
||
|
|
the same order as they occured. For example, a job that is running under commitment
|
||
|
|
control deletes a table, creates a new table with the same name as the one
|
||
|
|
that was deleted, then does a commit. This will be recorded in the auditing
|
||
|
|
journal as a create followed by a delete. This is because objects that are
|
||
|
|
created are journaled immediately. An object that is deleted under commitment
|
||
|
|
control is hidden and not actually deleted until a commit is done. Once the
|
||
|
|
commit is done, the action is journaled.</p>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
<div>
|
||
|
|
<div class="familylinks">
|
||
|
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="rbafysecurity.htm" title="All objects on the server, including SQL objects, are managed by the system security function.">Security for SQL objects</a></div>
|
||
|
|
</div>
|
||
|
|
<div class="relinfo"><strong>Related information</strong><br />
|
||
|
|
<div><a href="../books/sc415302.pdf" target="_blank">iSeries Security Reference PDF</a></div>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
</body>
|
||
|
|
</html>
|