D833: Cybersecurity and Information Assurance Capstone

D833 is the final course of WGU's Cybersecurity and Information Assurance degree.

The guidebook describes it as putting your learning to the test by responding to a security scenario, researching and writing a proposal, giving an executive summary and producing a technical report that uses peer feedback.

The task combines persuasion and technical depth for different audiences. Many students underestimate the writing, but each deliverable has a distinct reader, and mixing them is a common reason for revision.

What D833 Covers

Key Concepts Explained

One Scenario, Three Documents

All three deliverables describe the same solution but not in the same way. The proposal persuades, the summary decides, and the report proves. Keep facts identical across them and change emphasis, length and vocabulary.

Evidence for Stakeholders

Stakeholders respond to risk reduced, cost and disruption, not to product features. Quantify where honest data allows, and state assumptions.

Using Peer Feedback

The guidebook says the technical report uses feedback from peers. Record what you changed and why; it shows professional practice.

Typical Assignments and How to Approach Them

Planning Table

Writing for Three Readers

The same solution is described three times, so the writing choices need to differ.

Check that numbers, dates and names match across all three. Inconsistency between documents is easy for an evaluator to spot and hard to explain.

Pre-Submission Checklist

• The proposal compares at least two options before recommending one.
• The executive summary fits on one page and states the decision needed.
• The technical report includes configuration steps, tests and results.
• Figures, names and dates are consistent across all documents.
• Peer feedback is recorded with what you changed.

Ask someone outside the field to read the summary. If they can say what you recommend, it is working.

Worked Example: Framing the Problem

Suppose the scenario describes a clinic whose staff share logins and whose patient records are accessed from personal devices. A weak proposal opens with a product name. A strong one opens with the problem and its consequences: unclear accountability, weak audit trails and exposure of sensitive records.

It then compares two or three options, such as role-based access control with multi-factor authentication versus a device management approach, scoring each on cost, disruption and risk reduced.

The recommendation follows from that comparison, and the executive summary repeats it in three lines. The technical report then documents the chosen build and its tests.

Where Students Get Stuck

• One voice for all readers. Executives do not want configuration steps, and engineers need them.
• Weak justification. Compare options before recommending one.
• Missing testing evidence. A system described but not tested is not convincing.
• Late start on the technical part. Build time is the usual bottleneck.

Study Tips for D833

• Write the executive summary first as a draft, to force a clear recommendation, then revise it last.
• Keep a build log as you configure so the report writes itself.
• Read every deliverable with its audience in mind.
• Ask a peer or mentor to read the summary and tell you the recommendation back.

How We Help with D833

Send the scenario, rubric and any drafts. A tutor can help you plan the three deliverables, give feedback on structure and evidence, or prepare a custom outline to study. For general project advice, see our capstone project help guide.

GradeEssays is independent and not affiliated with Western Governors University. Use our help as a study aid, then build and write your own capstone under WGU's academic integrity policy. We do not take assessments or access portals, and we cannot promise a competency decision. Free revisions; full refund if late.