Compliance, Auditing, and Reporting
Hossein.K
6,646
Share
Report
Auditing for compliance was a manual task for administrators in previous
versions. There were no built-in features to help prevent fraud and ensure
compliance. You can now set up segregation of duties rules to make sure that a
user does not have access to conflicting duties (permissions required to perform a
task or service for a job). For example, you might set up a rule specifying one
person cannot both acknowledge the receipt of goods and pay the vendor. In
addition to helping you enforce compliance, Microsoft Dynamics AX 2012
includes better security audit trails and new security reports. Using these audit
trails, security reports, and role based security, administrators and auditors can
more easily receive information about each user's permissions. Doing this makes
it easier to determine whether adjustments to security must be made.
NOTE: The default security roles have application access by default, but no data
restrictions are applied by default.
Regards,
Hossein Karimi
versions. There were no built-in features to help prevent fraud and ensure
compliance. You can now set up segregation of duties rules to make sure that a
user does not have access to conflicting duties (permissions required to perform a
task or service for a job). For example, you might set up a rule specifying one
person cannot both acknowledge the receipt of goods and pay the vendor. In
addition to helping you enforce compliance, Microsoft Dynamics AX 2012
includes better security audit trails and new security reports. Using these audit
trails, security reports, and role based security, administrators and auditors can
more easily receive information about each user's permissions. Doing this makes
it easier to determine whether adjustments to security must be made.
NOTE: The default security roles have application access by default, but no data
restrictions are applied by default.
Regards,
Hossein Karimi
*This post is locked for comments