Well what I do with these systems and for the various on-line banks I've worked with, is...

A "Build Guide" documents the complete installation and configuration process used to create the "secure platform", including copies of all administration shell scripts, and step by step process of how it was built from scratch.  Appendices include outputs from "lslpp" and "lscfg" etc.

Once operating, there is the issue of "Change Control" to monitor and record changes made to configuration - adding new users, settings in config files, etc.  One of my special scripts, "copychk", holds a database of the critical files and reports differences.

On a daily basis a "heathcheck" script checks on the state of that "copychk" database and runs other standard AIX things: "lppchk", "usrck", "grpck", "pwdck", "tcbck" (requires the TCB to be installed), etc.

So in the event of disaster, not withstanding mirroring, complete system duplication etc, if having to re-build from the ground up, perhaps even on different hardware...

Follow the "Build Guide", copy in the critical file database and compare (part of the "copychk" function).

So I suggest what you need there on your "new" systems is at least a period of documentation for the set ups, before it's too late 

Mentioning "healthchecks" reminds me of another approach - TOPCAT2 COLA:

www.topcat2.com/HC (http://www.topcat2.com/HC)

- by invitation only, a means to essentially test your system, to generate an assessment of how your system matches up to best practices.