Notifications
Overview
Notifications are used to manage the notifications generated by activities, configuration changes, or system conditions that occur on the TAKAKRYPT platform. Through this feature, the administrator can determine the types of activities that will generate notifications, the priority level of the notifications, and the delivery method used.
Notifications Functions
Notifications serve to:
- Manage notifications based on activity categories.
- Set the severity level of a notification.
- Determine the notification delivery medium.
- Help monitor system activities and conditions more effectively.
Notifications Uses
Notifications can be used to:
- Obtain information when an activity occurs on the system.
- Monitor changes to configuration and security policies.
- Determine service conditions that require the administrator's attention.
- Support the operational and maintenance processes of the system.
- Assist the process of auditing activities that occur on the platform.
Notification Categories
TAKAKRYPT provides various notification categories that cover a number of events of two types. Events of the Configurable type can be set and adjusted by the administrator as needed. Meanwhile, events of the Automatic type are fully managed by the system and will be triggered automatically based on certain activities or conditions without requiring configuration from the administrator.
The following is an explanation of the notification categories:
Backup Recovery
Notifications related to the system backup and recovery process, such as:
- Backup completed successfully
- Backup encryption failed
- Backup failed
- Backup paused
- Backup retention expired
- Backup scheduled
- Backup started
- Backup storage quota reached
- Manual restore initiated
- Restore failed
- Restore initiated (scheduled)
- Restore successfully
Compliance Audit Trail
Notifications related to audit and compliance activities, such as:
- Audit log exported
- Audit log tampering detected
- SIEM integration failed
Integration API Activity
Notifications related to API usage and activity, such as:
- Agent connection lost
- Agent registered
- Token refresh failed
- Unauthorized integration attempt
Key Lifecycle Management
Notifications related to the management of cryptographic keys, such as:
- API Key nearing expiration
- Function created
- Function deleted permanently
- Function updated
- Key Versioning disabled
- Key Versioning enabled
- Key rotated successfully
- Key rotation failed
- Key rotation scheduled
- Key usage spike detected
- Restored successfully
- Rotation overdue
Network Connectivity
Notifications related to network connectivity and communication between services, such as:
- TLS certificate expired
- TLS certificate expiring soon
Operational Maintenance
Notifications related to operational activities and system maintenance, such as:
- Log file size exceeds threshold
Security Access Control
Notifications related to security and access control, such as:
- API Key expired
- Access from new IP/location
- Access revoked
- Account locked
- Administrator account deletion
- Failed authentication (single)
- MFA failed
- Multiple failed login attempts
- Policy modified
- Role privilege escalation
- Session hijacking detected
- Unauthorized API call
- Unauthorized access attempt
- User access change
System Health Performance
Notifications related to the condition and performance of the system, such as:
- Cluster sync error
- Disk space low
- Service down
- Service restarted
User Role Management
Notifications related to the management of users and roles, such as:
- Failed password attempts threshold exceeded
- MFA enabled
- MFA enrollment/disabled
- New user created
- Password changed
- Role assigned/changed
- User deleted
Notification Configuration Components
Each notification category can be configured through the following parameters:
1. Event
Determines the activity or occurrence that will generate a notification.
2. Severity Level
Determines the level of a notification based on its impact on system operations and security.
The available severity levels include:
- Critical: Indicates a critical condition that requires immediate handling because it could potentially cause serious disruption to the system.
- High: Indicates an event that requires attention and action in the near term.
- Medium: Indicates an event with a moderate impact that needs to be monitored and followed up on as needed.
- Low: Indicates information or an event with a low impact that is informative in nature.
3. Delivery Channel
Determines the medium used to deliver notifications to users or administrators.
TAKAKRYPT provides several notification delivery channels, namely:
- Dashboard: Notifications are displayed directly on the application dashboard so that they can be monitored by users who have access.
- Email: Notifications are sent via email to the recipient address that has been previously configured.
4. Status
Determines whether a notification is in an active or inactive state.