Cisco Security Licensing and Software Access 190319 PDF

Cisco Security Licensing and
Software Access Process
Global Security Sales Organization (GSSO)

Channel Engineering
March 19, 2019
Cisco Security Licensing and Software Access
Table of Contents
1 Introduction ................................................................................................................................ 5
2 Cisco Smart Licensing .............................................................................................................. 5
2.1 Creating a Cisco Smart Account ........................................................................................................ 5
2.2 Smart Licensing Account Activation Example ................................................................................... 8
2.2.1 Smart License Account Activation: FTD ..................................................................................... 8
2.2.2 Smart License Registration Example ......................................................................................... 9
3 Firepower Management Center (FMC) ............................................................................ 10

3.1 Software Download: FMC .............................................................................................................. 10
3.2 Software Request: FMC .................................................................................................................. 11
3.3 License Request: FMC ..................................................................................................................... 12
3.3.1 POV Smart License: FMC ......................................................................................................... 13
3.3.2 Lab Smart License: FMC .......................................................................................................... 14
3.3.3 POV Classic License: FMC ........................................................................................................ 15
3.3.4 Lab Classic License: FMC ......................................................................................................... 17
4 Firepower Threat Defense (FTD) ...................................................................................... 18

4.1 Software Download: FTD ................................................................................................................ 18
4.1.1 Software Request: FTD ............................................................................................................ 20
4.2 License Request: FTD ...................................................................................................................... 21
4.2.1 POV Smart License: AnyConnect for FTD................................................................................. 21
4.2.2 Lab License: AnyConnect for FTD ............................................................................................ 22
4.2.3 POV Smart License: FTD .......................................................................................................... 23
4.2.4 Lab License: Cisco Smart Licensing for FTD ............................................................................. 24
5 Firepower Services for ASA or Firepower ...................................................................... 25

5.1 Software Download: Firepower Services for ASA or Firepower ..................................................... 25
5.1.1 Software Request: Firepower Services for ASA or Firepower .................................................. 27
5.2 License Request: Firepower Services for ASA or Firepower ........................................................... 28
5.2.1 POV License: Firepower Services for ASA or Firepower ........................................................... 29
5.2.2 Lab License: Firepower Services for ASA or Firepower ............................................................ 30
6 Adaptive Security Appliance (ASA) ................................................................................... 31

6.1 Software Download: ASA5500-X and Firepower 2100/4100 / 9300 .............................................. 31
6.1.1 Software Request: ASA ............................................................................................................ 34
6.2 License Request: ASA ...................................................................................................................... 34
6.2.1 POV License: ASA on Firepower 2100/4100/9300 .................................................................. 35
6.2.2 Lab License: Firepower 2100/4100/9300 ................................................................................ 36
6.2.3 POV License: ASA..................................................................................................................... 37
6.2.4 Lab License: ASA ...................................................................................................................... 39
2
7 Adaptive Security Virtual Appliance (ASAv).................................................................. 41

7.1 Software Download: ASAv .............................................................................................................. 41
7.1.1 Software Request: ASAv .......................................................................................................... 42
7.2 License Request: ASAv .................................................................................................................... 43
7.2.1 POV License: ASAv ................................................................................................................... 43
7.2.2 Lab License: ASAv .................................................................................................................... 45
8 Umbrella Managed Security Services Partner (MSSP) Portal .................................. 46

8.1 Umbrella MSSP Portal Requirements ............................................................................................. 46
8.2 Umbrella MSSP Access .................................................................................................................... 46
9 Umbrella Partner POV (PPoV) Portal .............................................................................. 47

9.1 Umbrella PPoV Portal Requirements .............................................................................................. 47
9.2 Umbrella PPoV Access .................................................................................................................... 48
10 Cisco Security Manager (CSM) ............................................................................................ 49

10.1 Software Download: CSM ............................................................................................................... 49
10.1.1 Software Request: CSM ........................................................................................................... 49
10.2 License Request: CSM ..................................................................................................................... 50
10.2.1 Lab License: CSM ..................................................................................................................... 51
11 Identity Services Engine (ISE) ............................................................................................. 53

11.1 Software Download: ISE .................................................................................................................. 53
11.1.1 Software Request: ISE ............................................................................................................. 54
11.2 License Request: ISE ........................................................................................................................ 54
11.2.1 POV License: ISE ...................................................................................................................... 56
11.2.2 Lab License: ISE ....................................................................................................................... 56
12 Access Control System (ACS) ............................................................................................... 57

12.1 Software Download: ACS ................................................................................................................ 57
12.1.1 Software Request: ACS ............................................................................................................ 58
12.2 License Request: ACS ...................................................................................................................... 59
12.2.1 Lab License: ACS ...................................................................................................................... 59
13 Web Security Appliance (WSA) .......................................................................................... 60

13.1 Software Download: WSA ............................................................................................................... 60
13.1.1 Software Request: WSA .......................................................................................................... 61
13.2 License Request: WSA ..................................................................................................................... 62
13.2.1 POV License: WSA ................................................................................................................... 62
13.2.2 Lab License: WSA..................................................................................................................... 63
14 Email Security Appliance (ESA).......................................................................................... 64

14.1 Software Download: ESA ................................................................................................................ 64
14.1.1 Software Request: ESA ............................................................................................................ 65
3
14.2 License Request: ESA ...................................................................................................................... 66

14.2.1 POV License: ESA ..................................................................................................................... 66
14.2.2 Lab License: ESA ...................................................................................................................... 67
15 Security Management Appliance (SMA) .......................................................................... 69

15.1 Software Download: SMA ............................................................................................................... 69
15.1.1 Software Request: SMA........................................................................................................... 70
15.2 License Request: SMA ..................................................................................................................... 70
15.2.1 POV License: SMA.................................................................................................................... 71
15.2.2 Lab License: SMA ..................................................................................................................... 72
16 Cloud Email Security (CES) .................................................................................................. 73

16.1 License Request: Cloud Email Security ........................................................................................... 73
16.2 POV License: Cloud Email Security .................................................................................................. 73
17 Advanced Malware Protection (AMP) for Endpoint ................................................... 77

17.1 License Request: AMP ..................................................................................................................... 77
17.1.1 POV License: AMP ................................................................................................................... 77
17.1.2 Lab License: AMP .................................................................................................................... 78
18 Cisco Threat Grid ..................................................................................................................... 79

18.1 License Request: Cisco Threat Grid ................................................................................................. 79
18.1.1 POV License: Cisco Threat Grid................................................................................................ 79
18.1.2 Lab License: Cisco Threat Grid ................................................................................................. 80
18.1.3 Meraki Integration: Cisco Threat Grid..................................................................................... 81
19 Stealthwatch ............................................................................................................................. 82
19.1 Security Online Visibility Assessment (SOVA): Stealthwatch .......................................................... 82
19.2 On-premise POV: Stealthwatch ...................................................................................................... 82
19.2.1 On-premise POV Request ........................................................................................................ 82
19.2.2 On-premise POV Extension...................................................................................................... 83
19.3 Software Access and Lab License: Stealthwatch............................................................................. 84
19.3.1 Software Access and Lab License: Stealthwatch ..................................................................... 84
19.3.2 Lab License Renewal: Stealthwatch ........................................................................................ 85
20 Cisco Defense Orchestrator ................................................................................................. 86

