1回答
- 新しい順
- 投票が多い順
- コメントが多い順
0
Here some ideas to dig for the root cause.
- Make sure you update the AWS CloudTrail connector configuration in Azure Sentinel to account for these changes.
- Ensure that S3 data events are enabled and configured in your CloudTrail settings.
- Check if the specific "CopyObject" events are included in the CloudTrail logs you are sending to Azure Sentinel. These events might be categorized differently or may have specific attributes that need to be parsed and queried.
- Check for any errors or issues related to log ingestion. You may need to troubleshoot and resolve any connectivity problems.
回答済み 6ヶ月前
関連するコンテンツ
- 質問済み 6年前
- AWS公式更新しました 2年前
- AWS公式更新しました 2年前
- AWS公式更新しました 2年前