nscm.sys - Clean (27/100) - DriverShield Analysis

Analysis of nscm.sys: clean verdict, risk score 27/100. 2 YARA matches, 1/76 multi-engine detections. SHA256 0f726d8ce21c0c9e. Kernel imports, IOCTL codes, MITRE ATT&CK, and code-signing details.

nscm.sys - Analysis Report

DriverShield analyzed the Windows kernel driver nscm.sys and assigned a verdict of Clean with a composite risk score of 27/100, indicating no notable risk signals (0-29 band).

VerdictClean (27/100)
YARA matches2
Multi-engine detections1 / 76
File size40968 bytes
Code-signing signerMicrosoft Windows Hardware Compatibility Publisher
Analyzed2026-09-06
SHA2560f726d8ce21c0c9e01ebe6b55913c519ad6086bcaec1a89f8308f3effacd435f
SHA13a5d176c50f97b71d139767ed795d178623f491d
MD598637b5e724ad6fdf30791f0b0d15c91

Driver identity

Version resource data embedded in the nscm.sys PE header, as extracted by the analysis engine.

File descriptionXTier Security Context Manager
ProductMicro Focus XTier
CompanyMicro Focus
Original filenamenscm.sys
File version3.1.12.0
Copyright(C) Copyright 2000-2017, Micro Focus. All Rights Reserved.

How the 27/100 score breaks down

Each component is scored 0-100 and then weighted into the composite. See the analysis methodology for the exact formula.

ComponentSub-score
Multi-engine consensus0 / 100
YARA signature matches10 / 100
Dangerous kernel imports100 / 100
IOCTL dispatch surface30 / 100
Known-vulnerable corpus0 / 100
Code-signing state80 / 100
Packing and entropy0 / 100
Dynamic behaviour0 / 100
CVE cross-reference0 / 100

Kernel imports (10)

Kernel-mode APIs resolved from the Import Address Table of nscm.sys, ranked by exploitation relevance.

APIRiskWhy it matters
PsLookupProcessByProcessIdhighPotentially dangerous - could be used for privilege escalation or security bypass
PsSetCreateProcessNotifyRoutinehighPotentially dangerous - could be used for privilege escalation or security bypass
ZwOpenProcesshighPotentially dangerous - could be used for privilege escalation or security bypass
KeBugCheckExmediumModerate risk - system modification capability
IoCreateDevicelowStandard kernel API - generally benign
KeWaitForSingleObjectlowStandard kernel API - generally benign
IoDeleteDevicelowStandard kernel API - generally benign
DbgPrintlowStandard kernel API - generally benign
ExAllocatePoolWithTaglowStandard kernel API - generally benign
ZwCloselowStandard kernel API - generally benign

IOCTL dispatch codes (10)

Control codes reachable through the driver dispatch routine. Codes tied to published exploit code are flagged, since they are the primary Bring Your Own Vulnerable Driver (BYOVD) entry points.

CodeSeverityTransferDescription
0x002200F0mediumMETHOD_BUFFEREDFILE_DEVICE_UNKNOWN Function #60
0x0080249CmediumMETHOD_BUFFEREDFILE_DEVICE_CUSTOM Function #2343
0x008024ACmediumMETHOD_BUFFEREDFILE_DEVICE_CUSTOM Function #2347
0x0022B315mediumMETHOD_IN_DIRECTFILE_DEVICE_UNKNOWN Function #3269
0x00802484mediumMETHOD_BUFFEREDFILE_DEVICE_CUSTOM Function #2337
0x0080248CmediumMETHOD_BUFFEREDFILE_DEVICE_CUSTOM Function #2339
0x00802494mediumMETHOD_BUFFEREDFILE_DEVICE_CUSTOM Function #2341
0x00222B0DmediumMETHOD_IN_DIRECTFILE_DEVICE_UNKNOWN Function #2755
0x008024B4mediumMETHOD_BUFFEREDFILE_DEVICE_CUSTOM Function #2349
0x00340300mediumMETHOD_BUFFEREDFILE_DEVICE_DISK Function #192

PE sections

Section layout and Shannon entropy. High entropy in a code section is a packing or encryption indicator.

SectionVirtual sizeRaw sizeEntropyFlags
.text0x5A660x5C005.96CODE, EXEC, READ
.rdata0x05940x06005.31IDATA, READ
.data0x05A80x02001.45IDATA, READ, WRITE
.pdata0x04500x06003.3IDATA, READ
.edata0x00630x02001.1IDATA, READ
INIT0x04E00x06004.65CODE, EXEC, READ, WRITE, DISCARD
.rsrc0x03600x04002.88IDATA, READ, DISCARD
.reloc0x00480x02000.25IDATA, READ, DISCARD

Exploit mitigations

Control Flow GuardNot enabled
ASLRNot enabled
DEPNot enabled
Integrity checkNot enforced
Mitigation score5 / 100

YARA rule matches (2)

RuleSeverityDetects
PUA_VULN_Driver_Microfocus_Microfocusxtier_5351mediumDetects vulnerable driver mentioned in known-vulnerable driver corpus project using VersionInfo values from the PE header - nscm.sys. Investigate matches in context: expected filenames or standard ven...
SUSP_CallbacksmediumKernel callback registration

MITRE ATT&CK techniques (14)

Techniques this driver could enable if loaded by an adversary.

IDTechniqueTactic
T1014RootkitDefense Evasion
T1055.001Process Injection: DLL InjectionDefense Evasion
T1071Application Layer ProtocolCommand and Control
T1112Modify RegistryDefense Evasion
T1211Exploitation for Defense EvasionDefense Evasion
T1489Service StopImpact
T1543.003Windows ServicePersistence
T1547.001Registry Run KeysPersistence
T1553.002Subvert Trust Controls: Code SigningDefense Evasion
T1562.001Impair Defenses: Disable/Modify ToolsDefense Evasion
T1562.006Indicator BlockingDefense Evasion
T1564.001Hidden Files and DirectoriesDefense Evasion
T1569.002Service ExecutionExecution
T1652Device Driver DiscoveryDiscovery

Code-signing chain

SignerMicrosoft Windows Hardware Compatibility Publisher
Signer organisationMicrosoft Corporation
IssuerMicrosoft Windows Third Party Component CA 2014
Serial33000000433A68189E33902987000000000043
Valid from2020-12-15 22:25 UTC
Valid until2021-12-02 22:25 UTC (expired)
Signature validityNot verified

Symbolic execution

Engine angr, status completed, 12 paths explored at a maximum depth of 12. Vulnerability classes reached: 1. Exploitable paths: 0.

Frequently asked questions about nscm.sys

Is nscm.sys safe?

Based on DriverShield static and dynamic analysis, nscm.sys is assessed as clean, with no notable risk signals. Its composite risk score is 27/100 (verdict: clean). Always validate findings independently before acting.

What is the risk score of nscm.sys?

nscm.sys has a DriverShield composite risk score of 27/100, placing it in the clean verdict band. SHA256: 0f726d8ce21c0c9e01ebe6b55913c519ad6086bcaec1a89f8308f3effacd435f.

What is nscm.sys?

nscm.sys is a Windows kernel-mode driver (.sys) analyzed by DriverShield for vulnerabilities, BYOVD abuse potential, and malware indicators. It is code-signed by Microsoft Windows Hardware Compatibility Publisher.

Related: Other drivers signed by Microsoft Windows Hardware Compatibility Publisher · What an IOCTL dispatch code is · How YARA matching feeds the score · BYOVD research index · full driver database · CVE library · code signing atlas


DriverShield © 2025-2026 · Terms · Privacy · Contact