Skip to content

Latest commit

 

History

History
64 lines (38 loc) · 1.9 KB

google_logging_project_sink.md

File metadata and controls

64 lines (38 loc) · 1.9 KB
title platform
About the google_compute_zone Resource
gcp

google_logging_project_sink

Use the google_logging_project_sink InSpec audit resource to test properties of a single GCP logging project sink.


Syntax

A google_logging_project_sink resource block declares the tests for a single GCP logging project sink by project and sink name.

describe google_logging_project_sink(project: 'chef-inspec-gcp',  sink: 'sink-name-abcd') do
  it { should exist }
  its('name') { should eq 'sink-name-abcd' }
end

Examples

The following examples show how to use this InSpec audit resource.

Test that a GCP project logging sink destination is correct

describe google_logging_project_sink(project: 'chef-inspec-gcp',  sink: 'sink-name-abcd') do
  its('destination') { should eq 'storage.googleapis.com/gcp-inspec-logging-bucket' }
end

Test that a GCP project logging sink filter is correct

describe google_logging_project_sink(project: 'chef-inspec-gcp',  sink: 'sink-name-abcd') do
  its('filter') { should eq "resource.type = gce_instance AND resource.labels.instance_id = \"12345678910123123\"" }
end

Test a GCP project logging sink output version format

describe google_logging_project_sink(project: 'chef-inspec-gcp',  sink: 'sink-name-abcd') do
  its('output_version_format') { should eq "V2" }
end

Test a GCP project logging sink writer identity is as expected

describe google_logging_project_sink(project: 'chef-inspec-gcp',  sink: 'sink-name-abcd') do
  its('writer_identity') { should eq "serviceAccount:my-logging-service-account.iam.gserviceaccount.com" }
end

Properties

  • destination, filter, name, output_version_format, writer_identity

GCP Permissions

Ensure the Stackdriver Logging API is enabled for the project.