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/*}
[[["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-07-01 UTC."],[],[],null,["# Method: organizations.locations.effectiveEventThreatDetectionCustomModules.get\n\n- [HTTP request](#body.HTTP_TEMPLATE)\n- [Path parameters](#body.PATH_PARAMETERS)\n- [Request body](#body.request_body)\n- [Response body](#body.response_body)\n- [Authorization scopes](#body.aspect)\n- [IAM Permissions](#body.aspect_1)\n- [Try it!](#try-it)\n\nGets the effective Event Threat Detection custom module at the given level.\n\nThe difference between an [EffectiveEventThreatDetectionCustomModule](/security-command-center/docs/reference/security-center-management/rest/v1/folders.locations.effectiveEventThreatDetectionCustomModules#EffectiveEventThreatDetectionCustomModule) and an [EventThreatDetectionCustomModule](/security-command-center/docs/reference/security-center-management/rest/v1/folders.locations.eventThreatDetectionCustomModules#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`.\n\n### HTTP request\n\n`GET https://securitycentermanagement.googleapis.com/v1/{name=organizations/*/locations/*/effectiveEventThreatDetectionCustomModules/*}`\n\nThe URL uses [gRPC Transcoding](https://google.aip.dev/127) syntax.\n\n### Path parameters\n\n### Request body\n\nThe request body must be empty.\n\n### Response body\n\nIf successful, the response body contains an instance of [EffectiveEventThreatDetectionCustomModule](/security-command-center/docs/reference/security-center-management/rest/v1/folders.locations.effectiveEventThreatDetectionCustomModules#EffectiveEventThreatDetectionCustomModule).\n\n### Authorization scopes\n\nRequires the following OAuth scope:\n\n- `https://www.googleapis.com/auth/cloud-platform`\n\nFor more information, see the [Authentication Overview](/docs/authentication#authorization-gcp).\n\n### IAM Permissions\n\nRequires the following [IAM](https://cloud.google.com/iam/docs) permission on the `name` resource:\n\n- `securitycentermanagement.effectiveEventThreatDetectionCustomModules.get`\n\nFor more information, see the [IAM documentation](https://cloud.google.com/iam/docs)."]]