Improving with kawak®

It would be good if they included a field where, when information security incidents are recorded, there is a field of lessons learned to be part of the entire traceability of the incident.

In order to be able to relate the lessons learned generated from information security incidents, we consider including this field.

Within the Information Security module, in Assets, a solution is needed to include in the “guardian”, “administrator”, and/or “owner” field a third party, someone who is not part of the company. Currently, when creating a new position, it is created in the organization chart and Human Talent, affecting their content.

It would be very useful to have the option of duplicating assets, to facilitate the creation process, since many of them have similar characteristics.

Add the process (according to the process map) to which the asset belongs, which can be seen in asset tracking, such as what the owner looks like to see the process

Associating Information assets to the process map, it is understood that everything must be linked and it is clear that processes bring risks from the process map but not assets, these are of great importance to be able to identify by process

In the events and incidents scheme, everything is entered by event and depending on the analysis and classification, it may still be an event in which it must remain in the risk module, but if it is classified as an incident there is automatically the system transfers it to the incident security module, the application should not duplicate the events in incidents because it lends itself to misinterpretation by the auditor. They must improve that process.

It would be interesting if there were logs about the actions taken on information assets. (Create, Modify, Delete)

The fact that it is possible to filter assets by process, for auditing and visualizing information assets, it is very helpful to be able to filter assets by process.