D833 Cybersecurity and Information Assurance Capstone is recorded under banner number ITAS 4200 and is worth 4 competency units. It asks you to respond to an information security scenario by researching and creating a proposal that applies best practices, compliance guidance and frameworks from across the whole program. D833 and ITAS 4200 are one requirement. Its difficulty is not technical; it is that nothing tells you which of the last twelve courses to use.
A capstone tests selection, not recall
Every earlier course handed you a bounded topic. The capstone hands you a situation and expects you to decide what is relevant. That is the actual skill being assessed, and it explains why strong students sometimes struggle here: they try to demonstrate everything they learned, producing a proposal that covers twelve domains at two paragraphs each and recommends nothing clearly.
The discipline that fixes it is deciding early what the scenario's central problem is and writing one sentence stating it. Everything in the proposal then either serves that sentence or comes out. If the scenario describes an organization that has grown quickly with no access governance, that is the spine; cryptography and forensics may still appear, but as supporting material rather than as chapters proving you took those courses.
Research is named explicitly in the course description, which means the proposal must be grounded in published sources rather than in your own accumulated opinion. At capstone level the expectation is that recommendations trace to frameworks, guidance or research, and that you engage with those sources rather than listing them.
The proposal format matters too. This is a document written to persuade someone in the scenario organization to act, which means it needs a problem statement, an argued recommendation, an implementation path, a cost position and a way of knowing whether it worked. A capstone that reads as an academic survey has chosen the wrong genre.
The record shows Competent or Not Competent, since WGU issues no letter grades and holds no ordinary grade point average, leaving 4 competency units as the only size figure attached to a flat-rate six month term. Capstones are frequently the course a student underestimates at the end of a term, so plan it as the largest single piece of writing in the degree.
Turning a large capstone rubric into a plan
Capstone rubrics are typically the longest you will meet, and that is the main risk. WGU requires a score of 2 in each aspect for a task to pass and judges each aspect independently, so a proposal with excellent analysis and a missing implementation timeline comes back for the timeline alone.
Budget deliberately. Take a rubric with twelve scored aspects and a target near 4,000 words. Reserve 250 words for the introduction and problem statement, and 200 for the conclusion, leaving 3,550 across twelve aspects, or roughly 296 each. Weight by demand: four aspects requiring analysis and justification take 420 each, which is 1,680; the eight remaining aspects, covering description, method, implementation detail, cost, timeline and evaluation, take 234 each, which is 1,872. Together that is 3,552.
Build the aspect list into a checklist document before writing a word, and tick items as they are genuinely answered rather than as they are mentioned. On a twelve aspect rubric the difference between mentioned and answered is where most capstone returns live.
Draft in the order that makes argumentative sense, then reorder to match the rubric before submitting. Writing the recommendation before the implementation plan, for example, prevents the common failure where an implementation section describes something the recommendation never quite committed to.
Shape for a capstone security proposal
D833 deliverables are proposals responding to a scenario. These proportions fit that document.
| Section | Content | Share |
|---|---|---|
| Problem statement | The organization, the central security problem in one paragraph, and why it matters now. | 10 percent |
| Current state analysis | What exists today, assessed against the frameworks the organization should be meeting. | 17 percent |
| Research foundation | What published guidance and research say about problems of this shape, engaged with rather than listed. | 14 percent |
| Proposed solution | The recommendation, argued, with alternatives considered and rejected for stated reasons. | 21 percent |
| Implementation plan | Phases, owners, dependencies, timeline and resources, at a level someone could act on. | 17 percent |
| Compliance and risk | Obligations addressed, residual risk accepted and who accepts it. | 12 percent |
| Evaluation | How success is measured, when it is measured, and what would count as failure. | 9 percent |
Research standards at capstone level
The capstone raises the sourcing bar because research is part of the requirement. Frameworks and control guidance belong to the publishing body, cited by revision. Empirical claims belong to peer-reviewed research or industry data with a method and a year. Regulatory obligations belong to the regulation or its official guidance. Vendor material is acceptable for product capability and nothing else.
Engagement is what separates capstone research from an annotated list. Where two sources recommend different approaches, say so and say which fits this organization. Where guidance assumes an organization larger than the one in your scenario, note the mismatch and adapt deliberately. Those moves are the visible evidence that you read your sources rather than harvested them.
Keep the scenario in the foreground. A capstone that could be submitted for any organization has failed the central selection task, and the fastest way to prevent that is to make sure every major section refers to specific facts from the scenario by name.
Watch the age of your sources. Capstones are long documents assembled over weeks, and it is easy to accumulate references from different eras. Give dates, prefer current revisions, and note where practice has changed if you cite something older for historical context.
Cite in whatever style your task sets out and reference inline rather than in a closing pile. Reference list errors are one of the most common single causes of a capstone return and one of the easiest to prevent.
What returns a capstone, and what closes it
Competent capstones have a clear central problem, a recommendation that could be acted on, research genuinely engaged with, an implementation plan with owners and dates, and an evaluation section that names what failure would look like.
Returns cluster in four shapes. The proposal surveys many domains and recommends nothing decisively. An aspect is mentioned in passing rather than answered with its own section. The implementation plan has phases but no owners or dependencies. Or the evaluation section describes hopes rather than measures.
Length management is its own skill in a document this size. Capstones drift long because every section feels important while you are writing it, and the sections written first tend to be the most generous. Before the final pass, check each section against the word budget you set, and cut from wherever you exceeded rather than adding to wherever you fell short. A capstone that is uniformly proportioned reads as planned; one that spends a third of its length on background reads as a student who ran out of energy before the recommendation.
The most efficient final check is mechanical. Print the rubric aspects, then go through your document marking the exact paragraph that answers each one. Any aspect you cannot point to precisely is the one that will come back, and finding it yourself costs an hour rather than a revision cycle.
Performance assessment work at WGU can be revised and resubmitted without a grade penalty, which matters more here than anywhere else: a complete capstone submitted with three weeks of term remaining has room for a revision cycle, while a perfect one submitted in the final week does not. Where any part of your program uses an objective assessment, those exams are proctored and our boundary is absolute: we prepare and review, we take no part during any assessment, and we never ask for or handle portal credentials.
Capstone sprawling across every domain?
Send the D833 rubric and scenario. We find the central problem, map twelve aspects to sections and give each a word target.
Eight mistakes that return capstones
- Demonstrating everything. Selection is the skill being assessed. Choose the central problem and serve it.
- Mentioning instead of answering. Every aspect needs a locatable section, not a sentence somewhere in a paragraph.
- Implementation without owners. Phases with no named responsibility cannot be evaluated as workable.
- Research listed, not engaged. Say where sources disagree and which fits this organization.
- Generic proposal. If it could be submitted for another organization unchanged, the scenario was not used.
- Evaluation as aspiration. Name measures, timing and what failure would look like.
- Reference list drift. Check in-text citations against the list. This alone causes a large share of returns.
- Submitting in the final week. Revision is free but it needs time to exist. Build in a cycle.
Three questions students ask about D833
Can I base the capstone on my own workplace?
How long should the proposal be?
Should I start the capstone before finishing other courses?
Where D833 sits in WGU's programs
The July 2026 catalog places this code in 1 current WGU program. Open a program page for the complete standard path and term positions. The live Degree Plan remains authoritative after transfer credit, substitutions, and mentor planning.
The assessments, one by one
The public catalog does not publish this course's PA/OA identity or task count. WGU Tutors publishes at most one PA manual per course and only from a WGU-controlled public rubric. Until that source exists, PA help begins from the student's real Course of Study and OA support remains preparation only.