20.1 License Request: Cisco Defense Orchestrator ................................................................................ 86
20.1.1 POV License: Cisco Defense Orchestrator ............................................................................... 86
20.1.2 Lab License: Cisco Defense Orchestrator................................................................................. 86
21 Next Steps................................................................................................................................... 87
22 Change Log ................................................................................................................................. 88
4
1 Introduction
The Cisco Global Security Sales Organization (GSSO) is proud to continue the Security Licensing and
Software Access Program. This document outlines the processes that partner SEs will follow to request
licenses for Partner Executed POVs and labs or to obtain required software.
The Security Licensing and Software Access program supports multiple security products and evolves
with the Cisco Security portfolio. View the appropriate sections below to complete the Licensing and
Software Access request for supported Security products. The process is administered through Partner
Help which provides support in over 20 languages. Please send any escalations to
securitypov@cisco.com.
2 Cisco Smart Licensing
Many Security features are now enabled via Cisco Smart Licensing which will be configured within the
Management interfaces of those Security products. Before requesting any Security feature licenses
which are enabled via Smart Licensing, you or your organization must either have an existing Cisco
Smart Account or create a new Cisco Smart Account to associate the Security feature licenses to.
2.1 Creating a Cisco Smart Account
To create a new Cisco Smart Account and the Virtual Accounts within for Lab and Demo licenses, go to
http://software.cisco.com and select “Get a Smart Account” in the Administration section.
5
Select the appropriate radio button to either create the Smart Account yourself or proxy the creation to
the appropriate person. If you are creating the account, verify the Account information is correct and
select Continue.
The request will go through a validation process and the account will be created once the information
has been validated. After the account has been created, it is recommended to also create separate
Virtual Accounts to hold the Lab and/or POV licenses. To create the Virtual Accounts, log into the Smart
Account at http://software.cisco.com and select Manage Smart Account in the Administration section.
6
Next select Virtual Accounts and then select New Virtual Account.
Enter a name and description for the Virtual Account which would associate the Virtual Account to the
appropriate need (i.e. FTD Lab Account and/or FTD POV Account) and select Save.
Repeat this process as needed to create any additional Lab and/or POV Virtual Accounts.
7
2.2 Smart Licensing Account Activation Example
Many security licenses are now managed via Cisco Smart Licensing. The instructions that follow serve as
an example of enabling the Smart Software Licensing in the Smart Account Portal and then registering it
in a Firepower Management Center to utilize the POV/Lab licenses provisioned by Partner Help. These
instructions serve as an example, but need to be adjusted for the particular product being used.
2.2.1 Smart License Account Activation: FTD
To enable the Smart Licenses, go to http://software.cisco.com and log in using the credentials for the
appropriate Smart Account. Then select Smart Software Licensing in the License Window.
Next, select Inventory. Make sure the appropriate Virtual Account is selected, and then select New
Token.
8
Next, enter an appropriate description for the token (e.g. Customer FTD POV), set the Expire After field
to 60 days, click export controls box, and select Create Token.
Then copy the new token to then enter it into the FMC. On the token just created, click Actions and
then select Copy. This token will be utilized within the FMC as shown in the next section.
2.2.2 Smart License Registration Example
To enable the Smart Licenses in a Firepower Management Center (FMC), navigate through the FMC GUI
to System > Licenses > Smart Licenses and select Register. These instructions serve as an example, but
need to be adjusted for the particular product being used.
9
Paste the token created in the previous section into the Product Instance Registration Token field and
select Apply Changes.
You should now see details in the Smart License Status section and the FMC will be registered.
3 Firepower Management Center (FMC)
3.1 Software Download: FMC
This section covers the process to download the software required for the FMC. The instructions that
follow demonstrate how to obtain required software for a virtual FMC. There are many possible
software requirements and the information below serves as an example of a common configuration for
a partner executed POV or a Lab. Adjust the process outlined below as required to match your hardware
specifications.
To download the Firepower software, go to http://software.cisco.com/download/navigator.html. This

will present the Downloads Home > Products pane. Continue to navigate to Downloads Home >
Products > Security > Firewalls > Firewall Management > Firepower Management Center Virtual
10
Appliance > FireSIGHT System Software. Depending upon the features required, expand the All Releases
drop-down in the left hand pane to select a link such as 6.1.0 or later which provides an option to
download the software below. Select the following options and download the versions listed below or
later.
• Firepower Management Center Virtual64 VMWare
(Cisco_Firepower_Management_Center_VMware-6.1.0-330.tar.gz)
If you are unable to access the software due to entitlement, engage with your Cisco alliance manager to
associate your CCO account with your company to grant partner-level CCO access. If you are still unable
to access the software, open a case with partner help following the instructions in the following section.
3.2 Software Request: FMC
To complete a Software Request, open a case with Partner Help. You can go to the Partner support page
and under “Open a case to engage with GVE”, select open a case or chat with a GVE agent. In the case,
provide the following required information in the Case Description field.
• Architecture = Security
• Technology = Network Security
• Service Type = Cisco Product or Service Information
• Sub Service Type = Licensing
• Case Language= English (or adjust respectively)
Click the “next” button to advance to the next screen and enter the following information.
11
• Case Title = Software Access

• Case Description
o Product type is [FMC]
o FMC type is [Hardware or Virtual FMC Model]
o FMC Software [Version]
Click the “submit” button.
Upon receiving this case, partner help will use the special file publish tool to provide the requested
software. You will receive an email from Cisco to the address associated with your Cisco CCO ID. Partner
Help will be notified when you download the requested software.
Example Case Description

o FMC type is [Virtual]
o FMC Software [Cisco_Firepower_Management_Center_VMware-6.1.0-330.tar.gz]
3.3 License Request: FMC
As of v6.0 and later, the FMC uses smart licensing. In software version v5.4 and earlier, the FMC requires
a classic license. License duration is dependent on internal tools and currently all SMART Licenses are
limited to 60-days. Partner Help supports smart and classic license requests for POVs and Partner Labs.
If you are requesting a classic FMC license, you will need the FMC License Key. This can be found by
navigating through the FMC to System > Licenses > Classic Licenses.
On the screen which follows, you will be presented with the Add Feature License field where you can
copy the License Key and provide it in the case with the Partner Help agent.
12
3.3.1 POV Smart License: FMC
Starting in software version v6.0, the FMC requires a Smart License. The instructions for Smart Licensing
account creation and activation were provided in Section 2 of the guide. You must first complete that
section prior to requesting an FMC Smart License.
To complete a License Request, open a case with Partner Help. You can go to the Partner support page
• Deal ID= CCW Deal ID *Note: A CCW Deal ID is mandatory for this service.
• Case Title = FMC POV Smart License

o Cisco Cybersecurity Partner Account Manager [Cisco CyPAM if applicable]
o Partner AM CCO ID [Partner AM CCO ID]
o Partner SE CCO ID [Partner SE CCO ID]
o Partner Fire Jumper CCO ID [Partner Fire Jumper CCO ID if applicable]
o POV License for [Customer name]
o Customer Point of Contact [Customer POC]
o Customer Opportunity Value [Opportunity in USD]
o FMC type [Hardware or Virtual Sensor Model & OS (VMWare or KVM)]
o Partner Smart Account Domain ID [Smart Account Domain ID]
o Partner Smart Account [Smart Account Name]
o Partner Smart Virtual Account [Smart Virtual Account Name]
o Expected Start Date is [POV Start Date]
13

o Cisco Cybersecurity Partner Account Manager [John Smith]
o Partner AM CCO ID [dmurphy]
o Partner SE CCO ID [bhorner]
o Partner Fire Jumper CCO ID [ghubbard]
o POV License for [ACME Inc]
o Customer Point of Contact [Wiley Coyote]
o Customer Opportunity Value [$100k USD]
o FMC type is [2 Device FMCv on VMWare]
o Partner Smart Account Domain ID [partner.com]
o Partner Smart Account [POV]
o Partner Smart Virtual Account [Default]
o Expected Start Date is [2 January 2017]
Upon receiving this case, Partner Help will request Smart License keys. You will receive a FMC license in
your Smart account that can be loaded using the instructions in section 2. One POV license extension
will be granted per customer. To receive the extension, open a new Partner Help case following the
process above.
3.3.2 Lab Smart License: FMC
Starting in software version v6.0, the FMC requires a Smart License. The instructions for Smart Licensing
account creation and activation were provided in Section 2 of the guide. You must first complete that
section prior to requesting an FMC Smart License.
• Case Title = FMC Lab Smart License

14

o Expected Start Date is [Lab Start Date]
Example Question
o FMC type is [2 Device FMCv on VMWare]
o Partner Smart Account [Lab]
Upon receiving this case, Partner Help will request Smart License keys. You will receive a FMC license in
process above.
3.3.3 POV Classic License: FMC
• Case Title = FMC POV License

15

o FMC License Key [FMC Key found in Section 3.3]

o FMC type [2 Device FMCv on VMWare]
o FMC License Key [66:00:50:56:11:11:11]
Upon receiving this case, Partner Help will generate POV license keys. You will receive a FMC license and
this license can be loaded using the instructions provided by Partner Help.
One POV license extension will be granted per customer. To receive the extension, open a new Partner
Help case following the process above.
16
3.3.4 Lab Classic License: FMC
• Case Title = FMC Lab License

o FMC type [Hardware or Virtual Sensor Model]

o FMC type [2 Device FMCv on VMWare]
o FMC License Key [66:00:50:56:11:11:11]
Upon receiving this case, Partner Help will generate POV license keys. You will receive a FMC license and
this license can be loaded using the instructions provided by Partner Help.
17
Unlimited Lab license extensions will be granted to the Partner. To receive the extension, open a new
Partner Help case following the process above.
4 Firepower Threat Defense (FTD)
Starting in software version v6.0, the FTD features are managed via Cisco Smart Licensing which must be
enabled within the FMC. You must first enable the Smart Software Licensing in the Smart Account
Portal and then register the FMC to the Smart Account to utilize the POV/Lab licenses for FTD which will
be provisioned by Partner Help. The instructions for Smart Licensing account activities were provided in
Section 2 of the guide.
4.1 Software Download: FTD
This section covers the process to download the software required for Firepower Threat Defense on the
ASA 5515-X chassis. There are many possible software requirements and the information below serves
as an example of a common configuration for a partner executed POV or a Lab. Adjust the process
outlined below as required to match your hardware specifications. To download the FTD system
software, go to http://software.cisco.com/download/navigator.html. This will present the Downloads
Home > Products pane. Continue to navigate to Downloads Home > Products > Security > Firewalls >
Next-Generation Firewalls (NGFW) > ASA 5500-X with Firepower Services > ASA 5515-X with Firepower
Services > Firepower Threat Defense Software.
Select the following options and download the versions listed below or later.
• Firepower Threat Defense for ASA 55XX series v6.1.0

(ftd-6.1.0-330.pkg)
• Firepower Threat Defense v6.1.0 boot image for ASA 5512/5515/5525/5545/5555 devices
(ftd-boot-9.6.2.0.cdisk)
NOTE: The ASA5585-X platforms do not support FTD software.

