D490 Cybersecurity Graduate Capstone carries banner number ITAS 6460 and is worth 4 competency units. It integrates the skills from every domain of the graduate program into a single project addressing a significant real-world cybersecurity problem. D490 and ITAS 6460 are one requirement. The graduate distinction from an undergraduate capstone is the word significant: you choose the problem, and choosing a trivial one caps the grade before you write anything.
Problem selection is the first graded decision
A graduate capstone begins with a choice, and that choice determines how much room the rest of the project has. A problem that is too narrow leaves nothing to analyse: implementing a single control is a task, not a project. A problem that is too broad cannot be addressed within the scope: securing an entire enterprise is a career, not a capstone. The workable middle is a problem with a defined boundary, real stakeholders, competing considerations and a decision that could genuinely go more than one way.
Significance has to be argued rather than asserted. Why does this problem matter, to whom, and what happens if it is not addressed? A graduate reader expects that argument in the opening pages, supported by evidence rather than by the observation that security is important.
Integration across domains is the other requirement, and it works best when it is natural rather than performed. A well chosen problem will legitimately require identity thinking, architecture thinking, governance thinking and operations thinking, because real problems do not respect course boundaries. If you find yourself forcing a domain in to satisfy a checklist, the problem was probably too narrow.
The methodology section is where graduate capstones distinguish themselves. How did you gather information, what did you compare, on what criteria did you decide, and what are the limitations of that approach? A project that reaches conclusions with no stated method is asking to be taken on trust, which graduate marking does not do.
Outcomes are logged as Competent or Not Competent, with no letter grades and no ordinary grade point average behind them, while the 4 competency units simply size the course inside a flat-priced six month term. Plan it as the largest deliverable in the program, with time reserved for at least one revision cycle.
Planning a graduate capstone from the aspect list
Graduate capstone rubrics are long and their aspects are broad, which changes how you plan. WGU requires a score of 2 in each aspect for a task to pass and judges each aspect alone, so the risk is not that any aspect is hard but that one gets a fraction of the attention it needed.
Budget with care. Take a rubric with fourteen scored aspects and a target near 5,000 words. Reserve 300 words for the problem statement and significance argument, and 250 for the conclusion, leaving 4,450 across fourteen aspects, or roughly 318 each. Weight by demand: five aspects requiring original analysis take 450 each, which is 2,250; the nine remaining aspects, covering method, background, implementation, evaluation and limitations, take 244 each, which is 2,196. Together that is 4,446.
Write the problem statement first and then test it against the aspect list. If several aspects have no natural place in a project addressing that problem, the problem is wrong and changing it now costs a day rather than three weeks.
Keep a running decision log while you work. Graduate capstones require you to explain why you chose one approach over another, and reconstructing that reasoning weeks later produces vague justifications. A two line note at each decision point turns the methodology section into transcription.
Shape for a graduate capstone project
D490 deliverables are integrated project reports. These proportions fit that document.
| Section | Content | Share |
|---|---|---|
| Problem and significance | The problem, its boundary, the stakeholders and the argued case that it matters. | 12 percent |
| Background and literature | What is already known about problems of this kind, engaged with critically. | 15 percent |
| Methodology | How you gathered information, what you compared and the criteria you decided on. | 14 percent |
| Analysis | The original work: assessment, modelling, comparison or design applied to the problem. | 22 percent |
| Solution and integration | The recommendation, showing where each program domain contributes to it. | 18 percent |
| Implementation and evaluation | How it would be delivered, measured, and what would signal failure. | 13 percent |
| Limitations | What your method could not establish and what further work would resolve it. | 6 percent |
Graduate research standards
The literature section is not a summary, it is a positioning exercise: here is what is known, here is where it disagrees, here is the gap my project addresses. Peer-reviewed research, standards body publications and agency guidance carry the weight. Industry reports are usable when their method and population are stated. Vendor material supports capability claims only.
Critical engagement is expected throughout. Noting that a widely cited study used a sample unlike your scenario organization, or that guidance predates a significant technology change, is exactly the kind of remark that distinguishes graduate work from advanced undergraduate work.
Where your project uses any real organization or real data, handle it carefully. Anonymise anything sensitive, obtain whatever permission your institution and employer require, and never include material an organization would consider confidential. Say in the document what you anonymised and why. This is both an ethical requirement and a mark of professional judgement.
Limitations deserve a genuine section rather than a paragraph of modesty. Every method has boundaries: a document review cannot see actual practice, a single interview cannot represent an organization, a design cannot prove it would work until built. Naming those boundaries strengthens rather than weakens the work, and their absence is conspicuous.
Use the citation style your task names and cite at the point of claim. In a five thousand word document assembled over weeks, that reconciliation always finds something.
What closes a graduate capstone
Competent capstones choose a problem with room in it, argue significance with evidence, state a method, do original analytical work, integrate domains naturally, and name their own limitations. They read as a project rather than as an extended essay.
Returns follow four shapes. The problem is too narrow, so several aspects have nothing to attach to. Literature is summarised with no positioning. Analysis is descriptive where the aspect asked for original work. Or limitations are omitted, which at graduate level reads as a lack of self-awareness rather than as confidence.
Voice consistency is worth a pass of its own on a document written over many weeks. Long projects accumulate registers: an enthusiastic early section, a terse middle written under pressure, a conclusion written at speed. Reading the whole thing aloud in one sitting catches shifts that silent reading misses, and it also surfaces the paragraphs where you were writing to fill space rather than to say something. Those paragraphs are almost always the ones an evaluator marks as thin.
One structural check is worth an hour: for each rubric aspect, write the page number where it is answered. If two aspects share a page, one of them is probably underdeveloped; if any aspect has no page, you have found the return before the evaluator did.
Performance assessment work at WGU can be revised and resubmitted without a grade penalty, and on a document this size that is the whole strategy. Submit a complete draft with weeks of term remaining rather than a polished one at the end. Where your program includes objective assessments, those exams are proctored and our boundary does not move: we prepare and review only, we take no part during any assessment, and we never ask for or handle portal credentials.
Capstone problem too small or too large?
Send the D490 rubric and your project idea. We test the problem against the aspect list, then plan every section with word targets.
Eight mistakes that return graduate capstones
- Choosing a task, not a problem. If the answer is obvious once stated, there is nothing for the analysis aspects to score.
- Asserting significance. Argue it with evidence: who is affected, at what cost, and what happens without action.
- Literature summarised, not positioned. Show where sources disagree and where your project sits among them.
- No stated method. Conclusions without a method ask to be taken on trust, which graduate marking declines.
- Forced integration. A well chosen problem pulls in domains naturally. Forcing them signals the problem was too narrow.
- Descriptive where original work was asked for. Analysis means doing something with the material, not reporting it.
- No limitations section. Every method has boundaries. Naming them is expected at this level.
- Reference drift over a long document. Reconcile the list against in-text citations before submitting, every time.
Three questions students ask about D490
How do I know if my problem is significant enough?
Can I use my employer as the subject?
How does this differ from the undergraduate capstone?
Where D490 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.