Skip to main content

S3 SIEM Setup Runsheet

The Biza log service has permissions to assume a role that has an attached IAM user policy that authorises the role to write to configured customer S3 buckets. Customer bucket requires a matching bucket policy that authorises the assumed Biza log service role to write log data to the bucket.

Additionally, if you plan to use a customer-managed KMS key to encrypt the data written to the bucket (in preference of disabling S3 encryption entirely), you must attach a policy to the key enabling the Biza log writing role access to use the key for encryption.

info

Further background information about the intended configuration can be found here.


Inputs​

To allow Biza to write logs to the specified bucket securely, you must update your policy as provided in the sample below to allow the Biza IAM role from the context relevant to your HaaS Space.

ContextBiza IAM Role
Yellow/Non-productionarn:aws:iam::423623825533:role/BizaSiemAccessYellow
Red/Productionarn:aws:iam::869935064566:role/BizaSiemAccessRed

Additional Information​

The minimum valid policy to enable log writing is applied directly to the bucket itself. For further information on applying policies to S3 buckets, see AWS documentation for adding a bucket policy using the Amazon S3 console. The policy contains a few elements:

  • The first element with Sid EnforceSSL mandates all writes to the bucket must use SSL, ensuring the secure transfer of log information.
  • The second element with Sid AllowBizaPutObject authorises the Biza customer logs role to put objects on all keys under the bucket head and ensures objects are written with an ACL that grants full control to the bucket owner. For more information about Bucket ACL restrictions, see here.
  • The third element with Sid AllowBizaHealthCheck authorises the Biza customer logs role to do a healthcheck on the bucket's availability via the ListBucket operation on the bucket head.

To apply the example policy detailed below to your bucket, substitute the customer-bucket-name text in the resource ARN fields with your bucket name.


Actions​

  1. Review the AWS documentation: Refer to the AWS documentation on adding a bucket policy using the Amazon S3 console.

  2. Access the S3 console: Navigate to the target bucket in the S3 console.

  3. Edit existing S3 access policy: To apply the example policy detailed below to your bucket, substitute the customer-bucket-name text in the resource ARN fields with your bucket name.

  4. Save the policy.

Bucket Policy ​

{
"Version": "2012-10-17",
"Statement": [
{
"Sid": "EnforceSSL",
"Effect": "Deny",
"Principal": {
"AWS": "*"
},
"Action": "s3:*",
"Resource": ["arn:aws:s3:::customer-bucket-name","arn:aws:s3:::customer-bucket-name/*"],
"Condition": {
"Bool": {
"aws:SecureTransport": "false"
}
}
},
{
"Sid": "AllowBizaPutObject",
"Effect": "Allow",
"Principal": {
"AWS": "arn:aws:iam::869935064566:role/BizaSiemAccessRed"
},
"Action": ["s3:PutObject", "s3:PutObjectAcl"],
"Resource": "arn:aws:s3:::customer-bucket-name/*"
},
{
"Sid": "AllowBizaHealthcheck",
"Effect": "Allow",
"Principal": {
"AWS": "arn:aws:iam::869935064566:role/BizaSiemAccessRed"
},
"Action": "s3:ListBucket",
"Resource": "arn:aws:s3:::customer-bucket-name"
}
]
}

Key Policy ​

If you plan to use a customer-managed KMS key to encrypt data written to the S3 bucket, a policy must be applied to the KMS key. See AWS documentation for creating a key policy. An example policy is provided below.

Warning

If you don’t use a customer-managed KMS key to encrypt data, you MUST disable bucket encryption altogether.

{
"Sid": "AllowBizaKeyAccess",
"Effect": "Allow",
"Principal": {
"AWS": "arn:aws:iam::869935064566:role/BizaSiemAccessRed"
},
"Action": [
"kms:Encrypt",
"kms:Decrypt",
"kms:ReEncrypt*",
"kms:GenerateDataKey*",
"kms:DescribeKey"
],
"Resource": "*"
}

Outputs​

  • Bucket Policy Updated: S3 bucket policy now allows Biza to securely write logs and perform health checks.
  • Compliance Confirmed: Policy enforces secure transfers via SSL and sets proper ACL for ownership.
  • Health Check Enabled: Biza can validate bucket availability with listBucket.