Case Study #3: Technology & Product Review for Application Lifecycle Management Tools
As a Nofsinger consultant, you have been tasked with researching and recommending an Application Lifecycle Management (ALM) tool. Your deliverable for this task will be used to help obtain buy-in from the company’s program managersfor increased security investments.
An Application Lifecycle Management tool (product) is used to help manage and protect digital assets which are part of or contribute to the management of software applications (especially source code and design documents) throughout theSoftware & Systems Development Life Cycle (SDLC). The digital assets for each software application must be protected from initiation of a development or acquisition project through to disposal of equipment at the end of its useful lifespan.
Multiple Sifers-Grayson managershave responsibility for making sure that Sifers-Grayson products are developed and delivered on-time and in compliance with the contractual requirements for functionality (“quality”). For the current set of customers this means that Sifers-Grayson must implement security focused configuration management (see NIST SP 800-128). Configuration management is a first-line defense against attacks intended to compromise the security and integrity of software applications. This business process is part of a larger, more complex process known as application lifecycle management.
During initial interviews, the engineering managers and program managers provided the following information to your team.
1. Software and Systems Development are the lifeblood of the client company, Sifers-Grayson. From robots to drones to industrial control systems for advanced manufacturing, every product or system sold by the company depends upon software. Some system functions depend upon tiny control programs that capture data from a sensor or command an actuator to move. Other system functions depend upon sophisticated software algorithms to receive and analyze data to make sense out of the surrounding environment.
2. Sifers-Grayson’s engineers are responsible for writing and testing this software. But, they’ve never had to worry about cybersecurity … especially not internal security over software development activities in their own facilities.
3. The engineers feel ownership over their files and folders of source code.
4. There are occasional pranks between engineers working in the labs but software is “sacred” and “off limits.”
5. The engineers believe that “No one would dare mess with a file containing source code for an operational system or a system that has moved into the integration and test phase of the software lifecycle.”
The Nofsinger Engagement Leader (your boss), has provided the following advance notice information as part of your background briefing for this task.
1. Within the next 60 days, a Nofsinger Red Team will conduct penetration tests for the enterprise.
2. The Red Teamtest plan includes attacks designed to demonstrate to the engineers and managers (through penetration testing)that there is a need to protect digital assets, especially software designs, source code, and related artifacts from both insider and external threats.
1. Review the weeklyreadings.
2. Using Google or another search engine, identify anApplication Life Cycle Management product which could meet the needs of Sifers-Grayson.Then, research your chosen product using the vendor’s website and product information brochures.
3. Find three or more additional sources which provide reviews for (a) your chosen product or (b) information about Application Life Cycle Management.
Write a 3 page summary of your research. At a minimum, your summary must include the following:
1. An introduction or overview for the security technology category (Application Lifecycle Management)
2. A review of the features, capabilities, and deficiencies for your selected vendor and product
3. Discussion of how the selected product could be used by Sifers-Graysonto support its cybersecurity objectives by reducing risk, increasing resistance to threats/attacks, decreasing vulnerabilities, etc.
4. A closing section in which you restate your recommendation for a product (include the three most important benefits).
As you write your review, make sure that you address security issues using standard cybersecurity terminology (e.g. protection, detection, prevention, “governance,” confidentiality, integrity, availability, nonrepudiation, assurance, etc.). See the ISACA glossary https://www.isaca.org/pages/glossary.aspx if you need a refresher on acceptable terms and definitions.
Use standard APA formatting for the MS Word document that you submit to your assignment folder. Formatting requirements and examples are found under Course Resources > APA Resources.
Submit For Grading
Submit your case study in MS Word format (.docx or .doc file) using the Case Study #3 Assignment in your assignment folder. (Attach the file.)
1. There is no penalty for writing more than 3 pages but, clarity and conciseness are valued. If your essay is shorter than 3 pages, you may not have sufficient content to meet the assignment requirements (see the rubric).
2. You are expected to write grammatically correct English in every assignment that you submit for grading. Do not turn in any work without (a) using spell check, (b) using grammar check, (c) verifying that your punctuation is correct and (d) reviewing your work for correct word usage and correctly structured sentences and paragraphs.
3. You are expected to credit your sources using in-text citations and reference list entries. Both your citations and your reference list entries must comply with APA 6th edition Style requirements. Failure to credit your sources will result in penalties as provided for under the university’s Academic Integrity policy.