Academic Integrity: tutoring, explanations, and feedback — we don’t complete graded work or submit on a student’s behalf.

1. What are the five (5) threat mitigation techniques recommended by NIST? 2. Wh

ID: 3911670 • Letter: 1

Question

1. What are the five (5) threat mitigation techniques recommended by NIST?

2. What is 'secure' software? If you were in the role of CISO (Chief Information Security Officer) at a technology company, what policies would you put in place to ensure that programmers and developers practiced secure software development?

3. Describe one example of each of the following forms of malware. Compare and contrast these types of malware -- what characteristics are common and different with each type?

1) Worm,

2) Virus,

3) Trojan horse,

4) Bots, and

5) Spyware.

4. Compare and contrast the security features of Cloud storage and Virtual Machine software. If you were the CISO at a medium-sized healthcare provider, which would you recommend the organization use, and why?

5. What is a digital signature and what role does it play in investigating malware attacks?

6. Describe each of the following, give one example of each, and describe a technique for mitigating the attack:

1) Buffer Overflow,

2) Cross-site Scripting, and

3) SQL Injection.

7. Compare and contrast at least 3 security features that support Windows and Linux operating systems.

8. What does the term ‘hardening the operating system’ mean? Give three examples of steps that can be taken and explain how each step will provide value to an organization.

Explanation / Answer

Answer 1:

To enable associations to address these dangers, NIST issued a progression of prescribed controls to better secure and oversee SSH keys, and along these lines better shield basic systems from trade off. Since SSH keys give advantaged access to basic systems, NIST's suggested controls for SSH keys are fundamentally the same as those for special passwords.

1. Record Management to rotate, review and control access to private SSH keys.

2. Access Enforcement to prevent clients from allowing themselves access to basic systems and special SSH keys.

3. Minimum Privilege to limit root access to just circumstances in which it is completely essential.

4. Reviewing and Monitoring to track who or what accessed a specific framework utilizing a SSH key.

5. Hazard Assessment to find and approve SSH-key based trust connections amongst clients and systems.

DEAR PLEASE DO RATE IT IF HELPS ELSE LET ME KNOW YOUR DOUBT.

KINDLY POST SEPARATELY AS WE ARE RESTRICTED TO ANSWER MORE THAN ONE QUESTION FROM MULTIPLE POSTED QUESTIONS.

THANK YOU!!!