AWS access to the Glean environment should be as limited as possible. S3 and CloudWatch can store sensitive data and access to these resources should be restricted. Additionally, access to mutate IAM permissions within the Glean account should also be extremely limited.
Audit Log
All audit logs related to Glean itself are stored in theaudit-log CloudWatch log group. This log group is one that customers should integrate with their SIEM to perform alerting and overall analysis on user activity that takes place on the Glean platform. Because this is a CloudWatch log group, customers can use any AWS native tools or AWS native SIEM ingestion mechanisms to obtain the logs.
Sensitive Logs
Glean stores a number of logs that may be deemed sensitive. These are logs that should not leave the Glean environment. Glean provides a report in both JSON and Markdown formats outlining the CloudWatch Log Groups and S3 buckets that contain sensitive and non-sensitive data. To obtain this report, you will need AWS credentials from the Glean AWS account to pull contents from theglean-terraform-deploy-packages S3 bucket.
It is packaged in a zip file that contains the full terraform deployable that we package Glean in. Here is how to grab it:
- CloudWatch:
- Markdown:
terraform/glean.com/docs/aws/glean_cloudwatch_logging_resources.md - JSON:
terraform/glean.com/docs/aws/glean_cloudwatch_logging_resources/cloudwatch_log_group_sensitivity.json
- Markdown:
- S3:
- Markdown:
terraform/glean.com/docs/aws/glean_s3_resources.md - JSON:
terraform/glean.com/docs/aws/glean_cloudwatch_logging_resources/s3_sensitivity.json
- Markdown: