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
An attempt was made to modify the ld.so.preload file. Changes to ld.so.preload can be used by attackers to preload malicious shared libraries into a system's library set. An attacker could use this to hijack the execution flow by loading their own libraries during program execution, potentially leading to privilege escalation or evasion of defense mechanisms. This is a file monitoring detector and has specific GKE version requirements. This detector is disabled by default. For instructions on how to enable it, see Testing Container Threat Detection.
Container Threat Detection is the source of this finding.
How to respond
To respond to this finding, do the following:
Review finding details
Open the
Persistence: Modify ld.so.preloadfinding as directed in Reviewing findings. Review the details in the Summary and JSON tabs.Identify other findings that occurred at a similar time for this resource. Related findings might indicate that this activity was malicious, instead of a failure to follow best practices.
Review the settings of the affected resource.
Check the logs for the affected resource.
Research attack and response methods
Review the MITRE ATT&CK framework entry for this finding type: Persistence.
What's next
- Learn how to work with threat findings in Security Command Center.
- Refer to the Threat findings index.
- Learn how to review a finding through the Google Cloud console.
- Learn about the services that generate threat findings.