Method: projects.locations.effectiveEventThreatDetectionCustomModules.get

• HTTP request
• Path parameters
• Request body
• Response body
• Authorization scopes
• IAM Permissions
• Try it!

Gets an effective ETD custom module. Retrieves the effective module at the given level. The difference between an EffectiveCustomModule and a CustomModule is that the fields for an EffectiveCustomModule are computed from ancestors if needed. For example, the enablementState for a CustomModule can be either ENABLED, DISABLED, or INHERITED. Where as the enablementState for an EffectiveCustomModule is always computed to ENABLED or DISABLED (the effective enablementState).

HTTP request

GET https://securitycentermanagement.googleapis.com/v1/{name=projects/*/locations/*/effectiveEventThreatDetectionCustomModules/*}

The URL uses gRPC Transcoding syntax.

Path parameters

Parameters

name

string Required. The resource name of the ETD custom module. Its format is: "organizations/{organization}/locations/{location}/effectiveEventThreatDetectionCustomModules/{effective_event_threat_detection_custom_module}". "folders/{folder}/locations/{location}/effectiveEventThreatDetectionCustomModules/{effective_event_threat_detection_custom_module}". "projects/{project}/locations/{location}/effectiveEventThreatDetectionCustomModules/{effective_event_threat_detection_custom_module}".

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.