The most hard to achieve requirements are marked bold. Submit your app to Microsoft for periodic performance testing.Ĭertified through independent testing by at least one industry standard organization. These requirements define the behavior of antimalware apps necessary to ensure proper interaction with Windows. Have your own malware research team unless you build a product based on an SDK.īe active and have a positive reputation in the antimalware industry.Īctivity can include participation in industry conferences or being reviewed in an industry standard report such as AV Comparatives, OPSWAT or Gartner.īe willing to sign a non-disclosure agreement (NDA) with Microsoft.īe willing to sign a program license agreement.īe willing to adhere to program requirements for antimalware apps.

Developed by using an SDK (engine and other components) from another MVI Partner company and your organization adds a custom UI and/or other functionality.

Offer an antimalware or antivirus product that is one of the following:

The criteria have also changed and they are more complex.Īssuming you have a product build with a 3rd party SDK, here are the requirements to become a member: Just for the record, a few years later now, the requirements have changed a bit.

In order to do both these things, you need to be member in the MVI. In order to be able to register an AV product with Windows Security Center, you need a private API from Microsoft or, starting with Windows 10 build 1809 you need to register a Protected Service.

Antimalware de microsoft