From owner-p4-projects@FreeBSD.ORG Sat Aug 2 10:38:34 2003 Return-Path: Delivered-To: p4-projects@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 32767) id D927737B404; Sat, 2 Aug 2003 10:38:33 -0700 (PDT) Delivered-To: perforce@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 909BE37B401 for ; Sat, 2 Aug 2003 10:38:33 -0700 (PDT) Received: from repoman.freebsd.org (repoman.freebsd.org [216.136.204.115]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0861C43F85 for ; Sat, 2 Aug 2003 10:38:33 -0700 (PDT) (envelope-from bb+lists.freebsd.perforce@cyrus.watson.org) Received: from repoman.freebsd.org (localhost [127.0.0.1]) by repoman.freebsd.org (8.12.6/8.12.6) with ESMTP id h72HcW0U018572 for ; Sat, 2 Aug 2003 10:38:32 -0700 (PDT) (envelope-from bb+lists.freebsd.perforce@cyrus.watson.org) Received: (from perforce@localhost) by repoman.freebsd.org (8.12.6/8.12.6/Submit) id h72HcW4P018569 for perforce@freebsd.org; Sat, 2 Aug 2003 10:38:32 -0700 (PDT) Date: Sat, 2 Aug 2003 10:38:32 -0700 (PDT) Message-Id: <200308021738.h72HcW4P018569@repoman.freebsd.org> X-Authentication-Warning: repoman.freebsd.org: perforce set sender to bb+lists.freebsd.perforce@cyrus.watson.org using -f From: Robert Watson To: Perforce Change Reviews Subject: PERFORCE change 35400 for review X-BeenThere: p4-projects@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: p4 projects tree changes List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 02 Aug 2003 17:38:35 -0000 http://perforce.freebsd.org/chv.cgi?CH=35400 Change 35400 by rwatson@rwatson_paprika on 2003/08/02 10:37:38 Expand on the distinctions between the various periodic events and their relationship. Also document security-relevant activities by the other periodic events (daily, weekly, monthly). Affected files ... .. //depot/projects/trustedbsd/doc/en_US.ISO8859-1/books/developers-handbook/secarch/chapter.sgml#5 edit Differences ... ==== //depot/projects/trustedbsd/doc/en_US.ISO8859-1/books/developers-handbook/secarch/chapter.sgml#5 (text+ko) ==== @@ -2726,11 +2726,16 @@ Daily Security Event - The daily security event, executed once a day by the - system daily event, checks a variety of system security - properties, and generates a report that may be e-mailed to - the administrator, or sent to a file. - This report is intended to make it easier for administrators + FreeBSD executes a series of periodic maintenance events at + regular intervals: a daily event, daily security event, weekly + event, and monthly event. + These events check system configuration and usage activities, + and report on the activities to the system administrator by + e-mail, or to a file. + A number of elements of these events, especially the daily + security event, report on changes in security-relevent + configuration and activities. + These reports are intended to make it easier for administrators to track security-related changes to the system, such as the addition or modification of users, changes to the file system namespace, events relating to the password @@ -2741,7 +2746,16 @@ of compromised systems, as they provide some basic tripwire functionality, as well as long term tracking of system configuration. - The following activities are performed by the daily + The following security-relevent activities are performed + by the daily event: + + + Diff the password and group databases against + the previous days backups; back up these databases for + future comparison and restore. + + + The following activities are performed by the daily security event: @@ -2770,6 +2784,15 @@ Report on any logged TCP wrapper failures. + + The following security-relevent activities are performed + by the weekly event: + + + Report on files with an unknown user or + group (owner not present in password or group database). + +