Engine UX

[asteriscos]

Parent issue: wazuh/wazuh#23577

Description

This epic focuses on enhancing the user experience (UX) for configuring the engine, customizing rules/decoders with a wizard to guide users, relating decoders and rules, and providing a usable interface for viewing the history of an alert and all its associated elements. These improvements aim to make the system more intuitive, user-friendly, and efficient.

Functional Requirements

• Configuration management: Provide an intuitive interface for engine configuration changes, allowing users to easily adjust settings.
• Security policy management: Implement features to relate decoders and rules clearly, providing a comprehensive view of how events are processed and alerts are generated.
• KVDBs management: Provide a user interface to handle all KVDBs configurations.
• Dashboards and queries: Design a user-friendly interface to view the history of an alert, including all associated elements and their interactions, to facilitate better understanding and analysis.
• CTI Management: Provide an interface to handle CTI client.

Implementation Restrictions

• Each of the features mentioned above must be implemented as a stand-alone plugin.
• These plugins must use I18n for all the UI texts, so they can be translated to other languages.
• All plugins must use the same visual language, layout, and navigation, so they provide a coherent experience.
• The UI must be responsive for different viewport sizes
• The features of these plugins must be able to be restricted by the user role (RBAC). Define roles by default.

Plan

1. Design Phase:

   • Create prototypes for the new UX features:
     • POC engine UX - engine configuration management #215
     • POC engine UX - security policy management #216
     • POC engine UX - KVDBs management #217
     • POC engine UX - dashboards and queries #218
     • POC engine UX - CTI client management #219
   • Review WCS data model compliance with the requested features.
   • Validate designs with stakeholders through usability testing.

2. Development Phase:

   • Implement all the new plugins features
     • Engine UX - engine configuration management
     • Engine UX - security policy management
     • Engine UX - KVDBs management
     • Engine UX - dashboards and queries
     • Engine UX - CTI client management

3. Testing and Validation:

   • Implement acceptance test with playwright and imposter for all the developed features
     • Engine UX - test engine configuration management
     • Engine UX - test security policy management
     • Engine UX - test KVDBs management
     • Engine UX - test dashboards and queries
     • Engine UX - test CTI client management