Protecting and/or tracking changes to log files

[bschmidt]

Hello,

Please see the question below from our customer. There are a few ways we can log data with ctrlX including Codesys libraries, InfluxDB, DeviceBridge, but how to lock out the log file or track changes? 

We have a number of customers that require datalogging for the oven, with the ability to pull this data via batches and export to printable reports.  The big issue is that with AMS2750 (an aerospace heat treating standard that we need to comply with), is that the data needs to be not modifiable, or have an audit trail to indicate if a record has been modified.  We’ve seen multiple ways to do this by different vendors, either with a fully encrypted datalog file, and a modifiable csv saved alongside, with an audit viewer, which lists changes made, or a csv file with checksum file which indicates if the original was modified.

What options are available for the CtrlX for this?  Is influx DB the best way to log the information?  Is this modifiable or not?  If yes, is there an audit trail, or way of knowing if data has been modified?  What’s the best way to export this data to a csv file or report for customer use?

Best regards,

Brian

[TheCodeCaptain · Accepted solution]

Hi bschmidt,

I think the question is more if you would like to store such important data on an edge device.

Our ctrlX CORE would be the right device to collect all the values.

It security certified, so no one, which has not the rights, can access it. Additionally we have a Telegraf app which can send the data signed and encrypted to a database.

From my point the influxdb can be the right database for such a time series. It should maybe hosted in some safe environment like a small or bigger datacenter, which can also be on premise at your customer. Influxdb itself has aswell some user management which defines who is allowed to do what.

Would be interesting what your solution is at the end.

Regards

Codecaptain