What's new in AX 2012? Flash news 7, Role-based security - How does this differ from that user group security setting in AX 2009

Role-based security

In AX 2009, the management of application security was a complex and time-consuming process. Administrators had to determine which tables and fields were needed for a task, and then grant permissions to the user for those tables and fields, wide user groups.

In Microsoft Dynamics AX 2012, administrators manage security by defining roles and then assigning users to those roles. Security management is made more intuitive, it is role-based, and it is less time-consuming.

Role-based security What can you do?	Microsoft Dynamics AX 2009	Microsoft Dynamics AX 2012	Why is this important?
Define user groups.	No default user groups were provided.	Default roles have been defined and are available out of the box.	Security management has been simplified.
Set user group permissions.	Administrators had to determine which tables, fields, and menu items were required to complete tasks, and assign those items to user groups.	Default duties and privileges contain the tables, fields, and menu items required to complete tasks. Administrators assign duties and privileges to roles.	Security management has been simplified.
Reuse permissions across companies.	User groups were defined in each company, for each functional role.	After a role is defined, it can be used across multiple companies and organizations.	Security management has been simplified.
Filter columns that a user has access to.	Administrators determined which fields to restrict.	Only the appropriate columns are included in default duties and privileges.	Security management has been simplified, and security is improved.
Define permission levels (read only, create, update, and delete).	Security keys were used to define permission levels for user groups.	Separate default privileges are defined for each permission level.	Security management has been simplified.
Enforce regulatory and procedural compliance.	There were no built-in features to help prevent fraud and ensure compliance.	Administrators can set up rules for segregating duties to ensure that a user does not gain access to conflicting duties.	Security is improved.
Audit and report on security settings.	Auditing was a manual task for administrators.	Audit trails and reports to evaluate security setup are built into the application.	Security management has been simplified, and security is improved.