Remote Monitoring & Management Help

Protection Policy Migration Behavior

The following table covers the settings mapped as part of a protection policy migration.

General Settings

Bitdefender

VIPRE

End-User Interaction

Show Notifications

Enabled based on the Notify user when A.P. blocks known risks in Active Protection tab

Quarantine

Delete items from quarantine that are older than X day(s)

Active and day(s) settings copied from Quarantine section

Updating

Update threat definitions every X hour(s)

Active and hours setting(s) copied from Updating section

No communication from Managed Antivirus Agent

Uses the closest timeout value rounded down rather than up is selected

Installation Settings Bitdefender only

As these settings are either unavailable for the VIPRE engine or not configured at the Protection Policy level the default values as set in Bitdefender policy are used. For example:

Installation Settings

Automatically removed conflicting products

Disabled

Automatically reboot device when required

Disabled

Agent UI Language

English

Agent Branding Settings

Company Name

Managed Antivirus

Product Name

Managed Antivirus

Company Website

N/A

Company Phone

N/A

Company Email

N/A

Scanning

Bitdefender

VIPRE

If a scan is missed, run on next startup after

Enabled and the number of minutes copied from Perform a quick scan X minute(s) after start-up: setting.

Scan USB drives upon insertion

Activated based on corresponding entry

Detect the following:

Spyware - Bitdefender policy defaults

Adware - Bitdefender policy defaults

Dialers - Bitdefender policy defaults

Keyloggers - Bitdefender policy defaults

Rootkits

Enabled where VIPRE Quick Scan or Deep Scan has Scanning: Rootkits selected*, otherwise left unticked

Potentially Unwanted Applications (PUAs)

Disabled where VIPRE Exclude low risk threats from detections selected, otherwise Bitdefender policy defaults

Quick and Deep Scan Settings

Bitdefender

VIPRE

Use low priority

Enabled where Scan’s process priority set to Lowest, otherwise Bitdefender policy defaults

Type

Common threat locations

Common threat locations

None

System drive only

System drive only

All fixed drives

Internal drives only

All fixed and removable drives

All local drives

Scanning

Running Process

Processes

Registry

Registry

Boot sector(s) - Bitdefender policy defaults

Cookies

Cookies

Packed executables - Bitdefender policy defaults (Scanned automatically from Dashboard v2019.08.20)

Email archives

Archives

Archives

* Mapped to Policy Scanning section

Rootkits

Unmapped - No corresponding Bitdefender option

Common file types

Schedule

Schedule Type

Always set to Daily Schedule

Scans run on days of week

Scans run on days of week

Scan Time

Populated from First scan time

Active Protection

Bitdefender

VIPRE

On access type

All files

All touched files

Executables only

Execution only

Custom file extensions

High risk extensions only

Custom file extensions

All Custom High risk extensions are copied over

Notes

Any custom extensions specified in the default Bitdefender policy are not retained during the migration process, even where the source VIPRE policy does not include custom extensions.

As Bitdefender includes a list of built-in extensions, VIPRE's default high risk extensions are not transferred over; even where the High risk extensions only option is selected in the VIPRE policy.

Remediation

Bitdefender

VIPRE

Remediation action for infected files

Ignore

Allow

Report

Disinfect

Quarantine

Delete

Quarantine

Please note that when disinfecting a file a copy is also stored in the Quarantine, as such we have opted to map the VIPRE Quarantine option to Bitdefender's Disinfect.

VIPRE settings copied from Remediation, Default section

Remediation action for suspicious files

Ignore

Allow

Report

Quarantine

Quarantine

Delete

VIPRE settings copied from Remediation, Default section

Remediation action for Rootkits

Ignore

Allow

Report

Disinfect

Quarantine

Delete

VIPRE settings copied from Remediation Malware section, Rootkit

Behavioral Scanning (Bitdefender only)

As these settings are unavailable for the VIPRE engine the Bitdefender defaults for the policy are used.

Allowed Threats (VIPRE only)

There is not a corresponding Bitdefender section for Allowed Threats therefore these settings are not mapped to the Bitdefender Policy. However if the path and name of the threat are known they may be manually added as an Exclusion in the Bitdefender policy.

Exclusions (VIPRE Exceptions)

Only custom created Always Allow rules for File with Path or Folder exceptions that do not include wildcards are mapped from VIPRE Exceptions to Bitdefender Exclusions. To match the available Bitdefender settings no other custom VIPRE Exception types are migrated.

Please be aware that system VIPRE and Bitdefender exclusions are automatically included in the Bitdefender policy and are not displayed in the Exclusions dialog.

What do you want to do?