High School IntermediateModule I17Final Capstone Module

I17 Intermediate Capstone and Portfolio

Prepare for Intermediate practice tests and create portfolio-ready fictional defensive artifacts that demonstrate technical understanding, evidence-based judgment, clear communication, risk reasoning, validation, privacy, and reflection.

Module Snapshot

8

Lessons

1

Module Test

6

Capstone Steps

10

Portfolio Outcomes

Main Question

How Do You Prove Intermediate Defensive Readiness?

Readiness is more than remembering definitions. Students must connect technical evidence to scope, case boundaries, ownership, risk, recommendations, communication, validation, reflection, and a professional artifact another person can review.

Safety Boundary

Fully Fictional Portfolio Evidence Only

Do not copy, lightly edit, upload, or expose real credentials, employee records, school records, company systems, private logs, messages, incidents, suppliers, cloud resources, source code, reports, diagrams, or confidential organizational information.

Capstone Workflow

Six Steps from Review to Final Presentation

1

Review and select evidence

Choose fictional Intermediate work that demonstrates real learning across analysis, decision-making, documentation, communication, validation, and safe defensive practice.

2

Define audience and purpose

State the fictional reader, decision need, scope, privacy boundary, level of detail, artifact type, quality standard, and success criteria.

3

Build the artifact

Organize fictional evidence, timelines, diagrams, findings, risk, recommendations, ownership, communications, validation, limitations, and reflection.

4

Check technical accuracy

Verify fictional identifiers, timestamps, source health, case boundaries, impact language, confidence, terminology, calculations, and traceability.

5

Refine communication and design

Improve fictional structure, readability, diagrams, headings, summaries, audience fit, decision usefulness, accessibility, and portfolio presentation.

6

Validate, reflect, and present

Complete fictional peer review, privacy review, final validation, reflection, readiness assessment, improvement plan, and portfolio-safe presentation.

Learning Objectives

What You Will Be Able to Do

Objective 1

Review the complete Intermediate curriculum and identify strong skills, developing skills, evidence gaps, and final study priorities.

Objective 2

Build a polished fictional defender portfolio artifact that demonstrates scope, evidence handling, analysis, decisions, communication, validation, and reflection.

Objective 3

Write an accurate fictional incident report with traceable evidence, impact limits, ownership, recovery, closure criteria, and residual risk.

Objective 4

Create clear fictional security diagrams that communicate architecture, trust boundaries, data flows, evidence sources, controls, risks, and owners.

Objective 5

Convert fictional technical evidence into proportionate risk recommendations with options, rationale, implementation, validation, and success measures.

Objective 6

Complete a fictional Intermediate capstone and final-readiness package suitable for practice tests, reflection, presentation, and a privacy-safe student portfolio.

Professional Standard

Six Standards for a Strong Intermediate Portfolio

Evidence before certainty

Every fictional statement should distinguish observation, conclusion, alternate explanation, missing evidence, confidence, potential impact, confirmed impact, and limitation.

Audience before detail

The same fictional facts should be explained differently to analysts, service owners, leadership, users, suppliers, teachers, and portfolio reviewers.

Ownership before action

Every fictional recommendation should identify the correct owner, authority, priority, deadline, dependency, rollback, validation, and residual risk.

Validation before closure

A fictional ticket, document, diagram, or change is not complete until the intended access, configuration, service, communication, and risk outcomes are verified.

Privacy before presentation

Every portfolio artifact must use invented systems, identities, evidence, dates, organizations, incidents, messages, suppliers, and outcomes.

Reflection before completion

Strong capstone work explains what was learned, what remains difficult, what changed after review, and what the student will improve next.

Module Lessons

Eight Lessons from Review to Capstone

1

I17.1

Intermediate Knowledge Review

Focus

Review the full Intermediate track through networking, Linux, Windows, logs, tools, IAM, email, web, secure coding, vulnerability management, incident response, forensics, cloud, risk, SOC work, and defensive labs.

Portfolio Lab

Build a fictional readiness map that separates strong skills, developing skills, evidence gaps, review priorities, practice goals, and next actions.

Open I17.1
2

I17.2

Building a Defender Portfolio Artifact

Focus

