SSNGFW Labs

Lab can be accessed either though the "Learning Services Portal"
or through  ELT material. The video's opposite show the delegate and instructor access to these labs through the portal. There will be about a 10 minute wait before the start of each lab to spin up the virtual machines.

If  the labs for this course are accessed from the ELT material. This requires an email prior to every lab either to access immediately or reserve a time slot. The process is straightforward and from my experience took about 15 to 20 mins before the email arrived and a 3 hour time slot allocated. If this reservation overlaps with an existing lab  you have the option to exit the previous lab and start the new lab straight away.

---

Labs from ASA Advanced Course

Lab 7 is a major lab in the old ASA advanced course covering the Firepower code and FMC. It has some useful labs not covered in this course especially around SSL encryption/decryption.

Lab 7 FMC for ASA Firepower Part 1-5

​Lab 7 FMC for ASA Firepower Part 6-11

Lab 7 FMC for ASA Firepower Part 11-18

---

SSNGFW eReader SSL Lab
​Decrypt Known-Key

Lab Initial Set Up
​"Learning Services Portal"

Delegate Access

Instructor Access

---

LAB Videos

Lab 1: Initial Device Setup

Carry out changes after initial setup

Be careful when you enter the networking details from the command line. Check you are putting in the correct addresses as per the lab guide. Wait at the part after entering DNS information as the CLI has to wait to output info to the screen.

Lab 2: Device Mangement

Lab 3: Config High Availability

Be patient after configuring the High availability pair. Errors will appear (yellow icons) during sync they will eventually sync green.

​The output from the CLI regarding one of the IP address masks does not match.

Lab 4: Migrating ASA to FTD Part 1

Reason for 2 parts, is my mistake in not following the lab guide
and missing out the .sfo file download.

Lab 4: Migrating ASA to FTD Part 2

Lab 5: Implementing QOS

Lab 6: Implementing NAT

Lab 7: Tune Network Discovery

"application Protocol" ie port 80 etc = Pending is because the system cannot positively or negatively can identify the app, more information needs to be gathered.

Lab 8: Implementing Access Control Policy

Lab 9: Security Intelligence

Access to the Security Intelligence feed file was carried out with the "more" command in the sub directory where the file was. This is probably my bad as it worked later in Lab 12.

Lab 10: Site to Site VPN

Lab 11: Remote Access VPN's

Lab 12: Threat Analysis

Note:
Task 3 does not work (Oct 2021). It appears that in the build someone has forgotten to deploy the config with the IPS rules to the FTD.
Solution: Deploy -- open the deploy window and you will see the out date IPS policies. On deploy you will get a export license warning just continue.
​

Lab 13: System Admin

Lab 14: Troubleshooting

Some of the text output is not quite identical to the screen shots in the lab guide.