Skip to navigation Skip to main content Skip to footer

01 October 2024

Binary Comparison Verification

For business-critical software

What is a Binary Comparison Verification?

Binary Comparison Verification enables you to compare executable files built by us in an Independent Build Verification to those running in the business’ production environment.

Both the software vendor and licensee benefit from:

Assurance on file quality

Ensure that the files deposited in escrow in the Independent Build are accurate and complete, providing reassurance for the licensee’s business continuity.

Giving you a back-up option

A Binary Comparison Verification demonstrates that the software can be built by an independent third party outside of its native environment.

Remote service

We conduct this test using our own facilities, so we don’t require the software vendor to be present.

How a Binary Comparison Verification works?

1. Technical questionnaire review

We start by taking a look at the Independent Build Verification report (a technical questionnaire) and confirm whether there is a need to procure any additional software or utilities to complete the Binary Comparison Verification.

2. License purchase (to help us complete the build)

Then, we’ll coordinate the purchase of any third-party software, software licenses or utilities required to complete the build (charges may apply).

3. Agreeing start timings and setting up the build machine

Once the start timings have been agreed upon by all parties, we will then set up a machine in which to carry out the build. As part of this process, the vendor nominates an engineer or technical contact to provide remote support to the process.

4. Checking the software version and licenses

At this stage, we will check that the correct version of the software has been received, as detailed in the questionnaire. We will also check with the licensee that this is the version they wish the Binary Comparison Verification, to be conducted on.

5. Time to build

The Escode Verification Consultant will then move the source code onto the build environment and compile the software.

6. Resolving any build issues

If any gaps or challenges are encountered during this process, then Escode will liaise directly with the software vendor to resolve.

7. Reports for licensee and software vendor

Then, we will issue both the licensee and software vendor a report. The report compares the executable files built in the Independent Build Verification test (included in this service) to that of those in production at the licensee’s The report also includes all of the details and deliverables of the test.

8. Secure it all in escrow

We will then place the source code, documentation, and any additional information gained in escrow in the deposit account for this escrow agreement, ready to release whenever you need it.

Ready to get started?

Build a stronger software resilience strategy today. Book a demo to see our platform in action, or talk to our sales team for pricing details and solutions guidance.

Book a demo       Contact sales

Escode View Portal Dashboard (Banner)
Skip to navigation Skip to main content Skip to footer