From owner-svn-doc-all@freebsd.org Sun Oct 23 22:02:08 2016 Return-Path: Delivered-To: svn-doc-all@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 854E7C1E622; Sun, 23 Oct 2016 22:02:08 +0000 (UTC) (envelope-from bjk@FreeBSD.org) Received: from repo.freebsd.org (repo.freebsd.org [IPv6:2610:1c1:1:6068::e6a:0]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 465BF794; Sun, 23 Oct 2016 22:02:08 +0000 (UTC) (envelope-from bjk@FreeBSD.org) Received: from repo.freebsd.org ([127.0.1.37]) by repo.freebsd.org (8.15.2/8.15.2) with ESMTP id u9NM27EF087084; Sun, 23 Oct 2016 22:02:07 GMT (envelope-from bjk@FreeBSD.org) Received: (from bjk@localhost) by repo.freebsd.org (8.15.2/8.15.2/Submit) id u9NM27Lv087083; Sun, 23 Oct 2016 22:02:07 GMT (envelope-from bjk@FreeBSD.org) Message-Id: <201610232202.u9NM27Lv087083@repo.freebsd.org> X-Authentication-Warning: repo.freebsd.org: bjk set sender to bjk@FreeBSD.org using -f From: Benjamin Kaduk Date: Sun, 23 Oct 2016 22:02:07 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r49551 - head/en_US.ISO8859-1/htdocs/news/status X-SVN-Group: doc-head MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-BeenThere: svn-doc-all@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "SVN commit messages for the entire doc trees \(except for " user" , " projects" , and " translations" \)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 23 Oct 2016 22:02:08 -0000 Author: bjk Date: Sun Oct 23 22:02:07 2016 New Revision: 49551 URL: https://svnweb.freebsd.org/changeset/doc/49551 Log: Add audit log conversion entry from Mateusz Piotrow Modified: head/en_US.ISO8859-1/htdocs/news/status/report-2016-07-2016-09.xml Modified: head/en_US.ISO8859-1/htdocs/news/status/report-2016-07-2016-09.xml ============================================================================== --- head/en_US.ISO8859-1/htdocs/news/status/report-2016-07-2016-09.xml Sun Oct 23 21:12:52 2016 (r49550) +++ head/en_US.ISO8859-1/htdocs/news/status/report-2016-07-2016-09.xml Sun Oct 23 22:02:07 2016 (r49551) @@ -560,4 +560,63 @@ Continue working on unstable releases. + + + Non-BSM to BSM Conversion Tools + + + + + Mateusz + Piotrowski + + 0mp@FreeBSD.org + + + + + Wiki Page + GitHub Repository + Pull Request With Consolidated Patch + + + +

This project was started during Google Summer of Code this year. + The aim was to create a library which can convert the audit trail + files in Linux Audit format or the format used by Windows to the BSM + format (the format &os; uses for its audit logs). Apart from that, + I wanted to create a simple command-line tool and extend + auditdistd so that it is possible to send non-BSM logs to + auditdistd over a secure connection and save those audit + logs on disk, preferably in the BSM format.

+ +

So far, it is possible to reasonably convert some of the most + common Linux audit log events to BSM, but it still needs a lot of + work. Secondly, I was able to configure auditdistd to + communicate with CentOS over an insecure connection. Thirdly, the + command-line tool is usable but not perfect.

+ +

The present work focuses on configuring the secure TLS connection + between CentOS and auditdistd. I've already tried using + rsyslogd but wasn't able to make it work.

+ + + + Google Summer of Code + + + + I need more examples of rare Linux Audit logs; please send me + some examples if you have any. It is much easier to improve the + conversion process with real-life examples of the audit events you + try to convert. + + Configure auditdistd to be able to communicate with some + software on CentOS over TLS in order to receive audit logs. I + wasn't able to come up with a simple solution for that. + + Additional open tasks are listed on the Wiki page and in the + TODO file in the root directory of the project. + +