Audit Logs
Palette captures audit logs to track user interaction with the application resources along with the timeline. For certain resources, the system-level modifications are also captured in the audit logs.
The audit log contains information about the resource and the user who performed the action. Each user or system action on a resource has a log type, such as Create, Update, Delete, or Action. Each resource also has a resource type, which you can use to filter the audit logs.
View Audit Logs
Audits can be accessed for the tenant scope and the project scope. The tenant scope audits show all the activity logs across all projects and tenant actions. The project scope audits show the activity logs for the specific project.
-
Log in to Palette.
-
Select a project to view project scope audit logs or select Tenant Admin to view tenant scope audit logs.
- The Project Viewer role with
audit.getandaudit.listpermissions for the selected project are required to access the project scope audit logs. - The Tenant Admin role or the
audit.getandaudit.listpermissions at the tenant scope are required to access the tenant scope audit logs.
- The Project Viewer role with
-
Navigate to the left main menu and select Audit Logs.
-
You can filter audit logs based on user and resource attributes. The following attributes can be used to filter the audit logs.
- Project
- Log Type
- User
- Resource Type
-
You can also download audit logs as CSV files.
Kubeconfig Downloads
Palette records an audit log entry each time someone downloads a kubeconfig file for a cluster or virtual cluster from
the Palette UI or the API. Each entry identifies the user, the cluster, and the file. In each entry, admin kubeconfig
refers to the Admin Kubeconfig file, and user kubeconfig refers to the Kubeconfig file. Palette also records
failed and denied download attempts. To learn about the two files, refer to
Types of Kubeconfig Files.
Palette components also download the admin kubeconfig in some situations, such as during cleanup. These entries show
cluster-agent as the user.
To find these entries, set the Log Type filter to Action and the Resource Type filter to Cluster or Virtual Cluster.
Add Update Note
For certain resources, like cluster profiles, you can associate a custom update note in addition to the generic audit event log. On a successful save of a cluster profile, you will be prompted to provide an update note about the changes made to the profile. This message will be shown when you select an audit log from the list.
Push Audit Trails to Amazon CloudWatch or Splunk
You can push the compliance, management, operational, and risk audit logs to Amazon CloudWatch or Splunk. This enables continuous monitoring, security analysis, resource tracking, and troubleshooting of the workload cluster using the event history.
Prerequisites
- Splunk
- Amazon CloudWatch
Configure a HTTP Event Collector (HEC) in Splunk before configuring a Palette audit trail.
Refer to the Set up and use HTTP Event Collector in Splunk Web guide for more information.
Ensure that the IAM user or the ROOT user role created has the following IAM policy included for Amazon CloudWatch.
{
"Version": "2012-10-17",
"Statement": [
{
"Effect": "Allow",
"Action": [
"logs:DescribeLogGroups",
"logs:CreateLogGroup",
"logs:CreateLogStream",
"logs:PutLogEvents",
"logs:DeleteLogStream",
"logs:DescribeLogStreams"
],
"Resource": ["<CLOUDWATCH-LOG-GROUP-ARN>"]
}
]
}
Enablement
-
Log in to Palette as a tenant admin.
-
Navigate to the left main menu and select Tenant Settings. Then, select Audit Trails from the Infrastructure section.
-
Select Add new Audit Trail. The Add audit trail window appears.
-
Fill in the following details.
- Splunk
- Amazon CloudWatch
- Audit Name: Custom name to identify the logs.
- Type: Choice of monitoring service. Select Splunk.
- HEC endpoint: HEC URL retrieved from the Splunk console.
- Token: HEC token retrieved from the Splunk console.
- Advanced Configuration: Provide optional configuration for log routing and security.
- Index: Route logs to a specific Splunk index. Leave blank to use the token default.
- Source: Set a custom source identifier for easier filtering in Splunk searches. Leave blank to use the default.
- Certificate: Upload your server’s certificate if your Splunk instance uses a self-signed certificate.
- TLS Verification: Enabled by default. Disable if your endpoint uses a self-signed certificate and you choose not to upload it.
- Audit Name: Custom name to identify the logs.
- Type: Choice of monitoring service. Select CloudWatch.
- Group: The log group name obtained from CloudWatch logs for audit trail creation.
- Region: The region of the AWS account.
- Credentials : Use an Access Key and Secret Access Key to validate the AWS account for pushing the audit trails from Palette.
- STS: Use Amazon's unique resource identifier, ARN, to validate the AWS account for pushing the audit trails from Palette.
- Stream (Optional): CloudWatch log stream for audit trail creation.
-
Select Validate to verify your configuration.
-
Select Confirm to complete the audit trail configuration. Audit trails can be edited and deleted using the three-dot Menu.