Supported object types
The object types that you can create and manage depend on the managed device type.
Common object types
|
Object Type |
Description |
|---|---|
|
Network groups and network objects (collectively referred to as network objects) define the addresses of hosts or networks. |
|
|
Use URL objects and groups (collectively referred to as URL objects) to define the URL or IP addresses of web requests. You can use these objects to implement manual URL filtering in access control policies or blocking in Security Intelligence policies. |
ASA object types
|
Object |
Description |
|---|---|
|
Defines host or network addresses. This category includes network objects and network groups. |
|
|
Defines protocols or ports that are part of the TCP/IP protocol suite. This category includes service objects, service groups, and port groups. |
|
|
Defines a start time, an end time, and optional recurring entries for time-based access to features or assets. |
|
|
Manages and tracks digital certificates in ASA. |
FDM-managed device object types
|
Object |
Description |
|---|---|
|
Represents files used in configurations, typically for remote access VPN policies. These objects can contain AnyConnect Client Profile and AnyConnect Client Image files. |
|
|
Provides digital identification for authentication. Certificates are used for SSL, TLS, and DTLS connections, such as HTTPS and LDAPS. |
|
|
Defines DNS servers that resolve fully qualified domain names (FQDNs), such as www.example.com, to IP addresses. You can configure different DNS group objects for management and data interfaces. |
|
|
Defines countries and continents that host the source or destination of traffic. You can use geolocation objects in policies instead of IP addresses. |
|
|
Contains the parameters required for IKEv1 policies when defining VPN connections. |
|
|
IKEv2 Policy |
Contains the parameters required for IKEv2 policies when defining VPN connections. |
|
IKEv1 IPSEC Proposal |
IPsec Proposal objects configure the IPsec proposal used during IKE Phase 1 negotiations. The IPsec proposal defines the combination of security protocols and algorithms that secure traffic in an IPsec tunnel. |
|
IKEv2 IPSEC Proposal |
IPsec Proposal objects configure the IPsec proposal used during IKE Phase 2 negotiations. The IPsec proposal defines the combination of security protocols and algorithms that secure traffic in an IPsec tunnel. |
|
Defines host or network addresses. This category includes network objects and network groups. |
|
|
Defines protocols or ports that are part of the TCP/IP protocol suite. This category includes service objects, service groups, and port groups. |
|
|
Identifies source or destination addresses based on a security group tag (SGT) assigned by Cisco ISE. |
|
|
Defines URLs or IP addresses for web requests. URL objects and URL groups can be used for manual URL filtering in access control policies or blocking in Security Intelligence policies. |
On-Premises Firewall Management Center object types
|
Object |
Description |
|---|---|
|
Defines host or network addresses. This category includes network objects and network groups. |
|
|
Defines protocols or ports that are part of the TCP/IP protocol suite. This category includes service objects, service groups, and port groups. |
Meraki object types
|
Object |
Description |
|---|---|
|
Defines host or network addresses. This category includes network objects and network groups. |
|
|
Defines protocols or ports that are part of the TCP/IP protocol suite. This category includes service objects, service groups, and port groups. |