# Google Cloud Security Center Management V1 Client - Class Severity (1.4.0)

1.4.0 (latest) 1.3.3 1.2.1 1.1.3 1.0.0 0.3.2 0.2.7 0.1.0 Reference documentation and code samples for the Google Cloud Security Center Management V1 Client class Severity.

The severity of the finding.

Protobuf type `google.cloud.securitycentermanagement.v1.SimulatedFinding.Severity`

## Namespace

Google \\ Cloud \\ SecurityCenterManagement \\ V1 \\ SimulatedFinding

## Methods

### static::name

| **Parameter** ||
|---|---|
| **Name** | **Description** |
| `value` | `mixed` |

### static::value

| **Parameter** ||
|---|---|
| **Name** | **Description** |
| `name` | `mixed` |

## Constants

### SEVERITY_UNSPECIFIED

    Value: 0

Default value. This value is unused.

Generated from protobuf enum `SEVERITY_UNSPECIFIED = 0;`

### CRITICAL

    Value: 1

For vulnerabilities: A critical vulnerability is easily discoverable by
an external actor, exploitable, and results in the direct ability to
execute arbitrary code, exfiltrate data, and otherwise gain additional
access and privileges to cloud resources and workloads. Examples include
publicly accessible unprotected user data and public SSH access with weak
or no passwords.

For threats: Indicates a threat that is able to access, modify, or delete
data or execute unauthorized code within existing resources.

Generated from protobuf enum `CRITICAL = 1;`

### HIGH

    Value: 2

For vulnerabilities: A high-risk vulnerability can be easily discovered
and exploited in combination with other vulnerabilities in order to gain
direct access and the ability to execute arbitrary code, exfiltrate data,
and otherwise gain additional access and privileges to cloud resources
and workloads. An example is a database with weak or no passwords that is
only accessible internally. This database could easily be compromised by
an actor that had access to the internal network.

For threats: Indicates a threat that is able to create new computational
resources in an environment but not able to access data or execute code
in existing resources.

Generated from protobuf enum `HIGH = 2;`

### MEDIUM

    Value: 3

For vulnerabilities: A medium-risk vulnerability could be used by an
actor to gain access to resources or privileges that enable them to
eventually (through multiple steps or a complex exploit) gain access and
the ability to execute arbitrary code or exfiltrate data. An example is a
service account with access to more projects than it should have. If an
actor gains access to the service account, they could potentially use
that access to manipulate a project the service account was not intended
to.

For threats: Indicates a threat that is able to cause operational impact
but may not access data or execute unauthorized code.

Generated from protobuf enum `MEDIUM = 3;`

### LOW

    Value: 4

For vulnerabilities: A low-risk vulnerability hampers a security
organization's ability to detect vulnerabilities or active threats in
their deployment, or prevents the root cause investigation of security
issues. An example is monitoring and logs being disabled for resource
configurations and access.

For threats: Indicates a threat that has obtained minimal access to an
environment but is not able to access data, execute code, or create
resources.

Generated from protobuf enum `LOW = 4;`