This guide is intended for informational purposes only and does not constitute legal advice. While every effort has been made to ensure the accuracy of the information provided, it is recommended that you consult with a qualified legal professional to ensure compliance with all applicable laws and regulations.
Many industries and jurisdictions have strict privacy and security requirements that apply to the handling of log data—which can include personal and other sensitive information. Under these requirements, it may seem difficult to use tools such as Log Management and Analytics. With the right implementation strategy, however, you can achieve compliance and harness the value of log data.
This guide will help you understand the configuration options Dynatrace provides to address your regulatory and compliance requirements in Log Management and Analytics.
This guide is targeted at Dynatrace monitoring administrators who work with developers and product managers, and are responsible for instrumenting, monitoring, and achieving the business goals of their applications.
Dynatrace Log Management and Analytics aggregates all log data into the Dynatrace Grail data lakehouse, offering visibility into workloads, applications, environments, and forgotten assets—allowing customers to optimize cloud spending and enhance their compliance posture.
In many cases, log data includes personal and other sensitive information. This brings challenges when complying with global, local, and industry privacy and security requirements when collecting, handling, and sharing this information. To allow for efficient implementation by a diverse set of teams, these regulatory requirements need to be condensed into a set of guidelines that can be interpreted and understood by those teams.
The following use cases can help you achieve this with Dynatrace.
Mask sensitive data and configure appropriate access permissions in an e-commerce use case.
Identify and prevent potential financial fraud by masking sensitive data and configuring the required access permissions.
Inspect payment services to properly configure appropriate access permissions and define fitting retention periods.