How to use this industry guide
Use this guide to distinguish education privacy obligations from government-contract cybersecurity obligations. A school SaaS provider, testing vendor, learning-management vendor, university research subcontractor, or grant-supported service provider may encounter different rules depending on whether the work involves student education records, CUI, federal research data, state education agency requirements, or public-sector cloud hosting.
What usually drives cybersecurity obligations in this sector
Education obligations are commonly triggered by student records, education-program data, research data, grant terms, cloud/SaaS services, state education agency procurement rules, and university research contracts. Contractors supporting public schools, state universities, federal education programs, or federally funded research should expect data-use restrictions, access controls, breach-notification duties, and contractual security clauses.
University-affiliated research can add another layer: controlled research data, export-controlled data, CUI, human-subjects data, grant conditions, and agency-specific security requirements. Ed-tech SaaS providers may also face FedRAMP or GovRAMP-style authorization requirements when selling to public-sector customers.
Requirements to review for this sector
Review these areas first:
- FAR 52.204-21 for FCI in federal contract work.
- FERPA-related obligations where education records are handled for schools or institutions.
- Privacy Act obligations where federal education records are maintained for an agency.
- NIST SP 800-171 where education or research data is CUI.
- Federal grant/cooperative agreement cybersecurity conditions.
- Agency-specific requirements for Department of Education, NSF, NIH, DoD, DOE, or other research sponsors.
- State student-data privacy, breach, cloud, and education procurement laws.
- GovRAMP or equivalent cloud authorization where public-sector education customers require it.
Implementation focus areas
Education contractors should document who can access student records, research data, and platform administrative functions. Practical evidence should include access-control roles, data-sharing agreements, subcontractor controls, encryption decisions, audit logs, breach-response procedures, account provisioning/deprovisioning, data deletion/return processes, and separate handling rules for student records, CUI, and research data.
For ed-tech providers, the most important implementation step is often tenant and data segregation. Public schools and universities need confidence that their records are not commingled, over-retained, reused for unauthorized purposes, or exposed through weak administrative access.
This page is an index. The actionable items are the requirements below.
Standards and frameworks commonly adopted
Education
Educational institutions and EdTech contractors handling student, child, and federal research data (FERPA, COPPA).
Adopts: GLBA— Institutions handling student financial data
Mapped requirements and controls
Data-Type / Sector-Specific Safeguards
Requirement
Decontrol CUI When Safeguarding Is No Longer Required in accordance with 32 CFR 2002.18.
Plain-English explanation
CUI status is not permanent. 32 CFR 2002.18 lets the designating agency decontrol information when safeguarding is no longer required, and contractors should not keep treating decontrolled data as CUI. Decontrol is an agency decision — contractors follow it rather than make it.
Implementation examples
View implementation examples
Handling decontrol:
- Follow agency decontrol instructions and remove or update CUI markings accordingly.
- Note the decontrol decision and date in your records.
- Do not unilaterally decontrol CUI you received; confirm with the designating agency.
- Update access controls once data is decontrolled.
Required by
Requirement
Destroy CUI Using Approved Methods in accordance with 32 CFR 2002.14(f); NIST SP 800-88.
Plain-English explanation
CUI must be destroyed using methods that make it unreadable and irrecoverable. 32 CFR 2002.14(f) requires approved destruction, and NIST SP 800-88 provides the media-sanitization guidance the government relies on. Improper disposal is a common and avoidable cause of CUI loss.
Implementation examples
View implementation examples
Approved destruction practices:
- Cross-cut shred or pulp paper CUI to NSA/agency-approved standards.
- Sanitize digital media per NIST SP 800-88 (clear, purge, or destroy as appropriate).
- Use destruction logs or certificates of destruction for accountability.
- Include cloud and backup copies in your destruction process.
Required by
32 CFR 2002.16; CUI LDC Registry
Apply Limited Dissemination Controls and Lawful Government Purpose
DISSEM
Requirement
Apply Limited Dissemination Controls and Lawful Government Purpose in accordance with 32 CFR 2002.16; CUI LDC Registry.
Plain-English explanation
CUI may only be shared for a lawful government purpose, and Limited Dissemination Controls (LDCs) further restrict who may receive it. 32 CFR 2002.16 and the CUI Registry's LDC list govern which controls (e.g., NOFORN, FED ONLY) can be applied and how. Applying the wrong control — or ignoring one — is a disclosure risk.
Implementation examples
View implementation examples
Managing dissemination:
- Confirm a lawful government purpose before sharing CUI internally or externally.
- Apply only LDCs listed in the CUI Registry and only when authorized by the designating agency.
- Restrict distribution lists and shared drives to authorized recipients.
- Document dissemination decisions for CUI Specified categories.
Required by
Requirement
Protect Student Records in accordance with FERPA (20 USC 1232g; 34 CFR 99).
Plain-English explanation
Student education records are protected by FERPA, and when handled under federal contracts they are CUI in the Privacy/education category. 20 USC 1232g and 34 CFR Part 99 limit disclosure of personally identifiable information from education records. EdTech vendors and institutions sharing student data with the government should treat it as restricted.
Implementation examples
View implementation examples
Protecting student records:
- Limit access to education records to those with a legitimate educational interest.
- Obtain consent or use a FERPA exception before disclosing PII from records.
- Contract carefully around the 'school official' exception for vendors.
- Apply access controls, encryption, and retention limits to student data.
Required by
DFARS 252.204-7012(m); proposed FAR CUI rule
Flow Down CUI Safeguarding Requirements to Subcontractors
FLOWDOWN
Requirement
Flow Down CUI Safeguarding Requirements to Subcontractors in accordance with DFARS 252.204-7012(m); proposed FAR CUI rule.
Plain-English explanation
CUI obligations do not stop at the prime — they flow down to subcontractors that will handle CUI. DFARS 252.204-7012(m) requires the clause be included in covered subcontracts, and the proposed FAR CUI rule would extend flowdown government-wide. Primes remain responsible for ensuring subs are covered.
Implementation examples
View implementation examples
Managing flowdown:
- Include the applicable CUI/safeguarding clause in subcontracts that involve CUI.
- Verify subcontractors' safeguarding posture (e.g., SPRS score, SSP) before sharing CUI.
- Track which subs receive CUI and under which categories.
- Require subs to report incidents up the chain.
Required by
EO 13556; 32 CFR Part 2002; NARA CUI Registry
Identify and Categorize CUI Using the CUI Registry
IDENTIFY
Requirement
Identify and Categorize CUI Using the CUI Registry in accordance with EO 13556; 32 CFR Part 2002; NARA CUI Registry.
Plain-English explanation
Before you can protect CUI you have to recognize it. The CUI program replaced dozens of agency-specific markings with one government-wide system, and the NARA CUI Registry is the authoritative list of what qualifies and under which category. Contractors should map where covered information lives and tag it to a Registry category.
Implementation examples
View implementation examples
Practical steps to identify and categorize CUI:
- Inventory systems, shares, and email that may hold government information and trace each to a contract or data flow.
- Match each information type to a NARA CUI Registry category (e.g., Controlled Technical Information, Privacy, Procurement).
- Confirm categorization with the contracting officer or data owner when a marking is ambiguous.
- Re-run the inventory when new contracts, tools, or data sources are added.
Required by
32 CFR 2002.20; CUI Marking Handbook
Apply CUI Markings (Banner, Portion, Category, and Limited Dissemination)
MARK
Requirement
Apply CUI Markings (Banner, Portion, Category, and Limited Dissemination) in accordance with 32 CFR 2002.20; CUI Marking Handbook.
Plain-English explanation
CUI must carry consistent markings so everyone who handles it knows the limits. The ISOO CUI Marking Handbook prescribes banner marks, portion marks, category designators, and limited-dissemination controls. Correct marking is what makes downstream safeguarding and dissemination rules enforceable.
Implementation examples
View implementation examples
Ways to apply CUI markings correctly:
- Add a CUI banner at the top (and bottom) of documents and a designation indicator identifying the source.
- Use category markings (e.g., CUI//SP-CTI) for CUI Specified.
- Apply portion marks where required and add Limited Dissemination Control markings (e.g., NOFORN, FED ONLY) when authorized.
- Configure templates, email footers, and DLP labels so markings are applied by default.
Required by
NIST SP 800-171 Rev 3; 32 CFR 2002.14(g)
Protect CUI on Nonfederal Systems per NIST SP 800-171
NIST171
Requirement
Protect CUI on Nonfederal Systems per NIST SP 800-171 in accordance with NIST SP 800-171 Rev 3; 32 CFR 2002.14(g).
Plain-English explanation
For CUI on nonfederal information systems, NIST SP 800-171 is the control set the government expects. Revision 3 (2024) reorganized the families and tightened several controls; DFARS 252.204-7012 and 32 CFR 2002.14(g) make it contractually and regulatorily binding for many contractors. A System Security Plan and POA&M are the core evidence artifacts.
Implementation examples
View implementation examples
Implementing NIST SP 800-171:
- Maintain a current System Security Plan (SSP) describing how each control is met.
- Track gaps in a Plan of Action & Milestones (POA&M) with owners and dates.
- Implement the access-control, MFA, logging, configuration, and incident-response families.
- Confirm which revision (Rev 2 vs Rev 3) your contract requires before scoping work.
Required by
Requirement
Protect Proprietary Business Information / Trade Secrets in accordance with 18 USC 1905; FOIA Exemption 4.
Plain-English explanation
Proprietary business information and trade secrets shared with or generated for the government are protected from improper disclosure. 18 USC 1905 (Trade Secrets Act) and FOIA Exemption 4 limit government release of confidential commercial information. Contractors should mark and segregate proprietary data.
Implementation examples
View implementation examples
Protecting proprietary information:
- Mark proprietary/trade-secret data with appropriate restrictive legends.
- Segregate it and limit access to a need-to-know basis.
- Assert confidentiality when submitting data the government might disclose.
- Track where proprietary data is shared and stored.
Required by
Requirement
Protect Privacy CUI and Sensitive PII in accordance with Privacy Act (5 USC 552a).
Plain-English explanation
Privacy CUI and sensitive PII require protection under the Privacy Act and related guidance. 5 USC 552a governs federal records about individuals, and contractors operating systems of records inherit those duties. Sensitive PII (e.g., SSNs) warrants stronger controls.
Implementation examples
View implementation examples
Protecting privacy CUI / sensitive PII:
- Identify Privacy Act systems of records and apply the required safeguards.
- Encrypt and access-restrict sensitive PII; minimize collection.
- Follow breach-notification and reporting requirements.
- Honor Privacy Act use limitations and routine-use constraints.
Required by
Requirement
Safeguard CUI at the 32 CFR 2002 Baseline in accordance with 32 CFR 2002.14.
Plain-English explanation
This is the baseline duty to protect CUI at rest, in transit, and in use. 32 CFR 2002.14 sets the floor for all CUI; for CUI on nonfederal systems that floor is implemented through NIST SP 800-171. Treat it as the minimum standard every CUI handler owes regardless of category.
Implementation examples
View implementation examples
Baseline safeguarding measures:
- Limit access to CUI to people with a lawful government purpose and a need to know.
- Encrypt CUI in transit and at rest using FIPS-validated cryptography.
- Control physical access to printed CUI and CUI media.
- Log access and review it; train staff on handling rules.
Required by
Requirement
Apply Category-Specific (CUI Specified) Handling Controls in accordance with 32 CFR Part 2002 (CUI Specified).
Plain-English explanation
Some CUI categories are 'CUI Specified' — a law, regulation, or government-wide policy imposes handling controls beyond the CUI Basic baseline. 32 CFR Part 2002 directs you to the controlling authority for each Specified category. Always check whether a category is Basic or Specified before deciding how to handle it.
Implementation examples
View implementation examples
Handling CUI Specified:
- Identify the category's controlling law/regulation in the CUI Registry.
- Apply the category-specific dissemination and safeguarding rules, which may exceed the baseline.
- Mark Specified CUI with the correct category designator.
- Escalate questions to the contracting officer or the designating agency.
Required by
Requirement
Provide CUI Awareness Training to the Workforce in accordance with 32 CFR 2002.30.
Plain-English explanation
People are the front line of CUI protection, so the program expects workforce awareness training. 32 CFR 2002.30 contemplates training on identifying, marking, handling, and reporting CUI. Document that staff who touch CUI have completed it.
Implementation examples
View implementation examples
Building a CUI training program:
- Deliver role-based training before staff are granted CUI access and at least annually.
- Cover identification, marking, dissemination limits, incident reporting, and destruction.
- Track completion and retain records as evidence.
- Refresh content when CUI policies or contract requirements change.
Required by
GLBA Safeguards Rule (16 CFR 314)
Maintain a GLBA Safeguards-Rule Information Security Program
X-GLBA-ISP
Requirement
A financial institution subject to the FTC Safeguards Rule (16 CFR Part 314) must implement a written information security program with a qualified individual responsible for it, a written risk assessment, access controls and encryption of customer information, multi-factor authentication, secure development, vendor oversight, an incident response plan, and an annual written report to the board or governing body.
Plain-English explanation
GLBA's Safeguards Rule requires a documented, governed security program for customer financial information — not just controls, but named accountability and a yearly report to leadership. The 2021/2023 updates added concrete duties like MFA, encryption, and a written incident-response plan.
Implementation examples
View implementation examples
Examples of meeting this requirement:
- Designate a qualified individual and produce a written, risk-based information security program.
- Implement MFA and encryption for customer information; oversee service providers contractually.
- Deliver the required annual written report to the board or senior governing body.
Required by
International Data Protection
Requirement
Comply With Export Controls for CUI (EAR/ITAR) in accordance with 15 CFR 730-774 (EAR); 22 CFR 120-130 (ITAR).
Plain-English explanation
Much CUI is also export-controlled. The EAR (15 CFR 730-774) and ITAR (22 CFR 120-130) restrict releasing technical data to foreign persons, including 'deemed exports' to foreign nationals inside the U.S. Export and CUI controls overlap but are separate regimes — comply with both.
Implementation examples
View implementation examples
Export-control measures:
- Screen personnel for U.S.-person status where access to controlled technical data is restricted.
- Obtain licenses or use exemptions before exporting or releasing controlled data.
- Apply technology control plans and access controls to ITAR/EAR data.
- Train staff on deemed-export risks in mixed-nationality teams.
Required by
External Notification & Reporting
Requirement
Report Loss or Compromise of CUI in accordance with 32 CFR 2002; agency incident-reporting policy.
Plain-English explanation
Loss or compromise of CUI must be reported, often on tight timelines. 32 CFR Part 2002 and agency/contract incident-reporting policy (and DFARS 7012's 72-hour rule for DoD) govern when and to whom. Build the reporting path before an incident, not during one.
Implementation examples
View implementation examples
Incident-reporting readiness:
- Maintain an incident-response plan with defined roles and reporting timelines.
- Know the reporting channel (e.g., DIBNet for DoD) and required contract notifications.
- Preserve images and affected media for the period the contract requires.
- Run tabletop exercises so the team can meet the deadline.
Required by
Use Find My Requirements to narrow this list
This industry guide shows requirements that commonly arise in this sector. Find My Requirements lets you filter by contract type, agency customer, data categories, and selected jurisdictions to produce a tailored list for your specific situation.
Start Find My Requirements →