Google Cloud Security Command Center v1 API - Class Finding (3.14.0)

Reference documentation and code samples for the Google Cloud Security Command Center v1 API class Finding.

Security Command Center finding.

A finding is a record of assessment data like security, risk, health, or privacy, that is ingested into Security Command Center for presentation, notification, analysis, policy testing, and enforcement. For example, a cross-site scripting (XSS) vulnerability in an App Engine application is a finding.

Access details associated with the finding, such as more information on the caller, which method was accessed, and from where.

Represents an application associated with the finding.

The canonical name of the finding. It's either "organizations/{organization_id}/sources/{source_id}/findings/{finding_id}", "folders/{folder_id}/sources/{source_id}/findings/{finding_id}" or "projects/{project_number}/sources/{source_id}/findings/{finding_id}", depending on the closest CRM ancestor of the resource associated with the finding.

The additional taxonomy group within findings from a given source. This field is immutable after creation time. Example: "XSS_FLASH_INJECTION"

Cloud DLP data profile that is associated with the finding.

Cloud Data Loss Prevention (Cloud DLP) inspection results that are associated with the finding.

Contains compliance information for security standards associated to the finding.

Contains information about the IP connection associated with the finding.

Output only. Map containing the points of contact for the given finding. The key represents the type of contact, while the value contains a list of all the contacts that pertain. Please refer to: https://cloud.google.com/resource-manager/docs/managing-notification-contacts#notification-categories

{
  "security": {
    "contacts": [
      {
        "email": "person1@company.com"
      },
      {
        "email": "person2@company.com"
      }
    ]
  }
}

Containers associated with the finding. This field provides information for both Kubernetes and non-Kubernetes containers.

The time at which the finding was created in Security Command Center.

Database associated with the finding.

Contains more details about the finding.

The time the finding was first detected. If an existing finding is updated, then this is the time the update occurred. For example, if the finding represents an open firewall, this property captures the time the detector believes the firewall became open. The accuracy is determined by the detector. If the finding is later resolved, then this time reflects when the finding was resolved. This must not be set to a value greater than the current timestamp.

Represents exfiltrations associated with the finding.

Output only. Third party SIEM/SOAR fields within SCC, contains external system information and external system finding fields.

The URI that, if available, points to a web page outside of Security Command Center where additional information about the finding can be found. This field is guaranteed to be either empty or a well formed URL.

File associated with the finding.

The class of the finding.

FindingName-typed view over the Name resource name property.

Represents IAM bindings associated with the finding.

Represents what's commonly known as an indicator of compromise (IoC) in computer forensics. This is an artifact observed on a network or in an operating system that, with high confidence, indicates a computer intrusion. For more information, see Indicator of compromise.

Signature of the kernel rootkit.

Kubernetes resources associated with the finding.

MITRE ATT&CK tactics and techniques related to this finding. See: https://attack.mitre.org

Unique identifier of the module which generated the finding. Example: folders/598186756061/securityHealthAnalyticsSettings/customModules/56799441161885

Indicates the mute state of a finding (either muted, unmuted or undefined). Unlike other attributes of a finding, a finding provider shouldn't set the value of mute.

Records additional information about the mute operation, for example, the mute configuration that muted the finding and the user who muted the finding.

Output only. The most recent time this finding was muted or unmuted.

The relative resource name of the finding. Example: "organizations/{organization_id}/sources/{source_id}/findings/{finding_id}", "folders/{folder_id}/sources/{source_id}/findings/{finding_id}", "projects/{project_id}/sources/{source_id}/findings/{finding_id}".

Steps to address the finding.

The relative resource name of the source the finding belongs to. See: https://cloud.google.com/apis/design/resource_names#relative_resource_name This field is immutable after creation time. For example: "organizations/{organization_id}/sources/{source_id}"

Output only. The human readable display name of the finding source such as "Event Threat Detection" or "Security Health Analytics".

Represents operating system processes associated with the Finding.

For findings on Google Cloud resources, the full resource name of the Google Cloud resource this finding is for. See: https://cloud.google.com/apis/design/resource_names#full_resource_name When the finding is for a non-Google Cloud resource, the resourceName can be a customer or partner defined string. This field is immutable after creation time.

Output only. User specified security marks. These marks are entirely managed by the user and come from the SecurityMarks resource that belongs to the finding.

The severity of the finding. This field is managed by the source that writes the finding.

Source specific properties. These properties are managed by the source that writes the finding. The key names in the source_properties map must be between 1 and 255 characters, and must start with a letter and contain alphanumeric characters or underscores only.

The state of the finding.

Represents vulnerability-specific fields like CVE and CVSS scores. CVE stands for Common Vulnerabilities and Exposures (https://cve.mitre.org/about/)