Unisar 1.24.1867 manual Best practices

Page 79

Best practices

Using

13

BitDefender

 

Chapter 13. Best practices

These are some steps you should follow to ensure a system free from viruses.

1.After installing BitDefender Antivirus Scanner for Unices, perform a triggered update to have the latest virus signatures and engines, as described in Section Triggered update (page 73).

2.Perform a full system scan to find any already infected objects. Use the guidelines from Chapter Real life usage (page 51).

3.Make sure the license key has not expired and get a new one before the expiring date. Read more about license keys in Chapter Product registration (page 77).

4.If you use cron or something else to do regular updates, make sure the job scheduler really works and you have always the latest updates.

5.When using the quarantine action, so the infected objects are moved to quarantine directory, keep one eye on it. Check periodically the directory size, since it can grow rapidly and you could run out of disk space, and take a look at the files BitDefender has found infected. You could simply remove them if you are sure they are infected, you can double check them (the suspected objects can be false positive alarms) and you can send them to BitDefender Antivirus Lab as described below, for in-depth analysis.

6.Use BitDefender Antivirus Scanner for Unices to scan all the files you have from untrusted sources, such as the Internet, by web browsing or email. Scan the documents, archives, programs and anything else that could contain malicious code. Periodically, perform a full system scan.

7.Send to BitDefender Antivirus Lab at email address <virus_submission@bitdefender.com> all suspected objects for a prompt response to malware threats. To not be filtered by antivirus protected email servers, you can archive the suspected object, encrypt the archive and send both the archive and the key.

79

Image 79
Contents Users Guide Users Guide As every cat owner knows, nobody owns a cat BitDefender Antivirus Scanner for Unices Table of Contents BitDefender integration UninstallConfiguration file Testing BitDefender Real life usageBest practices UpdatesFrequently Asked Questions Support Product registrationBitDefender Antivirus Scanner for Unices Viii End User Software License Agreement End User Software License Agreement End User Software License Agreement Xii Conventions used in this book PrefaceTypographical conventions Admonitions CommandBook structure Request for Comments Description and features Description and features Overview Why BitDefender?Data Security Division Softwin Description BitDefender Antivirus Scanner for Unices Product featuresKey Features More in the manual Scanning mechanismFeatures Installation Installation System requirements PrerequisitesHardware system requirements Linux requirements Package naming conventionSoftware system requirements Linux conventionFreeBSD convention Installation Test the package for integrity Package installationTest the rpm and deb packages Test the FreeBSD tbz package Test the self-extractable archiveInstall the self-extractable archive Install the packageInstall the rpm package Install the deb packageAdditional parameters Install the FreeBSD package InstallerConfigures the quarantine directory Uninstall using the self-extractable archive UninstallUninstall the rpm package Uninstall the deb packageUninstall a package downloaded locally Uninstall the FreeBSD packageUninstall from the ports collection Using BitDefender Using BitDefender System versus User configuration Configuration fileKey Description More about triggered updateRegular users and quarantine Using07 BitDefenderProduct registration Using BitDefenderScan an executable file Testing BitDefenderEicar online resources Scan an archive Command output will be the followingScan a mailbox Tmp/mail.mbox Virus scanning Real life usageScan a regular file Scan a directory Scan the entire system Actions on archives Scan the archivesScan the mailbox Report Using the log fileDisplay the virus list Get more informationDisplay the product version Virus submissionBitDefender integration Midnight CommanderDesktop integration KDE Konqueror Different installation pathDo not break the last line Action on file in Konqueror KrusaderKrusaders User Actions ROX-FilerPine Information Center PineThis is how the screen should look like What to do with infected emailsExit Status Interval 1,254 BitDefender pipe bdscanpipe EvolutionKMail Filter actions in KMail Server integrationMailScanner installation Qmail-Scanner installationMailScanner Change it to the following form Amavisd-newAmavisd-new installation Using Regular updates UpdatesTriggered update Run the triggered updateEdit the cron table Http proxy Manual updateOrder to extract the updates Trial License License for home or personal use Product registrationCheck the expiration date License for commercial use Best practices Best practices Getting help Getting help Frequently Asked Questions Getting help Support department SupportBitDefender Knowledge Base Softwin GmbH Contact informationWeb addresses AddressBitDefender LLC RomaniaGetting help Manual Pages Manual Pages Description SynopsisOptions Manual Pages Actions Files ExamplesSee also BugsManual Pages Glossary Download Command lineCookie Disk driveHeuristic EventsFalse positive Filename extensionPacked programs Macro virusMail client Non-heuristicStartup items PortReport file ScriptWorm UpdateVirus Virus definition