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

AN0133: Analytic 0133

Detects attempts to clear RDP/network history and modify network configuration artifacts through command execution, registry key deletion, firewall rule changes, and suspicious file deletions (e.g., Default.rdp, registry edits to Terminal Server Client keys).

EnterpriseAN0133AnalyticObject v1.0 Modified
Glexia's Take

Analyst context for executives and security teams

Analyst confidence Medium

AN0133 is a Windows detection analytic focused on attempts to erase or alter traces of Remote Desktop Protocol (RDP) and network configuration activity. For leaders, the value is not just catching a cleanup command; it is validating whether the organization can see evidence tampering around remote access, firewall changes, registry deletions, and removal of files such as Default.rdp that may be important during incident response.

Executive priority

Prioritize this analytic where Windows remote administration and RDP are material to operations. It supports incident decision-making and audit readiness by testing whether teams can preserve and detect changes to artifacts commonly needed to reconstruct remote access activity. Because ATT&CK provides no tactic mapping, relationship context, or formal detection logic for this object, treat it as a control-validation prompt rather than a complete detection package.

Technical view

SOC and IR teams should validate visibility into Windows command execution, registry key deletion or modification affecting Terminal Server Client artifacts, firewall rule changes, network configuration changes, and suspicious deletion of RDP-related files such as Default.rdp. The analytic is scoped to Windows. Since no official detection query is supplied, teams should build or review local logic around combinations of command-line activity, registry operations, file deletion events, and firewall configuration changes, then tune against legitimate administrative activity.

Likely telemetry

  • Windows process creation and command-line telemetry
  • Windows registry modification and deletion telemetry, especially Terminal Server Client-related keys
  • Windows firewall rule change events or equivalent host configuration logs
  • File deletion telemetry for RDP-related artifacts such as Default.rdp
  • Endpoint detection and response alerts or raw endpoint event data

Detection direction

  • Confirm that command execution, registry activity, firewall changes, and file deletion events are collected from relevant Windows systems.
  • Correlate artifact-clearing behavior with recent or suspicious remote access activity when local telemetry allows, rather than alerting on a single benign administrative action alone.
  • Tune for known administrative scripts, helpdesk workflows, system hardening tasks, and endpoint cleanup tools that may legitimately modify firewall rules or remove RDP history artifacts.
  • Validate retention: these events may be most useful after an incident, so short log retention can create a major blind spot.
  • Because MITRE provides no official detection logic for AN0133, document local assumptions, event IDs, data sources, and test cases used to operationalize it.

Mitigation priorities

  • Restrict and govern who can modify Windows firewall rules, registry keys, and remote access configuration artifacts.
  • Use change management or privileged access controls for administrative actions that alter network or RDP-related settings.
  • Ensure endpoint logging and retention are sufficient to preserve evidence of registry deletion, command execution, and file deletion.
  • Review RDP use and remote administration policy where these artifacts are operationally important.
  • Include this analytic in IR readiness exercises to verify that teams can identify possible evidence-clearing behavior during Windows investigations.
Analyst notes and limits

This object is a detection analytic, not a technique description. The supplied ATT&CK fields identify Windows scope and describe behavior involving command execution, registry key deletion, firewall changes, and RDP/network history artifact deletion. No tactic, related technique, or official detection query was supplied, so implementation must be derived and tested locally.

The official detection field is not provided, and no relationships or tactic mappings were supplied. This take does not infer attribution, active exploitation, impact, or coverage. Local environment baselines are required to separate suspicious artifact clearing from approved administration.

Official MITRE ATT&CK definition

Analytic 0133

Detects attempts to clear RDP/network history and modify network configuration artifacts through command execution, registry key deletion, firewall rule changes, and suspicious file deletions (e.g., Default.rdp, registry edits to Terminal Server Client keys).

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.

Relationship explorer

All related ATT&CK context

No relationships are available in the current normalized data for this object.

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
dafb9ee841a44083...
Imported snapshots across ATT&CK releases (1)
Release Bundle imported Object version Modified Status Raw hash
19.1 1.0 Current bundle dafb9ee841a4…
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 AN0133
    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.