completed Practices for Secure Software Report

Instructions

Deliver this completed Practices for Secure Software Report documenting your process for writing secure communications and refactoring code that complies with software security testing protocols.

Respond to the steps outlined below and replace the bracketed text with your findings in your own words. If you choose to include images or supporting materials, be sure to insert them throughout.

Developer

[insert name here]

1. Algorithm Cipher

Determine an appropriate encryption algorithm cipher to deploy given the security vulnerabilities, justifying your reasoning. Be sure to address the following:

• Provide a brief, high-level overview of the encryption algorithm cipher.
• Discuss the hash functions and bit levels of the cipher.
• Explain the use of random numbers, symmetric vs non-symmetric keys, and so on.
• Describe the history and current state of encryption algorithms.

[Include your findings here.]

2. Certificate Generation

Generate appropriate self-signed certificates using the Java Keytool, which is used through the command line.

• To demonstrate that the keys were effectively generated, export your certificates (CER file) and submit a screenshot of the CER file below.

[Insert screenshot(s) here.]

3. Deploy Cipher

Refactor the code and use security libraries to deploy and implement the encryption algorithm cipher to the software application. Verify this additional functionality with a checksum.

• Insert a screenshot below of the checksum verification. The screenshot must show your name and a unique data string that has been created.

[Insert screenshot(s) here.]

4. Secure Communications

Refactor the code to convert HTTP to the HTTPS protocol. Compile and run the refactored code to verify secure communication by typing https://localhost:8443/hash in a new browser window to demonstrate that the secure communication works successfully.

• Insert a screenshot below of the web browser that shows a secure webpage.

[Insert screenshot(s) here.]

5. Secondary Testing

Complete a secondary static testing of the refactored code using the dependency check tool to ensure code complies with software security enhancements. You only need to focus on the code you have added as part of the refactoring. Complete the dependency check and review the output to ensure you did not introduce additional security vulnerabilities.

• Include the following below:
  • A screenshot of the refactored code executed without errors
  • A screenshot of the dependency check report

[Insert screenshots here.]

6. Functional Testing

Identify syntactical, logical, and security vulnerabilities for the software application by manually reviewing code.

• Complete this functional testing and include a screenshot below of the refactored code executed without errors.

[Insert screenshot(s) here.]

7. Summary

Discuss how the code has been refactored and how it complies with security testing protocols. Be sure to address the following:

• Refer to the Vulnerability Assessment Process Flow Diagram and highlight the areas of security that you addressed by refactoring the code.
• Discuss your process for adding layers of security to the software application and the value that security adds to the company’s overall wellbeing.
• Point out best practices for maintaining the current security of the software application to your customer.

When it comes to creating, releasing, and maintaining functional software, most organizations have a well-oiled machine in place.

However, when it comes to securing that software, not so much. Many development teams still perceive security as interference—something that throws up hurdles and forces them to do rework, keeping them from getting cool new features to market.

But insecure software puts businesses at increasing risk. Cool new features aren’t going to protect you or your customers if your product offers exploitable vulnerabilities to hackers. Instead, your team needs to integrate security into the entire software development life cycle (SDLC) so that it enables, rather than inhibits, the delivery of high-quality, highly secure products to the market.

What is the secure SDLC and why should I care?

A software development life cycle (SDLC) is a framework for the process of building an application from inception to decommission. Over the years, multiple SDLC models have emerged—from waterfall and iterative to, more recently, agile and CI/CD, which increase the speed and frequency of deployment.

In general, SDLCs include the following phases:

• Planning and requirements
• Architecture and design
• Test planning
• Coding
• Testing and results
• Release and maintenance

In the past, organizations usually performed security-related activities only as part of testing—at the end of the SDLC. As a result of this late-in-the-game technique, they wouldn’t find bugs, flaws, and other vulnerabilities until they were far more expensive and time-consuming to fix. Worse yet, they wouldn’t find any security vulnerabilities at all.

The Systems Sciences Institute at IBM reported that it cost six times more to fix a bug found during implementation than one identified during design. Furthermore, according to IBM, the cost to fix bugs found during the testing phase could be 15 times more than the cost of fixing those found during design.

Having great experience of working on various projects, academic writing tasks, essays, dissertations, proposals, presentations, spreadsheets, and reports. We have great research, communication, and problem-solving skills that distinguish us from others. We are responsible, committed, and dedicated to meeting the deadline by submitting high-quality work. We use SPSS, Eviews, and Stata that is all data analysis software for research purposes. We follow Harvard, MLA & APA referencing styles along with Endnote according to your requirements. We also check the plagiarism of our work on Turnitin, Grammarly, copy space, language space tool, and write check before submission that we can share with you for the originality of our work. Hopefully, we get this opportunity to work with you as we are sure it will be a good working experience.

Rest assured we will provide you “SUPREME QUALITY WORK” within your “GIVEN DEADLINE” with “PERFECT GRAMMAR” and “ZERO PLAGIARISM”. We have over 22,000 “EXCELLENT REVIEWS” which are a guarantee for our best Quality. Please see our profile and portfolio to assess our quality services. We usually produce over 50 pages of work every day with 100% accuracy.

Open chat and send us a message so we can finalize this deal within your budget.