Lab #1: Develop System Administration Procedures for Windows 8.1 Security Configuration
Purpose: Develop systems administration procedures to implement systems security configuration guidance and best practices.
1. Develop a Windows system restore point systems administration procedure to implement an industry recognized best practice for maintaining system integrity and availability.
2. Develop a Windows system administration procedure to manage programs and features.
3. Develop a systems administration procedure to implement configuration rules fromsystems security technical guidance issued by a vendor or government organization.
In this lab, our focus is upon developing a set of procedures which can be incorporated into an organization’s security implementation guidance and documentation. For each procedure, you will develop, test, and document the steps required to implement the selected best practices and security configuration guidance (as provided in the lab instructions and notes).
Your deliverables for this lab will become part of the final project for this course (System Administration Manual).
(a) Step-by-Step System Administration Procedure for Creating, Using, Removing System Restore Points for Windows 8.1
(b) Step-by-Step System Administration Procedure for Managing Windows 8.1 Programs and Features
(c) Step-by-Step System Administration Procedure for Implementing Security Configuration Rules for Windows 8.1
Submit your deliverables in a SINGLE FILE in MS Word format (.docx or .doc file types) using the corresponding assignment folder entry (in LEO). (Use the Deliverable Template file from Course Resources > Sample Files > CSIA 310 Lab Deliverable Template.docx.) Every deliverable must use the format shown below. (Replace [Section Name] with the heading for the section, e.g. Creating a System Restore Point).
Notes, Warnings, & Restrictions:
Resources (Further Reading):
Brief Introduction Paragraph
Brief Introduction Paragraph
PART (A): IMPLEMENTING SYSTEM RESTORE POINTS
1. Investigate the System Restore tool (used to manage system restore points). To access the tool, open the System tool from Control Panel (Control Panel > System and Security > System). Then, click on System Protection (left menu).
2. Identify appropriate sources of information (e.g. Windows Help, Microsoft Technet, etc.) for instructions for using the Windows 8.1 System Restore Point capability. Using those sources, research the procedures required to perform the following tasks:
a. Create a system restore point for a Windows 8.1 system
b. Use a system restore point to roll-back changes made to a Windows 8.1 system
c. Remove system restore points from a Windows 8.1 system (some and all)
3. Develop a systems administration procedure which can be used to perform tasks related to item #1 (management and use of system restore points).
4. Test your draft procedures using the virtual machine provided in the online lab environment (UMUC’s VDA) or using a locally installed Virtual Machine (VM) running Microsoft Windows 8.1 Professional. As you run your tests, collect screen snapshots to illustrate key steps in your procedures. Insert these snapshots at the appropriate points in your procedure.
PART (B): MANAGING PROGRAMS AND FEATURES FOR WINDOWS 8.1
1. Investigate the Programs and Features tool (used to manage installed programs and optional features / capabilities). To access the tool, open Programs and Features from the Windows Control Panel.
2. Identify appropriate sources of information (e.g. Windows Help, Microsoft Technet, etc.) for instructions for using the Programs and Features tool. Using those sources, research the procedures required to perform the following tasks:
a. Turn Windows Features On or Off
b. Modify, Repair, or Uninstall a program from a Windows 8.1 system
c. Select and Install Updates for Windows and Windows Applications, Find an installed Update, Remove an installed update
3. Develop a systems administration procedure which can be used to perform tasks related to item #2. Provide examples for each of the required tasks. (Select a specific feature, program, or update and use that as an example in your procedure.)
4. Test your draft procedures using the virtual machine provided in the online lab environment (UMUC’s VDA) or using a locally installed Virtual Machine (VM) running Microsoft Windows 8.1 Professional. As you run your tests, collect screen snapshots to illustrate key steps in your procedures.
PART (C): IMPLEMENTING SECURITY CONFIGURATION RULES USING THE LOCAL GROUP POLICY EDITOR
Note: you are NOT implementing the DISA / DoD STIG in this section. You are implementing a set of security configuration rules that your “company” has selected from industry accepted sources.
1. Investigate the Local Group Policy Editor tool (Windows Key + R then type gpedit.msc). Pay particular attention to the menu tree in the left hand pane (expand and review the categories of settings which can be changed using this tool).
2. Research the security configuration rules listed in Table 1. These rules were developed from the Department of Defense Security Technical Implementation Guidance for Windows 8.1.
3. Group related security configuration rules and then develop a step by step procedure for each category of rules. See the “Suggested Procedure Group” column in Table 1 for suggested categories. Your groupings should allow for inclusion of additional, related rules at a later date. (For example, there are two “energy saving” rules in the table; an organization may wish to add additional rules to this category at some point in the future.)
4. For each category of rules, develop step-by-step written procedures for systems administrators. Your written procedures must implement the “remediation” guidance as listed in Table 1[i].
5. Test your draft procedures using the virtual machine provided in the online lab environment (UMUC’s VDA) or using a locally installed Virtual Machine (VM) running Microsoft Windows 8.1 Professional. As you run your tests, collect screen snapshots to illustrate key steps in your procedures.
6. Incorporate your screen snapshots for key steps into the draft procedures. Each snapshot should be placed UNDER (after) the step to which it applies. Captions are not required.
7. Make any additional changes required to address issues found during testing of the step-by-step procedures.
FINALIZE YOUR DELIVERABLE
1. Using the grading rubric as a guide, refine your step-by-step procedures. Your final products should be suitable for inclusion in an organization’s Systems Administrator’s Handbook. Remember that you are preparing multiple system administration procedures which must be presented separately.
2. As appropriate, cite your sources using footnotes or another appropriate citation style.
3. Use the resources section to provide information about recommended readings and any sources that you cite. Use a standard bibliographic format (you may wish to use APA since this is required in other CSIA courses). Information about sources and recommended readings, including in-text citations, should be formatted consistently and professionally.
4. At a minimum, each systems administration procedure document must include the following sections:
b. Operating Environment
d. Notes, Warnings, & Restrictions
e. Resources (format as Bibliography or Reference list)
5. Each procedure document should be placed in the listed order in a SINGLE FILE (see deliverables list above). Each file should start with a title page which lists the following information:
· Lab Title and Number
· Procedure Name
· Your Name
6. The CSIA 310 Template for Lab Deliverable.docx file is set up to provide the required title page and three lab procedure templates.
Additional Requirements for this Lab
1. Given the large number of security configuration rules which must be implemented, you must group the rules into categories or sub-sections within your step-by-step procedures.
2. Your step-by-step procedures should tell the reader where to find and how to launch the systems administration tools used to change security configuration settings for the Windows 8.1 operating system.
3. It is not necessary to specify every step that a system administrator must take to implement the security rules. But, you must address each security configuration rule separately and include enough detail that your reader will understand how to perform the required steps to implement the security configuration changes.
4. Use screen snapshots to cue the reader to important steps or provide information required to complete check points for proper completion of a step or set of steps (e.g. including a snapshot which shows the “after” state for a group of security settings).
5. Make sure that your snapshots will enhance the reader’s understanding of the procedure and required configuration changes. Too many snapshots or illustrations can make a procedure difficult to use.
6. All snapshots must be created by you for this lab using screen captures showing how you personally performed (tested) the systems administration procedure as written by you. You may not copy and paste images from help pages, manuals, or the Internet.
7. Images (screen snapshots) should be cropped and sized appropriately.
8. A screen snapshot belonging to a specific procedure step does not require a caption.
9. Your procedures must be submitted to Turn It In for originality checking. You are encouraged to consult existing configuration instructions, guidance, and procedures for both content and format. Your work must be substantially your own, however, which means you should paraphrase whenever possible. Credit the sources of information used via footnotes and in your “Resources” section.
10. Make sure that the sources you cite or recommend (additional reading) are authoritative and are the best ones available.
11. Your Operating Environment section should identify the hardware, operating system, and/or software applications to which the procedure applies. For this lab, your procedures will apply to:
a. Hardware: Laptop or Desktop Computers
b. Operating System: Windows 8.1 Professional
Your Notes, Warnings & Restrictions section should include important information that is not found elsewhere in the procedures document. For example, this section could include information about alternatives to the selected security configuration settings. Or, this section could include information about related security procedures or policies. If this procedure implements controls relevant to an external security requirement, e.g. the HIPAA Security Rule, then that information should be included in the notes section. Consult the
Windows 8.1 STIGto see what types of information you may need to include in your document. This section should also include important information about harm or risk that could occur if the procedure is not correctly followed or implemented. If there are no such warnings then this section should so
[i] Table 1 was adapted from the Department of Defense Security Technical Implementation Guidance (STIG) for Windows 8/8.1. Available from:http://iasecontent.disa.mil/stigs/zip/Apr2015/U_Windows_8_and_8-1_V1R9_STIG.zip