audit_trailing
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
audit_trailing [2022/03/31 17:28] antreas [Notes on storage requirements] |
audit_trailing [2022/11/29 14:45] (current) yves |
||
|---|---|---|---|
| Line 1: | Line 1: | ||
| ====== Audit trailing ====== | ====== Audit trailing ====== | ||
| - | An **audit trail** (also called audit log) is a security-relevant chronological record, set of records, and/or destination and source of records that provide documentary evidence of the sequence of activities that have affected at any time a specific operation, procedure, event, or device. For PMA.core audit trailing is implemented as part of [[21_cfr_part_11|21 CFR.11]] | + | An **audit trail** (also called audit log) is a security-relevant chronological set of records that provide documentary evidence of the sequence of activities that have affected at any time a specific operation, procedure or event. In PMA.core audit trailing is implemented as part of [[21_cfr_part_11|21 CFR.11]] |
| + | |||
| + | A [[https://realdata.pathomation.com/audit-trailing/|background article on audit trailing can be found on our blog]]. | ||
| ==== How does it work? ==== | ==== How does it work? ==== | ||
| - | PMA.core implements audit trailing by implementing a middleware between the application and the connection to the SQL server database. That middleware catches all requests from the application to the database and depending on the operation creates records on a sub-schema of the database with all the required information to recreate them. | + | PMA.core implements audit trailing as a middleware between the application and the connection to the SQL server database. This middleware captures all requests from the application to the database and, depending on the operation, creates records on a sub-schema of the database with all the required information to recreate them. |
| The sub-schema of the audit trail database can be seen in the table diagram bellow | The sub-schema of the audit trail database can be seen in the table diagram bellow | ||
| Line 35: | Line 37: | ||
| ==== Notes on storage requirements ==== | ==== Notes on storage requirements ==== | ||
| - | Keeping an Audit trail of all changes happening in a live production PMA.core server can be quite space consuming you can always check all storage requirements of PMA.core in the [[installation_check#storage_checks|Diagnostics -> Installation Checks -> Storage Checks page]] | + | Keeping an Audit trail of all changes happening in a live production PMA.core server can be quite space consuming. You can always check all storage requirements of PMA.core in the [[installation_check#storage_checks|Diagnostics -> Installation Checks -> Storage Checks page]] |
| {{ :storage_checks.jpg?600 |}} | {{ :storage_checks.jpg?600 |}} | ||
| In that page you can check the total size of SQL database including the audit trail but also check other storages used such as the tile cache directory and the cloud cache | In that page you can check the total size of SQL database including the audit trail but also check other storages used such as the tile cache directory and the cloud cache | ||
audit_trailing.1648736923.txt.gz · Last modified: 2022/03/31 17:28 by antreas
