Policy Management

The Policy module is one of the “Solutions” in eramba and it links to different modules doing different things. In the Policy module, you will find two tabs, Policies and Reviews, this is because one policy will have one or more reviews associated.

The diagram below shows the key relationships of the policy module with other modules in the system:

• Internal Controls: since controls are activities they require a procedure, standard and many times a policy. Without these documents, the activity lacks governance and therefore is likely to be non-systematically executed.
• Risks: some risks might be mitigated with a process or a contract stored on the policy module.
• Compliance Analysis: many compliance requirements simply ask for Diagrams, Policies, etc.
• Data Flows: some flows might be mitigated with a process or a contract stored on the policy module.
• Awareness Module: some awareness training might link back to a policy, for example, if you created an awareness training for the "Acceptable use of Assets" policy you could then know how many people have accepted these terms.
• Projects: policies might be working ok and they might need a project to improve.