Am I OESIS OK?

The Am I OESIS OK? Utility is a free tool with several functions:

  1. It detects installed security applications interoperability level with third-party products.
  2. Detects interoperability errors with application manageability.
  3. Operates as a diagnostic and error reporting tool for the OESIS Framework
  4. Indicates whether your malware definitions are up to date
  5. Shows the OESIS OK interoperability level and certification information from West Coast Labs, ICSA Labs, AV-Comparatives and VB100 for your installed applications

 

Download Now

 

 

Am I OESIS OK? is also available for use with a command line interface. Instructions on on how to use the application this way are available here.

 

Useful information for support staff about application interoperability with solutions from Cisco, Juniper, F5 and many others.

 

When you get a technical support question or issue like…
“Does your antivirus work with product from Cisco NAC or Cisco ASA?”
“Does your antivirus work with Juniper SSL VPN or Juniper Host Checker?”
“Juniper Host Checker/F5 Firepass/etc. does not detect that I have X antivirus installed and I can’t access my corporate network.”

 

How can someone check what type of products a particular application interoperates with?
1) Locate the product at Application Lists. If your product is not featured, submit it to OESIS OK for integration.
2) You can see a list of the interoperable products for Certified-level applications here, and for Gold Certified-level applications here.

 

How can you troubleshoot a possible integration issue?
1) Have the user run the Am I OESIS OK? diagnostic tool. It offers the ability to submit issues directly to our development team. It’s available for download here.
2) If it is discovered that the application is not recognized or if it is not Certified, submit the application to OPSWAT (http://members.oesisok.com/login) or via ftp

Shown below is a workflow for Am I OESIS OK?
The Am I OESIS OK? utility can be used to diagnose connectivity issues and can export a log containing a complete snapshot of the local user’s environment. It can also pinpoint whether the issue is due to:
1) Lack of detection support in OESIS (if the security product isn’t detected at all by the utility).
2) A lack of supported features (OESIS OK criteria/function calls) in the current version of OESIS Framework.