Cisco Systems ASA 5585-X, ASA 5505, ASA 5545-X, ASA 5555-X, ASA 5580 manual 15-19

Page 321

Chapter 15 Using the Cisco Unified Communication Wizard

Configuring the UC-IME by using the Unified Communication Wizard

Step 1 To configure the Cisco Intercompany Media Engine Proxy as part of a basic deployment, select the interface that connects to the local Cisco Unified Communications servers.

Or

To configure the Cisco Intercompany Media Engine Proxy as part of an off-path deployment, complete the following steps:

a.From the Listening Interface drop-down list, choose the interface on which the ASA listens for the mapping requests.

b.In the Port field, enter a number between 1024 and 65535 as the TCP port on which the ASA listens for the mapping requests. The port number must be 1024 or higher to avoid conflicts with other services on the device, such as Telnet or SSH. By default, the port number is TCP 8060.

c.From the UC-IME Interface drop-down list, choose the interface that the ASA uses to connect to the remote ASA that is enabled with the Cisco Intercompany Media Engine Proxy.

Note In a basic and an off-path deployment, all Cisco Unified Communications servers must be on the same interface.

Step 2 In the Unified CM Servers area, the wizard displays the private IP address, public IP address, and security mode of any Cisco Unified Communications server configured on the ASA. If necessary, click Add to add a Cisco Unified Communications server. You must include an entry for each Cisco UCM in the cluster with Cisco Intercompany Media Engine that has a SIP trunk enabled.

Step 3 In the Ticket Epoch field, enter a integer from 1-255.

The epoch indicates the number of times that password has changed. When the proxy is configured the first time and a password entered for the first time, enter 1 for the epoch integer. Each time you change the password, increment the epoch to indicate the new password. You must increment the epoch value each time your change the password. Typically, you increment the epoch sequentially; however, the security appliance allows you to choose any value when you update the epoch.

If you change the epoch value, the current password is invalidated and you must enter a new password.

Step 4 In the Ticket Password field, enter a minimum of 10 and a maximum of 64 printable character from the US-ASCII character set. The allowed characters include 0x21 to 0x73 inclusive, and exclude the space character. The ticket password is stored onto flash.

Note We recommend a password of at least 20 characters. Only one password can be configured at a time.

The epoch and password that you configure on the ASA must match the epoch and password configured on the Cisco Intercompany Media Engine server. See the Cisco Intercompany Media Engine server documentation for information.

Step 5 In the Confirm Password field, reenter the password.

Step 6 In the X.509 Subject Name field, enter the distinguished name (DN) of the local enterprise. The name that you enter must match the name configured for the Cisco Unified Communications servers in the cluster. See the Cisco Unified Communications server documentation for information.

Step 7 Click Next.

Cisco ASA Series Firewall CLI Configuration Guide

15-19

Image 321
Contents Software Version Cisco ASA Series Firewall CLI Configuration GuideCisco ASA Series Firewall CLI Configuration Guide Iii N T E N T SGuidelines and Limitations Default Inspection Policy Maps NAT for VPN Guidelines and Limitations Vii RulesViii Getting Started with Application Layer Protocol InspectionIPv6 Inspection Verifying and Monitoring Sun RPC Inspection Configuring Unified Communications Xii Installing a CertificateXiii Enabling the Phone Proxy with SIP and Skinny InspectionXiv CTL Client OverviewArchitecture Xvi Configuring Connection Settings and QoSXvii Configuring the Standard Priority Queue for an InterfaceXviii Bypassing Scanning with WhitelistsXix Information About the Static DatabaseConfiguring Java Applet Filtering Xxi Filtering URLs and FTP Requests with an External Server30-15 XxiiXxiii ASA 5505 Configuring Basic Network SettingsXxiv Related Documentation Document ObjectivesConventions Convention IndicationXxvi Obtaining Documentation and Submitting a Service RequestR T Page Information About Service Policies Feature Directionality Supported FeaturesFeature Traffic? See For ThroughFeature Matching Within a Service Policy FeatureGlobal Direction ASA IPS ASA CX Order in Which Multiple Feature Actions are AppliedIncompatibility of Certain Feature Actions Licensing Requirements for Service Policies Feature Matching for Multiple Service PoliciesGuidelines and Limitations Service Policy Guidelines Class Map GuidelinesPolicy Map Guidelines Default Settings Default ConfigurationDefault Configuration, Default Class Maps, Default Class Maps Task Flows for Configuring Service PoliciesTask Flow for Using the Modular Policy Framework This section includes the following topicsSee the Identifying Traffic Layer 3/4 Class Maps section on Layer 3/4 Policy Map Identifying Traffic Layer 3/4 Class Maps Command PurposeCreating a Layer 3/4 Class Map for Through Traffic ExampleSee the Default Settings and NAT Limitations section on Ports are included in the match default-inspection-trafficMatch default-inspection-traffic command to narrow Except for the match any , match access-list , or match Match flow ip destination-address command to match flowsCreating a Layer 3/4 Class Map for Management Traffic Defining Actions Layer 3/4 Policy Map Creates a management class map, where classmapname is aSee the Supported Features section on Task Flow for Configuring Hierarchical Policy Maps forIdentifying Traffic Layer 3/4 Class Maps section on QoS Traffic Shaping section on page 1-11 for moreApplying Actions to an Interface Service Policy Displays the service policy statistics Configuration Examples for Modular Policy FrameworkMonitoring Modular Policy Framework IPv6, see the IPv6 Guidelines section onCiscoasaconfig# class-map httptraffic See the following commands for this exampleApplying Inspection and QoS Policing to Http Traffic Applying Inspection to Http Traffic GloballyCiscoasaconfig# service-policy httptrafficpolicy global Ciscoasaconfig# policy-map httptrafficpolicyApplying Inspection to Http Traffic with NAT Ciscoasaconfig# service-policy httpclient interface insideObj-192.168.1.1 HostFeature Name Releases Feature Information Feature History for Service PoliciesIntroduced class-map type management, and inspect Radius-accountingInformation About Inspection Policy Maps Guidelines and Limitations Default Inspection Policy Maps Identifying Traffic in an Inspection Class Map section on Defining Actions in an Inspection Policy MapIdentifying Traffic in an Inspection Class Map Getting Started with Application Layer Protocol Inspection Where to Go Next Feature History for Inspection Policy Maps1lists the release history for this feature Page Configuring Network Address Translation Page Information About NAT Why Use NAT?NAT Terminology NAT Types Overview NAT TypesStatic NAT Information About Static NATInformation About Static NAT with Port Address Translation Information About Static NAT with Port TranslationStatic NAT with Identity Port Translation Information About One-to-Many Static NAT4shows a typical few-to-many static NAT scenario Information About Other Mapping Scenarios Not RecommendedInformation About Dynamic NAT Dynamic NATDynamic PAT Dynamic NAT Disadvantages and AdvantagesInformation About Dynamic PAT Dynamic PAT Disadvantages and Advantages Per-Session PAT vs. Multi-Session PATNAT in Routed and Transparent Mode Identity NATNAT in Routed Mode, NAT in Transparent Mode, NAT in Transparent Mode NAT in Routed Mode10 NAT Example Transparent Mode NAT and IPv6 How NAT is ImplementedMain Differences Between Network Object NAT and Twice NAT Information About Twice NAT Information About Network Object NAT11 Twice NAT with Different Destination Addresses 12 Twice NAT with Different Destination Ports 13 Twice Static NAT with Destination Address Translation Rule Type Order of Rules within the Section NAT Rule OrderRouting NAT Packets NAT InterfacesMapped Addresses and Routing Too late Transparent Mode Routing Requirements for Remote NetworksNAT for VPN 203.0.113.16075 NAT and Remote Access VPNSame-security-traffic permit intra-interface NAT and Site-to-Site VPN19 Interface PAT and Identity NAT for Site-to-Site VPN See the following sample NAT configuration for ASA1 BoulderSubnet 10.2.2.0 NAT and VPN Management AccessObject network boulderinside Subnet 10.1.1.0 Object network vpnlocal Subnet 10.3.3.0Subnet 10.1.1.0 Nat inside,outside dynamic interface Management-access insideAdd the identity NAT configuration Troubleshooting NAT and VPNDNS and NAT Enter show nat detail and show conn all22 DNS Reply Modification, DNS Server on Outside 192.168.1.10 24 DNS Reply Modification, DNS Server on Host Network 2001DB8D1A5C8E1 26 PTR Modification, DNS Server on Host Network Page Information About Network Object NAT Configuring Network Object NATLicensing Requirements for Network Object NAT Prerequisites for Network Object NATSupports IPv6. See also the NAT and IPv6 section on Additional Guidelines Adding Network Objects for Mapped Addresses Configuring Network Object NATConfiguring Dynamic NAT ObjectObject network objname DNS and NAT section on page 3-28 for more information Additional Guidelines section onNat inside,outside dynamic nat-pat-grp interface Configuring Dynamic PAT HideOptional Create a network object or group for Configures a network object for which you want to configureSee the Adding Network Objects for Mapped Addresses section Mapped addressesInterface-Routed mode only The IP address Configures dynamic PAT for the object IP addresses. You canUsed. For this option, you must configure a specific When you want to use the interface IP address youCiscoasaconfig-network-object#nat inside,outside dynamic Configuring Static NAT or Static NAT-with-Port-Translation Ciscoasaconfig# object network IPv4POOLCiscoasaconfig# object network IPv6INSIDE Addresses IPv4 or IPv6 that you want to translate Static NAT section on See the DNS and NAT section on page 3-28. This option isSee the Mapped Addresses and Routing section on Configuring Identity NAT Translate. See the Adding Network Objects for MappedAddresses section on See the Additional Guidelines section on NAT command. See the Determining the Egress InterfaceMapped Addresses and Routing section on Section on page 3-22 for more informationBy default, the following rules are installed Configuring Per-Session PAT RulesMonitoring Network Object NAT Shows NAT statistics, including hits for each NAT ruleHow many times they were allocated Configuration Examples for Network Object NAT Configure static NAT for the object Providing Access to an Inside Web Server Static NATCiscoasaconfig# object network myWebServ Create a network object for the internal web serverCiscoasaconfig-network-object#nat outside,inside static Configure static NAT for the web serverCreate a network object for the inside network Create a network object for the outside web serverCiscoasaconfig# object network myPublicIPs Configure static NAT for the load balancerCiscoasaconfig# object network myLBHost Create a network object for the load balancerCiscoasaconfig# object network Httpserver Ciscoasaconfig# object network FtpserverCreate a network object for the FTP server address Create a network object for the Http server addressCreate a network object for the Smtp server address Ciscoasaconfig# object network SmtpserverDNS Reply Modification DNS Reply Modification Using Outside NAT 2001DB8D1A5C8E1 Ciscoasaconfig# object network Dnsserver Platform Feature Name Releases Feature Information Feature History for Network Object NATPat-pool mappedobject extended Pat-pool mappedobject flat include-reserveGeneral-attributes configuration mode Configuration mode, show nat, show nat pool, show xlateNat-assigned-to-public-ip interface tunnel-group Show nat pool Page Information About Twice NAT Configuring Twice NATLicensing Requirements for Twice NAT Prerequisites for Twice NATSupports IPv6 Configuring Twice NAT Guidelines and Limitations Adding Network Objects for Real and Mapped Addresses Configuring Twice NATConfiguring Twice NAT Configure service objects for Optional Adding Service Objects for Real and Mapped PortsCommand Purpose See the Optional Adding Service Objects for Real and Mapped See the Adding Network Objects for Real and MappedPorts section on Section and Line-Optional By default, the NAT rule is Configure dynamic NAT. See the following guidelinesAnywhere in the applicable section using the line argument You can optionally configure the following fallbackCommand Purpose For a PAT pool Subnet 203.0.113.0Subnet 2001DB8AAAA/96 Configuring Twice NAT Detailed Steps Mapped-Configure one of the following Configures dynamic PAT hide. See the following guidelinesInterface-Routed mode only Specify the interface Interface keyword enables interface PAT fallback. AfterCommand Purpose Command Purpose Service tcp destination eq Subnet 192.168.1.0Host 2001DB823 Source or Destination mapped ports Source or Destination real portsSee the Static Interface NAT with Port Translation Rule Order section on page 3-18for more information aboutExamples MAPPEDIPv6NW ObjectSubnet 2001DB8BBBB/96 OUTSIDEIPv6NWSource real addresses you will typically use Static Interface NAT with Port Translation section on Monitoring Twice NAT To monitor twice NAT, enter one of the following commandsShows NAT statistics, including hits for each NAT rule How many times they were allocatedCiscoasaconfig# object network PATaddress1 Configuration Examples for Twice NATAdd a network object for the inside network Add a network object for the DMZ networkConfigure the second twice NAT rule Configure the first twice NAT ruleAdd a service object for Telnet Add a network object for the PAT address when using TelnetCiscoasaconfig# object network myInsideNetwork Ciscoasaconfig# object network TelnetWebServerAdd a service object for Http We modified the following command nat source static Feature History for Twice NATShow nat, show xlate, show nat pool Existing functionality. The unidirectional keyword isPat-pool mappedobject flat include-reserve Nat-assigned-to-public-ip interface tunnel-group Show nat pool Configuring Access Control Page Information About Access Rules Configuring Access RulesGeneral Information About Rules Implicit PermitsInformation About EtherType Rules, Inbound and Outbound Rules Implicit DenyOutbound ACL Transactional-Commit ModelInformation About Extended Access Rules Access Rules for Returning TrafficAdditional Guidelines and Limitations Information About EtherType Rules Management Access RulesSupported EtherTypes and Other Traffic Traffic Type Protocol or PortPrerequisites Licensing Requirements for Access RulesAllowing Mpls Supported in routed and transparent firewall modesConfiguring Access Rules Default SettingsTo apply an access rule, perform the following steps Per-User ACL GuidelinesSee Per-User ACL Guidelines, Per-user-override optionTo monitor network access, enter the following command Monitoring Access RulesShow running-config access-group Hostname config# object-group service myaclogFeature History for Access Rules ExtendedPermit deny is-is Ipv6 access-list webtype, ipv6-vpn-filter Extended, access-list webtypeAccess-list extended, service-object, service Transactional-commit,show running-config aspLicensing Requirements for AAA Rules AAA PerformanceInformation About Authentication Configuring Authentication for Network AccessASA Authentication Prompts One-Time AuthenticationAAA Prompts and Identity Firewall Name name1@name2 Password password1@password2Static PAT and Http AAA Rules as a Backup Authentication MethodNat inside,outside static 10.48.66.155 service tcp 111 Configuring Network Access Authentication Authentication include command whichUser-group any and user-group none can be Lockout command Ldap-over-ssl enable Ldap-login-passwordAaa authentication match Auth inside Ldap Protocol ldapEnabling Secure Authentication of Web Clients Authenticating Https Connections with a Virtual Server Authenticating Directly with the ASAAuthenticating Telnet Connections with a Virtual Server Authentication include command Configuring TACACS+ Authorization Configuring Authorization for Network AccessAuthentication, while deny entries exclude matching Authenticate. For details, see the general operationsTraffic from authentication. Be sure to include FTP in the ACL, because the user must authenticateAuthorization include command which Authentication match commandAbout the Downloadable ACL Feature and Cisco Secure ACS Configuring Radius AuthorizationACSCiscoSecure-Defined-ACL=acl-set-name Access-list aclname extended Configuring Cisco Secure ACS for Downloadable ACLsDownloaded ACL on the ASA consists of the following lines With the following textIpinacl#nnn= Filter-id=aclname Configuring Accounting for Network AccessAuthentication section on page 7-7. If you want Information, see the Configuring Network AccessAccess-list command Accounting include command whichConfiguring AAA Rules for Network Access Mac-exempt match command Feature History for AAA Rules Page Configuring Application Inspection Page How Inspection Engines Work Getting Started with Application Layer Protocol InspectionHow Inspection Engines Work When to Use Application Protocol InspectionSupports IPv6 for the following inspections Failover Guidelines323 H.225 Default Settings and NAT LimitationsNetBIOS Name IP OptionsServer over IP Smtp SQL*NetSun RPC over Configuring Application Layer Protocol Inspection View the entire class map using the following command Ciscoasaconfig# policy-mapname ciscoasaconfig-pmap# Keywords Netbios mapname Icmp Icmp error IlsIp-options mapname Ipsec-pass-thru mapnameScansafe mapname Sqlnet SunrpcTftp Waas Xdmcp 10-1 DNS InspectionInformation About DNS Inspection Default Settings for DNS InspectionGeneral Information About DNS DNS Inspection ActionsDo one of the following 10-3Class-map type inspect dns match-all 10-4 Defining Actions in an Inspection Policy Map section onSection the authority keyword specifies the Authority RR Keyword specifies the question portion of a DNS message.Section the additional keyword specifies the Additional RR SectionMatches a DNS message domain name list. The regexname 10-6Match not domain-name regex regexid Message-length maximum length client length auto Id-mismatch count number duration seconds actionTsig enforced action drop log-Requires a Tsig 10-7Configuring DNS Inspection Layer 3/4 Class Maps section on page 1-12 for more10-8 Monitoring DNS Inspection Dynamic-filter-snoop keyword, see the Enabling DNS10-9 FTP Inspection Ciscoasa# show service-policyFTP Inspection Overview 10-1010-11 Using the strict Option10-12 10-13 10-14 Ciscoasaconfig# policy-map type inspect ftp mymapHttp Inspection Ciscoasaconfig# service-policy ftp-policy interface insideVerifying and Monitoring FTP Inspection Http Inspection Overview10-16 10-17 Ciscoasaconfig-cmap#match not req-resp content-type mismatch10-18 Ciscoasaconfig# policy-map type inspect http policymapname10-19 Icmp Inspection Icmp Error InspectionInstant Messaging Inspection IM Inspection OverviewCiscoasaconfig-cmap#match not protocol im-yahoo im-msn 10-21Conference games 10-22 Ciscoasaconfig# policy-map type inspect im policymapname10-23 IP Options Inspection10-24 IP Options Inspection OverviewCiscoasaconfig-pmap-p#router-alert action allow clear IPsec Pass Through Inspection10-25 IPsec Pass Through Inspection Overview IPv6 InspectionExample for Defining an IPsec Pass Through Parameter Map 10-26Optional Configuring an IPv6 Inspection Policy Map Default Settings for IPv6 InspectionInformation about IPv6 Inspection 10-2710-28 Routing-address count gt number -Sets the maximumConfiguring IPv6 Inspection To enable IPv6 inspection, perform the following steps10-29 NetBIOS Inspection NetBIOS Inspection Overview10-30 10-31 Smtp and Extended Smtp Inspection Pptp InspectionSmtp and Esmtp Inspection Overview 10-3210-33 10-34 Ciscoasaconfig# policy-map type inspect esmtp policymapname10-35 Tftp Inspection10-36 Ctiqbe Inspection Ctiqbe Inspection Overview11-1 Limitations and Restrictions Verifying and Monitoring Ctiqbe Inspection11-2 11-3 InspectionInspection Overview How H.323 Works11-4 11-5 Support in H.245 Messages11-6 Ciscoasaconfig-cmap#match not media-type audio data video Ciscoasaconfig# policy-map type inspect h323 policymapname11-7 Ciscoasaconfig-pmap-p#rtp-conformance enforce-payloadtype Ciscoasaconfig# ras-rcf-pinholes enableCiscoasaconfig-pmap-p#state-checking h225 ras 11-8Verifying and Monitoring H.323 Inspection Configuring H.323 and H.225 Timeout ValuesMonitoring H.225 Sessions 11-9Monitoring H.323 RAS Sessions Monitoring H.245 Sessions11-10 Ciscoasa# show h323-rasMgcp Inspection Mgcp Inspection Overview11-11 11-12 Ciscoasaconfig# policy-map type inspect mgcp mapnameConfiguring Mgcp Timeout Values Following example shows how to define an Mgcp map11-13 Rtsp Inspection Verifying and Monitoring Mgcp Inspection11-14 Rtsp Inspection Overview Using RealPlayerRestrictions and Limitations 11-1511-16 Ciscoasaconfig-cmap#match not request-method method11-17 Ciscoasaconfig# policy-map type inspect rtsp policymapnameSIP Inspection SIP Inspection Overview11-18 11-19 SIP Instant Messaging11-20 11-21 Ciscoasaconfig-cmap#match not content length gt lengthCiscoasaconfig-cmap#match not uri sip tel length gt length Ciscoasaconfig# policy-map type inspect sip policymapname11-22 Ciscoasaconfig-pmap-p#software-version action mask log log Ciscoasaconfig-pmap-p#uri-non-sip action mask log log11-23 Skinny Sccp Inspection Configuring SIP Timeout ValuesVerifying and Monitoring SIP Inspection 11-24Sccp Inspection Overview Supporting Cisco IP Phones11-25 11-26 Ciscoasaconfig# policy-map type inspect skinny policymapname11-27 Ciscoasaconfig-pmap-p#sccp-prefix-len max min valuelength11-28 Verifying and Monitoring Sccp InspectionILS Inspection ILS Inspection, SQL*Net Inspection, Sun RPC Inspection,12-1 12-2 SQL*Net InspectionSun RPC Inspection Sun RPC Inspection Overview12-3 Managing Sun RPC Services Verifying and Monitoring Sun RPC Inspection12-4 Ciscoasa# show sunrpc-server active 12-512-6 Dcerpc Inspection Dcerpc Overview13-1 13-2 Ciscoasaconfig# policy-map type inspect dcerpc policymapnameGTP Inspection GTP Inspection Overview13-3 13-4 Ciscoasaconfig# policy-map type inspect gtp policymapnameCiscoasaconfig# object-group network GSN-pool-name Ciscoasaconfig-network#network-object host13-5 Ciscoasaconfig# object-group network SGSN-name Ciscoasaconfig# object-group network sgsn3213-6 Ciscoasa# show service-policy inspect gtp statistics Ciscoasaconfig# service-policy globalpolicy globalVerifying and Monitoring GTP Inspection 13-7Ciscoasa# show service-policy gtp statistics grep gsn Radius Accounting Inspection13-8 Radius Accounting Inspection Overview Configure the service policy13-9 Inspect radius-accounting radiusaccountingmapSnmp Inspection RSH InspectionSnmp Inspection Overview 13-1013-11 Xdmcp Inspection13-12 Configuring Unified Communications Page 14-1 14-2 Certificate for Might not needPhone proxy ApplicationASA Base License and Security Plus License 2 sessions Model License Requirement1ASA Base License 2 sessions 14-4ASA 5585-X with Base License 2 sessions SSP-10 ASA 5585-X with Base License 2 sessions SSP-20, -40, or14-5 14-6 IMECisco Presence Federation Proxy Cisco Mobility Advantage ProxyCisco Intercompany Media Engine Proxy 15-115-2 15-3 Licensing Requirements for the Unified Communication Wizard15-4 Supports IPv6 addresses15-5 Configuring the Private Network for the Phone ProxyConfiguring Servers for the Phone Proxy Click the Generate and Export LDC Certificate button15-6 15-7 Address Default Port Description15-8 15-9 Configuring the Public IP Phone Network15-10 15-11 15-12 15-13 15-14 Dialog box. See Installing a Certificate, Certificate,15-15 15-16 15-17 Basic Deployment Off-path Deployment15-18 15-19 15-20 Cisco UCMs need to be installed on the security appliance Wizard supports using self-signed certificates onlySupports installing self-signed certificates Other, respectively, during TLS handshakes15-22 Installing a Certificate Exporting an Identity Certificate15-23 15-24 Click Install Certificate15-25 Saving the Identity Certificate Request15-26 15-27 15-28 Information About the Cisco Phone Proxy Phone Proxy Functionality16-1 TCP/RTP TLS/SRTP 16-2Cisco Unified Communications Manager Supported Cisco UCM and IP Phones for the Phone ProxyCisco Unified IP Phones 16-316-4 Licensing Requirements for the Phone Proxy16-5 Media Termination Instance Prerequisites Prerequisites for the Phone ProxyThis section contains the following topics 16-6DNS Lookup Prerequisites Certificates from the Cisco UCMCisco Unified Communications Manager Prerequisites ACL RulesAddress Port Protocol Description NAT and PAT PrerequisitesNAT Prerequisites PAT Prerequisites7940 IP Phones Support Prerequisites for IP Phones on Multiple InterfacesThere must be two CTL file record entries for the Cisco UCM 16-9Cipc security-mode authenticated Cisco IP Communicator Prerequisites16-10 Prerequisites for Rate Limiting Tftp Requests Rate Limiting Configuration ExampleIcmp deny any outside 16-11End-User Phone Provisioning Phone Proxy Guidelines and LimitationsWays to Deploy IP Phones to End Users 16-1216-13 General Guidelines and LimitationsConfiguring the Phone Proxy Media Termination Address Guidelines and Limitations16-14 Importing Certificates from the Cisco UCM Choose Security Certificate Management16-15 Hostnameconfig# crypto ca trustpoint trustpointname Authenticating IP phones with an LSCHostnameconfig# crypto ca authenticate trustpoint Certificate Name Required for16-17 Creating Trustpoints and Generating CertificatesPrerequisites Creating the CTL FileWhat to Do Next 16-1816-19 16-20 Using an Existing CTL File16-21 Creating the TLS Proxy for a Mixed-mode Cisco UCM Cluster16-22 Cucm/cucos/504/iptpch6.html#wp1040848 Creating the Media Termination InstanceCucm/cucos/504/iptpch6.html#wp1040354 16-23Creating the Phone Proxy Instance See Media Termination Instance Prerequisites16-24 16-25 See Creating the Media Termination InstanceEnabling the Phone Proxy with SIP and Skinny Inspection See Cisco IP Communicator Prerequisites16-26 16-27 Configuring Your Router Troubleshooting the Phone ProxyDebugging Information from the Security Appliance 16-2816-29 Use the Command16-30 Debugging Information from IP Phones Show asp dropShow asp table classify domain Show conn all16-32 Debugging Information from IP PhonesProblem The IP phone displays the following Status message Tftp Auth Error Displays on IP Phone ConsoleIP Phone Registration Failure 16-33Configuration File Parsing Error Unable to Get DNS Response Configuration File Parsing ErrorCiscoasa# show running-config all ctl-file ctlname 16-34Phone-proxy tftp Non-configuration File Parsing Error16-35 Hostname# debug phone-proxy tftpHostname# capture out interface outside 16-36Hostnameconfig# show running-config all phone-proxy IP Phone Requesting Unsigned File ErrorIP Phone Unable to Download CTL File 16-3716-38 IP Phone Registration Failure from Signaling ConnectionsDebug sip Debug skinny To add the required ciphers, enter the following command16-39 Hostname# show run all ssl16-40 SSL Handshake FailureMedia Termination Address Errors Certificate Validation Errors16-41 Audio Problems with IP Phones Saving Sast Keys16-42 16-43 16-44 Configuration Examples for the Phone ProxyRecord-entry cucm trustpoint trustpoint address address Record-entry capf trustpoint trustpoint address addressCorporate Network 16-45Fqdn my-ldc-ca.exmaple.com 16-46Phone a 10.10.0.24 16-4716-48 ASA Outside Interface Phone a 10.10.0.24 16-4916-50 16-51 Enroll terminal crypto ca authenticate capf ctl-file myctl16-52 Example 6 Vlan TransversalASA Inside Interface 10.130.50.24 16-5316-54 Feature History for the Phone Proxy17-1 17-2 Supported Cisco UCM and IP Phones for the TLS Proxy17-3 CTL Client Overview17-4 CTL Client TLS Proxy Features ASA IP Address or Domain Name17-5 Licensing for the TLS Proxy17-6 17-7 Configuring the TLS Proxy for Encrypted Voice InspectionCiscoasaconfig# tls-proxy maximum-sessions Ciscoasaconfig# show crypto ca server certificate17-8 17-9 17-10 Creating an Internal CA17-11 Creating a CTL Provider Instance17-12 Creating the TLS Proxy Instance17-13 Crypto ca trustpoint command17-14 17-15 Monitoring the TLS ProxyAES128-SHA 17-162lists the release history for this feature TLS Proxy TLS proxy feature was introduced17-17 17-18 18-1 Cisco Mobility Advantage Proxy FunctionalityHostnameconfig-tlsp#no server authenticate-client Mobility Advantage Proxy Deployment Scenarios18-2 TLS 18-3Mobility Advantage Proxy Using NAT/PAT Versus18-4 18-5 Trust Relationships for Cisco UMA DeploymentsConfiguring Cisco Mobility Advantage Longer requires a Unified Communications Proxy license18-6 Installing the Cisco UMA Server Certificate Task Flow for Configuring Cisco Mobility AdvantageEnabling the TLS Proxy for MMP Inspection, 18-718-8 18-9 Enabling the TLS Proxy for MMP InspectionEnables the service policy on all interfaces Exits from the Policy Map configuration modeMonitoring for Cisco Mobility Advantage 18-1018-11 Configuration Examples for Cisco Mobility Advantage18-12 18-13 18-14 Feature History for Cisco Mobility Advantage19-1 Information About Cisco Unified Presence19-2 Ciscoasaconfig# object network obj-10.0.0.2-0119-3 19-4 Trust Relationship in the Presence Federation19-5 Xmpp Federation DeploymentsConfigure the following NAT commands Configuration Requirements for Xmpp FederationAllow traffic from any address to any single node on port 19-619-7 Licensing for Cisco Unified Presence19-8 Configuring Cisco Unified Presence Proxy for SIP Federation19-9 Install the certificates. See Installing Certificates,Installing Certificates Trustpoint for the remote entity19-10 19-11 19-12 Trust-pointcommand is the remote entity proxy Enabling the TLS Proxy for SIP Inspection19-13 Example Configuration for SIP Federation Deployments, Configuration Example for Cisco Unified PresenceMonitoring Cisco Unified Presence 19-1419-15 Example Configuration for SIP Federation Deployments19-16 19-17 Example ACL Configuration for Xmpp Federation19-18 Example NAT Configuration for Xmpp Federation19-19 19-20 Feature History for Cisco Unified Presence20-1 Features of Cisco Intercompany Media Engine Proxy20-2 How the UC-IME Works with the Pstn and the Internet20-3 Tickets and Passwords20-4 Call Fallback to the PstnArchitecture Architecture, Basic Deployment, Off Path Deployment,20-5 20-6 Basic DeploymentLicensing for Cisco Intercompany Media Engine Off Path Deployment20-7 Supported in routed firewall mode only Supported in single context mode onlyDoes not support IPv6 addresses 20-820-9 Configuring Cisco Intercompany Media Engine Proxy Task Flow for Configuring Cisco Intercompany Media Engine20-10 Configuring NAT for Cisco Intercompany Media Engine Proxy Create the TLS proxy. See Creating the TLS Proxy,20-11 20-12 Cisco UCM that you want to translate20-13 Configuring PAT for the Cisco UCM Server20-14 20-15 Creating ACLs for Cisco Intercompany Media Engine ProxyProcedure Guidelines20-16 Creating the Cisco Intercompany Media Engine Proxy See Creating the Cisco Intercompany Media Engine20-17 20-18 20-19 Show running-config uc-ime command20-20 20-21 Prerequisites for Installing Certificates20-22 Creating Trustpoints and Generating Creating the TLS ProxyCertificates section on 20-2320-24 Created in , page 20-15of the task Creating ACLs for Cisco Intercompany Media Engine Proxy20-25 Where policymapname is the name of the policy Optional Configuring TLS within the Local EnterpriseMap you created in of this task 20-2620-27 Commands PurposeWhere proxytrustpoint for the server trust-point Where proxytrustpoint for the client trust-point20-28 20-29 Optional Configuring Off Path SignalingCreating the Cisco Intercompany Media Intercompany Media Engine Proxy,Engine Proxy, 20-3020-31 20-32 20-33 Show uc-ime signaling-sessionsShow uc-ime signaling-sessions statistics Show uc-ime media-sessions detail20-34 Show uc-ime mapping-service-sessions statistics Show uc-ime mapping-service-sessionsShow uc-ime fallback-notification statistics 20-3520-36 Configuring Connection Settings and QoS Page 22-1 Information About Connection SettingsTCP Intercept and Limiting Embryonic Connections Dead Connection Detection DCD22-2 TCP Normalization TCP Sequence RandomizationTCP State Bypass 22-322-4 Licensing Requirements for Connection SettingsMaximum Concurrent and Embryonic Connection Guidelines TCP State Bypass Unsupported FeaturesTCP State Bypass TCP NormalizerTask Flow For Configuring Connection Settings Configuring Connection SettingsFor each TCP map, you can customize one or more settings Customizing the TCP Normalizer with a TCP Map22-7 22-8 Command22-9 Command22-10 Urgent-flag allow clear Configuring Connection SettingsWindow-variation allow drop 22-1122-12 TCP Sequence Randomization section on page 22-3 section for Random-sequence-number enable disable keywordEmbryonic-conn-max keywords 22-13Embryonic hh mm ss keyword sets the timeout period until a Command in the command referenceIdle hh mm ss keyword sets the idle timeout period after To 0, which means the connection never times outConfiguration Examples for Connection Settings Monitoring Connection SettingsConfiguration Examples for Connection Limits and Timeouts 22-15Configuration Examples for TCP Normalization Configuration Examples for TCP State BypassFollowing is a sample configuration for TCP state bypass 22-1622-17 Feature History for Connection SettingsConn-max,set connection embryonic-conn-max,set Timeout half-closed,timeout half-closedConnection per-client-embryonic-max,set connection Per-client-max23-1 Information About QoSSupported QoS Features What is a Token Bucket?23-2 Information About Policing Information About Priority Queuing23-3 How QoS Features Interact Information About Traffic Shaping23-4 Dscp and DiffServ Preservation Licensing Requirements for QoSDoes not support IPv6 Model Guidelines23-6 Configuring QoS125 MbpsKbps 23-7Priority queue, or for the ASA 5505 or ASASM, the Vlan Configuring the Standard Priority Queue for an InterfaceInterface name 23-823-9 23-10 23-11 Step23-12 23-13 23-14 Configuring the Service RuleMultiple of 8000. See the Information About Traffic Shaping Priority Queuing Policy section on23-15 Monitoring QoS Ciscoasa# show service-policy policeViewing QoS Police Statistics 23-16Viewing QoS Standard Priority Statistics Viewing QoS Shaping Statistics23-17 Viewing QoS Standard Priority Queue Statistics 23-18Ciscoasa# show priority-queue statistics test 23-19 Feature History for QoS23-20 Troubleshooting Connections and Resources Testing Your Configuration24-1 24-2 Enabling Icmp Debugging Messages and Syslog Messages24-3 Pinging ASA Interfaces24-4 ASA24-5 Passing Traffic Through the ASA24-6 Disabling the Test ConfigurationDetermining Packet Routing with Traceroute Monitoring Per-Process CPU UsageTracing Packets with Packet Tracer 24-724-8 Configuring Advanced Network Protection Page 25-1 Configuring the ASA for Cisco Cloud Web SecurityInformation About Cisco Cloud Web Security User Authentication and Cloud Web SecurityRedirection of Web Traffic to Cloud Web Security 25-2Company Authentication Key Group Authentication Key Authentication KeysCompany Authentication Key, Group Authentication Key, 25-3Directory Groups ScanCenter PolicyCustom Groups 25-4How Groups and the Authentication Key Interoperate Cloud Web Security Actions25-5 Licensing Requirements for Cisco Cloud Web Security Failover from Primary to Backup Proxy ServerBypassing Scanning with Whitelists IPv4 and IPv6 SupportPrerequisites for Cloud Web Security Optional User Authentication PrerequisitesOptional Fully Qualified Domain Name Prerequisites 25-7Configuring Cisco Cloud Web Security By default, Cisco Cloud Web Security is not enabled25-8 25-9 See the Authentication Keys section on25-10 Config-url disk0/onectx.cfg Context two25-11 Optional Configuring Whitelisted Traffic section on25-12 Adding an Extended Access Control List,25-13 Policy section on page 1-17for more information25-14 25-15 Optional Configuring Whitelisted TrafficConfiguring the Cloud Web Security Policy Optional Configuring the User Identity MonitorObject-group-user-Specifies an object-group user name 25-16Monitoring Cloud Web Security Http//Whoami.scansafe.net25-17 Configuration Examples for Cisco Cloud Web Security Single Mode Example25-18 Whitelist Example Multiple Mode ExampleTo attach class-maps to the Cloud Web Security Policy map 25-19Configuring the Active Directory Server Using Ldap Directory Integration Examples25-20 Testing the AD Agent Configuring the Active Directory Agent Using RadiusConfiguring the Identity Options on the ASA Creating the ASA as a Client on the AD Agent ServerMonitoring the Active Directory Groups Cloud Web Security with Identity Firewall ExampleDownloading the Database from the AD Agent Showing a List of Active Users25-23 Aaa-server AD inside host 192.168.116.220 server-port 25-24No call-home reporting anonymous call-home 25-25Related Documents Feature History for Cisco Cloud Web SecurityRelated Documents 25-26Information About the Botnet Traffic Filter Botnet Traffic Filter Address Types,26-1 Botnet Traffic Filter Actions for Known Addresses Botnet Traffic Filter Address TypesBotnet Traffic Filter Databases Information About the Dynamic Database26-3 Information About the Static Database26-4 26-5 How the Botnet Traffic Filter WorksLicensing Requirements for the Botnet Traffic Filter Prerequisites for the Botnet Traffic Filter26-6 Configuring the Botnet Traffic Filter Task Flow for Configuring the Botnet Traffic Filter26-7 26-8 Configuring the Dynamic DatabaseAdding Entries to the Static Database See the Adding Entries to the Static Database section on26-9 See the Enabling DNS Snooping section on Enabling DNS SnoopingTCP DNS traffic is not supported 26-1026-11 26-12 Inspection section on page 10-1 for more information about26-13 Recommended ConfigurationSee the Blocking Botnet Traffic Manually section on Subset of the dynamic-filter enable ACLThreat-level range moderate very-high Very-low Low Moderate High Very-highBlocking Botnet Traffic Manually For dropping purposes. If you do not enable this commandAbout the greylist 26-1526-16 Searching the Dynamic DatabaseMonitoring the Botnet Traffic Filter Botnet Traffic Filter CommandsBotnet Traffic Filter Syslog Messaging 26-17Infected-hosts command Dns-snoop command26-18 Recommended Configuration Example Configuration Examples for the Botnet Traffic Filter26-19 Ciscoasa# show dynamic-filter reports top malware-portsOther Configuration Examples 26-20Outside 26-21 26-22 Feature History for the Botnet Traffic FilterInformation About Threat Detection Configuring Threat DetectionLicensing Requirements for Threat Detection 27-1Configuring Basic Threat Detection Statistics Information About Basic Threat Detection Statistics27-2 Guidelines and Limitations Trigger Settings Packet Drop Reason Average Rate Burst RateSecurity Context Guidelines Types of Traffic Monitored27-4 Configuring Basic Threat Detection StatisticsMonitoring Basic Threat Detection Statistics Threat Detection Statistics section on27-5 Feature History for Basic Threat Detection Statistics Configuring Advanced Threat Detection StatisticsInformation About Advanced Threat Detection Statistics 27-627-7 Configuring Advanced Threat Detection Statistics27-8 27-9 Monitoring Advanced Threat Detection Statistics27-10 27-11 Using the show threat-detection rate acl-drop commandStatistics Protocolnumber argument is an integer between 0Field 27-1227-13 Field Description27-14 Feature History for Advanced Threat Detection StatisticsConfiguring Scanning Threat Detection Information About Scanning Threat Detection27-15 27-16 Average Rate Burst RateConfiguration see the Configuring Basic Threat Detection Configuring Scanning Threat DetectionMonitoring Shunned Hosts, Attackers, and Targets Displays the hosts that are currently shunned27-18 Feature History for Scanning Threat Detection27-19 Configuration Examples for Threat Detection27-20 28-1 Preventing IP SpoofingConfiguring the Fragment Size Blocking Unwanted Connections28-2 Configuring IP Audit Configuring IP Audit for Basic IPS SupportConfiguring IP Audit, IP Audit Signature List, 28-31lists supported signatures and system message numbers IP Audit Signature ListSignature Message Number Signature Title 28-428-5 28-6 28-7 28-8 29-1 Information About Web Traffic FilteringLicensing Requirements for ActiveX Filtering Configuring ActiveX FilteringInformation About ActiveX Filtering 29-2Configuration Examples for ActiveX Filtering Configuring ActiveX FilteringGuidelines and Limitations for ActiveX Filtering 29-3Feature History for ActiveX Filtering Configuring Java Applet FilteringInformation About Java Applet Filtering Licensing Requirements for Java Applet FilteringConfiguration Examples for Java Applet Filtering Configuring Java Applet FilteringGuidelines and Limitations for Java Applet Filtering 29-5Filtering URLs and FTP Requests with an External Server Feature History for Java Applet FilteringInformation About URL Filtering 29-6Licensing Requirements for URL Filtering Guidelines and Limitations for URL Filtering29-7 Identifying the Filtering Server Choose from the following options29-8 29-9 Buffering the Content Server Response Configuring Additional URL Filtering SettingsReplaces block-buffer with the maximum number of Http Maximum memory allocation of 2 KB to 10 MBFiltering Http URLs Caching Server AddressesOn the Websense server Websense server29-12 29-13 Filtering Https URLsFiltering FTP Requests Might enter cd ./files instead of cd /public/files29-14 Monitoring Filtering Statistics Following is sample output from the show url-servercommand29-15 Ciscoasa# show url-serverFollowing is sample output from the show perfmon command Following is sample output from the show url-blockcommandFollowing is sample output from the show filter command 29-1629-17 Feature History for URL Filtering29-18 Configuring Modules Page 30-1 Information About the ASA CX Module30-2 How the ASA CX Module Works with the ASAService Policy in Monitor-Only Mode Monitor-Only ModeTraffic-Forwarding Interface in Monitor-Only Mode 30-3Initial Configuration, Policy Configuration and Management, Initial ConfigurationInformation About ASA CX Management 30-4Compatibility with ASA Features Information About Authentication ProxyPolicy Configuration and Management Information About VPN and the ASA CX Module30-6 Licensing Requirements for the ASA CX ModuleASA Clustering Guidelines Monitor-Only Mode GuidelinesDoes not support clustering 30-7See the Compatibility with ASA Features section on Configuring the ASA CX ModuleParameters Default Task Flow for the ASA CX ModuleConnecting the ASA CX Management Interface ASA 5585-X Hardware Module30-9 If you have an inside router If you do not have an inside router30-10 30-11 ASA 5512-X through ASA 5555-X Software Module30-12 Example Partition the SSD30-13 ASA 5585-X Changing the ASA CX Management IP Address Session 1 do setup host ipSets the ASA CX management IP address, mask, and gateway 30-1430-15 Configuring Basic ASA CX Settings at the ASA CX CLICiscoasa# session cxsc console Enter an IPv6 address 2001DB80CD301234/64Change the admin password by entering the following command Asacx config passwd30-16 30-17 Optional Configuring the Authentication Proxy PortCreating the ASA CX Service Policy Redirecting Traffic to the ASA CX Module30-18 30-19 See the Monitor-Only Mode section on page 30-3 for moreConfiguring Traffic-Forwarding Interfaces Monitor-Only Mode See the Feature Matching Within a Service Policy section on30-20 30-21 Managing the ASA CX ModuleReloading or Resetting the Module Resetting the PasswordFor a software module ASA 5512-X through ASA 30-2230-23 Shutting Down the ModuleNew module type Sw-module module cxsc uninstall30-24 ReloadMonitoring the ASA CX Module Admin123Showing Module Status 30-2530-26 Showing Module Statistics30-27 Monitoring Module Connections‘X’ flag Dp-cp30-28 Show asp event dp-cp cxsc-msg30-29 Ciscoasa# show asp dropCiscoasa# show asp event dp-cp cxsc-msg Capturing Module Traffic Troubleshooting the ASA CX ModuleDebugging the Module 30-3030-31 Problems with the Authentication ProxyCheck the authentication proxy port Configuration Examples for the ASA CX ModuleCheck the authentication proxy rules 30-3230-33 Feature History for the ASA CX ModuleFail-close fail-openmonitor-only,traffic-forward We modified or introduced the following commands cxscCxsc monitor-only 30-34Capture interface asadataplane command Asadataplane30-35 30-36 31-1 Information About the ASA IPS Module31-2 How the ASA IPS Module Works with the ASAUsing Virtual Sensors ASA 5510 and Higher Operating Modes31-3 31-4 Information About Management Access31-5 Licensing Requirements for the ASA IPS module1lists the default settings for the ASA IPS module Management Vlan ASA 5505 only31-6 Configuring the ASA IPS module Task Flow for the ASA IPS Module31-7 31-8 Connecting the ASA IPS Management Interface31-9 31-10 ASAASA 5512-X through ASA 5555-X Booting the Software Module Sessioning to the Module from the ASA31-11 For example, using the filename in the example in , enter Configuring Basic IPS Module Network SettingsCiscoasa# sw-module module ips recover boot 31-12ASA 5505 Configuring Basic Network Settings ASA 5510 and Higher Configuring Basic Network SettingsConnecting the ASA IPS Management Interface section on Sessioning to the Module from the ASA Section on31-14 Configuring the Security Policy on the ASA IPS Module Details command31-15 31-16 31-17 31-18 Diverting Traffic to the ASA IPS module31-19 31-20 Managing the ASA IPS module Installing and Booting an Image on the ModuleIPS module 31-2131-22 Sw-module module ips uninstall Uninstalling a Software Module ImageFor a software module for example, the ASA 5545-X 31-23Sw-module module ips password-reset For a software module for example, the ASA31-24 Monitoring the ASA IPS module Ips for a software module31-25 Configuration Examples for the ASA IPS module 31-26Ciscoasa# show module ips Allow-ssc-mgmt,hw-module module ip, and hw-module Feature History for the ASA IPS moduleModule allow-ip 31-27Inventory, show environment Session, show module, sw-module31-28 32-1 Information About the CSC SSM32-2 ASA32-3 Determining What Traffic to Scan32-4 Common Network Configuration for CSC SSM ScanningLicensing Requirements for the CSC SSM Prerequisites for the CSC SSM32-5 Parameter Default 1lists the default settings for the CSC SSMSupported in single and multiple context modes 32-6Configuring the CSC SSM Before Configuring the CSC SSM32-7 Connecting to the CSC SSM See the Connecting to the CSC SSM section on32-8 32-9 See the Diverting Traffic to the CSC SSM section on Diverting Traffic to the CSC SSMDetermining What Traffic to Scan section on 32-1032-11 32-12 Guidelines and Limitations section onSee the Monitoring the CSC SSM section on Monitoring the CSC SSMDisplays the status Displays additional status informationTroubleshooting the CSC Module Installing an Image on the Module32-14 Resetting the Password Recover command32-15 32-16 Reloading or Resetting the ModuleCiscoasaconfig-cmap#policy-map cscinpolicy Configuration Examples for the CSC SSMShutting Down the Module Shuts down the moduleRelated Topic Document Title Additional ReferencesInstructions on use of the CSC SSM GUI Assistance with the Startup WizardFeature Name Platform Releases Feature Information Feature History for the CSC SSMDetails recover 32-1932-20 IN-1 IN-2 IN-3 IN-4 IN-5 LDP 6-7router-id 6-7TDP Multi-session PAT See also policy mapRPC not supported with IN-6IN-7 IN-8 IN-9 IN-10
Related manuals
Manual 754 pages 55.66 Kb Manual 52 pages 35.74 Kb

