Configuration of Amazon S3 upload feature
Technical Articles ID:
KB94656
Last Modified: 2023-07-12 04:27:08 Etc/GMT
Last Modified: 2023-07-12 04:27:08 Etc/GMT
Languages:
This article is available in the following languages:
了解不断适应的 XDR 生态系统如何为您的企业赋能。
Trellix 首席执行官 Bryan Palma 解释称,现在亟需能够不断学习的安全防护。
下载 Magic Quadrant 报告,该报告根据执行能力和愿景完成情况,对 19 家供应商进行了评估。
Gartner 报告称,“XDR 是一种新兴技术,可以提供增强的威胁防护、检测和响应。”
企业在 2022 年应警惕哪些网络安全威胁?
网络安全行业绝不是一潭死水,而是危机不断,现在便是接受这一全新安全防护理念,将其转化为自身优势,为企业赋能的最佳时机。
网络安全领域备受信赖的两大领导者携手打造弹性化的数字世界。
Trellix 首席执行官 Bryan Palma 解释称,现在亟需能够不断学习的安全防护。
Configuration of Amazon S3 upload feature
Technical Articles ID:
KB94656
Last Modified: 2023-07-12 04:27:08 Etc/GMT Environment
Endpoint Detection and Response (EDR)
SummarySystem Requirements:
NOTE: The responsibilities of customers include the following:
S3 Bucket – Suggested Settings Customers must review their usage needs for sending traces to S3. The following are a set of suggested settings. Customers must make sure that they choose a configuration that meets their functional and security needs.
IAM Permissions – Suggested Policies: An IAM user needs to be created to write traces to the appropriate S3 bucket. The access key and secret key for this user is entered in the ePO EDR Client Extension and distributed securely to EDR endpoints. It's advised that only the minimum needed permissions are given to this user. The following suggested policy only allows write or "Version": "2012-10-17", "Statement": [ { "Sid": "VisualEditor0", "Effect": "Allow", "Action": "s3:PutObject", "Resource": "arn:aws:s3:::<bucketname>/<prefix>" } ] } A different user with a targeted policy must be used for reading traces from the EDR bucket. "Version": "2012-10-17", "Statement": [ { "Sid": "VisualEditor0", "Effect": "Allow", "Action": [ "s3:GetObject", "s3:GetObjectVersion" ], "Resource": "arn:aws:s3::: <bucketname>/<prefix>” }, { “Sid”: “VisualEditor1”, “Effect”: “Allow”, “Action”: [ “s3:ListBucketVersions”, “s3:ListBucket” ], “Resource”: [ “arn:aws:s3::: <bucketname>” ] } ] } Other Considerations:
AWS implements a limit of 3,500 Put requests per second per prefix in an S3 bucket. If this threshold is consistently reached, it causes the local EDR client buffers to reach their limits and some traces are lost. When scaling up to many endpoints, you must segment the endpoints in ePO into groups that use different buckets or prefixes to avoid hitting the limits.
For details, seee KB51417 - How to create and apply tags in ePolicy Orchestrator. Languages:This article is available in the following languages: |
|