AST Blog Series: Security Setup and Configuration

Welcome to week 8 of our exclusive blog series about saving time and money during your Hyperion implementation!  This week is all about security.

Defining security standards is a fundamental task for any software application implementation. EPM applications are in-built with a very robust and flexible security framework. This allows you to define security from the highest level to the most minuscule detail.  With so much flexibility, however, it is tempting to create complex security schemes which may not always be easy to maintain. Keeping it “simple yet strong” is the best way to properly map security to your firm’s business needs.

Role-based security is easier to maintain, because you define a role-based group and assign that group to specific artifacts. For example, if you want a particular ‘business rule’ to be run by power users only, then define a group called ‘Power Users’ and assign it to the ‘business rule’ artifact. This approach is easier to maintain and manage. As with every step of the project, you must work closely with your implementation partner to define a blueprint for a clean and easily maintainable security setup.