10602049836327222433493328
Lab Access DetailsLab access Link
Useful Videos |
Lab VideosGeneral Notes:
1) Start each lab 3 minutes before required, it takes that time to spin the VM up. 2) Follow the instructions exactly as written and do not skip any steps. 3) When typing in the virtual machines, going from the instructions to the VM requires you to click into the VM. Example in the Terminal window you always miss the first letter of the command. 4) There are some keyboard mapping issues eg #=\ @= shift 2 5) Some of the questions in the lab you must get correct first time, otherwise you cannot go back and redo. These questions do not stop you from progressing. 6) The Applied labs are a repeat of the Assisted labs without as many tips. A good idea to make a note of some of the Linux commands used in the Assisted labs as there will be no hints. Assisted LabsLab 01: Exploring the Lab EnvironmentNotes:
1) In the Lab, I could not open the CDROM to access Odyessus, this caused no problem with the lab. 1) Click on the icon of the DVD drive :) in the notes Lab 02: Scanning and Identifying Network NodesNotes:
1) Remember that in the terminal window typing the first letter of the command needs you to be in the window. 2) Output in the terminal window often exceed the window size, scroll back in the window to see the full output 3) There is an arrow after the score for the questions, this can be used to get more details related to the answer for the question. Lab 03: Intercepting and Interpreting Network Traffic and Packet Sniffing ToolsNotes:
1) Q13 the answer is UDP yet you are analysing TCP ? 2) Step 10 in the url there is \\ and it should be // 3) Step 11 #=\ (Keyboard mismatch mappings) 4) Step 2 @=" (Keyboard mismatch mappings) Lab 04: Analysing the Results of a Credentialed VulnerabilityNotes:
1) There are screen shots of the options to choose in the lab instructions. Small black arrow next to instruction. Lab 05: Installing Using and Blocking a Malware based BackdoorApplied LabLab 06: Performing Network Reconnaissance and Vulnerability scanning.Notes:
1) Login to Centros tricky 2) Wireshark expand the arrow next to authorization to see credentials 3) When opening the report the default browser is chromium select firefox. 4) The script for testing 4450 in the question failed, it looks like it could not find the firewall rules. Assisted LabsLab 07: Managing the Life Cycle of a CertificateNotes:
1) Tricky to find the CA ie issued by (515support-CA) Lab 08: Managing Certificates with OpenSSLLab 09: Auditing Passwords with a Password Cracking UtilityNotes:
1) fiddly to edit password file:( Lab 10: Managing Centralised AuthenticationLab 11:Managing Access Controls in Windows ServerNotes:
1) Quite tricky to add the AD groups and permissions if not before. Lab 12: Configuring a System for Auditing PoliciesNotes:
1) Tiresome lab :( Lab 13: Managing Access Control in LinuxApplied LabLab 14: Configuring Identity and Access Management ControlsAssisted LabsLab 15: Implementing a Secure Network DesignLab 16: Configuring a FirewallNotes:
1) states sign in with Centos default account Pa$$w0rd did not work for this so logged in as root 2) ~ tilda was top left keyboard quotation mark 3) refresh firefox as it caches pages There is a question why this happens in the lab. 4) | pipe = shift # Lab 17: Configuring and Intrusion Detection SystemNotes:
1) The DDOS attack freezes the MS1 windows machine Lab 18: Implementing Secure Network Addressing ServiceNotes:
1) Confusing setting up theDHCP from Server Manager, just next through wizard. select the DHCP server option not clear in the lab guide during wizard. Takes time to install at end. Lab 19: Implementing a Virtual Private NetworkNotes:
1) vpn box was originally greyed out went back in and it was ok Lab 20: Implementing a Secure SSH ServerNotes:
1) This lab is approx 50 minutes long. For a very simple process this is way over complicated with editing of Unix files to achieve an outcome. 2) click and drag on cento screen to login 3) centos account password did not appear to work use root 4) commands reference su when we are already logged in as su because of above. 5) Authorized not Authrised in issue.net (RTFM) otherwise sript check does not work 6) Last part of lab did not work ie test root login (Probably my mistake) 7) Last question did not work because of above Lab 21: Implementing Endpoint ProtectionLab 22: Securing the Network InfrastructureNotes:
1) Centos login worked 2) VPN box appears second try. 3) Wrong input for q4 on the DHCP meant I could not put the correct one in. The lab allowed me to progress after time. Lab 23: Identifying Application Attack IndicatorsNotes:
1) Latest report for Memory Baseline did not create last task step :( Lab 24: Identifying a Browser AttackNotes:
1) # = shift £ Lab 25: Implementing Powershell SecurityLab 26: Identifying Malicious codeNotes:
1) Click on the icon of the DVD drive :) in the notes 2) Some of the questions in the lab you must get correct first time, otherwise you cannot go back and redo. These questions do not stop you from progressing. 3) Select powershell ISE from start menu Applied LabLab 27: Identifying Application AttacksNotes:
1) Last question "what is the execution policy with the new GPO effect" was the wrong answer. I put Unrestricted Assisted LabsLab 28: Managing Data Sources for Incident ResponseLab 29: Configuring Mitigation ControlsLab 30: Acquiring Digital Forensics EvidenceNotes:
1) Timeline Editor SLOW Lab 31: Backing Up and Restoring data in Windows and LinuxApplied LabLab 32: Managing Incident Response Mitigation and recoveryNotes:
1) Active directory Users and Computers not groups 2) Failed check of edit of rsyslog.conf but it was ok, so assume checking script at fault. 3) Totally messed up logger stuff which is in a previous lab anyway :) |