Last reviewed:
T1078 covers the abuse of legitimate credentials to enter, persist, and operate inside an environment: the technique behind the SolarWinds, Snowflake, and Okta-era compromises that shaped the cloud-breach playbook of recent years. It has the broadest detection surface in DCV's catalog, anchored by GuardDuty's UnauthorizedAccess:IAMUser/ConsoleLogin and complemented by FSBP IAM controls and GCP MFA-not-enforced findings. T1078 detection density is what cloud SOC maturity actually looks like.
Adversaries may obtain and abuse credentials of existing accounts as a means of gaining Initial Access, Persistence, Privilege Escalation, or Defense Evasion. Compromised credentials may be used to bypass access controls placed on various resources on systems within the network and may even be used for persistent access to remote systems and externally available services, such as VPNs, Outlook Web Access, network devices, and remote desktop. Compromised credentials may also grant an adversary increased privilege to specific systems or access to restricted areas of the network. Adversaries may choose not to use malware or tools in conjunction with the legitimate access those credentials provide to make it harder to detect their presence.
In some cases, adversaries may abuse inactive accounts: for example, those belonging to individuals who are no longer part of an organization. Using these accounts may allow the adversary to evade detection, as the original account user will not be present to identify any anomalous activity taking place on their account.
The overlap of permissions for local, domain, and cloud accounts across a network of systems is of concern because the adversary may be able to pivot across accounts and systems to reach a high level of access (i.e., domain or enterprise administrator) to bypass access controls set within the enterprise.
Platforms: Containers, ESXi, IaaS, Identity Provider, Linux, macOS, Network Devices, Office Suite, SaaS, Windows.
DCV maps 60 detections across 2 cloud providers to T1078. Coverage by source:
| Source | Cloud | Findings mapped | Avg confidence |
|---|---|---|---|
| AWS Security Hub | AWS | 34 | 0.84 |
| AWS GuardDuty | AWS | 25 | 0.86 |
| GCP Chronicle | GCP | 1 | 0.85 |
CloudSigma has coverage metadata for 60 T1078 rules across 9 platforms. The linked platform page remains the canonical rule surface; this page will embed an example after a rule clears the public embed bar.
CloudSigma has coverage metadata for T1078, but no public example rule clears the embed bar for this page yet. Generate a fresh starting-point rule in CloudSigma from the relevant advisory or threat-research input, then validate it against your local telemetry before enabling it in production.
T1078 covers the abuse of legitimate credentials to enter, persist, and operate inside an environment: the technique behind the SolarWinds, Snowflake, and Okta-era compromises that shaped the cloud-breach playbook of recent years. It has the broadest detection surface in DCV's catalog, anchored by GuardDuty's UnauthorizedAccess:IAMUser/ConsoleLogin and complemented by FSBP IAM controls and GCP MFA-not-enforced findings. T1078 detection density is what cloud SOC maturity actually looks like.
DCV maps 60 cloud-native detections to T1078 across 2 cloud providers, drawn from AWS GuardDuty, AWS Security Hub and GCP Chronicle.
T1078 is part of MITRE ATT&CK TA0001 Initial Access: How adversaries get into the environment.
T1078 requires multi-event correlation that exceeds a single Sigma rule's structure. CloudSigma can generate a starting-point rule from a CVE, vulnerability disclosure, or threat-research blog post that exercises T1078-style abuse; pair it with SIEM-side correlation logic before enabling in production.