Episode 4
Incident Management Module Associations
Module associations with other modules
The Incident Management module is a stand alone module, this means you could use the module without any asociation. But to make the best out of the module you can link Incidents to:
- Risks: if the organization knew the incident was possible (as part of the Risk assessment exercise) and a Risk existed, eramba will take information from the Risk (asset, controls, third parties, etc) and link them to the Incident. .
- Assets: to describe what assets have been affected.
- Internal Controls: what controls did not work and permitted the incident to take place.
- Third Parties: who else could have been affected by this incident
There are other uses for the Internal Control module. You can review them by clicking “Help” on the menu bar:
Playlist
- Episode 1Introduction to the Incident Management Module7 mins left
- Episode 2Access Management & User Interface1 min left
- Episode 3Configuring the Incident Management Module1 min left
- Episode 4Incident Management Module Associations7 mins left
- Episode 5Creating an Incident2 mins left
- Episode 6Analysing Incidents1 min left
- Episode 7Typical Dynamic Statuses: Incident Module1 min left
- Episode 8Typical Filters: Incident Management Module1 min left
- Episode 9Typical Reports: Incident Management Module1 min left
- Episode 10Incident Management Implementation Guidance0 mins left