File Integrity Monitoring on AIX for Money Transfer System

[Reggie]

We are running Prognosis 11.8 on AIX Server for Money Transfer system.  I am looking for a File Inegrity Monitor specification for the AIX server.  I have found the MS-Windows version.  This clearly states what to exclude, but not so clear what to include in File Monitoring.

[Scott_Clement]

Hi @Reggie,

There are a lot of similarities across the different platforms and the Linux/Unix equivalent would be close to the following:

Executables: 

• $PROGNOSIS_HOME/server
• Key Configurations
• $PROGNOSIS_HOME/server/configuration/*.ini
• $PROGNOSIS_HOME/server/configuration/license
• $PROGNOSIS_HOME/server/configuration/solutions/*.* and subfolders
• $PROGNOSIS_HOME/server/configuration/defssrv
• $PROGNOSIS_HOME/server/configuration/udefssrv

Scripts:

Scripting is used extensively. The scripts themselves should only ever change with an official release.

• *.pl across all subfolders  
• *.pm across all subfolders
• *.js across all subfolders
• *.json across all subfolders
• *.sh across all subfolders

Exclusions 

In the $PROGNOSIS_HOME/server/configuration folder:

All identified log files as described in the Local Log Files.

• *.log
• *.txt
• avsfmap
• avsfmapl
• avpers/
• confdb
• confdb.dir/*
• confpro
• confpro.dir/*
• cpqimhev.tmp
• dsthist
• f00*
• gfdbdet
• ir*.log*
• ir*.pid
• LASTDAY.taf
• LicenseAnalyst
• prgn*.bak
• prgn*.dld
• s00*
• ssafmap
• ssafmapl
• MTS/*.txt
• MTS/*.tmp
• MTS/*.log.lock

All Database folders:

• $PROGNOSIS_HOME/server/configuration/Capacity Planning
• $PROGNOSIS_HOME/server/configuration/Trouble Shooting
• Any other configured database collections

I've removed most of the Windows specific entries I could identify and added some attitional exceptions for MTS. 

I hope this helps!

Regards,

Scott