Protected URL Database

Transcription

1 Revised: October, 2008, Contents Managing URL Blacklists Using the SCE 1 Configuring User Authorization 2 How to specify a new owner of the sce-url-database 2 How to configure the sce-url-database write-protection 3 How to configure the sce-url-database lookup-protection 3 How to configure the sce-url-database encryption key 4 How to remove all sce-url-database protection 4 How to view the current sce-url-database protection settings 5 Managing the sce-url-database 5 sce-url-database Import File 6 How to import the sce-url-database file 6 How to add an entry to the sce-url-database 7 How to view the sce-url-database 7 How to look for a specific URL in the sce-url-database 8 How to clear the sce-url-database 8 Configuration Example 8 Americas Headquarters: Cisco Systems, Inc., 170 West Tasman Drive, San Jose, CA USA

2 Managing URL Blacklists Using the SCE The SCE platform managed URL database is a URL database that resides in the SCE platform and is managed via CLI commands rather than being managed by the SCA BB Console. In addition to the advantage of having a separate URL database that is configurable directly by CLI commands, this database can be used to hide a list of URLs so that they are not accessible by the Console or the CLI. The database must be declared as a separate flavor in the SCA BB application, but all other configuration and management is performed using the CLI. The database can be protected. When the sce-url-database is protected, one user is designated as the owner of the database and only that user can execute any CLI commands on the database. This requires defining the AAA authorization method (either based on local users or based on a TACACS+ server, etc.) and defining at least one user to be the owner of the database. For further details see Configuring the Management Interface and Security. If the database is defined to be protected, none of the database information (including the owner, the database entries, and the authorization information itself) is accessible to any users, including the relevant saved configuration in the log files and in the relevant SCA BB reports. The database owner user may change the authorizations using the CLI; however, when any of the protections are relaxed (or all of the protections are relaxed by removing the protections entirely) the database is reset. In order to ensure the secrecy of the database information, the database entries may be imported to the SCE (using the CLI) in an encrypted form using 128-, 192-, or 256-bit key length AES. The key may be set or updated using the appropriate CLI command; typically, this command should be run over a secure Telnet session. There are two general categories of CLI commands related to the SCE managed URL database: User authorization commands Database management commands Configuring User Authorization The sce-url-database is managed by a single authorized user, who is the designated owner of the sce-url-database. When there is no designated owner, the sce-url-database is unprotected and the contents can be read and modified by any user. When there is a designated owner, the sce-url-database is protected. The default protection settings are as follows: Read permission no-user. This setting is not configurable Write permission owner-only. The owner can configure this setting to all-users. Lookup permission no-user. The owner can configure this setting to owner-only. Encryption key no key. The owner can configure an encryption key. User Authorization Guidelines: The default user cannot be the owner. Only the owner can configure the protection settings. If there is no owner, the database is unprotected and any user has read and write permission. A user may be configured to be the owner of the database only while no owner user is designated for the database. 2

3 When any protection setting is relaxed, the database is reset. Protection is relaxed in the following cases: Protection is removed completely using the no sce-url-database protection command. Write permission is changed from owner-only to all-users. Lookup permission is changed from no-user to owner-only. The sce-url-database configuration information is not accessible as part of the running config and startup config files. Protected information is not displayed when a show or more command is executed on the config files. Protected information is included when a copy command is executed on the config files. How to specify a new owner of the sce-url-database sce-url-database protection owner (myself (name user-name)) If there is currently an owner assigned to the sce-url-database, that owner must first remove the owner designation using the no sce-url-database protection command, which removes all DB protection (see How to remove all sce-url-database protection, page 5). myself The owner of the DB is the user who is currently logged in. Cannot be logged in under the default username. user-name The user name to be assigned as the owner of the DB. Cannot be the default username. Note that in this case, if no such user exists (either in the local database or in the Tacacs+ server) or the AAA authorization is not configured accordingly (that is, the logic user), there is no effective way of utilizing this owner user's permissions. Once the relevant user or AAA settings are configured, the owner user's permissions are effective accordingly. Default: no owner Results The specified user is the owner of the sce-url-database. Read of the sce-url-database is not permitted for any user (including the owner). No RDRs or traps will contain data of these URLs. By default, only the owner has Write permission to the sce-url-database. By default, Lookup is not permitted for any user (including the owner). 3

4 How to configure the sce-url-database write-protection This command can be executed only by the assigned owner of the sce-url-database. sce-url-database protection allow-write (all-users owner-only) Assign an owner to the sce-url-database. all-users owner-only Results If protections are relaxed (changed from owner-only to all-users), the sce-url-database is reset. Default: If no owner has been assigned, the default is all-users. If an owner has been assigned, the default is owner-only. How to configure the sce-url-database lookup-protection This command can be executed only by the assigned owner of the sce-url-database. sce-url-database protection allow-lookup (owner-only no-user) Assign an owner to the sce-url-database. owner-only no-user Results If protections are relaxed (changed from no-user to owner-only), the sce-url-database is reset. Default: If no owner has been assigned, the default is all-users. If an owner has been assigned, the default is no-user. 4

