- HTTP request
- Path parameters
- Request body
- Response body
- Authorization scopes
- IAM Permissions
- Try it!
Gets the effective Event Threat Detection custom module at the given level.
The difference between an EffectiveEventThreatDetectionCustomModule
and an EventThreatDetectionCustomModule
is that the fields for an EffectiveEventThreatDetectionCustomModule
are computed from ancestors if needed. For example, the enablement state for an EventThreatDetectionCustomModule
can be ENABLED
, DISABLED
, or INHERITED
. In contrast, the enablement state for an EffectiveEventThreatDetectionCustomModule
is always computed as ENABLED
or DISABLED
.
HTTP request
GET https://securitycentermanagement.googleapis.com/v1/{name=organizations/*/locations/*/effectiveEventThreatDetectionCustomModules/*}
The URL uses gRPC Transcoding syntax.
Path parameters
Parameters | |
---|---|
name |
Required. The resource name of the Event Threat Detection custom module, in one of the following formats:
|
Request body
The request body must be empty.
Response body
If successful, the response body contains an instance of EffectiveEventThreatDetectionCustomModule
.
Authorization scopes
Requires the following OAuth scope:
https://www.googleapis.com/auth/cloud-platform
For more information, see the Authentication Overview.
IAM Permissions
Requires the following IAM permission on the name
resource:
securitycentermanagement.effectiveEventThreatDetectionCustomModules.get
For more information, see the IAM documentation.