The planets of the Solar System can be divided into two major classes, terrestrial and Jovian planets, but each planet has their own interesting characteristics. With the Stellarium planetarium software, you can get a close up view of the planets and see their features for yourself. In this part of the project, use a computer simulation to examine the physical characteristics of planets of the Solar System. Please read through the assignment background information and follow the steps listed in the lab assignment instructions. You will be asked to form a hypothesis, state the lab objective, record your measurements and calculations, and answer each of the lab questions. Click here to download the instruction document for this piece of the project. Follow the instructions contained within and submit your results as this project deliverable. Submit your paper with a title page and in APA format. Here are the Instructions: dont need to click in the link.Module 03 – Physical Characteristics of Planets The planets of the Solar System can be divided into two major classes, terrestrial and Jovian planets, but each planet has their own interesting characteristics. With the Stellarium planetarium software, you can get a close up view of the planets and see their features for yourself.Background Question – Describe three characteristics of a planet that you think you could measure from visual observations.Object: Explain the purpose of this laboratory assignment in your own words. What do you think you will accomplish or learn from this exercise?Hypothesis: Write a simple hypothesis connected to planetary features that you will be able to test using the Stellarium software (for example, Jovian planets have faster rotation period than terrestrial planets)Procedure: Open the Stellarium software. Open the location window (F6) and change the planet to the Sun. This will change our observing location to the center of our Solar System.Open the Sky and Viewing options window (F4). Under the “Sky” tab, uncheck the Atmosphere, Stars, and Dynamic eye adaption. Check “Show planet markers” and “Show planet orbits”.Select the Landscape tab and uncheck “Show ground”.Open the Search window (F3) and enter in Mercury. The view should shift such that the Mercury is in the center of the screen. As long as Mercury is actively select, it will remain in your field of view as you advance time.In the table below, make note of the visible features of Mercury. This can include over color, surface features such as craters or ice caps, presence of an atmosphere and cloud structure, and any visible moons orbiting the planet. You can also advance time and try to observe in the planet has a faster or slow rotation.Repeat your observer with each of the eight planets. You can use the Search window (F3) to shift your view to each planet. We can use the small angle formula to find the physical diameter of a planet. Select one planet and record its angular size in arcseconds and distance from the observer (Distance displayed in units of millions of km). The physical size of an astronomical object is equal to the angular size times the object’s distance divided by 206, 265 ( similar formula can be found in the textbook on page 29). Continue using Stellarium to test your individual hypothesis. If you need further direction, please ask your instructor. |Planet| |Color| |Atmosphere (yes/no)| |Surface Features| |Rotation Speed| |Any Moons| Q1 In your opinion, which planet had the most distinct appearance?Q2: Which group of planets (terrestrial or Jovian) appear to have the most moons?Q3: Which group of planets (terrestrial or Jovian) appear to have the fastest rotation? Q4: Did you have any problem observing the rotation of any planet? If so, why do you think this was the case?Q5: Compare your calculation with the planet radius information in the textbook (Chapter 6 or Appendix E). Is your calculated radius close to the known value? Conclusion: In 1-2 paragraphs, explain if your observations and data support or conflict with your hypothesis and if you have met your assignment objective. Was there any portion of the assignment that was particularly interesting or difficult?

For your independent project, create an instructional presentation. Create a V-G diagram specific to your aircraft at a selected weight and atmospheric condition and explain how the V-G diagram can be utilized to identify specific maneuvering parameters. For inputs on how the V-G diagram is developed, review the discussion in the Flight Theory and Aerodynamics book (Dole, Lewis, Badick, & Johnson, 2017, pp. 229-235) At a minimum cover the following aspects: Positive and negative limiting load factor (i.e., the maximum G allowed for your aircraft) Stall speeds at 1, 2, 3, and so on G up to the maximum positive G (at your selected weight) Ultimate load factor (ULF) Positive ultimate load (i.e., the actual force [lbs]) at the selected weight Maneuvering speed The bank angle associated with the positive limiting load factor For the specific maneuvering speed of your aircraft identified above, explain how to numerically find (provide the specific example and values) the associated turn rate and radius utilizing both of the following methods: Rate and radius formula The turn performance diagram (Figure 2.29 in Aerodynamics for Naval Aviators, Hurt, 1965, p. 179 or Figure 13.14, Dole et al., 2017, p. 239). As in previous assignments, you will need to research a variety of additional information such as required formulas and pertinent aircraft data and/or assume a few parameters for your aircraft. Please make sure to detail those: Required Formulas: Bank angle to G relationship Turn rate and radius Stall speed under elevated G / bank Necessary aircraft information: Limiting load factors (positive and negative) for your example aircraft (from research) Assumed aircraft weight Previous information:  Utilize your previous module work to find 1G stall speed for your selected weight Assume atmospheric conditions Again, the emphasis in this project task is on explaining your methodology as if you attempted to instruct someone unfamiliar with the aerodynamic details and relationships. Therefore, make sure to detail all assumptions, all formulas used, and all steps that were taken. The aircraft is the Cessna 172.