5 How to configure the sce-url-database encryption key This command can be executed only by the assigned owner of the sce-url-database. sce-url-database protection encryption-key encryption-key Assign an owner to the sce-url-database. encryption-key The AES encryption key either 128-, 192-, or 256-bits long. The key is supplied in hexadecimal format and is 32, 48, or 64 hexadecimal digits respectively. Default: no encryption key Removing the Encryption Key no sce-url-database protection encryption-key No other sce-url-database protection settings are changed by this command. How to remove all sce-url-database protection This command can be executed only by the assigned owner of the sce-url-database. no sce-url-database protection Assign an owner to the sce-url-database. Results Removes all the sce-url-database protections and resets the sce-url-database Reverts to default protection settings: no designated owner user no protections no encryption key. How to view the current sce-url-database protection settings show interface linecard 0 sce-url-database protection Command Mode User Exec Authorization Level Viewer 5

6 Results Displays the following information: owner username current protection settings whether a key is configured Sample Output SCE>show interface linecard 0 sce-url-database protection Protection Domain BLACK_LIST_DOMAIN Status: Domain owner:black Read is allowed to no user Write is allowed to user black only Lookup is allowed to no user Encryption key is not set Managing the sce-url-database The designated owner of the sce-url-database can do the following: import the list of URLs from a sce-url-database file add a single entry to the sce-url-database clear the sce-url-database lookup a specific URL (unless lookup protection is set to no-user) If write protection is set to all-users, any user can do the following: import the list of URLs from a sce-url-database file add a single entry to the sce-url-database clear the sce-url-database If there is no designated owner (and therefore no protection), any user can do the following: display a listing of the entire sce-url-database If there is a designated owner, the contents of the sce-url-database are protected and cannot be displayed. Guidelines for Managing the sce-url-database When a new file is imported, the existing database is cleared before the import. Incremental update is not supported. Therefore the import file must contain all the relevant URLs, not only new ones to be added to the database. Add a large number of new URLs by importing an updated sce-url-database file. Typically, if the database is protected this option is used with an encrypted file. Add a few new URLs by adding the new URLs using the sce-url-database add-entry command. sce-url-database Import File The database import file may be either clear text or encrypted. If the file is encrypted, the matching encryption key must be configured by the database owner. 6

7 If the file is encrypted, it must be prefixed with a cleartext header specifying the relevant encryption information. The encrypted file header format is as follows: Encrypted file version: 0x01 Block cipher index: <a cipher index using two hexadecimal digits '0x01', '0x02', or '0x03' corresponding to AES 128, 192, or 256 respectively> Mode of operation index: 0x01 to 0X02 Padder index: 0x00 to 0X02 IV length: 0x10 Each line in the file represents a single URL. sce-url-database Import File Format [Flavor <tab>] URL Where: Flavor: Flavor-id. The flavor ID must either be included for every line in the file or none of the lines. The flavor must be separated from the URL by a <tab>. URL: ('*' URL-Prefix ['*'] [URL-Prefix] '*' URL-Suffix) How to import the sce-url-database file See sce-url-database Import File, page 6 for the required format of the sce-url-database import file. If the import file does not contain the flavor, you must specify the flavor in the CLI command. The specified flavor must be the one that was designated for the black list in the pqb file that was applied, other wise the operation will fail. sce-url-database import cleartext-file encrypted-file file-name flavor-id flavor-id If the import file does contain the flavor, you may not specify the flavor in the CLI command. sce-url-database import cleartext-file encrypted-file file-name The user executing the command must have write permission for the sce-url-database. cleartext-file encrypted-file An encrypted file may be imported only if a matching encryption key has been configured. file-name Path and filename of the sce-url-database import file. flavor-id The flavor is applied to all entries in the file. Default: sce-url-database is empty 7

8 Results The sce-url-database is first cleared. The entries from the file are written to the database. Duplicate keys in the file are overwritten with no warning. In case of a failure, writing continues to the next entry. The total number of failures and a listing of the failed file line numbers are reported when the import is finished. How to add an entry to the sce-url-database sce-url-database add-entry url-wildcard URL-wildcard-format flavor-id flavor-id The user executing the command must have write permission for the sce-url-database. flavor-id flavor-id is required when adding a single entry. Entry line format: URL Flavor Where: URL: ('*' URL-Prefix ['*'] [URL-Prefix] '*' URL-Suffix) flavor-id: Decimal number representing the Flavor How to view the sce-url-database show interface linecard 0 sce-url-database all-entries Command Mode Privileged Exec The sce-url-database must have all protection removed and no assigned owner. If there is an assigned owner, the database is protected and cannot be displayed. How to look for a specific URL in the sce-url-database show interface linecard 0 sce-url-database url url Command Mode Privileged Exec The user executing the command must have lookup permission for the sce-url-database. 8

