OWASP Security Research and Development Framework
Do you see writing a security tool in windows is hard?
Do you have a great idea but you can’t implement it?
Do you have a good malware analysis tool and you don’t need it to become a plugin in OllyDbg or IDA Pro?
So, Security Research and Development Framework is for you.
- 1 Abstract:
- 2 Introduction:
- 3 The Features:
- 4 The User-Mode Part:
- 4.1 The Design:
- 4.2 The Infrastructure:
- 5 The Kernel-Mode:
- 6 Source Code:
- 7 Join Us:
- 8 Roadmap:
- 9 Conclusion:
- 10 Project About
This is a free open source Development Framework created to support writing security tools and malware analysis tools. And to convert the security researches and ideas from the theoretical approach to the practical implementation.
This development framework created mainly to support the malware field to create malware analysis tools and anti-virus tools easily without reinventing the wheel and inspire the innovative minds to write their researches on this field and implement them using SRDF.
In the last several years, the malware black market grows widely. The statistics shows that the number of new viruses increased from 300,000 viruses to millions and millions nowadays.
The complexity of malware attacks also increased from small amateur viruses to stuxnet, duqu and flame.
The malware field is searching for new technologies and researches, searching for united community can withstand against these attacks. And that’s why SRDF
The SRDF is not and will not be developed by one person or a team. It will be developed by a big community tries to share their knowledge and tools inside this Framework
SRDF still not finished … and it will not be finished as it’s a community based framework developed by the contributors. We just begin the idea.
The SRDF is divided into 2 parts: User-Mode and Kernel-Mode. And we will describe each one in the next section.
Before talking about SRDF Design and structure, I want to give you what you will gain from SRDF and what it could add to your project.
In User-Mode part, SRDF gives you many helpful tools … and they are:
• Assembler and Disassembler
• x86 Emulator
• PE Analyzer
• Process Analyzer (Loaded DLLs, Memory Maps … etc)
• MD5, SSDeep and Wildlist Scanner (YARA)
• API Hooker and Process Injection
• Backend Database, XML Serializer
• And many more
In the Kernel-Mode part, it tries to make it easy to write your own filter device driver (not with WDF and callbacks) and gives an easy, object oriented (as much as we can) development framework with these features:
• Object-oriented and easy to use development framework
• Easy IRP dispatching mechanism
• SSDT Hooker
• Layered Devices Filtering
• TDI Firewall
• File and Registry Manager
• Kernel Mode easy to use internet sockets
• Filesystem Filter
Still the Kernel-Mode in progress and many features will be added in the near future.
Let’s now see the design:
The User-Mode Part:
This includes the essential elements of any development framework and it’s not related to security like: string, hash, list, serializer, database, registry manipulation, sockets and so on.
We decided to create this part rather than depending on any development framework to make this framework independent from any other development frameworks and to be portable on any development framework
This is the beginning of the SRDF. This part is simply the Target from your security tool. What do you want to secure or secure from. And it includes Files (PE Files and others), Processes and Packets.
That’s the security tools that the SRDF support. And it’s divided into two namespaces: malware and network
Malware includes the assemblers and disassemblers, emulator, debugger, API Hooker, Yara Scanner (wildcard scanner) file recursive scanner and other tools
Network includes User-Mode capturing and Firewall
Core (The Application Interface):
The Core includes the Logging system and the back-end Database.
And also, it’s the Application Interface. Like cConsoleApp … and you can inherit from it to create your own User-Interface.
We wish this part to be expanded to include more user interfaces and management systems
It’s divided into three namespaces:
1. String: it contains the string class, encoded string, hash and list 2. Code: it contains the NativeCode class and StoredProcedure … and they represents the shellcode and the code that stored in database. Like a virus detection routines inside an Antivirus 3. XML: and it contains the XML Encoder and the Serializer.
It’s divided into three namespaces:
1. Internet: and it contains the internet communication protocols like sockets, HTTP Sockets and so on. 2. IPC: and it contains the Inter-Process Communication protocol 3. User-Mode to Kernel-Mode Communication: and it contains the communication protocol to communicate to the kernel-mode part of the SRDF
It’s divided into three namespaces:
1. Databases: and it contains the Database class and SQLiteDB and so on. 2. Files: and contains the File writing and logging classes 3. Registry: and it contains the registry read and write
This namespace describes the File Formats of The Files that could contain malicious code like: Executable Files (PE and ELF) and Document Files (PDF, Docx …) and so on.
Until now it contains The PE Files parser
And it includes one class only named cProcess. And, this class describes a running process and parses its PEB and gives you the important information about the process and its memory map. And support injecting code and create a remote thread.
And it includes classes that describe an internet packets captured on the wire or generated for an attack.
It contains two namespaces:
This namespace contains the scanning, Hooking and emulation libraries and contains Pokas Emulator wrapper class, Yara wrapper class (wildcard scanner), a debugger and contains a directory recursive scanner and other tools
And also, it contains the x86 assembler and disassembler (using Pokas Emulator Assembler) and allow to contain other assemblers and for other platforms.
This namespace should contain the User-Mode Packet capture and firewall. And should contain the Winpcap Packet capturing and firewall system. It also should include Application Layer parsers for FTP, HTTP, IRC and all known protocols and include Pcap Reader and writer.
And the core includes the cApp class that contains the back-end database and logging and the User-Interface such as cConsoleApp
The Kernel-Mode Goals:
The Goals of the kernel-Mode development Framework are:
1. Easy to create a Kernel-Mode security tool 2. Support OOP using the native device driver programming APIs 3. Support detaching between devices in IRPs 4. Easy to use files, registry and so on 5. Create a User-Mode/Kernel-Mode communication protocol 6. Designed only for hooking and security tools.
The Kernel-Mode SRDF is designed on native device driver programming APIs and independent from the WDF (windows drivers foundation).
Now we will describe the design of Framework and then we will go through the IRP dispatching mechanism in the KM-SRDF
Driver: It’s the core management system that dispatching the IRPs to the devices and manage the devices.
Device: it represents a device object and it contains the IRP dispatching between the control device object and the filtering device objects and includes attaching and detaching from a devices chain and all necessary functions for a device object
SSDT Device: this class is inherited from device class and it’s created for SSDT Hooking
Filter Device: this class created for attaching to a chain and filtering the inputs and the outputs of the IRPs
File Filter Device: this class is inherited from Filter Device and it’s created for filtering the File system I/O request packets (IRPs) or monitoring file operations
TDI Firewall: this class is inherited from Filter Device and it’s created for filtering the internet packets and connections and the processes that tries to connect to the internet
DKOM Device: this class created to provide a generic way to work with opaque structures in windows without worrying about windows version and subversion (under construction)
Process Device: this class provides a way to inject code or modify the memory of a process from the kernel-mode
File/Registry Managers: they are tools created to support writing files and working with registry easily without worrying about IRQL
Sockets: it’s an easy interface to connect to the internet using the TDI interface
The IRP Dispatching:
• The IRP dispatching begins from the entry.cpp and it dispatch the IRP to the Driver • The driver checks the device object and dispatch the IRP to the related device • The device sends the IRP to the User-Mode communication object to work with it as it’s sent to the control device object • If it’s a FileFilter Device, the device dispatches the IRP based on the device object to the Attached Device Objects or to the control device object and the user-mode communication
Do you get benefit from this framework and you need to give something back?
Do you want to add something to your CV?
Do you want to meet smart developers and join a big community?
Do you want to learn new things?
Here is place … join the development community, meet new smart people and have fun.
a. XRAY Tool b. Heuristics Analysis c. Behavior-based Detection Tools. d. More File Formats (PDF, apk, …) e. OpenSBI and other Virus Classification File Formats f. Sandboxing Mechanism. i. Using API/ SSDT Hooking ii. Emulation Based on Pokas Emulator. g. Update System with Flexible Mechanism
2. Malware Analysis:
a. SSDT Hooking for (Processes, Files, Registry and Sockets System Calls) b. API Hooking (for the same as above) c. Improvement in Pokas Emulator, Assembler and Disassembler d. Packet Capturing Tool and Emulated IRC and HTTP Connection (Server emulate the replies to the malware and log the data) e. Recursive Disassembler f. More APIs Emulation in Pokas x86 Emulator g. Support more Instructions (All FPU instructions, All general purpose instructions and support mmx and 3dnow) h. Support idb (IDA Pro Database) to read it and use its analysis
I’m aiming to create a database for all static unpacking codes for the mostly common unpackers and I hope it could be updated by the community
a. Integration into IDA Pro Plugin Interface … and in (Debugger Menu) b. OllyDbg Plugin Interface c. Ollyscript Executer on cDebugger d. Metasploit Integeration (in Meterpreter Post Exploitation e. Python, Ruby, Delphi Header files and cTypes for SRDF.dll
a. Support NDIS, kernel sockets and more new libraries b. Process Analyzer in Kernel-Mode c. Packet Capturing Library d. More Debugging and Bug fixing
a. We need to build website. b. We need activities for learning. c. We need more documentations and tutorials d. We need more helpful tools and applications based on SRDF
This development framework will support the anti-malware technologies to grow and support implementing researches in the malware field more to withstand against the new attacks nowadays
The framework is based on community and we aim to create a big community for it. We didn’t finished the framework … we just begin
| PROJECT INFO
What does this OWASP project offer you?
| RELEASE(S) INFO|
What releases are available for this project?