Security Basics mailing list archives

RE: Administrator's Journal


From: "Chris Curtiss" <chrisc () VistaPrint com>
Date: Thu, 13 May 2004 11:47:05 -0400

Two and a half years ago I implemented a scoop (http://scoop.kuro5hin.org) system for my company, with a particular 
focus on IT/OPS, but with differernt sections for different departments should they want to use the system.  Certain 
sections are only accessibly by logged in users of a certain group, others are all-access.  So you can have a 
departmental bull-session corner that the rest of the world doesn't need to see.

Scoop is a very customizable application, I've added read-only access to certain directories on our fileserver and 
appropriate filesystem navigation pages, so you can link to a PDF easily for intance, or browse a shared software 
library.

The Scoop app was a bit ahead of its time, not that many people really used it at the time, except to check up for 
information regarding production outage windows and upcoming maintenance events.

It has been supplanted company-wide with a system running Drupal (http://www.drupal.org) running on Windows 2000.  This 
seems to have many of the same features and filesharing capabilities that I've added into my Scoop install, with the 
added benefit that people use it more.  It was launched as more of a "Blog" system, so people go there and chit chat 
about whatever.  The Scoop server is still in use for all the tools that were integrated over time, and for a certain 
amount of Operations project scheduling.

Check them both out, they're both nice systems.



-----Original Message-----
From: Jeff [mailto:Jeff@Not_A_Real_Address.com]
Sent: Monday, May 10, 2004 11:52 AM
To: security-basics () securityfocus com
Subject: Administrator's Journal


Not certain where else to send this ... but am open to suggestions.

In the past I have kept paper journals about everything that has
been done to a specific machine; date setup, software installed,
passwords for iLO etc., OS patches installed, app patches installed,
configuration changes.

If nothing else, it's been tedious and as a result, often incomplete.
It is very easy to "tweak and run". Later, while trying to remember
why you, (or worse, was it you or someone else) made the change, you
vow again to document better.

Is anyone aware of "Administrator's Journal" software? I would love
to be able to document on a much better scale the who, what, where,
when and how of install/changes, including the ability to add
attachments like the pdf of how to install the application change
or a link to a web page that documents what was done.

Thanks,

Jeff





--------------------------------------------------------------
-------------
Ethical Hacking at the InfoSec Institute. Mention this ad and 
get $545 off 
any course! All of our class sizes are guaranteed to be 10 
students or less 
to facilitate one-on-one interaction with one of our expert 
instructors. 
Attend a course taught by an expert instructor with years of 
in-the-field 
pen testing experience in our state of the art hacking lab. 
Master the skills 
of an Ethical Hacker to better assess the security of your 
organization. 
Visit us at: 
http://www.infosecinstitute.com/courses/ethical_hacking_training.html
--------------------------------------------------------------
--------------



---------------------------------------------------------------------------
Ethical Hacking at the InfoSec Institute. Mention this ad and get $545 off
any course! All of our class sizes are guaranteed to be 10 students or less
to facilitate one-on-one interaction with one of our expert instructors.
Attend a course taught by an expert instructor with years of in-the-field
pen testing experience in our state of the art hacking lab. Master the skills
of an Ethical Hacker to better assess the security of your organization.
Visit us at:
http://www.infosecinstitute.com/courses/ethical_hacking_training.html
----------------------------------------------------------------------------


Current thread: