CASP vLAB Bugs
-
Hi,
I have recently gone through all the CASP vLABs. There are several bugs and I have devised some workarounds I thought I'd share. Mods could probably share these with the lab provider to fix for us.• Implementing Security Controls for Hosts
○ Cannot add WSUS service to Server01 - configuration fails
○ Workaround: Add to Server02
○ BIOS Simulators no longer available on the web• Conducting Vulnerability Assessments
○ Sometimes your keyboard doesn't properly map to the KALI VM - functions as if a shift-key is stuck. Restart the lab to fix.
○ The RDP DoS attack using setoolkit doesn't crash the RDP server as it's supposed to.• Analysing and Implementing Network Security
○ Warning: check the actual time on Server01 as it effects the policy restriction you configure; adjust accordingly.
○ When you configure the VPN client; make it pass your Windows credentials automatically, else it won't establish the VPN connection.
○ VPN client instructions was written for an older version of Windows - it requires some improvisation to get right.• Implementing Crypto
○ Instead of using your own email account, you can put the files on the other server by connecting to the administrator's hidden share from file explorer. \server02\c$
○ Don't ever use personal details on an untrusted public server like these lab servers. You have no assurance that it gets cleared out after you use it.• Integrating Computing
○ Instead of using your own email account, you can put the invitation file on the other server by connecting to the administrator's hidden share from file explorer. \server01\c$
○ Don't ever use personal details on an untrusted public server like these lab servers. You have no assurance that it gets cleared out after you use it. -
@Neil-Du-Plessis
We will get Nate to look into these. Thanks for the heads up! -
I have forwarded the information to the team who manages the VMs. Thank you for providing the detailed the write-up on the bugs. I'll update with more information as I get it.