Obi
Checks all security-related file attributes of executables on a regular basis and reports any changes.
Overview
OBI — Guardian
Nowadays auditors demand data integrity checks: changes of critical files have to be reported on a regular basis. The most important critical files are program files (executables). OBI checks all security related file attributes of executables on a regular basis, and reports the changes. Critical security related changes get additional highlighting.
Checked file attributes include the last modification time stamp, EOF, file code, primary owner (*), license (*), ProgID (*), SQL-type, file type, Max EXT, clear on purge, RWEP, audit, broken, corrupt, number of alternate keys, proc callable, high PIN, high requestors, run named, executable, priv logon (*), trust (*), fingerprint (SWID, OBIHash, or MD5) and library name. (*) marks critical security attributes.
The basic version of OBI reports the changes to the OUT file, e.g. the SPOOLER. User written ENFORM queries can be used to produce additional customized reports. Customers using the management GUI iWAMS-TALIS can make use of an OBI module, which allows an intuitive evaluation of the OBI data base and reporting in the form of PDF documents.
OBI — OSS
OBIOSS checks all security related file attributes on a regular basis, and reports the changes. Checked attributes include type, md5, ossfilename, guardianfilename, mode, link, uid, gid, basemode, specialfile, size, accesstime, modificationtime and lastchangetime.