18
19
4.1.1 Software Request: FTD

o Product type [FTD]
o Sensor type [Hardware or Virtual Sensor Model]
o FTD Boot Image [Version]
o FTD Install Package [Version]

o Sensor Type [ASA5515-X]
o FTD Boot Image [v6.1.0]
o FTD Install Package [v6.1.0]
20
4.2 License Request: FTD
Partner Help supports license requests for both POVs and Partner Labs. License duration is dependent
on internal tools, but the goal is to provide 45-day keys for POVs and 60-day keys for labs for FTD and
60-day keys for POVs and 60-day keys for AnyConnect
4.2.1 POV Smart License: AnyConnect for FTD
To complete a License Request, open a case with Partner Help You can go to the Partner support page
• Case Title = FTD POV Smart License

o Product type [AnyConnect for FTD]
21

o Product Type [AnyConnect for FTD]
o Sensor type [Cisco Firepower Threat Defense Virtual Appliance]
Upon receiving this case, Partner Help will request Smart License keys. You will receive an AnyConnect
for FTD license in your Smart account that can be loaded using the instructions in section 2. One POV
license extension will be granted per customer. To receive the extension, open a new Partner Help case
following the process above.
4.2.2 Lab License: AnyConnect for FTD
To request a Partner Lab License, open a case with Partner Help. You can go to the Partner support page
• Case Title = AnyConnect for FTD Lab Instance

o Product type is [AnyConnect for FTD]
o Partner Smart Account Name [Smart Account Name]
o Partner Smart Virtual Account Name [Smart Virtual Account Name]
22

o Product type [AnyConnect for FTD]
Upon receiving this case, Partner Help will request Smart License keys. You will receive an AnyConnect
for FTD license in your Smart account that can be loaded using the instructions in section 2. Lab license
extensions will be granted for Partner labs. To receive the extension, open a new Partner Help case
4.2.3 POV Smart License: FTD
Starting in software version v6.0, the FTD requires a Smart License. The instructions for Smart Licensing
Account creation and activation were provided in Section 2 of the guide. You must first complete that
section prior to requesting an FTD Smart License.
• Case Title = FTD POV Smart License

23


o Product Type [FTD]
Upon receiving this case, Partner Help will request Smart License keys. You will receive an FTD license in
process above.
4.2.4 Lab License: Cisco Smart Licensing for FTD
24
• Case Title = FTD Lab License

o Product type is [FTD]
o Sensor type is [Hardware or Virtual Sensor Model]
o Partner Smart Account Name [Smart Account Name]
o Partner Smart Virtual Account Name [Smart Virtual Account Name]

Upon receiving this case, Partner Help will generate Lab license keys. You will receive confirmation that
the FMC and FTD licenses were loaded into your Smart Account and the licenses can be loaded using the
instructions provided in Section 2 of the Guide.
5 Firepower Services for ASA or Firepower
5.1 Software Download: Firepower Services for ASA or Firepower
This section covers the process to download the software required for Firepower Services for ASA or
Firepower. The instructions that follow demonstrate how to obtain required software for Firepower
Services for ASA on the 5515-X, Firepower on the 7110, and a virtual Firepower MC. There are many
possible software requirements and the information below serves as an example of a common
configuration for a partner executed POV. Adjust the process outlined below as required to match your
hardware specifications.
To download the Firepower Services for ASA software, go to

http://software.cisco.com/download/navigator.html. This will present the Downloads Home > Products
pane. Continue to navigate to Downloads Home > Products > Security > Firewalls > Next-Generation
Firewalls (NGFW) > ASA 5500-X with FirePOWER Services > ASA 5515-X with Firepower Services >
Firepower Services Software for the ASA. Depending upon the features required, expand the All
Releases drop-down in the left hand pane to select a link such as 6.0.0 or 5.4.0 which provides an option
to download the software below.
25
Select each of the following options and download the versions listed below or later.
• Cisco ASA with Firepower Services ASA 5512-X through 5555-X Boot Image (asasfr-5500x-boot-
5.4.0-763.img)
• Cisco ASA with Firepower Services Install Package (asafr-sys-5.4.0-763.pkg)
To download the Firepower software, go to http://software.cisco.com/download/navigator.html. This

Products > Security > Next Generation Intrusion Prevention System (NGIPS) > Firepower 7000 Series
Appliances > Firepower Appliance 7110 > Firesight System Software. As required, expand the All
Releases drop-down in the left hand pane to select a link such as 6.0.0.0 or 5.4.0 which provides an
option to download the software below. Select the following option and download the versions listed
below or later.
• Sourcefire 3D S3 Sensor Device Restore ISO 5.4
(Sourcefire_3D_Device_S3-5.4.0-763-Restore.iso)
Next, select the Security breadcrumb. Continue navigating to Downloads Home > Products > Security >
Firewalls > Firewall Management > Firepower Management Center Virtual Appliance > FireSIGHT System
Software. Depending upon the features required, expand the All Releases drop-down in the left hand
pane to select a link such as 6.0.0.0 or 5.4.0 which provides an option to download the software below.
26
Select the following options and download the versions listed below or later.
• FireSIGHT Virtual Defense Center for VMWare Package Installer
(Sourcefire_Defense_Center_Virtual64_VMware-5.4.0-763.tar.gz)
5.1.1 Software Request: Firepower Services for ASA or Firepower

o Product type [Firepower for ASA -OR- Firepower]
o ASA with FP Boot Image [Version]
27
o ASA with FP Install Package [Version]

o Product type [Firepower for ASA]
o Sensor type [ASA5515-X]
o ASA with FP Boot Image [v5.4.0]
o ASA with FP Install Package [v5.4.0]
5.2 License Request: Firepower Services for ASA or Firepower
on internal tools, but the goal is to provide 45-day keys for POVs and 180-day keys for labs.
If you are using software version v5.4 of the FMC, you will need the Firepower Management Center
License Key prior to initiating the License Request. The process for this is provided earlier in the guide.
If using the On-Box Firepower Manager in ASDM, you will navigate to Configuration > ASA Firepower
Configuration > Licenses. Select Add New License, copy the License Key, and open a request using the
same process as the FMC which is provided earlier in the guide.
If you do not see the ASA Firepower Configuration option, review the ASA 5506-X Quick Start Guide.
28
5.2.1 POV License: Firepower Services for ASA or Firepower
To request a POV License, open a case with Partner Help. You can go to the Partner support page and
under “Open a case to engage with GVE”, select open a case or chat with a GVE agent. In the case,
• Case Title = Firepower POV License

o Customer Opportunity [Opportunity in USD]

o Customer Opportunity [$100k USD]
o
29
Upon receiving this case, Partner Help will generate POV license keys. You will receive Control, AMP, and
URL license keys. All keys are required for full functionality of the appliance with a separate Firepower
MC and can be loaded using the instructions provided by partner help.
One POV license extension will be granted per customer. To receive the extension, open a new partner
help case following the process above.
5.2.2 Lab License: Firepower Services for ASA or Firepower
• Case Title = Firepower Lab License

30

Upon receiving this case, partner help will generate Lab license keys. You will receive Control, AMP, and
URL license keys.
License extension will be granted when required. To receive the extension, open a new partner help
case following the process above.
6 Adaptive Security Appliance (ASA)
6.1 Software Download: ASA5500-X and Firepower 2100/4100 / 9300
This section covers the process to download the software required for the Adaptive Security Appliance
on the ASA5500-X chassis or the Next-Generation Firepower 2100/4100/9300 chassis. The instructions
that follow demonstrate how to obtain required software for an ASA 5515-X and FP4100. There are
many possible software requirements and the information below serves as an example of a common
configuration for a partner executed POV. Adjust the process outlined below as required to match your
hardware specifications.
For best performance, Firepower Services for ASA requires system software 9.2(2) or later. For
additional information on migration paths and upgrade dependencies, please refer to the following link:
http://www.cisco.com/c/en/us/td/docs/security/asa/asa92/upgrade/upgrade92.html.
31
To download the ASA system software, go to http://software.cisco.com/download/navigator.html. This

Products > Security > Firewalls > Adaptive Security Appliances (ASA) > ASA 5500-X Series Next-
Generation Firewalls > ASA 5515-X Adaptive Security Appliance > Software on Chassis.
Select each of the following options and download the versions listed below or later.
• Adaptive Security Appliance (ASA) Device Manager: 7.3.3 (asdm-733.bin)
• Adaptive Security Appliance (ASA) Software: 9.2.3.SMP (asa923-smp-k8.bin)
As an example to download the Firepower 4110 system software, go to

http://software.cisco.com/download/navigator.html. This will present the Downloads Home > Products
pane. Continue to navigate to Downloads Home > Products > Security > Firewalls > Next-Generation
Firewalls (NGFW) > Firepower 4100 Series > Firepower 4110 Security Appliance > Adaptive Security
Appliance (ASA) Software.
Expand the Latest and then the 9.6 options on the left pane and then select the following option and
publish the version listed below or later.
32
• Cisco Adaptive Security Virtual Appliance CSP package for the Cisco Firepower Series (cisco-
asa.9.6.2.SPA.csp)
33
6.1.1 Software Request: ASA

