The System Design Document (SDD) describes the high-level system design and the low-level detailed design specifications from which a system is built. As part of the security development team, this document provides the information necessary for designing and implementing a system.
Create a system design document making sure to:
Don't use plagiarized sources. Get Your Custom Essay on
Computer Security
Just from $13/Page
Describe the design goals and considerations.
Provide a high-level overview of the system architecture.
Describe the data design associated with the system.
Describe the human-machine interface and operational scenarios.
Design a drawing appropriate for implementation. The high-level system design should be further decomposed into low-level detailed design specifications for each system component, including hardware, internal communications, software, system integrity controls, and external interfaces.
Refer to the “System Design Document,” provided within the required readings as an example. Note: Only the criteria listed above is required within the System Design Document; additional sections are not required.
CYB- 690 Security Architecture Scoring Guide
Performance Level Ratings
|
Meets Expectations
|
Performance consistently met expectations in all essential areas of the assignment criteria, at times possibly exceeding expectations, and the quality of work overall was very good. The most critical goals were met.
|
|
Near Expectations
|
Performance did not consistently meet expectations. Performance failed to meet expectations in one or more essential areas of the assignment criteria, one or more of the most critical goals were not met.
|
|
Below Expectations
|
Performance was consistently below expectations in most essential areas of the assignment criteria, reasonable progress toward critical goals was not made. Significant improvement is needed in one or more important areas.
|
|
Criteria
|
Below Expectations
|
Near Expectations
|
Meets Expectations
|
Earned
|
|
The student accurately creates an overall security architecture structure diagram with comprehensive descriptions of the architecture components making sure to:
|
|
Identify all types of data and sensitive data the organization will store.
|
|
|
|
|
|
|
0 pts – 2 pts
|
|
|
|
|
|
|
3 pts – 4 pts
|
|
|
|
|
|
|
5 pts
|
|
Define where that information is stored.
|
0 pts – 2 pts
3 pts – 4 pts
5 pts
|
Record of all hardware and software devices in the network.
|
0 pts – 2 pts
3 pts – 4 pts
5 pts
|
Describe how the security controls are positioned and how they relate to the overall systems architecture.
|
0 pts – 2 pts
3 pts – 4 pts
5 pts
|
Define security attacks, mechanisms, and services, and the relationships between these categories.
|
|
|
0 pts – 6 pts
|
|
|
7 pts – 9 pts
|
|
|
10 pts
|
|
Specify when and where to apply security controls.
|
0 pts – 2 pts
3 pts – 4 pts
5 pts
|
Present in-depth security control specifications.
|
0 pts – 6 pts
7 pts – 9 pts
10 pts
|
Address restricting access, layering security, employing authentication, encrypting storage, automating security, and IT infrastructure.
|
0 pts – 2 pts
3 pts – 4 pts
5 pts
|
Include the full scope of policy, procedural and technical responsibilities.
|
0 pts – 6 pts
7 pts – 9 pts
10 pts
|
Prose is largely free of mechanical errors. The writer uses a variety of effective sentence structures, figures of speech, and industry terminology.
|
0 pts – 2 pts
3 pts – 4 pts
5 pts
|
TOTAL
|
/65
|
|
Instructor Feedback
|
© 2019. Grand Canyon University. All Rights Reserved.
