Versions Compared


  • This line was added.
  • This line was removed.
  • Formatting was changed.

The Black Duck GKE Binary Authorization solution provides the ability to control container deployment into GKE by using attestations tied to Black Duck policies.  The Black Duck Policy Management feature enables you to create rules that govern your use of open source components in your code basecodebase, which can help you reduce open source security, license, and operational risks.  Black Duck's Binary Authorization solution is an add-on to the Synopsys Black Duck Cloud Build Solutionsolution, and  and creates an attestation based on the Black Duck policy violation status. The Black Duck attestation attests that a container has passed Black Duck policy and is ready for deployment.

Are you using Binary Authorization? The Synopsys Cloud Build Scanner can write Container Analysis Notes to an Attestor tied to Black Duck scan. If , a policy  policy violation occurs during a Black Duck scan in CloudBuild,  an attestation will not be created and the image will not be deployable to GKE. 


  • This solution is currently in alpha release.  Early adopters are welcome to provide design input.

  • This documentation is not fully tested and is currently used for design purposes only.

Please send any questions or suggestions to


  • Cloud Source Repositories or another secure repository that contains the source code used to build a container image.

  • Cloud Build, which runs builds and tests, and outputs the container image to a Container Registry or another software registry that stores your built images.

  • Synopsys Black Duck Cloud Build Scan added to Cloud Build when new image versions are built and makes make an attestation if the image passes Black Duck policy.

  • Container Analysis, which stores the attestations for Binary Authorization and the build records from Cloud Build.

  • Binary Authorization, which enforces the policy requiring attestations by Black Duck before a container image can be deployed.

  • Google Kubernetes Engine, which runs the deployed container images on Google Cloud Platform.

Before you begin

There are several steps to prepare your GCP Project, GKE Cluster, and Cloud Build to attest a container image with Black Duck.


  • Cloud Build Service Account.
  • Cloud KMS CryptoKey Decrypter.
  • Service Account Key Admin.
  • Storage Admin.
  • Binary Authorization Attestor Admin.

Create the Attestor for Black Duck and configure a policy that requires Black Duck attestation


  • Fourth Step (gcloud slim) - the storage bucket where the encrypted private key file was stored above.
  • Fifth Step (gsutil) - the KMS keyring and key name used to encrypt the secrets above.
  • Sixth Step (Synopsys CloudBuild Scanner) - Black Duck URL
  • Substitutions:
    • Image Name you're attesting. Will also be the Black Duck project name.
    • Image Tag. Will also be the Black Duck project version. 
    • Name of the Service Account Key, if you're using a different name in Step 3 below.
    • Name of the private Key file from above, if you used a different name.
  • Secrets: 
    • BD_TOKEN - use the base64 encrypted value for the Black Duck API token from the "Before you Begin" section.
    • PRIVATE_KEY_PASSWD - use the base64 encrypted value for the private key passphrase from the ' Before you Begin' section.

Code Block
titleSample build specification YAML to scan and attest an image in GCR
- name: ''
  args: ['pull', '$PROJECT_ID/${_IMAGE_NAME}:${_IMAGE_TAG}'] #Pull the Docker Image you want to attest
- name: ''
  args: ['save', '-o', './${_IMAGE_NAME}.tar', '$PROJECT_ID/${_IMAGE_NAME}:${_IMAGE_TAG}'] #Save the Docker Image to a TAR File
- name: ''
  args: ['iam', 'service-accounts', 'keys', 'create', '${_SA_KEY_FILE}', '--iam-account', '<<Service Account Name>>@$' ] #Create a Service Account Key
- name: ''
  args: [ 'cp', 'gs://<<Storage Bucket Name>>/${_PV_KEY_FILE}.enc', '.'] #Copy the encrypted Private Key file to the Cloud Build Worker
- name: '' #Decrypt all KMS Secrets using the Key Ring and Key Name
  - kms
  - decrypt
  - --ciphertext-file=${_PV_KEY_FILE}.enc
  - --plaintext-file=${_PV_KEY_FILE}
  - --location=global
  - --keyring=<<KMS KeyRing Name>>
  - --key=<<KMS Key Name>>
- name: ''
  secretEnv: [ 'PRIVATE_KEY_PASSWD', 'BD_TOKEN' ]
  - '--blackduck.url'
  - '<<Black Duck URL>>' #The URL of your Black Duck Instance
  - '--blackduck.api.token'
  - '$$BD_TOKEN' #Black Duck API Token decrypted by KMS
  - ''
  - 'true' #Use this option if your instance of Black Duck has a self-signed certificate
  - ''
  - '${_IMAGE_NAME}' #Project Name to map scan to in Black Duck UI
  - ''
  - '${_IMAGE_TAG}' #Project Version to map scan to in Black Duck UI
  - ''
  - '1200' #Set Timeout to prevent Detect from Timing Out while waiting for Policy Check
  - '' # List of Scanners to Run
  - '--detect.source.path' # Target for Signature Scan
  - './${_IMAGE_NAME}.tar'
  - ''
  - 'CRITICAL' #Will not generate an attestation if any CRITICAL policies are violated
  - ''
  - 'blackduck-scan'
  - '--binary.authorization.attestor.private.key.file'
  - '${_PV_KEY_FILE}'
  - '--binary.authorization.image.path'
  - '--binary.authorization.attestor.key.file'
  - '${_SA_KEY_FILE}'
  _SA_KEY_FILE: sa_key.json
  _PV_KEY_FILE: pv_key.pgp
- kmsKeyName: projects/[PROJECT_ID]/locations/global/keyRings/[KEY_RING_NAME]/cryptoKeys/[KEY_NAME]
    BD_TOKEN: <<base64 encoded encrypted Black Duck API Token>>
    PRIVATE_KEY_PASSWD: <<base64 encoded encrypted Private Key Password>>