9 url Specific URL to lookup in the sce-url-database. Result If the specified URL exists, the flavor index will be returned. How to clear the sce-url-database sce-url-database remove-all The user executing the command must have write permission for the sce-url-database. Configuration Example The following example shows how to configure the protected URL databse, including defining the flavor in the SCA BB console, configuring the protections in the SCE platform and importing a URL file. Step 1 From the Flavor Settings window, right-click HTTP URL and choose New > HTTP URL Flavor. 9

10 Step 2 Enter a Name and Index as required. Note Step 3 Step 4 Step 5 Step 6 Step 7 Step 8 Step 9 Step 10 The Index number is the flavor-id that is required by a number of CLI commands. Click OK. Define a Service that uses the new Flavor. Apply the service configuration to the SCE. Define the SCE to require user login and define the special owner user: #configure (config)#aaa authentication login default local enable none (config)#username BlacklistOwner privilege 10 password pass Login as the owner user: User Access Verification Username: BlacklistOwner Password: Set the owner of the sce-url-database: #configure (config)#interface LineCard 0 (config if)#sce-url-database protection owner myself (Optional) Allow all users to update the database: (config if)#sce-url-database protection allow-write all-users (Optional) Allow the owner to perform lookup on the database: (config if)#sce-url-database protection allow-lookup owner-only 10

11 Step 11 Step 12 Step 13 Step 14 Define an encryption key to be used when importing an encrypted URLs file: This is typically done periodically over a secure Telenet session. (config if)#sce-url-database protection encryption-key AABBCCDDEEFF Import an encrypted (according to the key defined in Step 11) file containing the required URLs for the relevant flavor ID: This is typically done periodically; either first copy the file to the SCE or import directly over FTP. (config if)#sce-url-database import encrypted-file urls.csv flavor-id 10 Save the configuration: (config if)#>ex (config)#>ex #>copy running-config-all startup-config-all Writing general configuration file to temporary location... Backing-up general configuration file... Copy temporary file to final location... Writing general (protected) configuration file to temporary location... Backing-up general (protected) configuration file... Copy temporary (protected) file to final location... Writing general configuration file to temporary location... Removing old application configuration file... Renaming temporary application configuration file with the final file's name... Writing general (protected) configuration file to temporary location... Removing old application (protected) configuration file... Renaming temporary application (protected) configuration file with the final file's name... Logout to prevent unauthorized users from manipulating the protected database: #logout Are you sure? y 11

12 Obtaining Documentation and Submitting a Service Request Obtaining Documentation and Submitting a Service Request For information on obtaining documentation, submitting a service request, and gathering additional information, see the monthly What's New in Cisco Product Documentation, which also lists all new and revised Cisco technical documentation, at: Subscribe to the What's New in Cisco Product Documentation as a Really Simple Syndication (RSS) feed and set content to be delivered directly to your desktop using a reader application. The RSS feeds are a free service and Cisco currently supports RSS version 2.0. CCDE, CCENT, Cisco Eos, Cisco Lumin, Cisco Nexus, Cisco StadiumVision, Cisco TelePresence, Cisco WebEx, the Cisco logo, DCE, and Welcome to the Human Network are trademarks; Changing the Way We Work, Live, Play, and Learn and Cisco Store are service marks; and Access Registrar, Aironet, AsyncOS, Bringing the Meeting To You, Catalyst, CCDA, CCDP, CCIE, CCIP, CCNA, CCNP, CCSP, CCVP, Cisco, the Cisco Certified Internetwork Expert logo, Cisco IOS, Cisco Press, Cisco Systems, Cisco Systems Capital, the Cisco Systems logo, Cisco Unity, Collaboration Without Limitation, EtherFast, EtherSwitch, Event Center, Fast Step, Follow Me Browsing, FormShare, GigaDrive, HomeLink, Internet Quotient, IOS, iphone, iquick Study, IronPort, the IronPort logo, LightStream, Linksys, MediaTone, MeetingPlace, MeetingPlace Chime Sound, MGX, Networkers, Networking Academy, Network Registrar, PCNow, PIX, PowerPanels, ProConnect, ScriptShare, SenderBase, SMARTnet, Spectrum Expert, StackWise, The Fastest Way to Increase Your Internet Quotient, TransPath, WebEx, and the WebEx logo are registered trademarks of Cisco Systems, Inc. and/or its affiliates in the United States and certain other countries. All other trademarks mentioned in this document or website are the property of their respective owners. The use of the word partner does not imply a partnership relationship between Cisco and any other company. (0809R) Any Internet Protocol (IP) addresses used in this document are not intended to be actual addresses. Any examples, command display output, and figures included in the document are shown for illustrative purposes only. Any use of actual IP addresses in illustrative content is unintentional and coincidental Cisco Systems, Inc. All rights reserved. 12