Ce contenu n'est pas disponible dans la langue sélectionnée.
Chapter 14. Configuring audit logging
Red Hat Advanced Cluster Security for Kubernetes provides audit logging features that you can use to check all the changes made in Red Hat Advanced Cluster Security for Kubernetes. The audit log captures all the PUT and POST events, which are modifications to Red Hat Advanced Cluster Security for Kubernetes. Use this information to troubleshoot a problem or to keep a record of important events, such as changes to roles and permissions. With audit logging you get a complete picture of all normal and abnormal events that happened on Red Hat Advanced Cluster Security for Kubernetes.
Audit logging is not enabled by default. You must enable audit logging manually.
Currently there is no message delivery guarantee for audit log messages.
14.1. Enabling audit logging
When you enable audit logging, every time there is a modification, Red Hat Advanced Cluster Security for Kubernetes sends an HTTP POST message (in JSON format) to the configured system.
Prerequisites
- Configure Splunk or another webhook receiver to handle Red Hat Advanced Cluster Security for Kubernetes log messages.
-
You must have
writepermission enabled on the Notifiers resource for your role.
Procedure
-
In the RHACS portal, go to Platform Configuration
Integrations. - Scroll down to the Notifier Integrations section and select Generic Webhook or Splunk.
- Fill in the required information and turn on the Enable Audit Logging toggle.
14.2. Sample audit log message
The log message has the following format:
{
"headers": {
"Accept-Encoding": [
"gzip"
],
"Content-Length": [
"586"
],
"Content-Type": [
"application/json"
],
"User-Agent": [
"Go-http-client/1.1"
]
},
"data": {
"audit": {
"interaction": "CREATE",
"method": "UI",
"request": {
"endpoint": "/v1/notifiers",
"method": "POST",
"source": {
"requestAddr": "10.131.0.7:58276",
"xForwardedFor": "8.8.8.8",
},
"sourceIp": "8.8.8.8",
"payload": {
"@type": "storage.Notifier",
"enabled": true,
"generic": {
"auditLoggingEnabled": true,
"endpoint": "http://samplewebhookserver.com:8080"
},
"id": "b53232ee-b13e-47e0-b077-1e383c84aa07",
"name": "Webhook",
"type": "generic",
"uiEndpoint": "https://localhost:8000"
}
},
"status": "REQUEST_SUCCEEDED",
"time": "2019-05-28T16:07:05.500171300Z",
"user": {
"friendlyName": "John Doe",
"role": {
"globalAccess": "READ_WRITE_ACCESS",
"name": "Admin"
},
"username": "john.doe@example.com"
}
}
}
}The source IP address of the request is displayed in the source parameters, which makes it easier for you to investigate audit log requests and identify their origin.
To determine the source IP address of a request, RHACS uses the following parameters:
-
xForwardedFor: The X-Forwarded-For header. -
requestAddr: The remote address header. -
sourceIp: The IP address of the HTTP request.
The determination of the source IP address depends on how you expose Central externally. You can consider the following options:
- If you expose Central behind a load balancer, for example, if you are running Central on Google Kubernetes Engine (GKE) or Amazon Elastic Kubernetes Service (Amazon EKS) by using the Kubernetes External Load Balancer service type, see Preserving the client source IP.
- If you expose Central behind an Ingress Controller that forwards requests by using the X-Forwarded-For header, you do not need to make any configuration changes.
- If you expose Central with a TLS passthrough route, you cannot determine the source IP address of the client. A cluster-internal IP address is displayed in the source parameters as the source IP address of the client.