CBR 600 9042 Communicating, Problem Solving, and Leading in Cybersecurity Project 6 Organizational Profile and Access Management Case Information Systems and Identity Management Transcript You are a systems administrator in the IT department of a major metropolitan hospital. Your duties are to ensure the confidentiality, availability, and integrity of patient records, as well as the other files and databases used throughout the hospital. Your work affects several departments, including Human Resources, Finance, Billing, Accounting, and Scheduling. You also apply security controls on passwords for user accounts. Just before clocking out for the day, you notice something strange in the hospital's computer system. Some person, or group, has accessed user accounts and conducted unauthorized activities. Recently, the hospital experienced intrusion into one of its patient's billing accounts. After validating user profiles in Active Directory and matching them with user credentials, you suspect several user's passwords have been compromised to gain access to the hospital's computer network. You schedule an emergency meeting with the director of IT and the hospital board. In light of this security breach, they ask you to examine the security posture of the hospital's information systems infrastructure and implement defense techniques. This must be done quickly, your director says. The hospital board is less knowledgeable about information system security. The board makes it clear that it has a limited cybersecurity budget. However, if you can make a strong case to the board, it is likely that they will increase your budget and implement your recommended tool company­wide. You will share your findings on the hospital's security posture. Your findings will be brought to the director of IT in a technical report. You will also provide a non­technical assessment of the overall identity management system of the hospital and define practices to restrict and permit access to information. You will share this assessment with the hospital board in the form of a narrated slide show presentation. You know that identity management will increase the security of the overall information system's infrastructure for the hospital. You also know that, with a good identity management system, the security and productivity benefits will outweigh costs incurred. This is the argument you must make to those stakeholders. Daily life requires access to a lot of information, and information systems help us access that information. Desktop computers, laptops, and mobile devices keep us connected to the information we need through information systems. However, our easy access to communication and information also creates security and privacy risks. Laws, regulations, policies, and guidelines protect information and information owners, and the role of cybersecurity is to protect the confidentiality, integrity, and availability of information. This project focuses on the processes and practices of identity management as a component of a layered security defense system that governs users' access, authorization, and authentication. You will work as part of a team to produce reports on the processes and practices of identity management at a health-care facility and deliver the key findings to the board in a presentation. Your team has four deliverables for this project: Executive summary. This will be a single, double-spaced page, and in the same template document as the technical report, located immediately following the cover sheet and before the text of the report. Technical report. A nine- to 10-page double-spaced Word document with structure and citations in APA format, using the provided template. This will include your organizational profile, threat analysis, and strategies for mitigation. The page count does not include the cover sheet, executive summary, figures, diagrams, tables, or the references section. Lab report. This will summarize the lab activity, including how your team came to the results, using screenshots to show your work. Narrated presentation. This presentation will not exceed 12 slides, excluding the cover and references slides. It will be narrated by a single voice. There are nine steps that will lead you through this project. Begin by watching the video above, which introduces the fictional scenario that serves as the framework for this project. Then continue to Step 1: Get to Know Your Team. Step 2: Learn About Organizational Behavior In the previous step, your team got to know each other and agreed on a communications plan. In this step, take some time to read about teamwork and leadership. Think about the challenges members must overcome to work together effectively and how they can do this to achieve a positive outcome for an organization. Bad experiences have their own lessons for individuals and groups. In your own group, you will experience some practical challenges such as schedules, resistance to group work, and perhaps failure of some members to contribute fully. Consider this an incubator of sorts in which you may encounter experiences similar to the case you are studying. As you grapple with logistical, technical, and other team issues, you are gaining experience with normal team challenges. So, relax and consider this a useful journey! In the next step, you will choose your case study, review the deliverables, and create a project plan. Step 3: Choose a Case and Complete the Project Plan Now that you have a better understanding of various aspects of organizational behavior from the readings in the previous step, select as your case to research a hospital or health-care organization that has suffered a cybersecurity breach. Consider an organization you are familiar with or one for which you can find sufficient information about cybersecurity policies and practices. To maintain confidentiality, you do not need to mention the name of the organization. You can start with this list of 2020 breaches. Most of these breaches are logged in the US Department of Health and Human Services (HHS) Breach Portal where you can also search. Verify that you can locate sufficient reputable information on your chosen case to complete the project; start with this custom CBR 600 research guide from the UMGC library. CYBERSECURITY FUNDAMENTALS The principles of confidentiality, integrity, and availability (CIA) are fundamental concepts in this field. Look at this cybersecurity field overview to consider different roles that may apply as you review your case. Finally, review the article Muddling Through Cybersecurity: Insights From the US Health-Care Industry After you have chosen a case, you need to establish how you will divide the work. Use your team space to share ideas and drafts of each member's contribution. Complete all portions of the project plan and submit it to your team space by the end of Week 8. Each team will have three weeks to complete your deliverables: Complete and submit the team communication and project plans by the end of Week 8. Conduct research to capture the organization's infrastructure and processes and the threats to personal health information (PHI) and to determine a strategy to mitigate the threats you anticipate. This research will go into the technical report (nine to ten pages excluding cover sheet, references, and any appendices), also called a white paper, in accordance with the directions in Steps 4 and 5. After the paper is written, you will create a one-page executive summary of the paper. It will be part of the technical report document, between the cover sheet and the text of the report. Complete the lab activity to crack passwords and create a summary lab report. This should be done by Week 9. Develop a high-level narrated slide presentation for the organization's board of directors. This asynchronous presentation must be no longer than 12 slides, excluding the references slide and cover slide. It is due at the end of Week 10. Finalize all deliverables and assign one group member to upload them into the team project assignment folder. All deliverables are due no later than the end of Week 10. Step 4: Create an Organizational Profile for Your Case Now you will research your chosen case to determine how the organization's IT department operates, how it is structured, and how PHI is moved around the organization. You may not find this exact information for your health-care organization that suffered a breach. In that case, use the material on organizational structure to draft a plausible layout for an organization like your case. Next, review Overview of Systems & Networks for the basics about an information system infrastructure. It is important to an organization that its workflow processes, such as how they move patient information to the business units that need to process and manage that information, are unimpeded and secure. All organizations employ hardware and software within their information systems and connect them in a network. It is critical to understand these components, termed system architecture, and how the components are connected so that IT professionals can ensure that there is sufficient security in place to protect sensitive information. Your profile of the organization's system architecture should include a high-level description of information systems' hardware and software components and their interactions. Take time to read the following resources on the roles and responsibilities within an IT department and some basic information about operation systems in general. Information systems hardware Information systems software As you write your organizational profile, consult scholarly resources as well as newspapers, websites, and IT blogs for information on how health-care organizations are generally set up. Revisit guidelines on conducting research or the CBR600 research guide, if needed. Use the information you find to create a plausible description and supporting diagram of the IT infrastructure for your organization, which will become part of your technical report. Include the following in your profile: Description and diagram of your organization and its structure and critical missions Describe the organization and structure. The structure will include the different business units and their functions. You will build an organizational chart and a description of the nodes to provide this information. Demonstrate the basic elements and describe how they are connected to each other via a network. Diagram what you describe above. This is just visual aid to help executives understand how security concepts can be applied to the existing system, not a detailed plan for network engineers. See a few example diagrams to get a sense of what yours might look like. An explanation of information security needs to protect mission-critical systems. Choose one or more mission-critical systems of the health-care organization. Define the information protection needs for the organization's mission-critical protected health information (PHI). Describe how this information is (or should be) stored so that it is accessible by those who need it (e.g., doctors, nurses, patients, insurance claims billing systems). You should also refer to the facts of the breach you are covering, especially if medical records were compromised. In the next step, you will consider threats to the organization's information security and how to mitigate them. Step 5: Develop Analysis of Threats to the Organization's Information Systems Infrastructure Now that you have defined your organization's information system infrastructure, you will learn about and demonstrate your understanding of the potential threats to those systems and the types of measures that could mitigate those threats. These pieces will finish your technical report. First, you will learn about different types of identity access management solutions and how they protect against unauthorized access. The National Initiative for Cybersecurity Education (NICE) framework refers to this work as conducting a vulnerability assessment. To conduct a vulnerability assessment, a trained specialist would assess threats and vulnerabilities; determine deviations from acceptable configurations, enterprise, or local policy; assess the level of risk; and develop and/or recommend appropriate mitigation countermeasures in operational and nonoperational situations. Your team will not carry out all of these tasks, but you will assess the potential threats and vulnerabilities and the risk to your organization, and you will develop a mitigation strategy that includes an identity management system and any other safeguards you deem necessary. To complete this section of your report, start by reviewing the following resources: Information System Architecture Web Security Issues Insider Threats Intrusion Motives/Hacker Psychology Take what you learned about potential threats to assess the threat(s) to the organization's information systems infrastructure that you wrote about in Step 4. Provide a brief summary of the kinds of threats that an organization could face, addressing insider threats, intrusions, hacker psychology, and other weakness that might provide opportunities to breach the system. Relate these threats to the vulnerabilities in the CIA triad. Next you will provide a mitigation strategy that will include a description of an identity management system, which will include authentication, authorization, and access control. Remember that you are already expecting that your organization will need to update its identity management processes and policies, and you are laying the groundwork for the investment this will require. As an example, think about the requirements for doctors' use of laptop devices when they visit their patients at a hospital and their need to connect to the hospital PHI data. Review the following resources: Authorization Access control Passwords Authentication Multifactor authentication Now, explain how your organization should restrict access to protect billing and PHI. Explain the organization's processes and workflows to safeguard PHI, including the use of passwords, password management, and password protection. Define types of authorization and authentication and the use of passwords, password management, and password protection in an identity management system. Describe common factor authentication mechanisms to include multifactor authentication. Finally, review the mission and organization structure of your organization as well as roles within it, and recommend accesses, restrictions, and conditions for each role. What will happen if the CIO and the leaders do nothing and decide to accept the risks? Could the CIO transfer, mitigate, or eliminate the risks? What are the projected costs to address the risks? You may not know exactly what your organization's current strategy is, but you can project a plausible scenario based on the CIO's acceptance or rejection of your proposal for an access control system. Write an Executive Summary Now that you have finished writing your technical report, it is time to write an executive summary. The goal of an executive summary is to capture the main highlights of a document in a concise, readable format that can bring key decision makers up to speed. Your executive summary should be double-spaced and no more than a page in length. When you submit it at the end of the project, it will go in the same template document as the technical report, immediately following the cover sheet and before the text of the report. After you have drafted your executive summary, your team will test the strength of passwords with two password cracking tools. Step 7: Test Password-Cracking Tools and Write a Lab Report You have successfully examined the threats to a health-care organization's information systems infrastructure and ways in which the organization can increase its security by an active management system. Now, you must begin your practical research into password-cracking software; authentication and hashing functions will get you started. Then, do some quick independent research on password cracking as it applies to your organization, then complete the lab activity Password Cracking With Cain & Abel and Ophcrack using the lab instructions under Complete This Lab. In this lab activity, you will test two password-cracking tools, since not all password-cracking tools will perform with the same speed, precision, and results. Your report will assess these characteristics as you test the organization's systems for password strength and complexity and complete the validation testing. You will compare the results you obtain using the two tools. COMPLETE THIS LAB RESOURCES Accessing the Virtual Lab Environment: Navigating UMGC Virtual Labs and Lab Setup Self-Help Guide (Workspace): Getting Started and Troubleshooting Link to the Virtual Lab Environment: https://vdi.umgc.edu/ LAB INSTRUCTIONS Password Cracking With Cain & Abel and Ophcrack GETTING HELP To obtain lab assistance, fill out the support request form. Make sure you fill out the fields on the form as shown below: Case Type: UMGC Virtual Labs Support Customer Type: Student (Note: faculty should choose Staff/Faculty) SubType: ELM-Cyber (CST/DFC/CBR/CYB) SubType Detail: Pick the category that best fits the issue you are experiencing Email: The email that you currently use for classroom communications In the form's description box, provide information about the issue. Include details such as steps taken, system responses, and add screenshots or supporting documents. LAB REPORT INSTRUCTIONS Explain to the director of IT and the members of the board that the health-care organization's antivirus software will detect password-cracking tools as malware. Also explain how this impacts the effectiveness of testing security controls like password strength. Through persuasive arguments in your lab report and presentation, help the organization's leaders understand the risks and benefits of using password-cracking tools. If any of the tools take longer than two to three minutes to guess a password, record the estimated length of time the tool anticipates taking to guess it. TOPICS TO ADDRESS IN THE LAB REPORT Compare and contrast the results from the two methods used to crack the user accounts. Describe the tools' speed at cracking the passwords and draw conclusions that are relevant to the organization's cybersecurity posture. Explain how the tools respond to password complexity. Explain how strong passwords are constructed and your team's recommendations for the organization. Explain the four types of character sets used for strong passwords, how many you should use, the general rules for password length, and recommendations for how often passwords should be changed. Discuss the benefit of penetration testing. Explain what that would entail in the organization and what the team could learn from the testing. Discuss the pros and cons of using the same usernames and passwords on multiple systems. Discuss any ethical or legal considerations for how you would use password cracking tools. When you have completed your lab report, complete with screenshots to demonstrate what you did, you will work on the presentation for the board of directors. Step 8: Prepare a Narrated Presentation Now that you have completed your technical report and lab report, you are ready to develop a narrated presentation for the members of your organization's board as well as the CIO and other managers. Your technical report will provide an analysis of the infrastructure and the threats, based on the incident that first brought the organization's security issues to your team's attention. You will use your team's finding from both reports as the basis for this presentation. The board will decide what actions are taken and how much money will be allocated for cybersecurity. Therefore, your slide deck must capture the salient points of your research, the results of the lab tests of the password-cracking tools, and the team's proposals to tighten information security practices. Consider the suggestions in the table below to focus your efforts for this presentation. TOPICS TO ADDRESS IN THE NARRATED PRESENTATION Keep the primary goals of your presentation in mind as you build your presentation to the board: Be credible, be clear, and provide reasoned, actionable recommendations. Present your technical findings succinctly for a non-technical audience. Avoid acronyms, slang, or jargon; opt for clear language and clear explanations. Provide a high-level summary of the infrastructure, the vulnerabilities that may have enabled the breach, and recommended actions. Explain what happened, the impact on the organization, and your proposed actions with rationales and estimated costs. You are limited to 12 slides, excluding the cover slide and references. You will choose your best narrator to narrate the presentation for wider distribution. The format should be professional and free from typos or grammatical errors. This is the board's impression of your team's performance! Step 9: Submit Your Work Your team project will require three files: a text document that contains the executive summary and the technical report, a lab report, and a narrated presentation. One team member will submit a copy to the team assignment folder by the end of Week 10. Each member of the team will receive the same grade, as long as all members provide a substantial contribution to the project. Make sure your submission includes all the pieces of the deliverable: Technical report. A nine- to 10-page double-spaced Word document with citations in APA format. The page count does not include the cover sheet, executive summary, figures, diagrams, tables, or the references section. The technical report includes your organizational profile, threat analysis, and mitigation strategy. The executive summary will be a single double-spaced page in the same document located immediately following the cover sheet and before the text of the report. Lab report. This will summarize the lab activity, including how your team came to the results, using screenshots to show your work. The length of this report will not exceed 10 pages to include the screenshots. Narrated presentation. This presentation will not exceed 12 slides, excluding the cover and references slides. It will be narrated by a single voice. Share a copy to the Project 6 discussion folder, and take time to review other teams' work and provide feedback.