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

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

percsas3i.sys - Analysis Report

DriverShield analyzed the Windows kernel driver percsas3i.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	68408 bytes
Code-signing signer	Microsoft Windows
Analyzed	2026-03-22
SHA256	92017ecb36eaa35ac454e890734915a658eb898c95970531d43c19461be6562b
SHA1	ac8f33dc88bfa7bd3f3af773901eb96c9194cf02
MD5	1c6720616ff300235509d5efbb2cae20

Driver identity

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

File description	MEGASAS RAID Controller Driver for Windows
Product	MEGASAS RAID Controller Driver for Windows
Company	Avago Technologies
Original filename	PercSas3.sys
Internal name	PercSas3.sys
File version	6.604.06.00
Copyright	Copyright © Avago Technologies2013

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	0 / 100
IOCTL dispatch surface	42 / 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

IOCTL dispatch codes (14)

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
0x00808B8B	high	METHOD_NEITHER	FILE_DEVICE_CUSTOM Function #738
0x0080898B	high	METHOD_NEITHER	FILE_DEVICE_CUSTOM Function #610
0x0080818B	high	METHOD_NEITHER	FILE_DEVICE_CUSTOM Function #98
0x0080918B	high	METHOD_NEITHER	FILE_DEVICE_CUSTOM Function #1122
0x0080838B	high	METHOD_NEITHER	FILE_DEVICE_CUSTOM Function #226
0x0080878B	high	METHOD_NEITHER	FILE_DEVICE_CUSTOM Function #482
0x0080A28B	high	METHOD_NEITHER	FILE_DEVICE_CUSTOM Function #2210
0x002200F0	medium	METHOD_BUFFERED	FILE_DEVICE_UNKNOWN Function #60
0x0080248C	medium	METHOD_BUFFERED	FILE_DEVICE_CUSTOM Function #2339
0x00802484	medium	METHOD_BUFFERED	FILE_DEVICE_CUSTOM Function #2337
0x0022FBE8	medium	METHOD_BUFFERED	FILE_DEVICE_UNKNOWN Function #3834
0x00808789	medium	METHOD_IN_DIRECT	FILE_DEVICE_CUSTOM Function #482
0x008024B4	medium	METHOD_BUFFERED	FILE_DEVICE_CUSTOM Function #2349
0x0034037C	medium	METHOD_BUFFERED	FILE_DEVICE_DISK Function #223

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	0xB0EA	0xB200	6.24	CODE, EXEC, READ
.rdata	0x113C	0x1200	4.74	IDATA, READ
.data	0x0635	0x0800	2.55	IDATA, READ, WRITE
.pdata	0x0858	0x0A00	3.98	IDATA, READ
.gfids	0x0004	0x0200	0.02	IDATA, READ
INIT	0x0364	0x0400	4.4	CODE, EXEC, READ, DISCARD
.rsrc	0x0788	0x0800	5.27	IDATA, READ, DISCARD
.reloc	0x00E4	0x0200	2.83	IDATA, READ, DISCARD

Exploit mitigations

Control Flow Guard	Not enabled
ASLR	Enabled
DEP	Enabled
Integrity check	Not enforced
Mitigation score	55 / 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.
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 (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 percsas3i.sys

Is percsas3i.sys safe?

Based on DriverShield static and dynamic analysis, percsas3i.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 percsas3i.sys?

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

What is percsas3i.sys?

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