Reverse Engineering
Protocol and File Format Analysis
We analyze undocumented communication protocols and data formats, specifying them for integration and security testing.
What it is
Legacy or closed systems often use undocumented protocols and data formats. The analysis derives the protocol structure from observation and compiled code. Message fields, commands and data formats are specified. This specification can be used for integration with a new system and for security testing.
Scope
- Recording and decoding undocumented protocol traffic
- Specifying message fields, commands and the state machine
- Decoding data and file formats
- Determining whether the protocol includes authentication and integrity
- Preparing a usable protocol specification for integration or testing
The need
When organizations need it
- When an unsupported system with an undocumented protocol must be integrated with a new one.
- When communication between two systems must be assessed for security.
- When an undocumented data format must be read or generated.
Method
How we work
-
Record
We record protocol traffic in a controlled environment and collect samples.
-
Decode
We identify message fields and commands by matching observation with compiled code.
-
Specify
We document the protocol in a form usable for integration and testing.
Outcome
What you have at the end
A specification of the undocumented protocol or data format, ready for integration and security testing.
Frequently asked questions
Is monitoring the traffic alone sufficient?
Often not. Observation reveals only part of the protocol. Reviewing compiled code also uncovers rare messages and error cases.
Can our integration team use the result?
Yes. We prepare the protocol specification in a form your development team can use directly.
Reverse Engineering
Other services in this area
Let's talk about this service.
Tell us briefly what you need. We will agree on the scope and timing together in the first meeting.
Schedule a Meeting