Package Signing And Security - McAfee EPOLICY ORCHESTRATOR 3.6 - WALKTHROUGH GUIDE Manual

®
ePolicy Orchestrator 3.6 Walkthrough Guide

Package signing and security

Table 4-3 Supported packaged types
Package type Description
Supplemental virus The
definition ( . ) one or a few specific viruses
EXTRA DAT
files. that have appeared since the
last
File type: .
EXTRA DAT
threat has a high severity,
distribute the
immediately, rather than wait
until that signature is added to
the next
EXTRA
McAfee web site. You can
distribute them through
ePolicy Orchestrator.
Pull tasks do not retrieve
EXTRA
Product deployment A product deployment package
packages. contains the installation
software of a McAfee product.
File type: .
PKGCATALOG Z
Agent installation An agent installation package
package. contains the installation
software for the ePolicy
File type: .
PKGCATALOG Z
Orchestrator agent.
Agent language An agent language package
packages. contains files necessary to
display agent information in a
File type: .
PKGCATALOG Z
local language.
All packages created and distributed by McAfee are signed with a key pair using the
DSA (Digital Signature Algorithm) signature verification system, and are encrypted
using 168-bit 3DES encryption. A key is used to encrypt or decrypt sensitive data.
You are notified when you check in packages that are not signed by McAfee. If you are
confident of the content and validity of the package, continue with the check-in. These
packages are secured in the same manner described above, but are signed by ePolicy
Orchestrator when they are checked in.
Origination
. files address McAfee web site.
EXTRA DAT
Download and check
supplemental virus definition
file was posted. If the
DAT
files into the master repository
manually.
.
EXTRA DAT
file.
DAT
. files are from the
DAT
. files.
DAT
Product CD or downloaded
product ZIP file.
Check product deployment
packages into the master
repository manually. For a
specific location, see the
Configuration Guide for the
product.
Only the ePolicy Orchestrator
agent and System Compliance
Profiler deployment packages
are checked into the master
repository as part of the ePolicy
Orchestrator server installation.
Master repository — checked in
at installation.
For future versions of the agent,
you must check agent
installation packages into the
master repository manually.
Master repository — checked in
at installation.
For future versions of the agent,
you must check agent language
packages into the master
repository manually.
41
Deploying the Agent and Products
About deploying packages
4