Contactez-nous Suivez-nous sur Twitter En francais English Language

De la Théorie à la pratique

Freely subscribe to our NEWSLETTER

Newsletter FR

Newsletter EN



Claroty Researchers Introduce Open-Source Tool for Parsing AccessDB Files

July 2020 by Marc Jacob

The Claroty Research Team is excited to share AccessDB Parser, a new, purpose-built tool we developed to support activities such as testing, automation, fuzzing, and reverse-engineering research, among others. The standalone tool—which can be used to quickly parse through Microsoft AccessDB files (.mdb/.accdb)—is fully written in Python, thus eliminating any external binary dependencies.

Our parser supports Microsoft Access versions 1995 up to 2010. Microsoft Access is a database management system from Microsoft that combines the relational Microsoft Jet Database Engine with a graphical user interface (GUI) and software-development tools. It is a member of the Microsoft Office suite of applications, included in the Professional and higher editions or sold separately.

According to Claroty Researcher Uri Katz, who led the development of AccessDB Parser, the initial purpose of the tool was to support Claroty Continuous Threat Detection (CTD)’s Application DB (AppDB) scanning capabilities. Unique to Claroty, AppDB provides a safe, effective, and non-intrusive method for identifying and managing assets in operational technology (OT) environments by parsing artifacts such as programmable logic controller (PLC) and remote terminal unit (RTU) project configuration files.

As part of Claroty’s efforts to deliver the highest level of visibility into OT environments, we sought to develop a tool that would allow AppDB to process additional types of SCADA project files containing .mdb files. In addition, we wanted this tool to allow us to create multiple tests, verify test results, and automate some of our testing processes.

To address these needs, we decided to invest time in developing our own parsing tool which could easily be modified and improved on an ongoing basis as our needs evolve. We ensured to make the tool open-source, knowing that it would likely prove useful for other reverse engineers.

See previous articles


See next articles