Hardening
Recommendation
s
In this section, students should compile a list of at least 3 good hardening recommendations for each system for the service or protocol assigned. Hint: You may provide more than 3 in case a recommendation provided is not considered a good one so that it will not reduce points. Graphics should never be used as a primary method of making or illustrating a point students are trying to make. Instead, students should make their point using their own words or the words of others, if properly cited and referenced using the APA style.
Do not include unacceptable recommendations that are similar to the following such as: auditing, backup, changing default port number, disk encryption, logging, monitoring, patch/update, or Zero Trust. Be aware that we cover SSH in last module so any recommendations about hardening SSH will be unacceptable until that module.
This major section should start at the top of a new page, and should not appear on the same page as any of the technical discussion content.
Operating Systems
(10-20 points depending on Module)
Windows:
(Remove this Windows subsection if it does not apply to the protocol required per our checklist.)
Hardening Recommendation #1 (Append your actual hardening recommendation here, such as “disable root access”)
Vulnerability
speculative execution side-channel vulnerabilitiesL1 Terminal Fault (L1TF) and Microarchitectural Data Sampling Recommendation
•disable hyper-threading
•Endpoint Security management
Here, students should provide technical details ofhowto implement the recommendation with step-by-step instructions to follow for our specific Netlab server and justifywhy this best practice was included in the discussion. Graphics may be used to supplement an explanation, but should be secondary in nature and minimal in count.