Reporting is a vital part of Mentat system. Currently there are following two types of reporting implemented:
- Event reporting
Periodical reports generated for each abuse group and severity.
- Statistical reporting
Periodical informational reports about overall performance of Mentat system.
Event reporting feature is implemented within the mentat-reporter.py module. This module is intended to enable distribution of events in the form of periodical reports to appropriate users. These users are mostly administrators within networks for which the Mentat system has relevant data.
Currently Mentat system supports following types of event reports:
This type of report contains all relevant data for particular network formated neatly into one email.
This type of report contains all relevant data for particular network formated neatly into one email, but regarding only single IP address. This type can be prefered in case respondents are using some kind of ticket system and want to resolve the issues separately for each host. This means, that when there are 10 events regarding 10 different hosts, this will produce 10 separate email reports.
All report emails sent by Mentat mentat-reporter.py have following common features:
Report message in human readable format.
Various custom email headers to enable automated processing and filtering.
Attachment files containing raw data of all reported events, possibly in various formats.
Metadata summary in report footer.
The human readable message organizes reported events into sections containing events grouped according some internal classification. For example each detector may describe SSH bruteforce attack with different IDEA message. Mentat attempts to classify these messages into the same class and display them in the same section. The report message however attempts to keep things as simple as possible and be as brief as possible, so only source address, event time window and event count are displayed in the table in each section. For more information about the possible problem you have to look into the attached file containing raw data (or download it from the server).
Report emails contain following usefull headers, that can be used for automated report processing and filtering:
Please note the deprecation of some of the email headers from previous version of Mentat mentat-reporter.py and their new names.
Class of the current report. For periodical event reports this header has fixed value
Unique report identifier.
In previous version of Mentat mentat-reporter.py this header was called X-Cesnet-Report-Id. This should now be considered deprecated and you should not use it anymore, support for old header will be removed in one of the future versions.
Unique identifier of parent summary report for
Type of the current event report. It can contain one of the following values:
In previous version of Mentat mentat-reporter.py this header was called X-Cesnet-Report-Type. This should now be considered deprecated and you should not use it anymore, support for old header will be removed in one of the future versions.
Severity of the current report. It can contain one of the following values:
In previous version of Mentat mentat-reporter.py this header was called X-Cesnet-Report-Severity. This should now be considered deprecated and you should not use it anymore, support for old header will be removed in one of the future versions.
This header contains IP adress appropriate for
In previous version of Mentat mentat-reporter.py this header was called X-Cesnet-Report-Srcip. This should now be considered deprecated and you should not use it anymore, support for old header will be removed in one of the future versions.
Total number of events reported in current..ehm…report.
Time window for current report as two timestamps in ISO 8601 format (YYYY-MM-DDTHH:MM:SS) concatenated by
Flag indicating whether this report contains test or experimental data. It can contain one of the following values:
Report always contains either only experimental, or only production data, there can never be a mix of any kind. When this value is set to
True, you may safely ignore current report in production environment.
Report emails may contain multiple attachments containing raw event data. Currently JSON and CSV attachments are supported. We strongly recommend users to use only JSON attachments, because they contain complete event data. CSV is a flat format with many limitations and events exported into this format are shortened and do not contain all available data. This feature should be considered as deprecated, it is kept only for compatibility purposes and it will be removed in one of the future versions. Please use only JSON attachments.
Report detail in web interface¶
All generated reports are stored on the server and accessible for the registered users. Accessing the reports via web interface provides users with additional options and features.
Work in progress.
Reporting customization for users¶
Work in progress.
Reporting configuration for administrators¶
By default the reporter is configured to prevent from unwanted spamming of target abuse contacts. This is great for initial deployment I you have to make extra effort to really start sending emails. Please continue reading for more details.
Most important configuration files and directories related to reporting:
Common application configurations. Pay attention to
mail_settings, because they can override the reporting settings for abuse groups set in database. This approach is designed to prevent a recently installed Mentat system from spamming real world abuse contacts. So by default all reports are redirected to local
To enable reporting in production environments it is necessary to disable the
mail_tosetting in this file and to enforce
mail_to: nullin the main
Common reporting configurations. Contains paths to templates,
template_varsobject with data supplied to reporting templates.
Main configuration file of reporting component. Tweak this configuration file to customize the bahaviour of the reporting module itself. The most interesting options are customizations of various report email headers and report template customizations. Currently used convention uses names like following for classess:
Important: to enable reporting in production environment it is necesssary to set
mail_to: nullin this file and to disable its default value (
/etc/mentat/core/common.json.confconfiguration file (see above). Otherwise each report will be forcefully redirected to local
rootto prevent Mentat system from spamming abuse contacts.
Main configuration file for classifying instance of mentat-inspector.py module (in default installation). Rules contained in this file attempt to perform advanced event classification based on the event attributes. This classification can be then used for queries in web user interface and to organize events in generated reports to logically similar classes.
Jinja2 template defining content of summary event reports. This template is used when rendering summary event reports. It is completely localized, so it can be easily translated to additional languages. It is prepared for minor tweaks. For bigger content adjustments you have to create your own template and select it with
Jinja2 template defining content of extra event reports. This template is used when rendering summary event reports. It is completely localized, so it can be easily translated to additional languages. It is prepared for minor tweaks. For bigger content adjustments you have to create your own template and select it with
Directory containing subdirectories with information for every defined event class. Location of directory can be set with
/etc/mentat/core/reporting.json.conf. Name of subdirectory have to match the name of event class. It can contain files
hawat.j2and files for babel translations.
info.jsonshould contain root json object with
referencekeys that are supplied to reporting templates.
rowthat fill tables in email and hawat reports. For more information check guideline below. At least directory for default class have to exist. It supply information and macros for unknown classes and classes without its respective definitions. Its name can be set as
When you want to define your custom event class for reporting proceed according to following steps:
Tag event with new class using the mentat-inspector.py module. This means, that in default installation you have to edit configuration file
/etc/mentat/mentat-inspector.py.confand append new rule into the list of existing
inspection_rules. Restart inspector.
Create subdirectory in
/etc/mentat/event_classes/with same name as rule and in it create files
info.jsonpaste json object with
labelkey that contains short description of class and
referencekey that contains link to longer description. If file or any of keys does not exist data are supplied from default class.
row(key, data, additional_vars).
additional_varsis object containing data from
keycontains key for which data are aggregated (in current implementation it contains ip) and
datacontains that data (for its current structure see method
mentat/reports/event.pyin directory where mentat is installed). If file or any of macros does not exist macros are supplied from default class.
macro row(key, data, is_authenticated, dafault_class).
datacontains same data like in
dafault_classcontains name of default class that is set as
is_authenticatedcontains information about user log in status to system.
Following steps are required if you are using internationalization and are also required if you are adding new language:
If you are adding classes in git repository, change working directory to its root. If you are adding in installed instance, activate venv by running
. /var/mentat/venv/bin/activateand change directory to folder with your hawat installation. You can locate it by running
python3 -c "import hawat; import os.path; print(os.path.dirname(hawat.__file__))". If you changed default installation paths, you also need to change them in Makefile.
make cpybabel-init INIT_LOCALE=lcwhere lc is code of your locales.
Add translations to
make cpybabel-compile. Restart your hawat instance if you are adding to installed system.
If you changed data for existing event class run
make cpybabel-update, update your
messages.pofile and run