> [!NOTE]
> Premium and Enterprise (Deprecated) [service tiers](https://docs.cloud.google.com/security-command-center/docs/service-tiers.md.txt)

> [!CAUTION]
> The Security Command Center Enterprise service tier will shut down on May 21, 2027. If your organization uses the Enterprise service tier, then the organization will automatically move to the Premium service tier on or after May 21, 2027. Contact your account representative or a [Google Cloud sales specialist](https://cloud.google.com/contact) if you have questions.

This document describes a threat finding type in Security Command Center. Threat findings are generated by
[threat detectors](https://docs.cloud.google.com/security-command-center/docs/concepts-security-sources.md.txt#threats) when they detect
a potential threat in your cloud resources. For a full list of available threat findings, see [Threat findings index](https://docs.cloud.google.com/security-command-center/docs/threat-findings-index.md.txt).

## Overview

One of the binaries or configuration files in the `pam.d` directory
was modified. Pluggable authentication modules (PAM) are widely used for
authentication in Linux. Attackers might modify the binaries or configuration
files to establish persistent access.

This is a file monitoring detector and it
has [specific GKE version requirements](https://docs.cloud.google.com/security-command-center/docs/how-to-use-container-threat-detection.md.txt#gke-version).

This detector is disabled by default. For instructions on how to enable it,
see [Testing
Container Threat Detection](https://docs.cloud.google.com/security-command-center/docs/how-to-test-container-threat-detection).

[Container Threat Detection](https://docs.cloud.google.com/security-command-center/docs/concepts-container-threat-detection-overview.md.txt) is the source
of this finding.

## How to respond

To respond to this finding, do the following:

### Review finding details

1. Open the `Collection: Pam.d Modification` finding as directed in
   [Reviewing findings](https://docs.cloud.google.com/security-command-center/docs/how-to-investigate-threats.md.txt#reviewing_findings).
   Review the details in the **Summary** and **JSON** tabs.

2. 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.

3. Review the settings of the affected resource.

4. Check the logs for the affected resource.

### Research attack and response methods

Review the MITRE ATT\&CK framework entry for this finding type:
[Collection](https://attack.mitre.org/tactics/TA0009/).

## What's next

- Learn [how to work with threat
  findings in Security Command Center](https://docs.cloud.google.com/security-command-center/docs/how-to-investigate-threats).
- Refer to the [Threat findings index](https://docs.cloud.google.com/security-command-center/docs/threat-findings-index.md.txt).
- Learn how to [review a
  finding](https://docs.cloud.google.com/security-command-center/docs/how-to-investigate-threats#reviewing_findings) through the Google Cloud console.
- Learn about the [services that
  generate threat findings](https://docs.cloud.google.com/security-command-center/docs/concepts-security-sources#threats).