Pluggable Authentication Modules

Executive Summary

Pluggable Authentication Modules (T1556.003) is a MITRE ATT&CK technique associated with Defense Impairment, Persistence, Credential Access. Adversaries may modify pluggable authentication modules (PAM) to access user credentials or enable otherwise unwarranted access to accounts.

Why Attackers Use It

Attackers use Pluggable Authentication Modules because it provides a reliable way to advance their objective within the Defense Impairment, Persistence, Credential Access tactic, often with a favorable balance of impact versus detectability on Linux, macOS environments. Defenders should assess this behavior in the context of the affected platform and adjacent activity rather than treating it as a standalone indicator.

MITRE Description

Adversaries may modify pluggable authentication modules (PAM) to access user credentials or enable otherwise unwarranted access to accounts. PAM is a modular system of configuration files, libraries, and executable files which guide authentication for many services. The most common authentication module is <code>pam_unix.so</code>, which retrieves, sets, and verifies account authentication information in <code>/etc/passwd</code> and <code>/etc/shadow</code>.(Citation: Apple PAM)(Citation: Man Pam_Unix)(Citation: Red Hat PAM)

Adversaries may modify components of the PAM system to create backdoors. PAM components, such as <code>pam_unix.so</code>, can be patched to accept arbitrary adversary supplied values as legitimate credentials.(Citation: PAM Backdoor)

Malicious modifications to the PAM system may also be abused to steal credentials. Adversaries may infect PAM resources with code to harvest user credentials, since the values exchanged with PAM components may be plain-text since PAM does not store passwords.(Citation: PAM Creds)(Citation: Apple PAM)

Attack Flow

1. Attacker gains the prerequisite access or context described below.
2. Attacker executes Pluggable Authentication Modules to achieve its tactical objective (Defense Impairment, Persistence, Credential Access).
3. Resulting access/data/effect is leveraged to advance the broader attack chain (see Related Techniques).

Prerequisites

• Platform(s): Linux, macOS
• ATT&CK does not define one universal permission requirement for this technique. Establish the required access from the observed implementation and affected platform.

Common Tools

• Tool attribution is implementation-specific. Use ATT&CK procedure examples and local telemetry to identify the binaries, services, scripts, accounts, or cloud resources involved.

Commands

No universal command represents Pluggable Authentication Modules. Capture the exact command line, arguments, parent process, account, host, and execution time from the investigated environment; do not operationalize unverified examples.

Network Traffic

• Network observability is implementation-dependent. Review DNS, proxy, firewall, flow, authentication, and packet telemetry around the activity window, then correlate remote endpoints and protocol behavior with host evidence.

Windows Events

Sysmon Events

Detection Opportunities

No MITRE detection guidance published for this technique.

Relevant ATT&CK Data Sources: N/A

Sigma Rules

A universal Sigma rule would create unreliable results because this technique has no single guaranteed observable. Build detection logic from a documented behavior and supported data source, scope it to the affected platform, and validate it against benign administrative activity before deployment.

Splunk Queries

Start with the data sources named in the detection section. Scope searches by asset, identity, and time window; correlate the primary behavior with preceding access and subsequent actions. A portable query is intentionally not provided where the technique lacks a universal schema or observable.

Investigation Workflow

1. Confirm that the observed behavior is consistent with Pluggable Authentication Modules and rule out expected administrative or application activity.
2. Establish the first-seen time, initiating identity, source system, target system, and affected resources.
3. Collect relevant host, identity, network, cloud, and application telemetry for the surrounding time window.
4. Correlate parent and child activity, remote connections, file or configuration changes, and related ATT&CK techniques.
5. Determine scope by searching for the same observable across peer assets and identities.
6. Preserve volatile evidence and record confidence, assumptions, and telemetry gaps before containment.

Containment

1. Isolate affected host(s)/account(s) identified during investigation.
2. Revoke or rotate any credentials/tokens potentially exposed.
3. Apply the mitigations listed below where not already enforced.
4. Validate no related techniques (see Related Techniques) were chained against the same asset.

Mitigation

• M1032 -- Multi-factor Authentication: Multi-Factor Authentication (MFA) enhances security by requiring users to provide at least two forms of verification to prove their identity before granting access.
• M1026 -- Privileged Account Management: Privileged Account Management focuses on implementing policies, controls, and tools to securely manage privileged accounts (e.g., SYSTEM, root, or administrative accounts).

Related Techniques

• T1014
• T1059.004
• T1140
• T1556
• T1685