+1443 776-2705 panelessays@gmail.com

CMGT/400 – Secure Staging Environment Design and Coding Technique Standards Technical Guide

Assignment Content

  1. A Software Engineer designs, develop, tests, and evaluates the software and the systems that allow computers to execute their applications.

    Take on the role of Software Engineer for the organization: Sony Pictures.

    Use the technical guide template to create a 3- to 4-page Secure Staging Environment Design and Coding Technique Standards Technical Guide for the organization you chose.

    Research and include the following:

    • Design a secure staging environment for your organization
    • Diagram your staging environment
    • Include descriptions for each object in your environment
    • Create a secure coding technique/quality and testing standard for your organization covering the following secure coding techniques:
    • Proper error handling
    • Proper input validation
    • Normalization
    • Stored procedures
    • Code signing
    • Encryption
    • Obfuscation/camouflage
    • Code reuse/dead code
    • Server-side vs. client-side execution and validation
    • Memory management
    • Use of third-party libraries and ADKs
    • Data exposure
    • Code quality and testing
    • Automation
    • Static code analyzers
    • Dynamic analysis (e.g. fuzzing)
    • Stress testing
    • Sandboxing
    • Model verification

Hi Class – As a commitment to continuous improvement of student learning the University applies a formal assessment process.  The CMGT 400 week five individual assignment The Secure Staging Environment Design and Coding Technique Standards Technical Guide has been identified as a tool to assist in the University's Programmatic Assessment Project. The Secure Staging Environment Design and Coding Technique Standards Technical Guide assignment is a signature/benchmark assignment for assessing student learning using an automated, embedded rubric with dimensions to assess the student's assignment against predefined criteria that match the programmatic objectives.  Assignments are assessed versus defined programmatic student learning objectives (PSLOs) with assessment of the assignment dimension falling into one of four categories: does not meet, approaches, meets, and exceeds. Take a look at the week five individual The Secure Staging Environment Design and Coding Technique Standards Technical Guide assignment early. Look at the gradebook to view the automated grading rubric.  Make sure to read all the individual assignment instructions with this requirement in mind. Let me know if you have any questions. 

Ellen 

,

CMGT/400v7

Security Risk Mitigation Plan Template

CMGT/400 v7

Page 2 of 2

Secure Staging Environment Design and Coding Technique Standards Technical Guide C:UsersdjshireyOneDrive - University of PhoenixF_DriveStyle GuidesUPX LogosHorizontal formatUOPX_Sig_Hor_Black_Medium.pngTemplate

A Software Engineer designs, develop, tests, and evaluates the software and the systems that allow computers to execute their applications.

Take on the role of Software Engineer for the organization you selected in Week 1, and create a Secure Staging Environment Design and Coding Technique Standards Technical Guide using this template for the organization.

[Organization Name]

Diagram of Staging Environment

[Add or attach diagram. Include descriptions for each object in your environment.]

Secure coding Technique/Quality and Testing Standard

Proper Error Handling

[Response]

Proper Input Validation

[Response]

Normalization

[Response]

Stored Procedures

[Response]

Code Signing

[Response]

Encryption

[Response]

Obfuscation/Camouflage

[Response]

Code Reuse/Dead Code

[Response]

Server-side vs. Client-side Execution and Validation

[Response]

Memory Management

[Response]

Use of Third-Party Libraries and ADK’s

[Response]

Data Exposure

[Response]

Code Quality and Testing

[Response should include automation, static doe analyzers, dynamic analysis such as fuzzing, stress testing, sandboxing, model verification]

Copyright© 2018 by University of Phoenix. All rights reserved.

Copyright© 2018 by University of Phoenix. All rights reserved.