FireDocs SDK Overview

A cross platform, open development SDK that enables software engineers and technology vendors to develop products that detect and configure personal firewalls.

Firedoc SDK firewall configuration whitelist

FireDocs XML

Click the image for an example of the XML instructions.

avast firewall configuration large

FireDocs screen shots

Click to see six images from the screen shot walk though for the avast! Internet Security 5 firewall.


Personal firewalls are a critical part of any security set up. However, dozens of other important applications will face compatibility problems when a firewall is unconfigured. Powered by the detection and management libraries of the OESIS Framework, OPSWAT's FireDocs SDK offers a toolkit to create documentation that—after detecting their exact firewall product—can guide users to properly configure their firewalls to work with your applications. Thereby reducing support calls and keeping customers happier.

Containing dozens of the most popular personal firewalls, the SDK is regularly updated and contains an easily integrated XML document and screen shots for each configuration step. These combined features are ideal for creating your own instructional wizard to accompany your application. In addition, a library containing many more firewalls is available in this SDK, allowing for the creation of a utility that will  properly detect an end user's installed firewall.

Advantages

  • Reduction in go to market costs
  • Reduction in support costs
  • Continually enhanced and updated
  • Already exists as a ready-made package featuring dozens of applications and hundreds of screen shots
  • Built on application libraries that have been employed for years by market-leading technology solution providers

Includes Documentation For

  • avast!
  • AVG
  • Check Point (ZoneAlarm)
  • ESET
  • Kaspersky
  • McAfee
  • Microsoft
  • Symantec (Norton)
  • Trend Micro
  • And many others


FireDocs Use Cases

FireDocs is perfect for creating instructions for any application that demands outbound access from the system and could be negatively affected by an overzealous firewall.  Examples include:

  • Applications communicating with wireless peripherals such as keyboards, mice, printers, monitors, hard drives, digital picture frames, etc. The goal of any firewall is to prevent unauthorized inbound/outbound communication with a system. If the firewall is not familiar with a particular peripheral—and the list of peripheral products grows daily—it will naturally attempt to prevent access.
  • Applications requiring periodic access to the Internet (applications requiring data updates or access to online resources, etc.). Tax and accounting applications are obvious examples where external access is necessary, but potentially fraught with issues because of a poorly configured firewall.


Evaluating FireDocs

If you are a technology vendor or IT professional interested in evaluating the FireDocs SDK, please contact sales@opswat.com

Document Actions