Open salrashid123 opened 4 years ago
probably won't need tocheck the logs. PCR0 value from quote/verify should indicate SEV status
the GCP identity document now contains a claim that signals if its runing conf.compute. (it just means its a cc instance)
https://cloud.google.com/compute/docs/instances/verifying-instance-identity#payload
{
"iss": "[TOKEN_ISSUER]",
"iat": [ISSUED_TIME],
"exp": [EXPIRED_TIME],
"aud": "[AUDIENCE]",
"sub": "[SUBJECT]",
"azp": "[AUTHORIZED_PARTY]",
"google": {
"compute_engine": {
"project_id": "[PROJECT_ID]",
"project_number": [PROJECT_NUMBER],
"zone": "[ZONE]",
"instance_id": "[INSTANCE_ID]",
"instance_name": "[INSTANCE_NAME]",
"instance_creation_timestamp": [CREATION_TIMESTAMP],
"instance_confidentiality": [INSTANCE_CONFIDENTIALITY],
"license_id": [
"[LICENSE_1]",
...
"[LICENSE_N]"
]
}
}
}
The tokenserver should also scan StackDriver logs for the TokenClient and check for integrity event logs before returning the secret.
eg. somewhere here add on a check similar to the snippet below.
"bob" will need to grant alice and the tokenServer's service account the
roles/logging.Viewer
role on the tokenclient project.https://cloud.google.com/security/shielded-cloud/automating-responses-integrity-failures