Media content
Key Benefits
Incident Registry
A single registry: date and location of the event, description, incident classification and type, indicators, responsible person, reported by and registered by, impact, actions taken and additional measures, current status. Main report file and additional attachments. Classification, type, and current status with country-specific translations.
Incident Lifecycle
From registration to closure: current status (open, in progress, closed) from a directory with translations. Record the impact, actions taken, and recommendations to prevent recurrence. Comments and files for audit and analysis.
Export & Emails
Export the incident registry to Excel for reporting and analytics. Send emails using a template (for groups with the appropriate permission); retrieve a list of company users to select recipients.
Directories & Access
Incident classification, type, and current status with country-specific translations. Guide for the registry with translations and AI-powered translation support. Access by groups and companies; separate permissions for viewing, adding, editing, deleting, and sending emails.
Features & Capabilities
Incident Registry
- List of incidents: company, event date, location, classification, type, current status
- Add, view, edit, and delete incidents
- Incident card: description, indicators, responsible person, reported by and registered by, dates
- Impact, actions taken, and additional measures to prevent recurrence
- Reports and records, comment
- Main report file and additional attachments; file deletion
- Registry export to Excel
Classification & Type
- Incident classification: name, code, description with country-specific translations
- Incident type: name, code, description with translations
- Colors for displaying classification and type
Current Status
- Directory of current statuses: open, in progress, closed, etc.
- Display current status in the incident list and card
Files & Emails
- Main report file in the incident record
- Additional attachments (multiple files per incident)
- Email template and sending emails (for users with the permission)
Guide & Access
- Guide for the incident registry with basic content
- Access by user groups and company list
- Permissions: view, add, edit, delete, send emails
Use Cases
Incident Registration and Tracking
Record information security incidents: date and location, description, classification, and type from directories with translations. Specify the person responsible for handling, who reported and who registered, the impact, and actions taken. Add a main report file and additional attachments. Update the current status (open, in progress, closed) as the investigation progresses. Export the registry to Excel for reporting.
Investigation and Prevention of Recurrence
In the incident card, store the actions taken and additional measures to prevent recurrence. Supplement reports and records, impact, and comments. Manage the current status to track progress. Files and change history assist with audits and root cause analysis.
Sending Emails and Communication
Users with email sending permission can use an email template to send messages (e.g., incident-related notifications). A list of company users is available for selecting recipients. Emails are sent via the project's configured mail account.
Access Restriction by Company
Access to the incident registry is configured by user groups; each group is assigned a list of companies — users only see incidents from those companies. Separate permissions are set for adding, editing, deleting, and sending emails. The module link on the homepage can be hidden for groups without access.
Localization of Directories and Guide
Incident classification, type, and current status have country-specific translations — users see the names in their selected language. The incident registry guide also has country-specific translations and optional AI-powered translation for populating content in new languages.
Technical Details
Architecture
Incident registry module: directories for classification, incident type, and current status with country-specific translations. Incident record registry with company, event date and location, description, classification, type, current status, responsible person, reported by/registered by, impact, measures, and comment. Main file in the record and additional attachments (separate file records). Guide with translations and translation API. Emails via the project's mail configuration. Data in the project database.
Security
Access is managed by user groups and a company list — users only see incidents from allowed companies. Separate permissions: view, add, edit, delete, send emails. Permission checks when viewing, editing, and sending emails. CSRF protection and input validation. Files are stored in the project's storage with access restrictions.
Scalability
Incident list with pagination and filtering; queries use eager loading of related data. Excel export is handled within a typical request. Suitable for standard project deployment.
Customization
Incident classification, type, and current status with code, color, and country-specific translations. Guide with basic content and translations; optional AI-powered translation. Email sending via a configured mail account.
Frequently Asked Questions
Classification is the category of the incident (e.g., security breach, data leak), and type is the specific kind of event within that category. Both directories have a name, code, description, and country-specific translations. They help standardize recording and filter incidents in the registry.
The current status shows the stage of incident handling: for example, open, in progress, closed. Values are taken from a directory with country-specific translations. Changing the status helps track progress and closed cases.
Yes. An incident record has a main report file and the ability to add additional attachments. Each additional file is stored separately; they can be deleted from the incident card. Files are stored in the project's storage with access restricted by module permissions.
Users with email sending permission have access to an email template and the send function. They can select recipients from a list of company users. Emails are sent via the project's configured mail account. This feature is intended for incident-related communication (e.g., notifying responsible parties).
The module provides an export of the incident registry in Excel format. The exported data respects the user's access rights (only incidents from allowed companies). The file can be used for reporting and analytics.
Access is configured by user groups. Each group is assigned a list of companies — users can only see and work with incidents from those companies. Separate permissions are set for adding, editing, deleting, and sending emails. The option to show the module link on the homepage is also controlled by group permissions.
Yes. The incident registry includes a guide with basic content and country-specific translations. AI-powered translation of the guide's content is available for quickly adding new languages.
Related Modules
Ready to Get Started?
Explore this module and enhance your organization's security posture