ASA 5555-X, and the ASA Services Module, ASA 5545-X, ASA 5585-X, ASA 5580 specifications

Cisco Systems has long been a leader in the field of network security, and its Adaptive Security Appliance (ASA) series is a testament to this expertise. Within the ASA lineup, models such as the ASA 5505, ASA 5580, ASA 5585-X, ASA 5545-X, and ASA 5555-X stand out for their unique features, capabilities, and technological advancements.

The Cisco ASA 5505 is designed for small businesses or branch offices. It provides essential security features such as firewall protection, flexible VPN capabilities, and intrusion prevention. The ASA 5505 supports a user-friendly interface, allowing for straightforward management. Its built-in threat detection and prevention tools provide a layered defense, and with scalability in mind, it can accommodate various expansion options as organizational needs grow.

Moving up the line, the ASA 5580 delivers greater throughput and advanced security features. This model is suited for medium to large enterprises that require robust protection against increasingly sophisticated threats. Its multi-core architecture allows it to manage high volumes of traffic seamlessly while maintaining excellent performance levels. The ASA 5580 also supports application-layer security and customizable access policies, making it highly adaptable to diverse security environments.

The ASA 5585-X further enhances Cisco's security offerings with advanced malware protection and extensive security intelligence capabilities. It incorporates next-generation firewall features, including context-aware security, and supports advanced threat detection technologies. This model is ideal for large enterprises or data centers that prioritize security while ensuring uninterrupted network performance and availability.

For enterprises requiring a balance of performance and security, the ASA 5545-X presents a compelling option. This model features scalable performance metrics, high availability, and integrated advanced threat protection. Coupled with advanced endpoint protection and detailed monitoring capabilities, the ASA 5545-X enables organizations to manage their security posture effectively.

Lastly, the ASA 5555-X blends cutting-edge technologies with strong security infrastructures. It boasts high throughput and the ability to execute deep packet inspections. Its sophisticated architecture supports threat intelligence feeds that provide real-time security updates, making it a powerful tool against modern threats.

Each of these Cisco ASA models brings specific advantages to varied environments. Their integrative capabilities enable businesses to enhance their security postures while benefiting from seamless scalability and management. As cybersecurity threats evolve, these advanced appliances play a vital role in protecting valuable digital assets.