- Internal Audit Summary Report
- Dynamics 365 Audit Reporting
- Dynamic 365 Audit Summary In Dashboard Software
One of the important tasks for Microsoft Dynamics CRM 2011 administrators is ensuring users have appropriate access to the system. One of the challenges of doing an efficient user audit is easily seeing a list of all the security roles each user belongs to. No worries! There is a report that allows you to conquer this challenge.
Microsoft Dynamics CRM 2011 has about 25 out-of-the-box reports. Most of the reports analyze your CRM data. However, there is one report for administrators: the Dynamics CRM User Summary report.
Let’s take a look.
- In CRM, click on Workplace.
- Click on Reports.
- Double click on User Summary.
- The next screen allows you to filter the user list.
- Once you’ve set your filter criteria (you aren’t required to filter your report), click on Run Report.
- The resulting report will display:
- Information about each User
- Users grouped by Business Unit
- A listing of all the security roles to which each User belongs
Not only does the User Summary report give you a list of users, it allows you to see which security roles each user belongs to. The only other way to see if a user belongs to a specific security role is by accessing their user record. This can be time consuming especially for larger organizations. Another benefit is that you can access the User record directly from the report, making it easy to alter access levels. And it’s just a great way to audit user access.
NOTE: This report does NOT show roles assigned to Teams.
That’s all it takes!
Want to know more about security roles in Dynamics CRM? Take a look at this recent blog if you’d like to learn how to restrict how information can be taken out of your CRM system.
Happy CRM’ing!
-->Applies to Dynamics 365 for Customer Engagement apps version 9.x
Protecting data, preserving privacy, and complying with regulations such as the General Data Protection Regulation are certainly some of the highest priorities for your business. It's critical that you audit the entirety of data processing actions taking place to be able to analyze for possible security breaches. This information from Activity Logging can be used when you perform a Data Protection Impact Assessment (DPIA) addressing the use of Office and Dynamics 365 for Customer Engagement.
This topic covers how you can set Microsoft Dynamics 365 to audit a broad range of data processing activities and use the Office 365 Security and Compliance Center to review the data in activity reports.
Requirements
- An Office 365 Enterprise E3 or E5 subscription is required to do Activity Logging.
- For version 8.x, version 8.2.2.1310 or later is required.
- Available for Production and not Sandbox instances.
How this differs from past audit logging
Audit logging as described in Audit data and user activity for security and compliance covers enabling and viewing logging for specific entities and attributes which you select. What is logged is largely based on the context of the activity. Open a record and activities such as who created the record, what values were entered and changed, who updated it, etc, are logged for that particular record.
Activity Logging has two significant differences with prior Microsoft Dynamics 365 auditing:
- You can log user and admin activities across Office and Dynamics 365 for Customer Engagement apps.
- Auditing occurs at the SDK layer of Dynamics 365 for Customer Engagement apps which means much more data is logged than just activities.
What events are audited
Logging takes place at the SDK layer which means a single action can trigger multiple events that are logged. The following are a sample of admin and user events you can audit.
Admin-related events
Event | Description |
---|---|
Publishing customizations | An admin publishes a new customization which overrides a change done by the previous one. The action requires auditing for analysis. |
Attribute deletes | Admin accidentally deletes an attribute. This action also deletes the data. |
Team, user management | Who was added, who was deleted, what access rights a user/team had is important for analyzing impact. |
Configure instance | Adding solutions to an instance. |
Backup and restore | Backup and restore actions at the tenant. |
Manage applications | New instance added, existing instance deleted, trials converted to paid, etc. |
User and support-related events
Event | Description |
---|---|
User sign-in authentication | Logging all user sign-in to the environment - when the Start Read Auditing option is selected. |
Create, read, update, delete (CRUD) | Logging all CRUD activities essential for understanding the impact of a problem and being compliant with data protection impact assessments (DPIA). |
Multiple record view | Users of Dynamics view information in bulk, like grid views, Advanced Find search, etc. Critical customer content information is part of these views. |
Export to Excel | Exporting data to Excel moves the data outside of the secure environment and is vulnerable to threats. |
SDK calls via surround or custom apps | Actions taken via the core platform or surround apps calling into the SDK to perform an action needs to be logged. |
All support CRUD activities | Microsoft support engineer activities on customer environment. |
Admin activities | Admin activities on customer tenant. |
Backend commands | Microsoft support engineer activities on customer tenant and environment. |
Report Viewed | Logging when a report is viewed. Critical customer content information might be displayed on the report. |
Report Viewer Export | Exporting a report to different formats moves the data outside of the secure environment and is vulnerable to threats. |
Report Viewer Render Image | Logging multimedia assets that are shown when a report is displayed. They might contain critical customer information. |
Microsoft Social Engagement logging
The following Microsoft Social Engagement (MSE) entities and actions are logged.
MSE entity | MSE pages/panels/controls logged |
---|---|
Search Topic Category | Create, Rename, Delete |
Search Topic | Create, Update, Delete |
Custom Source | Create, Update, Delete |
Blocked Keyword | Add, Delete |
Blocked Domain | Add, Delete |
Stream | Create, Update, Delete |
Post (acquired) | Internal & External Actions |
Post (published) | Send |
Author | Add (GDPR), Delete (GDPR), Delete |
Activity Map | Create, Update, Delete |
Alert | Create, Update, Delete |
Preference | Update |
Social Profile | Create, Update, Reauthenticate, Delete |
User | Edit Role, E-mail |
Azure Event Hubs | Create, Update, Delete |
Dynamics 365 for Customer Engagement apps | Create, Update, Refresh, Delete |
Allowed Domain | Add, Delete |
Automation Rule | Create, Update, Delete |
AR Notification | Enable, Disable |
Tag | Add, Update, Delete |
Label | Add, Update Delete |
Search Language | Add, Delete |
Adaptive Sentiment | Enable, Disable, Reset |
Other Global Settings | Update |
Base schema
Schemas define which Dynamics 365 for Customer Engagement apps fields are sent to the Office 365 Security and Compliance Center. Some fields are common to all applications that send audit data to Office 365, while others are specific to Dynamics 365 for Customer Engagement. The Base schema contains the common fields.
Field name | Type | Mandatory | Description |
---|---|---|---|
Date | Edm.Date | No | Date and time of when the log was generated in UTC |
IP address | Edm.String | No | IP address of the user or corporate gateway |
Id | Edm.Guid | No | Unique GUID for every row logged |
Result Status | Edm.String | No | Status of the row logged. Success in most cases |
Organization Id | Edm.Guid | Yes | Unique identifier of the organization from which the log was generated. You can find this ID under Dynamics Developer Resources. |
ClientIP | Edm.String | No | IP Address of the user or corporate gateway |
CorrelationId | Edm.Guid | No | A unique value used to associate related rows (e.g., when a large row is split) |
CreationTime | Edm.Date | No | Date and time of when the log was generated in UTC |
Operation | Edm.Date | No | Name of the message called in Dynamics 365 for Customer Engagement apps SDK |
UserKey | Edm.String | No | Unique Identifier of the User in Azure AD. AKA User PUID |
UserType | Self.UserType | No | The Office 365 audit type (Admin, Regular, System) |
User | Edm.String | No | UPN of the user |
Dynamics 365 for Customer Engagement apps schema
The Dynamics 365 for Customer Engagement apps schema contains fields specific to Dynamics 365 for Customer Engagement apps and partner teams.
Field name | Type | Mandatory | Description |
---|---|---|---|
User Id | Edm.String | No | Unique identifier of the user GUID in the Dynamics 365 for Customer Engagement apps organization |
Crm Organization Unique Name | Edm.String | No | Unique name of the Dynamics 365 for Customer Engagement apps organization |
Instance Url | Edm.String | No | URL to the instance |
Item Url | Edm.String | No | URL to the record emitting the log |
Item Type | Edm.String | No | Name of the entity |
Message | Edm.String | No | Name of the message called in Dynamics 365 for Customer Engagement apps SDK |
User Agent | Edm.String | No | Unique identifier of the user GUID in the Dynamics 365 for Customer Engagement apps organization |
EntityId | Edm.Guid | No | Unique identifier of the entity |
EntityName | Edm.String | No | Name of the entity in the Dynamics 365 for Customer Engagement apps organization |
Fields | Edm.String | No | JSON of Key Value pair reflecting the values that were created or updated |
Id | Edm.String | No | Entity name in Dynamics 365 for Customer Engagement apps |
Query | Edm.String | No | The Filter query parameters used while executing the FetchXML |
QueryResults | Edm.String | No | One or multiple unique records returned by the Retrieve and Retrieve Multiple SDK message call |
ServiceContextId | Edm.Guid | No | The unique id associated with service context |
ServiceContextIdType | Edm.String | No | Application defined token to define context use |
ServiceName | Edm.String | No | Name of the Service generating the log |
SystemUserId | Edm.Guid | No | Unique identifier of the user GUID in the Dynamics 365 for Customer Engagement apps organization |
UserAgent | Edm.Guid | No | Browser used to execute the request |
UserId | Edm.Guid | No | The unique id of the Dynamics system user associated with this activity |
UserUpn | Edm.String | No | User principal name of the user associated with this activity |
Enable auditing in Dynamics 365 for Customer Engagement
- In Dynamics 365 for Customer Engagement apps (online), choose Settings > Administration > System Settings > Auditing tab.
- Under Audit Settings, enable the following check boxes:
- Start Auditing
- Audit user access
- Start Read Auditing (Note: this only appears if you enable Start Auditing.)
- Under Enable Auditing in the following areas, enable the check boxes for the areas you want to audit and then choose OK.
- Go to Settings > Customizations > Customize the System
- Under Components, expand Entities and select an entity to audit, such as Account.
- Scroll down and under Data Services enable Auditing.
- Under Auditing, enable the following check boxes:
- Single record auditing. Log a record when opened.
- Multiple record auditing. Log all records displayed on an opened page.
- Choose Save.
- Choose Publish to publish the customization.
- Repeat steps 5 - 9 for other entities you want to audit.
- Turn on audit logging in Office 365. See Turn Office 365 audit log search on or off.
Review your audit data using reports in Office 365 Security and Compliance Center
You can review your audit data in the Office 365 Security and Compliance Center. See Search the audit log for user and admin activity in Office 365.
To use the preconfigured Dynamics 365 for Customer Engagement apps reports, go to https://protection.office.com > Search & investigation > Audit log search and select the Dynamics 365 activities tab.
The following are the preconfigured Dynamics 365 for Customer Engagement apps reports:
Accessed out-of-box entity | Accessed custom entity | Accessed admin entity |
Performed bulk actions (such as delete and import) | Accessed other entity type | Accessed Dynamics 365 admin center |
Accessed internal management tool | Signed in or out | Activated process or plug-in |
Internal Audit Summary Report
Create reports
You can create your own reports to review your audit data. See Search the audit log in the Office 365 Security & Compliance Center.
What's logged
For a list of what's logged with Activity Logging, see Microsoft.Crm.Sdk.Messages Namespace.
We log all SDK messages except the following:
- WhoAmI
- RetrieveFilteredForms
- TriggerServiceEndpointCheck
- QueryExpressionToFetchXml
- FetchXmlToQueryExpression
- FireNotificationEvent
- RetrieveMetadataChanges
- RetrieveEntityChanges
- RetrieveProvisionedLanguagePackVersion
- RetrieveInstalledLanguagePackVersion
- RetrieveProvisionedLanguages
- RetrieveAvailableLanguages
- RetrieveDeprovisionedLanguages
- RetrieveInstalledLanguagePacks
- GetAllTimeZonesWithDisplayName
- GetTimeZoneCodeByLocalizedName
- IsReportingDataConnectorInstalled
- LocalTimeFromUtcTime
- IsBackOfficeInstalled
- FormatAddress
- IsSupportUserRole
- IsComponentCustomizable
- ConfigureReportingDataConnector
- CheckClientCompatibility
- RetrieveAttribute
How we categorize read and readmultiple
We use the prefix to categorize.
If the request starts with: | We characterize as: |
---|---|
RetrieveMultiple | ReadMultiple |
ExportToExcel | ReadMultiple |
RollUp | ReadMultiple |
RetrieveEntitiesForAggregateQuery | ReadMultiple |
RetrieveRecordWall | ReadMultiple |
RetrievePersonalWall | ReadMultiple |
ExecuteFetch | ReadMultiple |
Retrieve | Read |
Search | Read |
Get | Read |
Export | Read |
Example generated logs
The following are some examples of logs created with Activity Logging.
Example 1 – Logs generated when user reads an Account record
Schema Name | Value |
---|---|
ID | 50e01c88-2e43-4005-8be8-9ceb172e2e90 |
UserKey | 10033XXXA49AXXXX |
ClientIP | 131.107.XXX.XX |
Operation | Retrieve |
Date | 3/2/2018 11:25:56 PM |
EntityId | 0a0d8709-711e-e811-a952-000d3a732d76 |
EntityName | Account |
Query | N/A |
QueryResults | N/A |
ItemURL | https://orgname.onmicrosoft.com/main.aspx?etn=account&pagetype=entityrecord&id=0a0d8709-711e-e811-a952-000d3a732d76 |
Example 2 – Logs generated when user sees Account records in a Grid (Export to Microsoft Excel logs are like this)
Schema Name | Value |
---|---|
ID | ef83f463-b92f-455e-97a6-2060a47efe33 |
UserKey | 10033XXXA49AXXXX |
ClientIP | 131.107.XXX.XX |
Operation | RetrieveMultiple |
Date | 3/2/2018 11:25:56 PM |
EntityId | N/A |
EntityName | Account |
Query | <filter type='and'><condition column='ownerid' operator='eq-userid' /><condition column='statecode' operator='eq' value='0' /></filter> |
QueryResults | 0a0d8709-711e-e811-a952-000d3a732d76, dc136b61-6c1e-e811-a952-000d3a732d76 |
ItemURL | N/A |
Example 3 – List of messages logged when user converts a lead to opportunity
ID | EntityID | EntityName | Operation |
---|---|---|---|
53c98033-cca4-4420-97e4-4c1b4f81e062 | 23ad069e-4d22-e811-a953-000d3a732d76 | Contact | Create |
5aca837c-a1f5-4801-b770-5c66183a58aa | 25ad069e-4d22-e811-a953-000d3a732d76 | Opportunity | Create |
c9585748-fdbf-4ff7-970c-bb37f6aa2c36 | 25ad069e-4d22-e811-a953-000d3a732d76 | Opportunity | Update |
a0469f30-078b-419d-be61-b04c9a34121f | 1cad069e-4d22-e811-a953-000d3a732d76 | Lead | Update |
0975bceb-07c7-4dc2-b621-5a7b245c36a4 | 1cad069e-4d22-e811-a953-000d3a732d76 | Lead | Update |
Additional considerations
When audit log search in the Office 365 Security and Compliance Center is turned on, user and admin activity from your organization is recorded in the audit log and retained for 90 days. However, your organization might not want to record and retain audit log data. Or you might be using a third-party security information and event management (SIEM) application to access your auditing data. In those cases, a global admin can turn off audit log search in Office 365.
Known issues
- Office has a 3KB limit for each audit record. Therefore, in some cases a single record from Dynamics 365 for Customer Engagement apps needs to be split into multiple records in Office. The CorrelationId field can be used to retrieve the set of split records for a given source record. Operations that are likely to require splitting include RetrieveMultiple and ExportToExcel.
- Some operations need additional processing to retrieve all relevant data. For example, RetrieveMultiple and ExportToExcel are processed to extract the list of records that are retrieved or exported. However, not all relevant operations are yet processed. For example, ExportToWord is currently logged as single operation with no additional details about what was exported.
- In the Office 365 Security and Compliance Center (protection.office.com), the Activities drop-down has a section called Dynamics 365 for Customer Engagement apps activities, with nine activities listed. However, the audit logs currently only use the Accessed other entity type activity. Selecting any of the others alone will filter out all results. The simplest option for now is to click on the Dynamics 365 for Customer Engagement apps activities header, which will select all activities.
- In future releases, logging will disabled for operations that are determined to not be useful based on a review of the logs. For example, some operations result from automated system activity, not user activity.
- The new flags for enabling Read Auditing in the Organization settings and Entity Settings are not solution aware in version 8.2. Exporting a solution from an 8.2 instance to any other instance will not export these flags.
See also
Audit data and user activity for security and compliance
Search the audit log for user and admin activity in Office 365Office 365 Management APIs overview
Search the audit log for user and admin activity in Office 365Office 365 Management APIs overview
For new and current implementations of Dynamics 365 that require adherence to strict regulations such as FedRAMP and HIPAA, there are now powerful options available in the July 2017 update for Dynamics 365. These new features specifically address User Session Management, and Activity Log Management. To clarify for those slightly confused by the nomenclature of the latter, it does not specifically have to do with CRM Activity records, but is rather better described as functionality to replace the Audit Log.
User Session Management Settings in Dynamics 365
Some government regulations and company policies require strict management of session timeouts in software for security purposes. In previous versions of Dynamics CRM, the session timeout for a user was generally configured to 24 hours, which does not meet these guidelines.
Nevertheless, with the new User Session Management features in Dynamics 365 we can now easily configure within System Settings to change the timeout to what works best for your organization. This includes a setting for overall session timeout, as well as for inactivity timeout. Users can now receive a gentle warning when their session is about to expire, giving them the ability to save their work before it happens, or re-authenticate as needed. These new settings will reassure Compliance Officers that the system fully conforms with their security requirements going forward.
Activity Log Management in Dynamics 365
Perhaps one of the more interesting enhancements in the July 2017 release is a completely new framework for Activity Logging, which would replace what was previously known as the Audit Log.
The new Activity Logging functionality in CRM essentially provides the following benefits over the previous functionality:
- Management in a central location on the Office 365 portal: Office 365 Administrators can now manage settings and activity reporting for all environments within the “Security & Compliance Center” by simply browsing to https://protection.office.com. Previously, Audit Logging was set up separately within each instance of a Dynamics CRM environment.
- All data in the system is now logged: All data transactions including plugin operations, entity operations, bulk operations, user login/out sessions, and even Microsoft Support Personnel operations are logged by this new functionality. The previous Audit Log functionality was set up on an entity-by-entity basis.
- Configurable Alert Policies: The system can now be set up to notify administrators or Compliance Officers of certain events, according to configurable settings.
- Audit Log Search capability: Administrators can now easily query audit logs via predefined or custom filters.
- Analyze suspicious behavior with Security Information and Event Management (SIEM): Functioning in near real-time, the SIEM will work to analyze and alert administrators of possible suspicious behavior within the system, and provide actions to address these events. Needless to say, this new feature will be a powerful tool for Compliance Officers tasked with managing data integrity.
- SIEM Vendor Integration: Dynamics 365 now provides out-of-box integration with multiple SIEM vendors such as ArcLight, Microsoft OMS, Okta, SumoLogic, BetterCloud, and many others.
- Minimized impact to system performance: This new Activity Logging Management functionality has a smaller footprint on system resources compared to the previous Audit Log functionality.
With these new security tools available to organizations for configuring user sessions and audit logging, Dynamics 365 has demonstrated its long-term commitment to addressing the security and regulatory needs of all its customers.
To learn more about Dynamics 365 July Updates, sign up for our Update Webinar Series – running now through August 22. 7.3 5 addons. Online shop template blogger.
Happy Dynamics 365’ing!
Fl studio 12 indir. Please note: All content and information is presented on preview versions and not the launched product. Product is subject to changes per Microsoft’s discretion.
At Microsoft, we believe that transparency is key to earning customer trust. When you entrust your data to the Microsoft Cloud, you will have questions:
- Where is it and who can access it?
- What is Microsoft doing to protect it?
- What does Microsoft do to comply with regulatory requirements?
- How can I verify that Microsoft is doing what it says?
Because it’s your data, you decide who has access, and you work with us to decide where it is located. To safeguard your data, we use advanced security technology and cryptography. Our compliance with US and international standards is independently audited, and we’re transparent on many levels—from how we handle legal demands for customer data to the security of our code. We offer detailed trust information on each of our cloud services, which we group into four categories:
- Secure
- Private
- Compliant
- Transparent
We do this not just to be transparent, but to also help you answer the questions above, and to make it easier for you to perform your own risk assessment of using Office 365. And we do this to help you understand how the controls within Office 365 meet the security, compliance, and privacy requirements of your organization.
To that end, we have launched a new Office 365 Security & Compliance Center, which is designed to be a one-stop portal for protecting your Office 365 data. It is a new portal that is an evolution of the Office 365 Compliance Center. The Security & Compliance Center is designed for organizations that have data protection or compliance needs, or that want to audit user and administrator activity. You can use the Security & Compliance Center to manage compliance for all of your organization’s data across Office 365.
You can access the Security & Compliance Center at http://protection.office.com using your Office 365 admin account. Administrators can also delegate access to compliance, security, and other teams in your organization. For more information, see Give users access to the Security & Compliance Center.
The Security & Compliance Center includes several navigation panes that provide access to several auditing and reporting features:
- Permissions Enables you to assign permissions such as Compliance Administrator, eDiscovery Manager, and others to people in your organization so they can perform tasks in the Security & Compliance Center.
- Security policies Enables you to create and apply device management policies using Office 365 Mobile Device Management and to set up Data Loss Prevention (DLP) policies for your organization.
- Data management Enables you to import email or SharePoint from other systems into Office 365, configure archive mailboxes, and set retention policies for email and other content within your organization.
- Search & investigation Provides content search, audit log and eDiscovery case management tools to quickly drill into activity across Exchange Online mailboxes, groups and public folders; SharePoint Online, and OneDrive for Business.
- Reports Enables you to quickly access reports for SharePoint Online, OneDrive for Business, Exchange Online, and Azure AD.
- Service assurance Provides information about how Microsoft maintains security, privacy and compliance with global standards for Office 365, Azure, Microsoft Dynamics CRM Online, Microsoft Intune, and other cloud services. Also includes access to third-party ISO, SOC and other audit reports, as well as Audited Controls, which provides details about the various controls that have been tested and verified by third-party auditors of Office 365.
Service Assurance
Many of our customers in regulated industries are subject to extensive compliance requirements. To perform their own risk assessments, customers often need in-depth information on how Office 365 maintains the security and privacy of their data. Office 365 is committed to the security and privacy of customer data in its cloud services and to earning customer trust by providing a transparent view of its operations, and easy access to independent compliance reports and assessments.
As mentioned above, the Service Assurance area provides information about how Microsoft's cloud services maintain security, privacy and compliance with global standards. The Service Assurance area includes independent third-party audit reports for Office 365, Yammer, Azure, CRM Online, and Intune, as well implementation and testing details for the security, privacy, and compliance controls used by Office 365 to protect customer data, which can be found in the Audited Controls area.
The Service Assurance section in the Security & Compliance Center provides transparency of operations and information on how Microsoft maintains the security, privacy and compliance of customer data in Office 365. Customers can use the third-party reports on advanced security and compliance standards, along with a library of white papers, FAQs, and other materials on Office 365 topics such as data encryption, data resiliency, security incident management and more, to perform their own regulatory risk assessments. Compliance officers can assign the “Service Assurance User” role in Permissions to give users access to the Service Assurance dashboard. The tenant administrator can also provide external users, such as independent auditors, with access to information in the Service Assurance dashboard through the Microsoft Cloud Service Trust Portal (STP). For details on how to access the STP, visit Get started with the Service Trust Portal for Office 365 for business, Azure, and Dynamics CRM Online subscriptions.
Audited Controls
The Audited Controls area provides information about how the controls used within Office 365 meet security, compliance, and privacy requirements. Microsoft's internal control system is based on the National Institute of Standards and Technology (NIST) special publication 800-53. With Audited Controls, we are also mapping our internal control system to other standards, such as International Organization for Standardization (ISO) 27001:2013 and ISO 27018:2014.
Dynamics 365 Audit Reporting
Using the Audited Controls feature, customers can perform their own assessment of the risks of using Office 365. Customers view the details of a given control, that includes:
- Control ID (as assigned by the particular mapped standard)
- Test status (whether or not the control passed testing)
- Test date (when the control was last tested)
- Tested by (typically third-party auditors or Microsoft)
- Control implementation details (how the control is implemented)
- Testing performed to evaluate control effectiveness (how the control was tested)
The following figure is an example of a control and the available details for it:
Example control from the Audited Controls area of Service Assurance
Dynamic 365 Audit Summary In Dashboard Software
Because a control can map to multiple standards, the Test Date is the date when the control was last tested during any audit. As a result, the Test Date may me more recent than the date of the audit for the standard to which it is mapped. For example, a control such as one of our cryptographic key management policy controls, is typically tested by multiple third-party auditors as part of separate audits that are being conducted (e.g., ISO, SOC, etc.).
Audited Controls also enables customers to download an Excel file containing the details on all of the controls that were tested as part of a specific audit (e.g., ISO 27001:2013, or ISO 27018:2014, etc.). As of this writing, the only standards mapping files available are for ISO, but additional mapping against other standards is planned for a future release.
Check out Service Assurance and Audited Controls and let us know what you think. You can use the Feedback mechanism in Service Assurance to send us anonymous or non-anonymous comments and feedback.