For threats: Indicates a threat that is able to
access, modify, or delete data or execute
unauthorized code within existing resources.
HIGH (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.
MEDIUM (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.
LOW (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.
Enums
Name
Description
SEVERITY_UNSPECIFIED
Default value. This value is unused.
CRITICAL
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.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Hard to understand","hardToUnderstand","thumb-down"],["Incorrect information or sample code","incorrectInformationOrSampleCode","thumb-down"],["Missing the information/samples I need","missingTheInformationSamplesINeed","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-09-04 UTC."],[],[],null,["# Class Severity (0.1.22)\n\nVersion latestkeyboard_arrow_down\n\n- [0.1.22 (latest)](/python/docs/reference/google-cloud-securitycentermanagement/latest/google.cloud.securitycentermanagement_v1.types.SimulatedFinding.Severity)\n- [0.1.20](/python/docs/reference/google-cloud-securitycentermanagement/0.1.20/google.cloud.securitycentermanagement_v1.types.SimulatedFinding.Severity) \n\n Severity(value)\n\nThe severity of the finding. \n\n For threats: Indicates a threat that is able to\n access, modify, or delete data or execute\n unauthorized code within existing resources.\n HIGH (2):\n For vulnerabilities: A high-risk\n vulnerability can be easily discovered and\n exploited in combination with other\n vulnerabilities in order to gain direct access\n and the ability to execute arbitrary code,\n exfiltrate data, and otherwise gain additional\n access and privileges to cloud resources and\n workloads. An example is a database with weak or\n no passwords that is only accessible internally.\n This database could easily be compromised by an\n actor that had access to the internal network.\n\n For threats: Indicates a threat that is able to\n create new computational resources in an\n environment but not able to access data or\n execute code in existing resources.\n MEDIUM (3):\n For vulnerabilities: A medium-risk\n vulnerability could be used by an actor to gain\n access to resources or privileges that enable\n them to eventually (through multiple steps or a\n complex exploit) gain access and the ability to\n execute arbitrary code or exfiltrate data. An\n example is a service account with access to more\n projects than it should have. If an actor gains\n access to the service account, they could\n potentially use that access to manipulate a\n project the service account was not intended to.\n\n For threats: Indicates a threat that is able to\n cause operational impact but may not access data\n or execute unauthorized code.\n LOW (4):\n For vulnerabilities: A low-risk vulnerability\n hampers a security organization's ability to\n detect vulnerabilities or active threats in\n their deployment, or prevents the root cause\n investigation of security issues. An example is\n monitoring and logs being disabled for resource\n configurations and access.\n\n For threats: Indicates a threat that has\n obtained minimal access to an environment but is\n not able to access data, execute code, or create\n resources."]]