20-12
Cisco ASDM User Guide
OL-16647-01
Chapter 20 Configuring Access Rules and EtherType Rules
Configuring Access Rules
• Description—(Optional) Enter a description of the access rule.
• Enable Logging—Enables logging for the access rule.
–
Logging Level—Specifies default, emergencies, alerts, critical, errors, warnings, notifications,
informational, or debugging.
• More Options—Shows additional configuration options for the rule.
–
Enable Rule—Enables or disables the rule.
–
Traffic Direction—Determines which direction of traffic the rule is applied. Options are either
incoming or outgoing.
–
Source Service—Specifies a source protocol and service (TCP or UDP service only).
...—Lets you select, add, edit, delete or find a source service from a preconfigured list.
–
Logging Interval—Specifies the interval for logging in seconds if logging is configured.
–
Time Range—Specifies a time range defined for this rule from the drop-down list.
...—Lets you select, add, edit, delete or find a time range from a preconfigured list.
Modes
The following table shows the modes in which this feature is available:
Manage Service Groups
The Manage Service Groups dialog box lets you associate multiple TCP, UDP, or TCP-UDP services
(ports) in a named group. You can then use the service group in an access or IPSec rule, a conduit, or
other functions within ASDM and the CLI.
The term service refers to higher layer protocols associated with application level services having well
known port numbers and “literal” names such as ftp, telnet, and smtp.
The security appliance permits the following TCP literal names:
bgp, chargen, cmd, daytime, discard, domain, echo, exec, finger, ftp, ftp-data, gopher, h323, hostname,
http, ident, irc, klogin, kshell, lpd, nntp, pop2, pop3, pptp, smtp, sqlnet, sunrpc, tacacs, talk, telnet, time,
uucp, whois, www.
The Name of a service group must be unique to all four types of object groups. For example, a service
group and a network group may not share the same name.
Multiple service groups can be nested into a “group of groups” and used the same as a single group.
When a service object group is deleted, it is removed from all service object groups where it is used.
If a service group is used in an access rule, do not remove it. A service group used in an access rule
cannot be made empty.
Firewall Mode Security Context
Routed Transparent Single
Multiple
Context System
• • • • —