7.9.5. Kubernetes API ログと Advanced Audit ロギングの出力の比較
Advanced Audit ロギングの価値を理解するには、Kubernetes API Server Audit Log と Advanced Audit ロギングの出力結果を比較してください。
Kubernetes API サーバー監査ログ
{
"kind": "Event",
"apiVersion": "audit.k8s.io/v1",
"level": "Metadata",
"auditID": "4d434cd4-xxxx-xxxx-xxxx-2d9aa46292ce",
"stage": "ResponseComplete",
"requestURI": "/api/v1/namespaces/test-namespace/pods/test-pod/exec?command=sh&command=-c&command=touch+/tmp/testfile.txt&container=nginx",
"verb": "create",
"user": {
"username": "kube:admin",
"groups": ["system:cluster-admins", "system:authenticated"]
},
"sourceIPs": ["xxx.xxx.xxx.xxx"],
"userAgent": "oc/4.19.0 (linux/amd64)",
"objectRef": {
"resource": "pods",
"namespace": "test-namespace",
"name": "test-pod",
"subresource": "exec"
},
"responseStatus": {
"code": 101
},
"requestReceivedTimestamp": "2026-02-16T14:01:06.056518Z",
"annotations": {
"authorization.k8s.io/decision": "allow",
"authorization.k8s.io/reason": "RBAC: allowed by ClusterRoleBinding...",
"execmetadata.spo.io/SPO_EXEC_REQUEST_UID": "aec3e0e1-xxxx-xxxx-xxxx-a7c58241f1a9"
}
}
相関キーは、上記のファイルの最終行にある SPO_EXEC_REQUEST_UID です。
高度な監査ロギング出力
{
"auditID": "d586679d-xxxx-xxxx-xxxx-9dc8ab273065",
"cmdLine": "touch /tmp/testfile.txt ", // Linux command with arguments
"executable": "/bin/dash",
"gid": 0,
"node": {
"name": "worker-1"
},
"pid": 144968,
"requestUID": "aec3e0e1-xxxx-xxxx-xxxx-a7c58241f1a9", // Correlation key
"resource": {
"container": "nginx",
"namespace": "test-namespace",
"pod": "test-pod"
},
"syscalls": ["execve"],
"timestamp": "2026-02-16T14:01:07.000Z",
"uid": 0,
"version": "spo/v1_alpha"
}