Govern
Direction, accountability, policy, oversight and supplier risk. Who decides, and how decisions are followed through.
6 categories
How it works
K12 Cyber Forward follows one guided improvement cycle: join, build a Cybersecurity Rubric 2.0 baseline, own the next steps and show the work. Each district moves at its own pace, with support from GLET and Georgia peers.
The journey at a glance
Every district follows the same five-stage path at its own pace, then loops back each school year as practice matures.
The journey at a glance: five stages, repeated as practice matures.
The improvement cycle
The cycle is designed for real district calendars. Work happens in short sessions, owners are named and evidence builds up as a by-product of doing the work.
An authorized district contact requests participation. GLET reviews the district and the contact before preparing any account access, and the requester receives a private receipt link to follow the status. Nothing is provisioned automatically.
This week: agree internally who will be the district's program contact.
Agree on the scope, then rate each of the 22 categories of the Cybersecurity Rubric 2.0. Every category comes with authored guidance: what the control is for, how it looks in a school district, evidence examples, quick wins and crosswalks to NIST CSF 2.0 subcategories and CIS Controls v8.1. Record the method, your confidence and the rationale behind each rating.
This week: invite the people who own the processes being rated, not just IT.
Turn the lowest or least-supported areas into an improvement plan with owners and dates. Connect it to school-year operations such as account rollover and access reviews, tabletop exercises, vendor renewals and policy discussions, so improvement fits the calendar instead of competing with it.
This week: pick three actions you can finish this semester.
Keep redacted supporting evidence next to the work it supports. Evidence is reviewed by people and can expire, so the record stays honest. Choose the review pathway that fits, then return to the baseline as practices improve.
This week: decide what "good evidence" looks like for your top three actions.
The rubric, mapped
The rubric is what districts rate. NIST CSF 2.0 is the alignment layer that keeps the language consistent with the wider field.
The rubric leads; NIST CSF 2.0 is the alignment layer. The Cybersecurity Rubric 2.0 rates 22 categories, grouped under the six NIST CSF 2.0 functions, and describes each category across five maturity levels.
Category names follow NIST CSF 2.0. Orientation graphic, not an assessment result.
The framework underneath
The Cybersecurity Rubric 2.0 organizes its 22 categories under the six functions of the NIST Cybersecurity Framework 2.0. Most districts already do some of this work; the rubric helps describe how consistently.
Direction, accountability, policy, oversight and supplier risk. Who decides, and how decisions are followed through.
6 categories
Knowing your systems, data, dependencies and risks, and improving from what you learn.
3 categories
Accounts and access, awareness and training, data security, platform security and resilient infrastructure.
5 categories
Monitoring and analysis that turn signals into timely, informed escalation.
2 categories
Managing, analyzing, communicating about and containing incidents.
4 categories
Restoring services and communicating during recovery so learning resumes.
2 categories
Review pathways
Rubric ratings describe practice. Review pathways describe who examined the work and how. The two stay separate, so a district can be honest about both.
Your district team establishes its own baseline and records the current practice.
A named facilitator helps the team examine its baseline and work through questions.
A named third-party verifier reviews the stated scope and shared supporting evidence.
A review records what was examined, for a stated scope and period. It does not certify that a control works or predict incidents.
Rubric ratings describe practice; the pathway describes who examined the work. A review records what was examined for a stated scope and period. It is not a certification.
Inside the private portal
Participating districts get a private, role-based workspace. A few of the tools teams use most:
It depends on the scope and who takes part. Plan for a series of short working sessions over several weeks rather than one long meeting. A clear scope and the right people in the room matter more than speed.
Include the technology lead plus people who own the processes being rated: someone from the superintendent's cabinet, finance or business operations, human resources, student information and, where possible, a school-level leader. Each person brings knowledge the rubric asks about.
No. A baseline shows where to start. The program is supportive, not punitive: low ratings point to help and practical next steps, and individual district results are never ranked publicly.
Level 1 is self-assessed by the district team. Level 2 adds a named facilitator who helps the team examine the baseline. Level 3 is independently reviewed by a named third-party verifier who issues a time-bounded review record for a stated scope. Compare the pathways.
No. A Level 3 review records what a verifier examined, for a stated scope and period. It is not a certification that any control works, and it does not predict or prevent incidents.
Ready when your district is
Request participation, or ask the program team how the cycle would fit your district's calendar.