Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Incidents log #9

Closed
Enygma2002 opened this issue Oct 19, 2018 · 1 comment
Assignees
Milestone

Comments

@Enygma2002
Copy link
Member

@Enygma2002 Enygma2002 commented Oct 19, 2018

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.
Enygma2002 added a commit that referenced this issue Nov 1, 2018
* 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.
Enygma2002 added a commit that referenced this issue Nov 1, 2018
* 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.
Enygma2002 added a commit that referenced this issue Nov 1, 2018
* 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.
Enygma2002 added a commit that referenced this issue Nov 1, 2018
* 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.
@Enygma2002 Enygma2002 self-assigned this Nov 1, 2018
@Enygma2002 Enygma2002 added this to the 1.1 milestone Nov 1, 2018
@Enygma2002

This comment has been minimized.

Copy link
Member Author

@Enygma2002 Enygma2002 commented Nov 1, 2018

  • Incidents Log section was added in the Administration section:
    antivirus-administration-incidentslog
  • Each incident can be inspected individually
    antivirus-incidentslog-incident
  • Each incident can be deleted individually
    antivirus-administration-incidentslog-delete
  • Or all incidents can be removed at once
    antivirus-administration-incidentslog-deleteall
@Enygma2002 Enygma2002 closed this Nov 1, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
1 participant
You can’t perform that action at this time.