sisraid2.sys - Clean (8/100) - DriverShield Analysis

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

sisraid2.sys - Analysis Report

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

Verdict	Clean (8/100)
YARA matches	0
File size	44856 bytes
Code-signing signer	Microsoft Windows
Analyzed	2026-03-22
SHA256	567710c90bd71600a31a3408db065b43c844dcfd12045fde04cd59d932dc8353
SHA1	3be39a3fcd9253158eaf832aaa21335029f67506
MD5	9ab1badc5a324da39186b81bc6ce6e2e

Driver identity

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

File description	SiS RAID Stor Miniport Driver
Product	Microsoft® Windows® Operating System
Company	Silicon Integrated Systems Corp.
Original filename	sisraid2.sys
Internal name	sisraid2.sys 2.60.01
File version	2.60.01 (NT.070926-1510)
Copyright	Copyright (c) SiS Corp. 2000-2010

How the 8/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	0 / 100
IOCTL dispatch surface	27 / 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 (1)

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

API	Risk	Why it matters
KeBugCheckEx	medium	Moderate risk - system modification capability

IOCTL dispatch codes (9)

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
0x00802484	medium	METHOD_BUFFERED	FILE_DEVICE_CUSTOM Function #2337
0x008024B4	medium	METHOD_BUFFERED	FILE_DEVICE_CUSTOM Function #2349
0x008024BC	medium	METHOD_BUFFERED	FILE_DEVICE_CUSTOM Function #2351
0xC350B9EE	medium	METHOD_OUT_DIRECT	CUSTOM_MSI Function #3707
0x00222BE8	medium	METHOD_BUFFERED	FILE_DEVICE_UNKNOWN Function #2810
0x00808A88	medium	METHOD_BUFFERED	FILE_DEVICE_CUSTOM Function #674
0x00340390	medium	METHOD_BUFFERED	FILE_DEVICE_DISK Function #228
0x00220068	medium	METHOD_BUFFERED	FILE_DEVICE_UNKNOWN Function #26

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	0x79E9	0x7A00	6.57	CODE, EXEC, READ
.rdata	0x03E4	0x0400	4.78	IDATA, READ
.data	0x0112	0x0200	0.3	IDATA, READ, WRITE
.pdata	0x01D4	0x0200	3.88	IDATA, READ
INIT	0x025C	0x0400	3.2	CODE, EXEC, READ, WRITE, DISCARD
.rsrc	0x03F0	0x0400	3.39	IDATA, READ, DISCARD

Exploit mitigations

Control Flow Guard	Not enabled
ASLR	Not enabled
DEP	Not enabled
Integrity check	Not enforced
Mitigation score	5 / 100

No CFG - Control Flow Guard is not enabled. Indirect call targets are not validated, making the driver susceptible to control flow hijacking via corrupted function pointers or vtables.
No ASLR - ASLR is disabled. The driver loads at a predictable address, enabling reliable exploitation of memory corruption vulnerabilities.
No DEP - DEP is disabled. Data pages are executable, allowing shellcode execution from stack/heap buffers.
Expired Certificate - The driver is signed but the certificate has expired. Windows may still load it depending on revocation policy.

MITRE ATT&CK techniques (3)

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
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 sisraid2.sys

Is sisraid2.sys safe?

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

What is the risk score of sisraid2.sys?

sisraid2.sys has a DriverShield composite risk score of 8/100, placing it in the clean verdict band. SHA256: 567710c90bd71600a31a3408db065b43c844dcfd12045fde04cd59d932dc8353.

What is sisraid2.sys?

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