Download Print Version

OESISOK™ Peripheral Protection
Criteria - Version 1.1

OESISOK™ Peripheral Protection designation is available for periperal protection applications. Applications submitted for certification must meet the following criteria before they are designated OESISOK.

Installation Test

A submitted application is installed on all supported operating systems. In order to complete this test, it must clear all of the following checks:

• The application installer completes without errors on all supported operating system and language combinations reflected in application documentation.

Rogue Application Test

A submitted application is checked against known lists of rogue applications. In order to complete this test, it must clear all of the following checks:

• Application or its vendor is not listed as ”rogue” according to the OPSWAT internal database.
• Application installer and binaries are scanned against multiple anti-malware engines listed below. None of the following engines should report any application file as “suspicious”, “threat” or other nomenclature indicative of the submitted application being rogue.

  • Spybot Search & Destroy 1.5
  • Lavasoft Ad-Aware 2007 Free Edition
  • Symantec Antivirus
  • McAfee VirusScan
  • CA eTrust™
  • Norman Virus Control
  • ESET NOD32 Antivirus Engine
  • VirusBuster EDK
  • Microworld eScan Engine
  • Kaspersky Anti-Virus®
  • ClamAV

OESIS® Local Detection Test

A submitted application is checked to ensure it will be detected by the OESIS Framework.

Appendix - Verification Testing

When an application is submitted for the OESISOK Peripheral Protection designation, the following tests will be performed for statistical data analysis:

Device Detection / Permission Test

The following tests will be performed:

• Device Identification: The application should be able to correctly identify the type of external device plugged-in.
• Permission: The application will allow or deny usage of the device based on the device policy.