o Product type is [ASA]
o Appliance type is [Hardware Model]
o ASA Device Manager [Version]
o ASA Software [Version]

o Product type [ASA]
o Appliance Type [ASA5515-X]
o ASA Device Manager [7.3.3]
o ASA Software [9.2.3]
6.2 License Request: ASA
on internal tools, but the goal is to provide 45-day keys for POVs and 180-day keys for labs on the
ASA5500-X chassis using Classic licenses. For the Firepower 4100/9300 chassis, ASA features are
enabled via Smart Licensing with a 60-day key.
Partners will need the ‘show version’ from the ASA5500-X chassis prior to initiating the License Request.
On the ASA you will be using for the customer opportunity, you can issue the ‘show version’ command
34
in the CLI or login to ASDM and select Tools > Command Line Interface. In the Command drop-down,
select show version and click Send.
Copy all the text in the Response section and paste it into a local text editor.
6.2.1 POV License: ASA on Firepower 2100/4100/9300
To request a POV Smart License for ASA on the Firepower 2100/4100/9300 Appliances, open a case with
Partner Help. You can go to the Partner support page and under “Open a case to engage with GVE”,
select open a case or chat with a GVE agent. In the case, provide the following required information in
the Case Description field.
• Case Title = ASA on Firepower Appliance POV License

35

o Product type [ASA on Firepower Appliance]
o Partner Smart Account Domain ID [Partner Smart Account Domain ID]
o Partner Smart Account Name [Partner Smart Account Name]
o Partner Smart Virtual Account Name [Partner Smart Virtual Account Name]
o Sensor type is [Hardware Model]

o Partner Smart Account Name [POV]
o Partner Smart Virtual Account Name [Default]
o Sensor type is [FP4140]
Upon receiving this case, Partner Help will generate POV license keys. You will receive confirmation that
the ASA on Firepower Appliances licenses were loaded into your Smart Account and the licenses can be
loaded using the instructions provided in Section 2 of the Guide.
6.2.2 Lab License: Firepower 2100/4100/9300
36

• Case Title = ASA on Firepower Appliance Lab License

o Product type is [ASA on Firepower Appliance]
o Partner Smart Account Domain ID [Partner Smart Account Domain ID]
o Partner Smart Account Name [Partner Smart Account Name]
o Partner Smart Virtual Account Name [Partner Smart Virtual Account Name]
o Sensor type is [Hardware Model]

o Partner Smart Account Name [Lab]
o Sensor type is [FP4140]
Upon receiving this case, Partner Help will generate Lab license keys. You will receive confirmation that
the ASA on Firepower Appliances licenses were loaded into your Smart Account and the licenses can be
loaded using the instructions provided in Section 2 of the Guide.
6.2.3 POV License: ASA
37
• Case Title = POV License

o Appliance type [Hardware Model]
o Customer Point of Contact is [Customer POC]
o Customer Opportunity is [Opportunity in USD]
o ASA Serial Number [Serial Number]
o Platform License [Base or Security Plus]
o VPN Features [Strong Encryption, Advanced Endpoint Assessment, AnyConnect Mobile,
AnyConnect Essentials, AnyConnect VPN Phone, Clustering]
o Firewall Features [Botnet Traffic Filter]
o AnyConnect Premium Licenses [Quantity]
o Security Contexts [Quantity]
o Show Version [Paste output from ‘Show Version’ command]

o Appliance type [ASA5515-X]
o Customer Point of Contact is [Wiley Coyote]
o Customer Opportunity is [$100k USD]
o ASA Serial Number [FTX999999QQ]
o Platform License [Base]
o VPN Features [Strong Encryption, AnyConnect Mobile, AnyConnect Essentials]
o Firewall Features [None]
o AnyConnect Premium Licenses [25]
o Security Contexts [0]
Upon receiving this case, Partner Help will generate POV license keys. You will receive the appropriate
ASA license activation key that can be loaded into ASDM by browsing to Configuration > Device
Management > Licensing > Activation Key.
38
Load the Activation Key in to the New Activation Key field, select Update Activation Key, save your
configuration, and reload the ASA.
6.2.4 Lab License: ASA
To request a Lab License, open a case with Partner Help. You can go to the Partner support page and
• Case Title = Lab License
39
o Appliance type [Hardware Model]
o ASA [Serial Number]
o Platform License [Base or Security Plus]
o VPN Features [Strong Encryption, Advanced Endpoint Assessment, AnyConnect Mobile,
AnyConnect Essentials, AnyConnect VPN Phone, Clustering]
o Firewall Features [Botnet Traffic Filter]
o AnyConnect Premium Licenses [Quantity]
o Security Contexts [Quantity]

o Appliance type [ASA5515-X]
o ASA Serial Number [FTX999999QQ]
o Platform License [Base]
o VPN Features [Strong Encryption, AnyConnect Mobile, AnyConnect Essentials]
o Firewall Features [None]
o AnyConnect Premium Licenses [25]
o Security Contexts [0]
Upon receiving this case, Partner Help will generate Lab License keys. You will receive the appropriate
ASA license activation key that can be loaded into ASDM by browsing to Configuration > Device
Management > Licensing > Activation Key.
40
Load the Activation Key in to the New Activation Key field, select Update Activation Key, save your
configuration, and reload the ASA.
7 Adaptive Security Virtual Appliance (ASAv)
7.1 Software Download: ASAv
This section covers the process to download the software required for the Adaptive Security Virtual
Appliance (ASAv). For best performance, the ASAv requires system software 9.5(1) or later. For
additional information on migration paths and upgrade dependencies, please refer to the following link:
http://www.cisco.com/c/en/us/support/security/asa-5500-series-next-generation-firewalls/products-
release-notes-list.html.
41
To download the ASA system software, go to http://software.cisco.com/download/navigator.html. This

Products > Security > Firewalls > Adaptive Security Appliances (ASA) > Adaptive Security Virtual
Appliance (ASAv) > Adaptive Security Appliance (ASA) Software.
Select the following option and download the versions listed below or later.
• Cisco Adaptive Security Appliance (ASA) Device Manager: 7.5.1 (asdm-751.bin)
• Cisco Adaptive Security Virtual Appliance OVA Package for the Cisco ASAv Virtual Firewall:
(asav951.ova)
7.1.1 Software Request: ASAv
42

o Product type is [ASAv]
o ASA Device Manager [Version]
o ASAv Software [Version]

o Product type is [ASAv]
o ASA Device Manager [v9.5.1]
o ASAv Software [asav951.ova]
7.2 License Request: ASAv
Partner Help supports license requests for both POVs and Partner Labs. The ASAv ships with a license by
default that is limited to 100kbps to connectivity testing and lab environments. Follow the process
below if you require a license for regular operation.
7.2.1 POV License: ASAv
provide the following required information in the Case Description field. Note that a SMART Account is
required for ASAv licenses. The instructions for Smart Licensing account activities were provided in