Turn fictional defensive work into a polished artifact that demonstrates scope, evidence handling, judgment, ownership, communication, validation, privacy, and reflection.

Portfolio Lab

Create a fictional portfolio artifact with a project brief, evidence register, analysis, decisions, visual support, final report, lessons learned, and portfolio-safety statement.

Open I17.2
3

I17.3

Writing an Incident Report

Focus

Write a fictional incident report that separates observations, conclusions, alternate explanations, impact, decisions, actions, validation, limitations, and residual risk.

Portfolio Lab

Produce a fictional incident report with document control, executive summary, scope, timeline, findings, communications, recovery, closure criteria, and appendices.

Open I17.3
4

I17.4

Creating a Security Diagram

Focus

Create clear fictional security diagrams showing systems, identities, trust boundaries, data flows, controls, evidence sources, owners, risk points, and defensive decisions.

Portfolio Lab

Build a fictional architecture or incident-flow diagram with a legend, boundaries, labels, evidence references, assumptions, limitations, and reviewer notes.

Open I17.4
5

I17.5

Creating a Risk Recommendation

Focus

Translate fictional technical evidence into a proportionate risk recommendation with likelihood, impact, control state, business need, options, owners, deadlines, validation, and residual risk.

Portfolio Lab

Write a fictional risk recommendation package with evidence, scoring rationale, response options, decision criteria, implementation plan, and success measures.

Open I17.5
6

I17.6

Explaining Technical Evidence Clearly

Focus

Explain fictional technical evidence to analysts, service owners, leadership, users, suppliers, teachers, and portfolio reviewers without changing the underlying facts.

Portfolio Lab

Create multiple fictional audience summaries from one evidence set and compare detail, tone, terminology, action requests, limitations, and next-update needs.

Open I17.6
7

I17.7

Intermediate Final Readiness Review

Focus

Evaluate complete Intermediate readiness through knowledge, applied analysis, case boundaries, documentation, communication, portfolio quality, ethics, privacy, and safe defensive judgment.

Portfolio Lab

Complete a fictional final-readiness dashboard with mastery evidence, weak-area review, test strategy, portfolio checklist, study plan, and improvement commitments.

Open I17.7
8

I17.8

Intermediate Capstone Lab

Focus

Integrate fictional evidence from multiple defensive domains into one complete, decision-ready, portfolio-safe capstone while preserving scope, ownership, case boundaries, service continuity, and uncertainty.

Portfolio Lab

Produce a fictional capstone package with charter, evidence register, timeline, diagrams, findings, risk recommendation, incident report, communications, validation, metrics, reflection, and final presentation.

Open I17.8

Fictional Evidence Preview

One Capstone Evidence Set, Several Professional Artifacts

1

A fictional audit source reports delayed events while a compensating source remains healthy.

2

A fictional supplier role retains more cloud access than current business need supports.

3

A fictional suspicious message causes one click but no confirmed credential entry.

4

A fictional web role reaches a restricted page while no modification is recorded.

5

A fictional control change is completed, but effective-state validation remains open.

6

Students must decide which records belong together, which artifacts best communicate the work, and what can be claimed confidently.

Capstone Goal

Show the Complete Defensive Reasoning Chain

A strong fictional artifact shows what question was asked, which evidence was reviewed, how sources were validated, what conclusions were supported, who owned the decision, what action occurred, and how the outcome was verified.

It also explains uncertainty, alternatives, privacy, communication choices, design decisions, reflection, and the next improvement.

Portfolio Outcomes

Ten Artifacts You Can Complete

1

Intermediate knowledge and readiness map

2

Defender portfolio artifact

3

Professional fictional incident report

4

Security architecture or evidence-flow diagram

5

Risk recommendation and decision brief

6

Technical analyst summary

7

Leadership and service-owner summary

8

Final readiness and study plan

9

Intermediate capstone case package

10

Portfolio reflection and safety statement

Module Test

I17 Intermediate Capstone and Portfolio Module Test

Complete 25 questions covering comprehensive Intermediate readiness, portfolio artifacts, evidence explanation, incident reports, security diagrams, risk recommendations, audience communication, validation, and defensive capstone judgment.

Open Module Test

Module Navigation

Begin the Final Intermediate Module