well, file integrity/permissions and malware scan can be triggered also automatically. What I am mainly missing is to initialize the database remotely after the (bulk) update. Each update changes/modifies the file which are the reported in file integrity scan results until I initialize each database and run the scan to set up the baseline again.
You should not have to initialize the database on every scan. If you need to do that then you must increase the memory_limit (a php directive) or enable the "scan only executable files' to reduce the amount of memory needed.
I am not sure I am getting you. The integrity scan after any update naturally find a bunch of integrity deviations (updated files, newly added files). Is there any way how to set up the new baseline for integrity scan other than re-initializing the database?
Ok, I thought the file integrity scanner didn't end after launching a new scan. That's what I name as "Initialize Database" in Securitycheck Pro (this is, all data is deleted and a new baseline is created).
But if file integrity works fine you don't need to do that. If you set launching a file integrity in Cron every day all the info will be shown in Control Center after launching a "Refresh info" task (manually or using Cron).