volume.sys - Clean (9/100) - DriverShield Analysis

Analysis of volume.sys: clean verdict, risk score 9/100. 0 YARA matches. SHA256 c03e3367b9230799. Kernel imports, IOCTL codes, MITRE ATT&CK, and code-signing details.

volume.sys - Analysis Report

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

Verdict	Clean (9/100)
YARA matches	0
File size	16696 bytes
Code-signing signer	Microsoft Windows
Analyzed	2026-03-22
SHA256	c03e3367b92307993bc169583cb298265fc1c35cf5973ec352c1e08ffcfd1928
SHA1	75a9914dd254894eca795aec481478e1f6271c2d
MD5	770e710bea3ccc595ee3703297b40d76

Driver identity

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

File description	Volume driver
Product	Microsoft® Windows® Operating System
Company	Microsoft Corporation
Original filename	volume.sys
Internal name	volume.sys
File version	10.0.19041.1 (WinBuild.160101.0800)
Copyright	© Microsoft Corporation. All rights reserved.

How the 9/100 score breaks down

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

Component	Sub-score
Multi-engine consensus	0 / 100
YARA signature matches	0 / 100
Dangerous kernel imports	24 / 100
IOCTL dispatch surface	6 / 100
Known-vulnerable corpus	0 / 100
Code-signing state	80 / 100
Packing and entropy	0 / 100
Dynamic behaviour	0 / 100
CVE cross-reference	0 / 100

Kernel imports (3)

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

API	Risk	Why it matters
IoCreateDevice	low	Standard kernel API - generally benign
IofCompleteRequest	low	Standard kernel API - generally benign
IoDeleteDevice	low	Standard kernel API - generally benign

IOCTL dispatch codes (2)

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.

Code	Severity	Transfer	Description
0x002200F0	medium	METHOD_BUFFERED	FILE_DEVICE_UNKNOWN Function #60
0x00340378	medium	METHOD_BUFFERED	FILE_DEVICE_DISK Function #222

PE sections

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

Section	Virtual size	Raw size	Entropy	Flags
.text	0x00B8	0x0200	1.91	CODE, EXEC, READ
.rdata	0x0448	0x0600	3.01	IDATA, READ
.data	0x0090	0x0200	0.28	IDATA, READ, WRITE
.pdata	0x00C0	0x0200	1.57	IDATA, READ
.idata	0x015C	0x0200	2.89	IDATA, READ
PAGE	0x0368	0x0400	5.13	CODE, EXEC, READ
INIT	0x0162	0x0200	3.55	CODE, EXEC, READ, DISCARD
GFIDS	0x001C	0x0200	0.25	IDATA, READ, DISCARD
.rsrc	0x03E8	0x0400	3.23	IDATA, READ, DISCARD
.reloc	0x008C	0x0200	1.03	IDATA, READ, DISCARD

Exploit mitigations

Control Flow Guard	Enabled
ASLR	Enabled
DEP	Enabled
Integrity check	Not enforced
Mitigation score	85 / 100

CFG Enabled - Control Flow Guard is active - indirect calls are validated against a bitmap of valid targets at runtime.
ASLR Enabled - Address Space Layout Randomization is active - base address is randomized on each load.
DEP/NX Enabled - Data Execution Prevention is active - non-executable pages cannot be executed.
Expired Certificate - The driver is signed but the certificate has expired. Windows may still load it depending on revocation policy.

MITRE ATT&CK techniques (4)

Techniques this driver could enable if loaded by an adversary.

ID	Technique	Tactic
T1071	Application Layer Protocol	Command and Control
T1543.003	Windows Service	Persistence
T1569.002	System Services: Service Execution	Execution
T1652	Device Driver Discovery	Discovery

Code-signing chain

Signer	Microsoft Windows
Signer organisation	Microsoft Corporation
Issuer	Microsoft Windows Production PCA 2011
Serial	330000023241FB59996DCC4DFF000000000232
Valid from	2019-05-02 21:24 UTC
Valid until	2020-05-02 21:24 UTC (expired)
Signature validity	Not verified

Certificate revision: 0x0200
Certificate type: PKCS#7
Chain: Microsoft Windows Production PCA 2011

Symbolic execution

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

Frequently asked questions about volume.sys

Is volume.sys safe?

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

What is the risk score of volume.sys?

volume.sys has a DriverShield composite risk score of 9/100, placing it in the clean verdict band. SHA256: c03e3367b92307993bc169583cb298265fc1c35cf5973ec352c1e08ffcfd1928.

What is volume.sys?

volume.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.

Related: Other drivers signed by Microsoft Windows · What an IOCTL dispatch code is · BYOVD research index · full driver database · CVE library · code signing atlas