Cisco ASA lab 1 of 15
ASA initial setup: interfaces, security levels and the default policy
Bring a new Cisco ASA online with inside, outside and DMZ interfaces, a default route and ICMP inspection, then prove exactly what the security levels allow and block before a single ACL exists.
Run this lab
It needs Lite: its 4 nodes are set to 4 vCPU and 3,584 MB in total. That fits the free demo too.
In your workspace: Shared, then Cisco ASA Firewall SCOR 350-701 guided labs, then 01 - ASA initial setup - interfaces security levels and the default policy
- Level
- Beginner
- Time
- About 45 minutes
- Nodes need
- 4 vCPU, 3,584 MB
- Smallest plan
- Lite
The scenario
Kestrel Logistics is replacing the access lists on its old head-office router with a Cisco ASA, HQ-FW. The cabling is done: Gi0/0 goes to the office LAN, Gi0/1 to the ISP and Gi0/2 to a small DMZ that holds the public web server.
Your job today is the first day of any firewall project: bring the interfaces up with the right trust levels, give the firewall a default route, and prove what the firewall does on its own, before anyone writes an access list. In later labs you will add ACLs, NAT, VPNs and more on top of exactly this design.
| Interface | Name | Security level | Address |
|---|---|---|---|
| Gi0/0 | inside | 100 | 10.10.10.1/24 |
| Gi0/1 | outside | 0 | 203.0.113.2/24 |
| Gi0/2 | dmz | 50 | 172.16.10.1/24 |
For this first lab only, the ISP routes Kestrel's internal ranges back to the firewall, so you can watch the security levels work without NAT. Lab 4 replaces that shortcut with NAT.
What you’ll practise
- Name ASA interfaces and give them security levels that match their trust
- Explain and test the default policy: higher to lower allowed, lower to higher denied
- Add a default route and read the ASA routing table
- Turn on ICMP inspection in the global policy and explain why ping failed without it
- Read the connection table and syslog messages 106001 and 106014
The tasks
- Look around
- Configure the three interfaces
- Add the default route
- Test outbound traffic and fix ping
- Prove what is blocked
- Save your work
The Lab Tasks pane has the scenario, these tasks, the checks to run, hints and the full solution.
Topology and devices
The network as it opens in EVE-NG, drawn from the lab’s own canvas, and the image each node runs.
Every link, as text
- HQ-FW
Gi0/0to PC1Gi0/0 - HQ-FW
Gi0/1to ISPGi0/0 - HQ-FW
Gi0/2to WEBGi0/0
| Node | Device | Image in Add Node | Set to |
|---|---|---|---|
| HQ-FW | Cisco ASAv | asav-9.22.1.1-PLR-Licensed | 1 vCPU, 2,048 MB |
| PC1 | Cisco IOSv | vios-adventerprisek9-m.SPA.159-3.M6 | 1 vCPU, 512 MB |
| WEB | Cisco IOSv | vios-adventerprisek9-m.SPA.159-3.M6 | 1 vCPU, 512 MB |
| ISP | Cisco IOSv | vios-adventerprisek9-m.SPA.159-3.M6 | 1 vCPU, 512 MB |
How to open this lab
Sign in to your workspace at
lab.cloudlabbox.com.In File Manager, open Shared, then the folder
Cisco ASA Firewall SCOR 350-701 guided labs.Open
01 - ASA initial setup - interfaces security levels and the default policyand start its nodes, then open Lab Tasks for the scenario and the steps.
The lab is read-only. You can start the nodes and configure the devices, but changes to the topology can’t be saved. To change it, rebuild it in your own folder.
More Cisco ASA labs
Related labs in other courses
CloudLabBox is independent of Cisco. The lab follows exam topics and isn’t vendor training material; vendor names identify the exams and the images in the workspace.