Configuration of Amazon S3 upload feature
Last Modified: 2023-07-12 04:27:08 Etc/GMT
Languages:
This article is available in the following languages:
Trellix CEO, Bryan Palma, explains the critical need for security that’s always learning.
As per Gartner, "XDR is an emerging technology that can offer improved threat prevention, detection and response."
Trellix announced the establishment of the Trellix Advanced Research Center to advance global threat intelligence.
Trellix Advanced Research Center analyzes threat data on ransomware, nation-states, sectors, vectors, LotL, MITRE ATT&CK techniques, and emails.
After December 1, 2024, please log in to the Thrive Portal for support, knowledge articles, tools, and downloads. For information about using the Thrive Portal, view the Trellix Thrive Portal User Guide.
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: |
|