Component Object Model Class Identifier, or CLSID, is a unique identifier for a COM class on Windows. It maps a 128-bit GUID to the class registration used to create COM objects, load servers, and resolve interfaces through the registry.
What a CLSID does in Windows COM
A CLSID is the registry-facing identifier that tells Windows which COM class to instantiate. In practice, it is the lookup key that ties an object request to a registered server, so the system can create the class, load the right component, and expose its interfaces to calling code.
That indirection is useful because COM lets software discover components at runtime instead of hard-coding implementation details. It also means the identifier is not just metadata, it is part of the activation path, so a bad registration, hijack, or unexpected replacement can change what code runs.
How CLSIDs relate to COM registration and activation
CLSID values are typically stored alongside other COM registration data in the Windows registry. When an application asks for a COM class, Windows uses the CLSID to resolve the correct class factory or server location, then activates the component and returns the requested interface.
That mechanism supports both local and distributed component models, which is why CLSIDs appear in many enterprise Windows workflows. A single identifier can represent an in-process DLL, an out-of-process EXE, or a remote COM server, depending on how the class is registered.
The identifier itself is usually a GUID, but the operational security question is not the format, it is trust in the registration. If an attacker can alter the registration or influence search order, they may redirect activation to malicious code while the calling application believes it is using a legitimate component.
Why CLSIDs matter for security and detection
CLSID abuse is important because COM activation is often implicit. A user opening a document, a script, or a shell extension can trigger COM objects without seeing a clear executable launch, which makes CLSID-based execution paths attractive for stealth, persistence, and living-off-the-land abuse.
This is why CLSIDs show up in attack techniques such as COM hijacking and related inter-process communication abuse. The security issue is not the identifier alone, but the control it gives over which binary or server is launched when software resolves the class.
Defenders should watch for unexpected registry changes under COM class registration paths, unusual server paths, and CLSID activation from applications that do not normally instantiate those objects. In Windows environments, these signals can reveal both persistence mechanisms and execution redirection that would otherwise look like normal component use. For a deeper treatment of this attack surface, see MITRE ATT&CK T1559 Inter-Process Communication.
Common failure modes and defensive controls
The main failure modes are registration tampering, overbroad component exposure, and poor monitoring of COM-related registry locations. If class registration can be modified by a low-privilege user or a compromised process, the CLSID becomes a pivot point for unintended code execution or persistence.
Hardening starts with limiting who can write to COM registration keys, validating software provenance, and monitoring for changes to class registrations that are rarely modified in normal operations. Where component activation is part of a larger persistence or lateral movement pattern, defenders should correlate CLSID activity with host telemetry and process lineage. Related Windows execution abuse often overlaps with other persistence and movement paths, as covered in Persistence Techniques Guide and Lateral Movement Guide.
For organisations that want a broader model of minimizing ambient trust in component activation, capability-oriented design can help reduce what a caller can do just by resolving an object. That is the practical lesson behind Capability-Based Security Guide.
Standards & Framework Alignment
This section maps relevant standards and security frameworks to the operational risks and controls described in this guidance.
MITRE ATT&CK addresses the attack surface, CIS Controls v8 and NIST SP 800-53 Rev 5 set the technical controls, and ISO/IEC 27001:2022 defines the regulatory obligations.
| Framework | Control / Reference | Relevance |
|---|---|---|
| MITRE ATT&CK | T1559 — Inter-Process Communication | CLSIDs are a COM activation mechanism covered by IPC abuse techniques. |
| Recommendation — Map COM activation paths to T1559 and hunt for suspicious registry-driven object creation. | ||
| CIS Controls v8 | CIS-8 — Audit Log Management | CLSID abuse is often found through registry and process telemetry. |
| Recommendation — Collect and review registry and process logs for unexpected COM registration changes. | ||
| NIST SP 800-53 Rev 5 | CM-7 — Least Functionality | Restricting unnecessary COM exposure reduces the CLSID attack surface. |
| SI-4 — System Monitoring | Monitoring detects abnormal COM activation and class registration tampering. | |
| Recommendation — Disable unnecessary COM components and limit writable registration paths. Monitor COM activation and registry changes for unexpected class redirection. | ||
| ISO/IEC 27001:2022 | A.8.9 — Configuration management | CLSID registration is configuration that must be controlled and reviewed. |
| Recommendation — Control and review COM registration changes as part of secure configuration management. | ||
Practitioner Guidance
What to watch for: Treat CLSID activity as both an application mechanism and a security signal. A CLSID is benign in normal COM use, but it becomes high-value when it is tied to persistence, unexpected activation, or registry-controlled redirection. Review any class registration that sits on an execution path you would not expect to change frequently.
Governance implication: Ownership of COM registration surfaces should be explicit, because registration changes can alter runtime behavior without changing application code. In practice, that means the teams responsible for endpoint hardening, software deployment, and detection engineering all need a clear view of which CLSIDs are business-critical and which are suspiciously writable.
Practitioner takeaway: If a CLSID can change what code runs, then treat the registration path as part of your attack surface, not just a configuration detail.
Related resources from NHI Mgmt Group
Deepen Your Knowledge
Free weekly newsletter
Subscribe to the NHI & AI Identity Journal
The latest on NHI and Agentic AI security – articles, research, breaches, news and events every week.
Bonus 33% off our NHI Course when you subscribe.
Reviewed and updated by the NHIMG editorial team on November 16, 2026.
NHI Mgmt Group — the #1 independent authority on Non-Human Identity, IAM, and Agentic AI security. nhimg.org