43
o Product type [ASAv]
o Partner Smart Account Domain ID [domain.com]
o Partner Smart Account Name [account name]
o Partner Smart Virtual Account Name [virtual account name]
o ASAv Model [ASAv5, ASAv10, or ASAv30]
o ASAv Serial Number [Serial Number]
o Quantity [#]

o Partner Smart Account Name [POV]
o ASAv Model [ASAv10]
o ASAv Serial Number [FTX999999QQ]
o Quantity [1]
Upon receiving this case, Partner Help will request Smart License keys. You will receive an ASAv license
in your Smart account that can be loaded using instructions similar to section 2. One POV license
extension will be granted per customer. To receive the extension, open a new Partner Help case
44
7.2.2 Lab License: ASAv
provide the following required information in the Case Description field. Note that a SMART Account is
required for ASAv licenses. The instructions for Smart Licensing account activities were provided in

o Partner Smart Account Domain ID [domain.com]
o Partner Smart Account Name [account name]
o Partner Smart Virtual Account Name [virtual account name]
o ASAv Model [ASAv5, ASAv10, or ASAv30]
o ASAv [Serial Number]
o Quantity [#]

o Partner Smart Account Name [Lab]
o ASAv Model [ASAv10]
o ASAv Serial Number [FTX999999QQ]
o Quantity [1]
Upon receiving this case, Partner Help will request Smart License keys. You will receive an ASAv license
in your Smart account that can be loaded using instructions similar to section 2. One POV license
extension will be granted per customer. To receive the extension, open a new Partner Help case
45
8 Umbrella Managed Security Services Partner (MSSP) Portal
The Selling Umbrella page on the Partner Community at https://communities.cisco.com/docs/DOC-

64565 contains information on the training and requirements to be eligible for MSSP Portal access, but
these requirements will also be noted below.
Please note: Only one MSSP Portal is allowed per Partner organization. As such, the first Partner SE
requesting MSSP Portal access will be set as the Administrator for the entire Partner organization. All
subsequent Partner SEs will need to work with this Administrator to create additional Partner SE
Administrator accounts in the MSSP Portal. If find there is an existing MSSP Portal for a Partner
organization, we will provide the Administrator information for follow up within the Partner
organization. Also, the email address associated with the nominated Administrator’s CCO profile will be
used as the authentication mechanism for the MSSP Portal, so please ensure the correct email address is
associated BEFORE submitting a request in the PMA tool. Personal email addresses in CCO profiles will
not be accepted, so please ensure the correct business email address is used.
8.1 Umbrella MSSP Portal Requirements
In order to qualify for Umbrella MSSP Portal access, the Partner Organization must meet the following
requirements.
The Partner Organization MUST:

1. Be an authorized Cisco partner in good standing
2. Have an operational SOC and preferably an API developer/team
3. Provide frontline support
4. Have (2) SEs on staff per Partner GEO ID who have either:
• Completed at least Stage 4 in the Fire Jumper Cloud, Web, and Email Security
Competency Area
OR
• Completed the Cisco Umbrella Pre-Sales Technical Training and COLT exam as well as
the Cisco Umbrella MSSP Pre-Sales Training for SEs and COLT exam.
8.2 Umbrella MSSP Access
To request Umbrella MSSP Portal access, an authorized person from the Partner organization must
follow the process outlined on the Selling Umbrella Community at
https://communities.cisco.com/docs/DOC-64565. Partners may not reach out directly to Partner Help
for MSSP Portal access. The Partner Help team can only create the MSSP Portal and provide the
relevant information for the Umbrella MSSP Portal to the nominated Administrator once the approval
process has completed via the Program Management and Application (PMA) tool as outlined in the
Selling Umbrella Community page.
46
9 Umbrella Partner POV (PPoV) Portal
This section covers the process to request Umbrella Partner POV (PPoV) Portal access. The Selling
Umbrella page on the Partner Community at https://communities.cisco.com/docs/DOC-64565 contains
information on the training and Partner requirements to be eligible for PPOV Portal access, but these
requirements will also be noted below.
Please note: Only one PPoV Portal is allowed per Partner organization. As such, the first Partner SE
requesting PPoV Portal access will be set as the Administrator for the entire Partner organization. All
subsequent Partner SEs will need to work with this Administrator to create additional Partner SE user
accounts in the PPoV Portal. If find there is an existing PPoV Portal for a Partner organization, we will
provide the Administrator information for follow up within the Partner organization. Also, the email
address associated with the nominated Administrator’s CCO profile will be used as the authentication
mechanism for the PPoV Portal, so please ensure the correct email address is associated to the Partner
organization BEFORE submitting a request to the Partner Help team.
9.1 Umbrella PPoV Portal Requirements
In order to qualify for Umbrella PPoV Portal access, the Partner Organization and Partner SE MUST meet
the following requirements.
1. The Partner Organization must not be a Distributor

2. The Partner Organization must hold one of the following Partner Certifications/Specializations:
a. Security Express Track (CESSEC)
b. Advanced Security Architecture Specializations (ASAS)
3. The Partner SE must either:
a. Complete at least Stage 4 in the Fire Jumper Cloud, Web, and Email Security
Competency Area
OR
b. Complete the Cisco Umbrella Technical Training Exam COLT exam and provide a screen
shot of the passing score in the request to Partner Help
47
9.2 Umbrella PPoV Access
To request Umbrella PPoV Portal access, open a case with Partner Help. You can go to the Partner
support page and under “Open a case to engage with GVE”, select open a case or chat with a GVE agent.
In the case, provide the following required information in the Case Description field.
• Technology = Cloud
• Case Title = PPoV Portal Access

o Product type [Umbrella PPoV]
o Administrator Email [Partner SE CCO Email Address]
o Administrator First Name [Partner SE First Name]
o Administrator Last Name [Partner SE Last Name]

o Product type [Umbrella PPoV]
o Administrator Email [jdoe@partner.com]
o Administrator First Name [John]
o Administrator Last Name [Doe]
o **Also attach screen shot of passing score on COLT exam if applicable
Upon receiving this case, Partner Help will review the information and if all of the criteria has been met,
the Partner Help Agent will create the PPoV Portal and provide the relevant information for the
Umbrella PPoV Portal. The requester should also receive an activation email with the same information
and a link to access the portal and create a password to the portal to begin provisioning.
48
10 Cisco Security Manager (CSM)
10.1 Software Download: CSM
This section covers the process to download the software required for a Cisco Security Manager
installation. There are many possible software requirements and the information below serves as an
example of a common configuration for a partner executed POV. Adjust the process outlined below as
required to match your hardware specifications.
To download the CSM software, go to http://software.cisco.com/download/navigator.html. This will

present the Downloads Home > Products pane. Continue to navigate to Downloads Home > Products >
Security > Security Management > Security Manager.
Scroll down to the following options and download the versions listed below or later. You should
download any patches for the best performance.
• Cisco Security Manager 4.9 (fcs-scm-490-win-k9.zip)
10.1.1 Software Request: CSM
To complete a Software request, open a case with Partner Help. You can go to the Partner support page
• Technology = Security Management and Orchestration
49

o Product type [CSM]
o CSM Software [Version]
o Additional CSM Software [Version]

o CSM Software [v4.9]
o Additional CSM Software [N/A]
10.2 License Request: CSM
on internal tools, but the goal is to provide 45-day keys for POVs and 180-day keys for labs. CSM ships
with a standard 90-day 50 device evaluation enterprise license which is ideal for POVs. Follow the
process below if you require a longer term license for a lab.
10.2.1 POV License: CSM
50

o Product type [ISE]
o Appliance type is [Hardware Model or VM Model
o Serial Number [Serial Number]

o Customer Opportunity [$100k]
o Appliance Type [S170]
o Serial Number [0022195D9132-GKVRBJ4]
Upon receiving this case, Partner Help will generate POV License keys. You will receive CSM license keys
that can be loaded into CSM by browsing to Tools > Security Manager Administration > Licensing. Select
the CSM tab and click Install a License. License extension will be granted when required. To receive the
extension, open a new partner help case following the process above.
10.2.2 Lab License: CSM
51



Upon receiving this case, Partner Help will generate Lab License keys. You will receive CSM license keys
that can be loaded into CSM by browsing to Tools > Security Manager Administration > Licensing. Select
the CSM tab and click Install a License. License extension will be granted when required. To receive the
extension, open a new partner help case following the process above.
52
11 Identity Services Engine (ISE)
11.1 Software Download: ISE
This section covers the process to download the software required for a virtual Identity Services Engine
To download the ISE software, go to http://software.cisco.com/download/navigator.html. This will

Security > Access Control and Policy > Identity Services Engine > Identity Services Engine Software.
Scroll down to the following options and download the versions listed below or later. You should
download any patches for the best performance.
• Cisco ISE Software version 1.3.0 full installation (no IPN functionality) (ise-1.3.0.876.x86_64.iso)
• Cisco Identity Services Engine Software Patch Version 1.3.0.876-Auto1-125229
(ise-patchbundle-1.3.0.876-Auto1-125229.x86_64.tar.gz)
53
11.1.1 Software Request: ISE
provide the following required information in the Case Description field. In the additional ISE software
section, enter the file names for any additional software required.
• Technology = Policy & Access

o ISE Software [Version]
o ISE Patch [Version]
o Additional ISE Software [Version]

o ISE Software [ise-1.3.0.876.x86_64.iso]
o ISE Patch [ise-patchbundle-1.3.0.876-Auto1-125229.x86_64.tar.gz]
o Additional ISE Software [N/A]
11.2 License Request: ISE
on internal tools, but the goal is to provide 45-day keys for POVs and 180-day keys for labs. ISE ships
with a standard 90-day 100 device evaluation license which is ideal for POVs. Follow the process below if
you require a longer term license for a lab.
54
Partners will need the ‘show udi’ from the ISE prior to initiating the License Request. On the ISE
appliance you will be using for the customer opportunity, issue the ‘show udi’ command in the CLI or
login to the ISE interface and select Help > About in the lower left corner. Copy the Product Identifier
(PID or SPID), Version Identifier (VID or VPID) and Serial Number (SN) and paste it into a local text editor.
11.2.1 POV License: ISE

o Product Name [Product Name]
o Email [Partner SE Email]
o Primary Product ID [Product ID]
o Primary Serial Number [Serial Number]
o Primary Version ID [Version ID]
55

o Product Name [ISE-APX-90DAY-100-ENDPTS]
o Email [Partner SE Email]
o Primary Product ID [ISE-VM-K9]
o Primary Serial Number [ABCDEFGHIJK]
o Primary Version ID [V01]
Upon receiving this case, Partner Help will generate POV License keys. You will receive ISE license keys
that can be loaded into ISE by browsing to Administration > System > Licensing. If your license is already
expired, you will immediately be prompted to import a new License File. Browse to the License Keys
provided and click Import for each.
11.2.2 Lab License: ISE

56

o Primary Product ID [SPID]
o Primary Version ID [VPID]
o Primary Serial Number [SN]

o Primary Product ID [ISE-VM-K9]
o Primary Version ID [V01]
o Primary Serial Number [ABCDEFGHIJK]
Upon receiving this case, Partner Help will generate Lab License keys. You will receive ISE license keys
that can be loaded into ISE by browsing to Administration > System > Licensing. If your license is already
expired, you will immediately be prompted to import a new License File. Browse to the License Keys
provided and click Import for each.
12 Access Control System (ACS)
12.1 Software Download: ACS
This section covers the process to download the software required for a virtual Access Control System
To download the ACS software, go to http://software.cisco.com/download/navigator.html. This will

Security > Access Control and Policy > Secure Access Control System.
57
Scroll down to the following options and publish the versions listed below or later. You should publish
any patches and may also publish a specific release or file requested by a partner.
• ACS 5.7 FCS Official Version (ACS_v5.7.0.15.iso)
12.1.1 Software Request: ACS
58
o Product type [ACS]
o ACS Software [Version]
o ACS Patch [Version]
o Additional ACS Software [Version]

o ACS Software [5.7.0.15]
o ACS Patch [N/A]
o Additional ACS Software [N/A]
12.2 License Request: ACS
on internal tools, but the goal is to provide 45-day keys for POVs and 180-day keys for labs. ACS has a
standard 90-day evaluation license which is ideal for POVs. Follow the process below if you require a
longer term license for a lab.
12.2.1 Lab License: ACS

o Product type is [ACS]
59

Upon receiving this case, Partner Help will generate Lab License keys. You will receive an ACS license key
that can be loaded into ACS after login. If your license is already expired, you will immediately be
prompted to import a new License File.
Browse to the License Key provided and click Install.
If you would like to replace an existing ACS license, browse to System Administration > Configuration >
Licensing > Base Server License. Select a license and click Upgrade.
13 Web Security Appliance (WSA)
13.1 Software Download: WSA
This section covers the process to download for the software required for WSA. The instructions that
follow demonstrate how to provide required software for a virtual WSA S000V installation on VMware
ESXi. There are many possible software requirements and the information below serves as an example
of a common configuration for a partner executed POV. Adjust the process outlined below as required
to match your hardware specifications. For best performance, partners should run WSA 8.5 or later.
Note that this software download process only supports virtual appliances because software is
automatically downloaded to physical appliance.
To download the software, go to http://software.cisco.com/download/navigator.html. This will present

the Downloads Home > Products pane. Continue to navigate to Downloads Home > Products > Security
> Web Security > Web Security Virtual Appliance
60
Scroll down to the following options and download the version listed below or later.
• Cisco Web Security Virtual Appliance S000V (coeus-8-5-0-497.ova)
13.1.1 Software Request: WSA
• Technology = Content Security

o Product type [WSA]
o Appliance type [VM Model]
o WSA Version [Version]

61

o Appliance Type [S000V]
o WSA Version [coeus_8_7_0_172_S000V.zip]
13.2 License Request: WSA
on internal tools, but the goal is to provide 45-day keys for POVs and 180-day keys for labs. As of the
recent update of this document, partner help is able to provide lab and POV licenses for both virtual and
physical appliances.
Partners will need the Serial Number from the WSA prior to initiating the License Request. The serial
number can be found by looking at the sticker on the back of the appliance, issuing the ‘version’
command in the CLI or navigating to Monitor/Reporting > System Status in the GUI. This is required for
all physical appliances and virtual appliances with existing licenses.
13.2.1 POV License: WSA

62


Upon receiving this case, Partner Help will generate POV license keys. You will receive WSA license keys
that should be saved and unzipped on your local machine and can be loaded using the instructions
provided by partner help.
13.2.2 Lab License: WSA
63


Upon receiving this case, Partner Help will generate Lab License keys. You will receive WSA license keys
14 Email Security Appliance (ESA)
14.1 Software Download: ESA
This section covers the process to download software required for ESA. The instructions that follow
demonstrate how to provide required software for a virtual ESA C000V installation on VMware ESXi.
There are many possible software requirements and the information below serves as an example of a
common configuration for a partner executed POV. Adjust the process outlined below as required to
match your hardware specifications. For best performance, partners should run ESA 9.0 or later. Note
that this software download process only supports virtual appliances because software is automatically
downloaded to physical appliance.

> Email Security > Email Security Virtual Appliance
Scroll down to the following options and publish the versions listed below or later. If requested by the
partner in the case, you can provide a specific release or model.
64
• Cisco Email Security Virtual Appliance C000V (phoebe-9-0-0-500-C000V.zip)
14.1.1 Software Request: ESA

o Product type [ESA]
o Appliance type [VM Model]
o ESA Software [Version]

o Appliance Type [C000V]
o ESA Software [phoebe_9_0_500_C000V.zip
65
14.2 License Request: ESA
Partners will need the Serial Number from the ESA prior to initiating the License Request. The serial
14.2.1 POV License: ESA

o Product type is [ESA]
66
o Serial Number [SN]

Upon receiving this case, Partner Help will generate POV license keys. You will receive ESA license keys
14.2.2 Lab License: ESA

o Appliance type [Hardware Model or VM Model
o Serial Number [SN]
67

Upon receiving this case, Partner Help will generate Lab License keys. You will receive ESA license keys
68
15 Security Management Appliance (SMA)
15.1 Software Download: SMA
This section covers the process to download the software required for SMA. The instructions that follow
demonstrate how to provide required software for a virtual SMA M000V installation on VMware ESXi.
There are many possible software requirements and the information below serves as an example of a
common configuration for a partner executed POV. Adjust the process outlined below as required to
match your hardware specifications. For best performance, partners should run SMA 9.0 or later.

> Security Management > Content Security Management Virtual Appliance
Scroll down to the following options and publish the versions listed below or later. If requested by the
partner in the case, you can provide a specific release or model.
• Cisco Content Security Management Virtual Appliance M000V (zeus-9-0-0-087-M000V.zip)
69
15.1.1 Software Request: SMA

o Product type [SMA]
o Appliance type [Hardware Model or VM Model]
o SMA Software [Version]

o Appliance Type [M000V]
o SMA Software [zeus_9_0_0_087_M000V.zip]
15.2 License Request: SMA
Partners will need the Serial Number from the WSA prior to initiating the License Request. The serial
70
15.2.1 POV License: SMA


71
Upon receiving this case, Partner Help will generate POV license keys. You will receive SMA license keys
15.2.2 Lab License: SMA

o Appliance type [Hardware Model or VM Model

Upon receiving this case, Partner Help will generate Lab License keys. You will receive SMA license keys
72
16 Cloud Email Security (CES)
16.1 License Request: Cloud Email Security
Partner Help supports 45-day license requests for POVs with the ability to request one 45-day extension.
Activation instructions will go to the customer, so please ensure the Customer Technical contact
information is provided below.
16.2 POV License: Cloud Email Security

o Product type [CES]
o POV License for [Customer Name]
o Customer Contact Information
▪ Customer Contact Name: [First Name, Last Name]
▪ Customer Contact Email Address: [Email Address]
▪ Customer Contact Telephone Number: [Telephone Number]
o Cisco Contact Information
▪ Cisco Account Manager Name [First Name, Last Name]
▪ Cisco Account Manager Email Address: [Email Address]
▪ Cisco Systems Engineer Name [First Name, Last Name]
▪ Cisco Systems Engineer Email Address: [Email Address]
o Partner Contact Information
73
▪ Partner Systems Engineer Name [First Name, Last Name]

▪ Partner Systems Engineer Email Address: [Email Address]
o Customer Address Information [Actual Location]
▪ Street Address: [Address]
▪ City: [City]
▪ State/Province: [State/Province]
▪ Country: [Country]
▪ Postal Code: [Postal Code]
o Cloud Email Security EXACT Seat Count: [Quantity]
o POV Start Date: [MM/DD/YYYY]
o Cloud Email Security Data Center Region: [CHOOSE ONE FROM OPTIONS BELOW]
▪ United States
▪ Europe
▪ Canada
o Office 365 Support Required: [CHOOSE ONE FROM OPTIONS BELOW]
▪ No
▪ Yes
o Intelligent Multi-scan Support Required: [CHOOSE ONE FROM OPTIONS BELOW]
▪ No
▪ Yes
74

o Product type [CES]
o Customer Opportunity [$50k USD]
o Customer Contact Information
o Customer Contact Name: [Wiley Coyote]
o Customer Contact Email Address: [wcoyote@acme.com]
o Customer Contact Telephone Number: [(444) 555-2121]
o Cisco Contact Information
o Cisco Account Manager Name [Ralph Emerson]
o Cisco Account Manager Email Address: [remerson@cisco.com]
o Cisco Systems Engineer Name [Waldo Jenkins]
o Cisco Systems Engineer Email Address: [wjenkins@cisco.com]
o Partner Contact Information
o Partner Systems Engineer Name [James Doe]
o Partner Systems Engineer Email Address: [jdoe@partner.com]
o End Customer Address [Actual Location]
o Street Address: [10 Any Street]
o City: [Notown]
o State/Province: [NY]
o Country: [USA]
o Postal Code: [12345]
o Cloud Email Security bundle EXACT Seat Count: [500]
o POV Start Date: [01/02/2017]
o Cloud Email Security Data Center Selection (Region): [United States]
o Office 365 Support Required: [Yes]
o Intelligent Multi-scan Support Required: [No]
Upon receiving this case, Partner Help will request the CES POV License activation. Provisioning and
configuration of the CES service may take some time so please be patient. Once the license has been
created, the CES Activation Team will contact the key personnel to continue the provisioning and
configuration steps. A 45-day license extension may be requested if required, but this request must be
processed before the original 45-day license expires. To receive the extension, open a new partner help
case following the process above requesting an extension.
75
76
17 Advanced Malware Protection (AMP) for Endpoint
17.1 License Request: AMP
on internal tools, but the goal is to provide 60-day keys for POVs with one extension and 180-day keys
for labs with unlimited extensions. There is no software access or required product information for the
AMP license request.
Please note, there should only be (1) parent AMP for Endpoint Console Lab account created for each
Partner Organization and all SEs at the Partner Organization should request licenses as a user under that
parent account. Personal accounts for Partner SEs are not supported. Also, the parent Lab license will
automatically expire at the end of the 180-day window, so the notification email for the parent Lab
Account should be someone who will be able to request a renewal before the license expires.
17.1.1 POV License: AMP
• Technology = Advanced Threat

o Product type [AMP for Endpoint]
o Customer Point of Contact Email [Customer POC Email Address]
77

o Customer Point of Contact Email [wcoyote@acme.com]
Upon receiving this case, Partner Help will generate POV licenses. You will receive an email from partner
help with credentials and instructions on how to access your account. Partners can request a single 30-
day license extension if required, but this request must be processed before the original 60-day license
expires. To receive the extension, open a new partner help case following the process above requesting
an extension.
17.1.2 Lab License: AMP


78
Upon receiving this case, Partner Help will generate lab licenses. You will receive an email from partner
help with credentials and instructions on how to access your account.
18 Cisco Threat Grid
18.1 License Request: Cisco Threat Grid
on internal tools, but the goal is to provide a 45-day API license key for POVs with one extension and a 6-
month API license key for Partner Labs with unlimited extensions. There is no software access or
required product information for the Cisco Threat Grid license request.
18.1.1 POV License: Cisco Threat Grid

o Product type [Cisco Threat Grid]
o Partner SE Name [Partner SE Name]
o Partner SE Email Address [Partner SE Email Address]
o POV License for [Customer Company Name]
o Customer Point of Contact [Customer POC Name]
o Customer Point of Contact Email [Customer POC Email Address]
79
o Customer Point of Contact Role [Customer POC Role]


o Partner SE Name [Harry McDonald]
o Partner SE Email Address [hmcdonald@partner.com]
o Customer Point of Contact Email [wcoyote@acme.com]
o Customer Point of Contact Role [Security Administrator]
Upon receiving this case, Partner Help will forward the request to the Threat Grid Provisioning team.
Once the team has provisioned the subscription, the Customer Point of Contact will receive an email
from the Threat Grid Provisioning team with API license key to use for the subscription. One 45-day API
license key extension will be granted when required. To receive the extension, open a new partner help
case following the same process above noting this is an extension to an existing POV license key.
18.1.2 Lab License: Cisco Threat Grid

o Partner Company Name [Company Name]
80
o Partner SE Email Address [Partner SE Email Address]


o Partner Company Name [Partner Company, Inc.]
o Partner SE Name [John Doe]
o Partner SE Title [Security Presales Engineer]
o Partner SE Email Address [jdoe@partner.com]
If multiple Partner SE Lab licenses are required with the Partner Organization, please provide the
information for each Partner SE in the email. Upon receiving this case, Partner Help will forward the
request to the Threat Grid Provisioning team. Once the team has provisioned the subscription, the
Partner SE will receive an email from the Threat Grid Provisioning team with API license key to use for
the subscription. Unlimited 6-month API license key extensions will be granted when required. To
receive the extension, open a new partner help case following the same process above noting this is an
extension to an existing Partner Lab license key.
18.1.3 Meraki Integration: Cisco Threat Grid
Threat Grid integration with Meraki is now supported and the process to request Customer POV / Lab
licenses is the same, but the mechanism to enable the integration is listed below.
Integrating Meraki and Threat Grid:
• Step 1: Log into Meraki as an organization admin and go to Organization > Settings
• Step 2: Scroll down to Threat Grid and choose an Integration type (NOTE: This will be set to
Disabled by default)
• Step 3: Choosing Cloud brings up status indicating it has not yet been set up, so click the link to
initiate the integration (NOTE: On-Premise will require an API key and URL)
• Step 4: You will be redirected the user to the Threat Grid portal, so log in if necessary
• Step 5: Authorize Meraki to interact with your Threat Grid account
• Step 6: After authorized, the user will be redirected back to the Meraki dashboard where they
will see a successful integration status message
Per MX/Network configuration: Users can use this to control the integration at a more granular level
and change it over time as necessary
• Step 1: Go to Security Appliance > Threat Protection for a particular network
• Step 2: There is a new section that will allow you to enable/disable Threat Grid for specific
networks and also set a per-network rate limit
81
19 Stealthwatch
There are three different options available to our Partners to utilize Stealthwatch and each has a
separate process for requests. The sections below will provide insight as to the available options and
how to create a request through the Partner Help team.
19.1 Security Online Visibility Assessment (SOVA): Stealthwatch
The newly rebranded Security Online Visibility Assessment (SOVA), previously known as Stealthwatch
Online Visibility Assessment, enables sellers to quickly and easily gain insight into prospect networks,
including areas of security risk, to help position Stealthwatch and other Cisco security products. It works
by deploying a lightweight virtual appliance which processes flow data and forwards it to a cloud-based
analytics platform. SOVA can drastically simplify the POV process to a 14-day trial period which does not
require a full product deployment and the insight it provides can lead to the sale of multiple products
and services. Please note, the level of granularity with SOVA is not as detailed as an on-prem POV, but if
this additional level of detail is not necessary, this is an efficient way to proceed.
There is a multi-step process to gain access to the SOVA portal which includes viewing a training
recording, taking a Cisco Online Test (COLT), and then submitting the score from the COLT to a mailer for
processing.
To begin the process for requesting access to your own SOVA portal, please view the Stealthwatch
Online Visibility Assessment deep-dive Training and then pass the Security Online Visibility
Assessment COLT Exam found at http://cs.co/SOVAHub. After successfully passing the COLT exam,
forward the confirmation email to sova-help@cisco.com and they will process your request and grant
access to the SOVA portal.
Additional SOVA training is also provided via regularly scheduled webinars and the information for the
webinars can be found at http://cs.co/sova-webinar.
Partners may request SOVA Flow Sensor licenses by emailing sova-help@cisco.com.
19.2 On-premise POV: Stealthwatch
This method can utilize the full complement of Stealtwatch sensors, if necessary, to deploy at the
customer location and will provide a greater level of detail about the environment. There are two
separate processes for requesting On-premise POVs which are detailed below.
19.2.1 On-premise POV Request
To make an initial request for an On-premise Stealthwatch POV, please reach out to your Global Security
Sales Account Manager as these are managed via internal processes which must be followed. If you are
unsure who this person might be or if you have any issues with the process, you can send an email to
stealthwatch-partner@cisco.com with the POV Customer’s Name, City, and State to request assistance.
82
19.2.2 On-premise POV Extension
Partner Help supports extensions for On-premise POVs. License duration is dependent on internal tools,
but the goal is to provide a single 45-day license extension with business justification. To complete a
POV License Extension, open a case with Partner Help. You can go to the Partner support page and
• Case Title = Stealthwatch POV License Extension

o Cisco Cybersecurity Partner Account Manager [Cisco CyPAM]
o Product type [Stealthwatch]
o POV License for [Customer Name]
o Partner SE Email [Partner SE Email Address]
o Business Justification [Business Justification for POV Extension]
Example Question
o Cisco Cybersecurity Partner Account Manager or SE [John Smith]
o POV License for [ACME Inc.]
o Partner SE Name [Joseph Doe]
o Partner SE Email [joedoe@partner.com]
o Business Justification [We need another three weeks for new network segment]
Upon receiving this case, Partner Help will forward the request to the Stealthwatch Provisioning team.
83
19.3 Software Access and Lab License: Stealthwatch
Partners may request Lab software and licenses for Stealthwatch for internal use, demos, and training.
This software should not be used for any POV requests nor any other customer facing activities beyond
demo. Partner Help supports initial and renewal requests for Partner Labs.
19.3.1 Software Access and Lab License: Stealthwatch
To complete a Software Access and Lab License Request, open a case with Partner Help. You can go to
the Partner support page and under “Open a case to engage with GVE”, select open a case or chat with
a GVE agent. In the case, provide the following required information in the Case Description field.
Upon receiving the required information below, Partner Help will assist in providing instructions for
downloading Stealthwatch software.
• Case Title = Software Access and Lab License Request

o License Type [Lab]

o License Type [Lab]
Once the instructions have been provided, download and install the appropriate files for the
Stealthwatch deployment.
84
19.3.2 Lab License Renewal: Stealthwatch
Partner Help supports renewals for Partner Labs. License duration is dependent on internal tools, but at
this time, a 90-day license extension is provided. To complete a Partner Lab License Renewal, open a
case with Partner Help. You can go to the Partner support page and under “Open a case to engage with
GVE”, select open a case or chat with a GVE agent. In the case, provide the following required
information in the Case Description field.
Note: By making this request, the Partner representative acknowledges and confirms that the
licenses renewals are for internal use only, for non-production environment, and restricted from use
in customer environments. If you require licenses for a customer POV please follow steps indicated
above.
• Case Title = Stealthwatch Lab License Renewal

o Partner SE Email [Partner SE Email Address]
o Stealthwatch Management Console (SMC) Serial Number [SMC Serial Number]
o Flow Collector Serial Number [FC Serial Number]
o Flow Sensor Serial Number (If installed) [FS Serial Number]
o UDP Director Virtual Appliance Serial Number (If installed) [UDPD Serial Number]

o Partner SE Name [Joseph Doe]
o Partner SE Email [joedoe@partner.com]
o Stealthwatch Management Console (SMC) Serial Number [ABC123]
o Flow Collector Serial Number [CBA321]
o Flow Sensor Serial Number (If installed) [XYZ789]
o UDP Director Virtual Appliance Serial Number (If installed) [ZYX987]
Upon receiving this case, Partner Help will forward the request to the Stealthwatch Provisioning team.
85
20 Cisco Defense Orchestrator
20.1 License Request: Cisco Defense Orchestrator
The CDO team supports license requests for both POVs and Partner Labs and provides license extensions
with business justification. There is no software access or required product information for the Cisco
Defense Orchestrator license request.
20.1.1 POV License: Cisco Defense Orchestrator
To request a POV License, email the CDO team at cdosales@cisco.com. In the email, provide the
following information so the team may begin to process your request:
Upon receiving this email, the CDO team will respond asking for any additional information. Once the
provisioning team processes the request, an email with the registration token to the Cisco Defense
Orchestrator One Login Portal and instructions on how to access the Portal will be generated and sent
back to you. To receive the extension, send another email to the CDO team following the same process
above noting this is an extension to an existing POV license.
20.1.2 Lab License: Cisco Defense Orchestrator
If you are interested in individual access to demo and test CDO, please proceed with leveraging dCloud
which is fully pre-populated with devices for a full and completed CDO experience. To access the dCloud
CDO demo, you can go to dcloud.cisco.com and log in with your CCO credentials. Once logged in, select
86
Catalog and enter CDO into the Search criteria. Select View for the Cisco Defense Orchestrator v1 –
Instant Demo option to access the CDO Demo instance.
The CDO team can also assist with a Partner Lab license which provides a single cloud tenant account
that can be used for testing by all engineers within your organization. To request a Lab License, email
the CDO team at cdosales@cisco.com. In the email, provide the following information so the team may
begin to process your request:
Upon receiving this email, the CDO team will respond asking for any additional information. Once the
provisioning team processes the request, an email with the registration token to the Cisco Defense
Orchestrator One Login Portal and instructions on how to access the Portal will be generated and sent
back to you. To receive the extension, send another email to the CDO team following the same process
above noting this is an extension to an existing Lab license.
21 Next Steps
87
This completes the Cisco Security Licensing and Software Access guide for partners. For additional
support, post questions on the partner security community: www.cisco.com/go/securitychannels.
Below are some key resources to meet the program requirements and continue your education.
• Cisco Partner Security Community

https://community.cisco.com/t5/partner-security/ct-p/2035j-partner-security
• Voice of the Engineer
https://community.cisco.com/t5/security-documents/training-security-voice-of-the-
engineer/ta-p/3611728
• Fire Jumper Program
https://community.cisco.com/t5/security-documents/overview-fire-jumper-academy-for-
cybersecurity-systems-engineers/ta-p/3657706
• POV Best Practices
https://community.cisco.com/t5/security-documents/product-proof-of-value-pov/ta-p/3633986
22 Change Log
• 5/29/2015: Added support for POV license requests on Web Security Appliance (WSA), Email
Security Appliance (ESA), and Security Management Appliance (SMA) physical appliances
• 8/25/2015: Added support for lab license requests for ASAv, CSM, and ACS. Added support for
POV license requests for AMP for Endpoint and CWS.
• 6/25/2016: Added support for POV license requests for CES, Firepower Threat Defense, and
Stealthwatch and updated requirements for CWS. Clarified that SN is required for all ESA, WSA,
and SMA submissions.
• 8/11/2016: Added support for downloading and licensing FMC for FTD.
• 10/11/2016: Added support for Cisco Smart Licensing for FMC and FTD. Clarified that partners
may only have one joint AMP for Endpoints lab account.
• 12/19/2016: Updated Smart License support information for applicable products.
• 02/17/2017: Updated Stealthwatch POV license support and PH engagement information
• 04/20/17: Added support for Cisco Threat Grid and Cisco Defense Orchestrator Lab and POV
licensing.
• 10/06/17: Added Cisco Cybersecurity Partner Account Manager (CyPAM) field as well as
mandatory requirement for Cisco Deal ID for any POV License request
• 01/24/18: Added AnyConnect for FTD and Stealthwatch SOVA information
• 04/15/18: Added Umbrella Partner POV (PPOV) Portal information
88
• 06/XX/18: Removed Fire Jumper Advanced Threat Stage 4 requirement for Threat Grid Lab
license. Updated Stealthwatch Lab software/license procedures. Updated Umbrella MSSP POV
Portal request instructions.
• 11/14/18: 1. Add FMC/FTD license key for ASA/NGFW Firepower license request requirements-
under firepower already (ADDED IN 5.2.1) 2. Update for CSM lab/POV license issuance process-
from team space- Added to Section 10.2.1 3. Add process for ISE POV license request- Section
Added 11.2.1 4. Add information regarding CES POV license extension process-Added under
Section 16.2 7. AMP4E POV license duration should be changed to 2 months. (3 months from
the guide)- Has been changed to 2 months (Section 17)8. Removed CWS from guide 9. For
classic licenses (Firepower) added this field FMC License Key [FMC Key found in Section 3.3]-
Added in 5.2.1 10. Updated all links under section 21 10. Updated all case opening instructions
to match the new GVE portal & removed the phone support option-replaced with chat 11.
Update ISE POV case description
• 12/03/18- Changed the instructions in the CDO section so that partners can directly contact CDO
instead of having to open a case with partner help first.
• 03/19/2019- Changed the AMP Lab License Requirement, no CCW DEAL ID is required
89

Cisco Security Licensing and Software Access 190319 PDF

Uploaded by

Document Information

Original Description:

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Cisco Security Licensing and Software Access 190319 PDF

Uploaded by

Copyright:

Available Formats

Cisco Security Licensing and

Software Access Process

Global Security Sales Organization (GSSO)

3 Firepower Management Center (FMC) ............................................................................ 10

4 Firepower Threat Defense (FTD) ...................................................................................... 18

5 Firepower Services for ASA or Firepower ...................................................................... 25

6 Adaptive Security Appliance (ASA) ................................................................................... 31

7 Adaptive Security Virtual Appliance (ASAv).................................................................. 41

8 Umbrella Managed Security Services Partner (MSSP) Portal .................................. 46

9 Umbrella Partner POV (PPoV) Portal .............................................................................. 47

10 Cisco Security Manager (CSM) ............................................................................................ 49

11 Identity Services Engine (ISE) ............................................................................................. 53

12 Access Control System (ACS) ............................................................................................... 57

13 Web Security Appliance (WSA) .......................................................................................... 60

14 Email Security Appliance (ESA).......................................................................................... 64

14.2 License Request: ESA ...................................................................................................................... 66

15 Security Management Appliance (SMA) .......................................................................... 69

16 Cloud Email Security (CES) .................................................................................................. 73

17 Advanced Malware Protection (AMP) for Endpoint ................................................... 77

18 Cisco Threat Grid ..................................................................................................................... 79

20 Cisco Defense Orchestrator ................................................................................................. 86

2 Cisco Smart Licensing

2.1 Creating a Cisco Smart Account

2.2 Smart Licensing Account Activation Example

2.2.1 Smart License Account Activation: FTD

2.2.2 Smart License Registration Example

3 Firepower Management Center (FMC)

3.1 Software Download: FMC

To download the Firepower software, go to http://software.cisco.com/download/navigator.html. This

3.2 Software Request: FMC

• Case Title = Software Access

Click the “submit” button.

Example Case Description

3.3 License Request: FMC

3.3.1 POV Smart License: FMC

• Case Title = FMC POV Smart License

Example Case Description

3.3.2 Lab Smart License: FMC

• Case Title = FMC Lab Smart License

o FMC type [Hardware or Virtual Sensor Model & OS (VMWare or KVM)]

3.3.3 POV Classic License: FMC

• Case Title = FMC POV License

o POV License for [Customer name]

Example Case Description

3.3.4 Lab Classic License: FMC

• Case Title = FMC Lab License

Example Case Description

4 Firepower Threat Defense (FTD)

4.1 Software Download: FTD

• Firepower Threat Defense for ASA 55XX series v6.1.0

NOTE: The ASA5585-X platforms do not support FTD software.

4.1.1 Software Request: FTD

• Case Title = Software Access

Example Case Description

4.2 License Request: FTD

4.2.1 POV Smart License: AnyConnect for FTD

• Case Title = FTD POV Smart License

Example Case Description

4.2.2 Lab License: AnyConnect for FTD

• Case Title = AnyConnect for FTD Lab Instance

Example Case Description

4.2.3 POV Smart License: FTD