Stay organized with collections
Save and categorize content based on your preferences.
This document describes a threat finding type in Security Command Center. Threat findings are generated by
threat detectors when they detect
a potential threat in your cloud resources. For a full list of available threat findings, see Threat findings index.
Overview
A local reconnaissance tool was executed within the container. This suggests
that a potential attacker is gathering information about the container
environment, such as network configurations, active processes, or mounted file
systems. Attackers often use this type of tool in the early stages of an attack
to map out potential targets and identify weaknesses. This is a medium-severity
finding, because it indicates that the attacker is actively probing the
container for further exploitation opportunities.
Open the Execution: Local Reconnaissance Tool Execution finding as directed
in Reviewing
findings.
Review the details on the Summary and JSON tabs.
On the Summary tab, review the information in the following sections.
What was detected, especially the following fields:
Program binary: the absolute path of the executed binary
Arguments: the arguments passed during binary execution
Affected resource, especially the following fields:
Resource full name: the full resource
name of the affected Cloud Run
resource
On the JSON tab, note the following fields.
resource:
project_display_name: the name of the project that contains
affected Cloud Run resource
finding:
processes:
binary:
path: the full path of the executed binary
args: the arguments that were provided when the binary was executed
Identify other findings that occurred at a similar time for the affected
container. Related findings might indicate that this activity was malicious,
instead of a failure to follow best practices.
Review the settings of the affected container.
Check the logs for the affected container.
Research attack and response methods
Review the MITRE ATT&CK framework entry for this finding type:
Active Scanning.
To develop a response plan, combine your investigation results with MITRE
research.
[[["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-08-29 UTC."],[],[],null,["| Premium and Enterprise [service tiers](/security-command-center/docs/service-tiers)\n\nThis document describes a threat finding type in Security Command Center. Threat findings are generated by\n[threat detectors](/security-command-center/docs/concepts-security-sources#threats) when they detect\na potential threat in your cloud resources. For a full list of available threat findings, see [Threat findings index](/security-command-center/docs/threat-findings-index).\n\nOverview\n\nA local reconnaissance tool was executed within the container. This suggests\nthat a potential attacker is gathering information about the container\nenvironment, such as network configurations, active processes, or mounted file\nsystems. Attackers often use this type of tool in the early stages of an attack\nto map out potential targets and identify weaknesses. This is a medium-severity\nfinding, because it indicates that the attacker is actively probing the\ncontainer for further exploitation opportunities.\n\nDetection service\n\n[Cloud Run Threat Detection](/security-command-center/docs/cloud-run-threat-detection-overview)\n\nHow to respond\n\nTo respond to this finding, do the following:\n\nReview finding details\n\n1. Open the `Execution: Local Reconnaissance Tool Execution` finding as directed\n in [Reviewing\n findings](/security-command-center/docs/how-to-investigate-threats#reviewing_findings).\n Review the details on the **Summary** and **JSON** tabs.\n\n2. On the **Summary** tab, review the information in the following sections.\n\n - **What was detected** , especially the following fields:\n - **Program binary**: the absolute path of the executed binary\n - **Arguments**: the arguments passed during binary execution\n - **Affected resource** , especially the following fields:\n - **Resource full name** : the [full resource\n name](/apis/design/resource_names) of the affected Cloud Run resource\n3. On the **JSON** tab, note the following fields.\n\n - `resource`:\n - `project_display_name`: the name of the project that contains affected Cloud Run resource\n - `finding`:\n - `processes`:\n - `binary`:\n - `path`: the full path of the executed binary\n - `args`: the arguments that were provided when the binary was executed\n4. Identify other findings that occurred at a similar time for the affected\n container. Related findings might indicate that this activity was malicious,\n instead of a failure to follow best practices.\n\n5. Review the settings of the affected container.\n\n6. Check the logs for the affected container.\n\nResearch attack and response methods\n\n1. Review the MITRE ATT\\&CK framework entry for this finding type: [Active Scanning](https://attack.mitre.org/techniques/T1595/).\n2. To develop a response plan, combine your investigation results with MITRE research.\n\nImplement your response\n\nFor response recommendations, see [Respond to Cloud Run threat\nfindings](/security-command-center/docs/respond-cloud-run-threats).\n\nWhat's next\n\n- Learn [how to work with threat\n findings in Security Command Center](/security-command-center/docs/how-to-investigate-threats).\n- Refer to the [Threat findings index](/security-command-center/docs/threat-findings-index).\n- Learn how to [review a\n finding](/security-command-center/docs/how-to-investigate-threats#reviewing_findings) through the Google Cloud console.\n- Learn about the [services that\n generate threat findings](/security-command-center/docs/concepts-security-sources#threats)."]]