You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, incidents (both on the upload and scheduled scan) are logged in the server's logs.
However, if no access to the server logs is possible (using a hosted/cloud solution), it would be useful to have the incidents logged in the wiki, for admins to review.
Implementation ideas:
The simplest would be to send them an email whenever such an event occurs, similar to the emails sent by the scheduled scan
The more complex alternative is to keep a log of incidents (i.e. one page per incident) and then maybe display (as a livetable) it in administration (displayed or linked from), with the option to remove log entries when they are no longer useful.
An incident would record a type (upload / scheduled scan) and maybe an action as well (blocked / deleted / quarantined), together with other info, like the file name, location, upload date, last author.
The text was updated successfully, but these errors were encountered:
* Added a log of incidents (one per page) and displaying them in a livetable inside the Antivirus Administration section.
* Each incident can be viewed individually, deleted or all incidents can be deleted at once.
* Both upload and scheduled scans create an incident when a virus is detected and an action is performed on the infected attachment.
* Fixed CSRF handling for the delete operation in JavaScript
** Moved the CSRF token retrieval and dumped it in the HTML in order to retrieve it with JS, instead of caching it together with the JS.
* Minor improvements.
* Added a log of incidents (one per page) and displaying them in a livetable inside the Antivirus Administration section.
* Each incident can be viewed individually, deleted or all incidents can be deleted at once.
* Both upload and scheduled scans create an incident when a virus is detected and an action is performed on the infected attachment.
* Fixed test.
* Fixed CSRF handling for the delete operation in JavaScript
** Moved the CSRF token retrieval and dumped it in the HTML in order to retrieve it with JS, instead of caching it together with the JS.
* Minor improvements.
Currently, incidents (both on the upload and scheduled scan) are logged in the server's logs.
However, if no access to the server logs is possible (using a hosted/cloud solution), it would be useful to have the incidents logged in the wiki, for admins to review.
Implementation ideas:
The text was updated successfully, but these errors were encountered: