Live Active security incident? Get immediate response
MITRE ATT&CK® Detection Strategy

DET0223: Detection of Adversary Abuse of Software Deployment Tools

This detection strategy matters because software deployment and configuration management platforms are built to run commands broadly and quickly. If an adv...

EnterpriseDET0223Detection StrategyObject v1.0 Modified
Glexia's Take

Analyst context for executives and security teams

Analyst confidence Medium

This detection strategy matters because software deployment and configuration management platforms are built to run commands broadly and quickly. If an adversary abuses them, normal administrative capability can become a path for execution and lateral movement across enterprise, cloud, SaaS, network device, Linux, and macOS environments. Leaders should treat coverage of these tools as a resilience issue, not only a SOC rule-writing task.

Executive priority

Prioritize this area where centralized deployment tools or CI/CD-integrated management platforms can affect large parts of the environment. The key business question is whether the organization can distinguish approved administration from unauthorized or suspicious use quickly enough to contain lateral movement and preserve operational continuity. Evidence from these controls can also support audit, change-management, incident response, and privileged access governance discussions.

Technical view

DET0223 is linked to ATT&CK technique T1072, Software Deployment Tools, under execution and lateral movement. Because the official detection text is not provided, defenders should validate coverage around the administrative control plane and the endpoints or services receiving actions. Focus on whether deployment jobs, command execution, package pushes, configuration changes, account usage, and resulting host activity can be correlated to approved change records and expected administrator behavior.

Likely telemetry

  • Software deployment and configuration management job logs
  • Administrator and service account authentication records
  • Authorization and role-change events for deployment platforms
  • Endpoint process creation and script execution events on managed Linux and macOS systems
  • Cloud, SaaS, and device-management audit logs where deployment tools operate

Detection direction

  • Baseline normal deployment activity by tool, administrator, service account, target group, timing, and change window.
  • Tune for unusual deployment scope, unexpected target platforms, out-of-cycle pushes, new or modified deployment jobs, and commands inconsistent with routine administration.
  • Correlate platform-side actions with endpoint or managed-service outcomes to avoid relying only on console logs.
  • Review false positives from patching, emergency changes, software rollouts, and infrastructure automation before escalating as malicious.
  • Validate that logging covers the related platforms named for T1072: Linux, macOS, Network Devices, and SaaS, where these are present in the local environment.

Mitigation priorities

  • Inventory software deployment, configuration management, and CI/CD-integrated administration tools with their managed targets.
  • Restrict privileged access and service account permissions to the minimum required for deployment operations.
  • Require documented approval and traceability for deployment jobs, especially broad-scope or emergency actions.
  • Ensure administrative actions and endpoint outcomes are logged and retained for investigation.
  • Segment or constrain management paths where feasible so compromise of one tool or account does not automatically enable broad lateral movement.
Analyst notes and limits

The ATT&CK object is a detection strategy for adversary abuse of software deployment tools and is related to T1072. The value for defenders is in validating visibility across the management plane and the execution targets, then tying activity back to authorized administration. Local tool inventory is essential because the object names example categories such as enterprise deployment suites, cloud systems managers, mobile/device management, and CI/CD-integrated platforms, but does not prescribe specific analytics.

The supplied object has no official description, no official detection text, no tactics, and no platforms directly on the detection strategy itself. Platform and tactic context comes from the relationship to T1072 only. This take does not assert active exploitation, attribution, or guaranteed detection coverage; organizations must confirm applicability against their own deployment tools, logging, and change-management processes.

Official MITRE ATT&CK definition

Detection of Adversary Abuse of Software Deployment Tools

No official description is available in the imported ATT&CK source object.

View the same entry on attack.mitre.org (MITRE-hosted reference; in-page links above use the Glexia ATT&CK library.)

Glexia analysis

How security teams should use this page

Treat this object as behavior context, not an attribution claim. Validate the related groups, software, data sources, and mitigations against official ATT&CK relationships and your own telemetry before making control-coverage decisions.

ATT&CK relationship table

Techniques used

This mirrors the MITRE pattern of making group, software, campaign, and technique relationships scannable. Relationship notes come from mirrored ATT&CK relationship text when available.

1 rows
Domain ID Name Relationship / procedure
Enterprise T1072 Software Deployment Tools This object detects Software Deployment Tools.
Relationship explorer

All related ATT&CK context

Change history

Object version and sync metadata

The fields below describe the current mirrored snapshot. When Glexia retains multiple ATT&CK source imports, you can open the table to compare the same object across releases (hashes and MITRE timestamps). For MITRE’s own release notes and roadmap, see ATT&CK resources — Updates .

ATT&CK release
19.1
Object version
1.0
Created
Modified
Raw hash
b67558f194fc2877...
Imported snapshots across ATT&CK releases (1)
Release Bundle imported Object version Modified Status Raw hash
19.1 1.0 Current bundle b67558f194fc…
Raw source

Mirrored ATT&CK source object

The raw object is retained through the mirrored ATT&CK source bundle and object hash. The raw endpoint returns the exact object from the mirrored bundle when available.

Source references

External references and citations

MITRE external references are preserved separately from Glexia analysis so citations remain traceable to their original source records.

  1. [1]
    mitre-attack DET0223
    Open source URL
Source and licensing

Source: MITRE ATT&CK®. © 2026 The MITRE Corporation. This work is reproduced and distributed with the permission of The MITRE Corporation. MITRE ATT&CK and ATT&CK are registered trademarks of The MITRE Corporation. Glexia is not affiliated with or endorsed by MITRE.