which password must be configured on the IDM Auto/Cisco…

When using the Cisco IPS signature and engine auto updates feature from Cisco.com, which password must be configured on the IDM Auto/Cisco.com Update
pane?

A.
the IPS appliance “cisco” user account password

B.
the IPS appliance “service” user account password

C.
the IPS appliance “support” user account password

D.
the IPS appliance enable password

E.
the CCO user account password

Explanation:
http://www.cisco.com/en/US/docs/security/security_management/cs- mars/6.0/device/configuration/guide/chIpsCisoc6x.html
IPS Signature Dynamic Update Settings
In releases 6.0 and later, Cisco IPS supports dynamic signature updates. MARS can discover the new signatures and correctly process and categorize received
events that match those signatures. If this feature is not configured, the events appears as unknown event type in queries and reports, and MARS does not include
these events in inspection rules. These updates provides event normalization and event group mapping, and they enable your MARS Appliance to parse Day Zero
signatures from the IPS devices.
The downloaded update information is am XML file that contains the IPS signatures. However, this file does not contain detailed information, such as vulnerability
information. Detailed signature information is provided in later MARS signature upgrade packages just as with 3 rd – party signatures.
Before You Begin
·Dynamic IPS signature updates are disabled by default. ·Custom IPS signatures are not supported. You must manually import these signatures using the process
defined in Applying Custom Signature Updates. ·You can retrieve updates from CCO or from a local web server. After downloading and installing an update, the
MARS Appliance performs an auto-activate to load the new signature information.
·If configured to retrieve the signatures from CCO, MARS downloads the most recent package as determined by a combination of package name and the MD5
sum. ·MARS checks for updates at the specified interval, hourly (1, 2, 3, 6, or 12) or daily (1 through
14).
·In a Global Controller-Local Controller deployment, configure the dynamic signature URL and all relevant settings on the Global Controller. Do not attempt to
configure these features on the Local Controllers even though the web interface allows you to do so. ·When the Global Controller pulls the new signatures from

CCO, all managed Local Controllers download the new signatures from the Global Controller.