Cybersecurity Processes And Technologies
vemylami
CSIA310Project2-IRManualPart2v1.docx
Project #2: Incident Response Procedures Manual (Part 2)
Purpose:
Develop a set of tool-focused incident response procedures.
Before You Begin:
Please make sure that you have read the Sifers-Grayson company profile, the weekly descriptions, and any/all announcements by your instructor prior to beginning this assignment. You also need to be familiar with the phases of the Incident Response Process as documented in NIST SP 800-61 r2 Computer Security Incident Handling Guide http://dx.doi.org/10.6028/NIST.SP.800-61r2 .
Background:
Recent contracts with the Departments of Defense and Homeland Security have imposed additional security requirements upon Sifers-Grayson and its lab operations. The company is now required to comply with NIST Special Publication 800-171 Protecting Controlled Unclassified Information in Nonfederal Information Systems and Organizations. The company must also comply with provisions of the Defense Federal Acquisition Regulations (DFARS) including section 252-204-7012 Safeguarding Covered Defense Information and Cyber Incident Reporting. These requirements are designed to ensure that sensitive technical information, provided by the federal government and stored on computer systems in the Sifers-Grayson SCADA Lab and the Sifers-Grayson R&D DevOps lab, is protected from unauthorized disclosure. This technical information includes software designs and source code for systems and devices that Sifers-Grayson builds or supports.
The contract requirements also mandate that Sifers-Grayson report cyber incidents to the federal government in a timely manner. As part of the reporting requirements, Sifers-Grayson must provide documentation about its Incident Response Processes and Procedures. The procedures that you develop for this project will become part of the contractually required documentation.
Vendor documentation for Windows 8.1, Windows 10, and other utilities / applications will provide information about how to use various features, tools, and utilities but, during an incident, responders may not have time to search vendor websites and/or the Internet for information about tools and tool usage procedures. For this reason, customized incident response procedures are required to ensure that response is timely and that all incident responders have the information needed to execute their tasks.
References
Cichonski, P., Millar, T., Grance, T., & Scarfone, K. (2012). Computer security incident handling guide (NIST SP 800-62 rev. 2). http://dx.doi.org/10.6028/NIST.SP.800-61r2
Your Task:
In this assignment, you will assess and document tools to be used by the Sifers-Grayson Incident Response Team during the preparation, detection, containment, eradication, and recovery phases of the Incident Response Process (as defined in NIST SP 800-61r2). The deliverable for this assignment is a set of three customized procedures suitable for inclusion in the Sifers-Grayson Incident Response Procedures Manual. Each procedure must be written so that it can be added / updated / removed without impacting other procedures in the manual. In other words, the procedures must be self-contained and stand on their own.
Detailed Instructions:
Your deliverable must use the provided MS Word template file (contact your instructor for formatting guidance if you cannot use this file). The required procedures are described below.
Procedure 1: Using System Restore Points under Windows 10
1. Identify appropriate sources of information and instructions for using the Windows 10 Control Panel and System Restore tool. Using those sources, research the procedures required to perform the following tasks:
a. Create a system restore point for a Windows 10 system
b. Use a specific system restore point to roll-back changes made to a Windows 10 system
c. Delete system restore points from a Windows 10 system
2. Identify how the System Restore tool could be used during the incident response and recovery process (it may be useful in more than one phase). Typical uses include:
a. Prepare a known-good backup for operating system files and data structures (e.g. the system registry and the information stored within it)
b. Remove unauthorized configuration changes
c. Restore the system to full operating status after an attack or suspected attack
d. Remove failed software installations and/or unwanted changes to the operating system, applications software, and/or files.
3. Write a guidance document that identifies the tool, explains the capabilities it provides, and then lists and briefly describes the recommended uses identified under item #2. Add a list of resources that can be consulted for additional information. Next, summarize the procedures required to perform the tasks listed under item #1 (do not provide step-by-step instructions). Close your guidance document with a Notes / Warnings / Restrictions section that answers the question “Is there anything else the incident responder needs to be aware of when using this tool?”
Procedure 2: Backup the System Disk for a Windows 8.1 Workstation
1. Using the Internet, research commercially available system backup tool or application. (Do not use any features or utilities that are part of the Windows operating system.) Then, identify appropriate sources of information and instructions for your selected tool. Using those sources, research the procedures required to
a. Create a “known good” copy (system backup or complete system image) of the hard drive containing the Windows 8.1 system and installed applications for a workstation in the SCADA lab.
b. Generate a hash code for use in verifying the validity and integrity of the backup file or system image file. (If your backup utility does not provide this, you will need to find a separate tool that will generate an MD-5 or SHA-256 hash value for the image file or backup file. See https://www.howtogeek.com/67241/htg-explains-what-are-md5-sha-1-hashes-and-how-do-i-check-them/ for an explanation of file integrity checking using hash codes.)
c. You should also research and document best practices for labeling and storing the digital media containing the backup files and/or system image files. The storage location should provide secure storage yet be readily available to incident responders in the event of an incident. The label or storage log should include the hash value for each backup file and system image file.
2. Identify how the backup tool could be used during the preparation phase of the incident response and recovery process. Typical uses include:
a. Create a “known good” backup that contains a complete, verified and approved system configuration that includes the operating system and all required application software.
b. Create a copy of the original operating system installation (before software applications are installed).
3. Write a guidance document that identifies the tool, explains the capabilities it provides, and then lists and briefly describes the recommended uses identified under item #2. Add a list of resources that can be consulted for additional information. Next, summarize the procedures required to perform the tasks listed under item #1 (do not provide step-by-step instructions). Close your guidance document with a Notes / Warnings / Restrictions section that answers the question “Is there anything else the incident responder needs to be aware of when using this tool?”
Procedure 3: Restore the System Disk for a Windows 8.1 Workstation
1. Use the same tool and tool research as performed for Procedure #5. If necessary, identify additional sources of information and instructions for using your selected tool(s) to perform the following tasks:
a. Verify the validity of the backup image or file (using the hash code).
b. Use the “known good” copy (system backup or system image) to rebuild a workstation hard drive so that it contains the Windows 8.1 operation system and installed applications.
2. Identify how the tool could be used during the containment, eradication & recovery phase of the incident response and recovery process. Typical uses include:
a. Restore workstation hard drives to a “known good” configuration.
b. Build a new system disk using a replacement or newly purchased hard drive.
c. Restore the system to full operating status after an attack or suspected attack.
3. Write a guidance document that identifies the tool, explains the capabilities it provides, and then lists and briefly describes the recommended uses identified under item #2. Add a list of resources that can be consulted for additional information. Next, summarize the procedures required to perform the tasks listed under item #1 (do not provide step-by-step instructions). Close your guidance document with a Notes / Warnings / Restrictions section that answers the question “Is there anything else the incident responder needs to be aware of when using this tool?”
Finalize Your Deliverable
1. Using the grading rubric as a guide, refine your incident response guidance. Your final products (incident response procedures) should be suitable for inclusion in the Sifers-Grayson Incident Responder’s Handbook. Remember that, even though you are submitting your work in a single file, you are preparing stand-alone guidance documents. FOLLOW THE TEMPLATE.
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 courses). Information about sources and recommended readings, including in-text citations, should be formatted consistently and professionally.
4. Use the required template file below: CSIA310_Template_for_IR_Manual.docx
5. This file is set up to provide the required title page and three incident response guidance documents.
6 For the submission of this assignment (All Projects), you are required to submit your work through Turnitin.
Recommended Resources for Project 2: System Backup Tools
· Review pp. 87-102 (Incident Response) in The InfoSec Handbook (see attachment)
· Read Chapter 13: Data Backups (pp. 233-273)( see attachment)
· What’s the Best Way to Back Up My Computer?- https://www.howtogeek.com/242428/whats-the-best-way-to-back-up-my-computer/
· The Best Backup Software of 2018-
https://www.pcmag.com/roundup/225753/the-best-backup-software
· The Best Online Backup Services of 2019-
https://www.pcmag.com/roundup/226992/the-best-online-backup-services
· Top 20 Enterprise Online Backup Solutions for Business Cloud Data Protection-
CSIA310_Template_for_IR_Manual.docx
Title
[Your Name]
[Due date for assignment]
3
Title: [title for guidance document #1]
Tool Identification: [official name of the tool]
Description of the Tool:
[Identify capabilities, features, publisher]
Typical Uses for Incident Response:
[identify phases or circumstances when used, identify and describe specific uses, expected benefits or impacts]
Resources (Further Reading):
1.
2.
3.
How to Use This Tool:
[summarize procedures, do not give step-by-step instructions]
Notes / Warnings / Restrictions:
[is there anything else the incident responder needs to be aware of when using this tool?]
Title: [title for guidance document #2]
Tool Identification: [official name of the tool]
Description of the Tool:
[Identify capabilities, features, publisher]
Typical Uses for Incident Response:
[identify phases or circumstances when used, identify and describe specific uses, expected benefits or impacts]
Resources (Further Reading):
1.
2.
3.
How to Use This Tool:
[summarize procedures, do not give step-by-step instructions]
Notes / Warnings / Restrictions:
[is there anything else the incident responder needs to be aware of when using this tool?]
Title: [title for guidance document #3]
Tool Identification: [official name of the tool]
Description of the Tool:
[Identify capabilities, features, publisher]
Typical Uses for Incident Response:
[identify phases or circumstances when used, identify and describe specific uses, expected benefits or impacts]
Resources (Further Reading):
1.
2.
3.
How to Use This Tool:
[summarize procedures, do not give step-by-step instructions]
Notes / Warnings / Restrictions:
[is there anything else the incident responder needs to be aware of when using this tool?]
The weekly descriptions: Operational Security, Incident Reporting Requirements, & Data Backup Strategies
· Operations Security (OPSEC)
· Cryptography & Encryption
· Safeguarding Controlled Information (DFARS)
· Reporting Requirements for Incidents (DFARS)
· Data Backups as a Supporting Service for Incident Recovery
This week, our focus moves to how IT can and should support IT Operations and Operational Security.
Sifers-Grayson has a test range where the engineers can fly test vehicles and determine if the drones and robots are operating properly. Communications with the test vehicles can occur via radio frequency (RF) transmission using the industrial, scientific, and medical (ISM) radio bands in the 2.4 - 2.5 GHz range. These bands do not require licenses and may be used by anyone for the stated purposes (fixed, mobile amateur). The test vehicles are controlled via hand-held devices at the test range. These devices are also connected to the Internet through wireless connections to a Wireless Access Point.
The test directors and test engineers communicate between the R&D Center and the test range using cellular phones, line of site RF, and microwave communications. For some tests and test vehicles they also use licensed satellite communications through a commercial SATCOM provider. Up until now, Sifers-Grayson has not used encryption technologies to protect the confidentiality and integrity of these communications.
In an early morning meeting with Sifers-Grayson Managers, Nofsinger Consultants advised the company that, at a minimum, it should encrypt its communications to and from the test vehicles. The sticking point in these discussions has been the company's belief that the Federal Communications Commission regulations ban the use of encrypted communications in the radio frequency (RF) bands used by Sifers-Grayson to communicate with test vehicles.
Clearly, a legal opinion is required to settle the issue of whether or not encryption is allowed for the RF bands currently in use.
In the meantime, the company's managers have accepted the Nofsinger recommendations and directed the R&D engineers to look into design changes required to implement encryption at OSI Layer 2 (Data Link Layer and Media Access Control Sub-Layer). They have also agreed to fund a study as to how the engineers should implement encryption at OSI Layer 3 (Network Layer) and OSI Layer 4 (Transport Layer) for each of the affected product lines (industrial control systems, drones, and robots).
At the end of the discussion about encryption, the Sifers-Grayson managers requested that Nofsinger's consultants perform a broader follow-on assessment of the cybersecurity issues arising from the Sifers-Grayson test range.
The Nofsinger team has decided to start their assessment by examining the company's Operations Security practices at the test range and in the engineering research areas of the firm. The five step OPSEC process used by Nofsinger has been adapted from OPSEC assessment methodologies used within the US Department of Defense. This process is:
1. Identify information that is critical to your business or mission
2. Analyze the threat
3. Analyze vulnerabilities and indicators
4. Assess the risk to your organization
5. Develop and apply countermeasures
Using an OPSEC approach will allow the Nofsinger team to determine what sensitive information about the company's operations, contracts, and R&D efforts may be at risk. The findings from this examination will allow Nofsinger to develop recommendations and propose solutions that can improve the security of the testing processes.
The third topic for this week is Data Backup Strategies and data backups as a supporting IT service. Data backups themselves are important parts of incident response and recovery. The readings for this topic are in the sub-folder for Project #2.
Rubric Name: IR Procedures
|
Procedure #2 (25%) |
|
|
Title, Tool Identification, Description of the Tool |
6 points Provided an acceptable title and accurate tool identification (name). Provided an excellent description which clearly, concisely, and accurately described the tool’s features and capabilities.
|
|
Recommended Uses of the Tool for IR |
10 points Provided an excellent description of how this tool can be used to support two or more phases of the Incident Response Process (as defined in NIST SP 800-61r2). Listed and briefly explained 5 or more appropriate uses.
|
|
Notes, Warnings, & Restrictions
Resources |
6 points Provided an excellent "notes, warnings, and restrictions" section with clear, concise, and accurate information to aid the reader in understanding what should or should not be done when using this procedure. 3 points Provided an excellent resources section which described and listed three or more relevant resource documents; section also included complete publication information (reference list entry) for all cited sources.
|
|
Procedure #3 (25%) |
|
|
Title, Tool Identification, Description of the Tool |
6 points Provided an acceptable title and accurate tool identification (name). Provided an excellent description which clearly, concisely, and accurately described the tool’s features and capabilities.
|
|
Recommended Uses of the Tool for IR |
10 points Provided an excellent description of how this tool can be used to support two or more phases of the Incident Response Process (as defined in NIST SP 800-61r2). Listed and briefly explained 5 or more appropriate uses.
|
|
Notes, Warnings, & Restrictions
Resources |
6 points Provided an excellent "notes, warnings, and restrictions" section with clear, concise, and accurate information to aid the reader in understanding what should or should not be done when using this procedure. 3 points Provided an excellent resources section which described and listed three or more relevant resource documents; section also included complete publication information (reference list entry) for all cited sources.
|
