Secure Staging Environment Design and Coding Technique Standards Technical Guide
bahlman2
cmgt400_v7_wk5_secure_staging_env_standards_tech_guide.docxCMGT/400v7
Security Risk Mitigation Plan Template
CMGT/400 v7
Page 2 of 2
Secure Staging Environment Design and Coding Technique Standards Technical Guide ![C:\Users\djshirey\OneDrive - University of Phoenix\F_Drive\Style Guides\UPX Logos\Horizontal format\UOPX_Sig_Hor_Black_Medium.png]()
Template
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.
