Rule register

Government: rules and guidance

The rules in the register that apply in government, by issuing body.

30 rules

Architectural and Transportation Barriers Compliance Board

  1. 36 CFR part 1194 (Revised 508 Standards: appendices A, C and D) · Effective (as of November 14, 2026)

    Information and Communication Technology (ICT) Standards and Guidelines (Section 508 standards)

    The Revised 508 Standards set the accessibility requirements for information and communication technology that federal agencies develop, procure, maintain or use. Public-facing electronic content, and non-public-facing official agency communications in listed categories, must conform to WCAG 2.0 Level A and AA success criteria, and the standards add requirements for hardware, software and support documentation. Agencies have had to comply since January 18, 2018, and existing technology that met the earlier standards and has not been altered on or after that day need not be modified.

    • Architectural and Transportation Barriers Compliance Board
    • Standard

Centers for Medicare & Medicaid Services

  1. 42 CFR 438.242 · Effective (as of November 14, 2026)

    Health information systems (Medicaid managed care)

    States must ensure through their contracts that each Medicaid MCO, PIHP and PAHP keeps a health information system that collects, analyzes, integrates and reports data, including utilization, claims, grievances and appeals, and disenrollments. Plans must verify and screen the data they receive from providers, make it available to the state and to CMS on request, and submit enrollee encounter data in standardized ASC X12N and NCPDP formats. The section also applies the Medicaid API rules to plans: a Patient Access API and a publicly accessible standards-based API from January 1, 2021, and the Provider Access and Prior Authorization APIs for rating periods beginning on or after January 1, 2027.

    • Centers for Medicare & Medicaid Services
    • Final rule
    • Next: compliance date January 1, 2027

Cybersecurity and Infrastructure Security Agency

  1. CISA Binding Operational Directive 19-02 · Superseded (as of November 14, 2026)

    BOD 19-02: Vulnerability Remediation Requirements for Internet-Accessible Systems

    BOD 19-02 required federal agencies to remediate critical vulnerabilities on their internet-accessible systems within 15 calendar days of initial detection and high vulnerabilities within 30 calendar days, based on CISA's Cyber Hygiene scanning reports. Agencies that missed a deadline had to return a completed remediation plan to CISA within three working days of receiving it. CISA issued the directive on April 29, 2019, and revoked it on June 10, 2026, when BOD 26-04 replaced it.

    • Cybersecurity and Infrastructure Security Agency
    • Directive
  2. CISA Binding Operational Directive 22-01 · Superseded (as of November 14, 2026)

    BOD 22-01: Reducing the Significant Risk of Known Exploited Vulnerabilities

    BOD 22-01 created the CISA-managed catalog of known exploited vulnerabilities and required federal agencies to remediate each listed vulnerability on the timeline set in the catalog. Its default timelines were six months for vulnerabilities with a CVE ID assigned before 2021 and two weeks for all others. CISA issued it on November 3, 2021, and revoked it on June 10, 2026, when BOD 26-04 replaced it.

    • Cybersecurity and Infrastructure Security Agency
    • Directive
  3. CISA Binding Operational Directive 23-01 · Effective (as of November 14, 2026)

    BOD 23-01: Improving Asset Visibility and Vulnerability Detection on Federal Networks

    BOD 23-01 requires federal civilian agencies to perform automated asset discovery every 7 days and to start vulnerability enumeration across all discovered assets every 14 days, using privileged credentials where technically feasible. Agencies must load the results into the CDM Agency Dashboard within 72 hours of discovery completion and be able to run on-demand discovery and enumeration within 72 hours of a CISA request. CISA issued the directive on October 3, 2022, and the required actions applied from April 3, 2023.

    • Cybersecurity and Infrastructure Security Agency
    • Directive
  4. CISA Binding Operational Directive 25-01 · Effective (as of November 14, 2026)

    BOD 25-01: Implementing Secure Practices for Cloud Services

    BOD 25-01 requires federal civilian agencies to apply the mandatory policies in CISA's SCuBA secure configuration baselines to their production cloud tenants; Microsoft Office 365 had final baselines when the directive was issued. Agencies had to report in-scope tenants by February 21, 2025, deploy CISA's assessment tools and begin continuous reporting by April 25, 2025, and implement every mandatory policy in effect at issuance by June 20, 2025. New cloud tenants must meet the mandatory baselines and be under continuous monitoring before they receive an authorization to operate.

    • Cybersecurity and Infrastructure Security Agency
    • Directive
  5. CISA Binding Operational Directive 26-02 · Effective (as of November 14, 2026)

    BOD 26-02: Mitigating Risk From End-of-Support Edge Devices

    BOD 26-02 requires federal civilian agencies to find and remove edge devices, such as firewalls, routers, load balancers and wireless access points, that no longer receive vendor support. Agencies must inventory devices on CISA's end-of-support edge device list within three months of issuance, within twelve months decommission listed devices whose support ends by then and all identified end-of-support edge devices within eighteen months, and within twenty-four months run continuous discovery so that devices are removed by the day support ends. CISA issued the directive on February 5, 2026.

    • Cybersecurity and Infrastructure Security Agency
    • Directive
  6. CISA Binding Operational Directive 26-04 · Effective (as of November 14, 2026)

    BOD 26-04: Prioritizing Security Updates Based on Risk

    BOD 26-04 directs federal civilian agencies to remediate vulnerabilities on timelines set by risk: whether the asset is publicly exposed, whether the vulnerability is in CISA's Known Exploited Vulnerabilities (KEV) catalog, whether an adversary can automate the exploit, and whether exploitation gives partial or total control. Agencies must update their vulnerability management policies at once, update their processes within 60 days of issuance, and within 180 days meet the remediation timelines and tag every agency-owned asset that can be reached from outside the agency network. CISA issued the directive on June 10, 2026.

    • Cybersecurity and Infrastructure Security Agency
    • Directive
    • Next: deadline December 7, 2026

Department of Defense

  1. 48 CFR 52.204-21; 48 CFR subpart 4.19 · Effective (as of November 14, 2026)

    Basic Safeguarding of Covered Contractor Information Systems

    FAR 52.204-21 requires contractors to apply fifteen basic safeguarding requirements and procedures to information systems that process, store or transmit Federal contract information. The clause is prescribed by FAR 4.1903 and must be flowed down to subcontractors that may have Federal contract information in their systems. The clause does not relieve contractors of other safeguarding requirements, including those for controlled unclassified information. The current version is dated November 2021.

    • Department of Defense, General Services Administration, National Aeronautics and Space Administration
    • Final rule
  2. 32 CFR part 170 · Effective (as of November 14, 2026)

    Cybersecurity Maturity Model Certification (CMMC) Program (the CMMC program rule)

    This rule establishes the Cybersecurity Maturity Model Certification (CMMC) Program, which verifies that defense contractors and subcontractors have implemented the security requirements needed to protect federal contract information and controlled unclassified information. Program managers and requiring activities select the CMMC status for each procurement, from Level 1 (Self) to Level 3 (DIBCAC), and the rule sets out how contractors reach and keep that status across the period of performance. The rule took effect on December 16, 2024, and Phase 1 of its four-phase rollout began on November 10, 2025.

    • Department of Defense
    • Final rule
  3. 48 CFR 252.204-7012 (DFARS clause; prescribed at DFARS 204.7304(c)) · Effective (as of November 14, 2026)

    DFARS 252.204-7012: Safeguarding Covered Defense Information and Cyber Incident Reporting

    The clause requires defense contractors to provide adequate security on covered contractor information systems, which for systems not operated on the government's behalf means the security requirements of NIST SP 800-171, and to report cyber incidents to the Defense Department within 72 hours of discovery. After an incident, contractors must preserve images of affected systems and relevant monitoring data for at least 90 days from the report, and a cloud service used for covered defense information must meet security requirements equivalent to the FedRAMP Moderate baseline. The current codified clause is dated May 2024 and set December 31, 2017 as the latest date to implement NIST SP 800-171.

    • Department of Defense
    • Final rule
  4. 48 CFR parts 204, 212, 217 and 252 (DFARS Case 2019-D041) · Effective (as of November 14, 2026)

    DFARS: Assessing Contractor Implementation of Cybersecurity Requirements (the CMMC acquisition rule)

    This rule puts the Cybersecurity Maturity Model Certification (CMMC) program into Defense Department contracts. Contracting officers may not award a contract, task order or delivery order to an offeror that does not have a current CMMC status at the level the solicitation requires. The rule took effect on November 10, 2025, which started Phase 1 of the phase-in set out in 32 CFR 170.3.

    • Department of Defense
    • Final rule
    • Next: deadline November 10, 2028

Department of Health and Human Services

  1. 45 CFR part 84, subpart I (45 CFR 84.82 to 84.89) · Effective (as of November 14, 2026)

    Nondiscrimination on the Basis of Disability in Programs or Activities Receiving Federal Financial Assistance: Web, Mobile, and Kiosk Accessibility (HHS section 504 rule)

    Subpart I requires recipients of HHS financial assistance to make the web content and mobile apps they provide, directly or through contractors and licensors, conform to WCAG 2.1 Level A and AA success criteria, and bars disability discrimination in programs or activities provided through kiosks. Under a May 2026 interim final rule, recipients with fifteen or more employees must meet the web and mobile standard beginning May 11, 2027. Recipients with fewer than fifteen employees must meet it beginning May 10, 2028.

    • Department of Health and Human Services
    • Final rule
    • Next: compliance date May 11, 2027

Department of Justice

  1. 28 CFR part 35, subpart H (28 CFR 35.200 to 35.205) · Effective (as of November 14, 2026)

    Nondiscrimination on the Basis of Disability; Accessibility of Web Information and Services of State and Local Government Entities (ADA Title II web and mobile rule)

    Subpart H requires state and local governments to make the web content and mobile apps they provide, directly or through contractors and licensors, conform to WCAG 2.1 Level A and AA success criteria, subject to listed exceptions and the fundamental alteration and undue burden defenses. Under an April 2026 interim final rule, public entities with a total population of 50,000 or more, other than special district governments, must comply beginning April 26, 2027. Smaller public entities and all special district governments must comply beginning April 26, 2028.

    • Department of Justice
    • Final rule
    • Next: compliance date April 26, 2027

National Archives and Records Administration

  1. 32 CFR part 2002 · Effective (as of November 14, 2026)

    Controlled Unclassified Information (CUI)

    32 CFR part 2002 sets up the executive branch's Controlled Unclassified Information Program for designating, safeguarding, disseminating, marking, decontrolling and disposing of unclassified information that law, regulation or government-wide policy requires or permits agencies to protect. Agencies may not apply safeguarding or dissemination controls to unclassified information other than those consistent with the program. For CUI Basic on non-federal information systems, the rule points to NIST SP 800-171 as the security requirements, which reach contractors through their agreements. The rule took effect on November 14, 2016.

    • National Archives and Records Administration
    • Final rule
  2. 36 CFR part 1236 · Effective (as of November 14, 2026)

    Electronic Records Management

    Part 1236 requires agencies to build records management and preservation into the design of electronic information systems, with controls for reliability, authenticity and integrity, and sets added requirements for email and other electronic records. Subparts D and E set the standards agencies must meet when digitizing temporary or permanent records so that they may dispose of the source records. Subpart F sets the metadata required when permanent digital records are transferred to the National Archives. The most recent amendments, on digitizing temporary records, took effect on August 28, 2024.

    • National Archives and Records Administration
    • Final rule
  3. 36 CFR 1222.32 · Effective (as of November 14, 2026)

    How do agencies manage records created or received by contractors? (NARA)

    Agencies must make sure contractors performing agency functions create and keep records of that work, and must state in the contract that the Government owns, and will receive, all records needed to document contractor-operated activities. Electronic records and background data to be delivered must come with enough technical documentation to understand and use them, and contracts that create data for Government use must also call for background data that may have reuse value. All data created for Government use and delivered to, or under the legal control of, the Government are Federal records subject to 44 U.S.C. chapters 21, 29, 31 and 33, FOIA and the Privacy Act.

    • National Archives and Records Administration
    • Final rule

Office of Management and Budget

  1. 2 CFR 200.303 · Effective (as of November 14, 2026)

    Internal controls (Uniform Guidance), including reasonable cybersecurity measures to safeguard information

    Each recipient and subrecipient must establish, document and maintain effective internal control over the Federal award that gives reasonable assurance it is managed in compliance with Federal statutes, regulations and the award's terms. It must evaluate and monitor its compliance and act promptly on noncompliance. Paragraph (e) requires reasonable cybersecurity and other measures to safeguard information, including protected personally identifiable information and information the agency or pass-through entity designates as sensitive. The current text took effect on October 1, 2024, and OMB proposed further changes on May 29, 2026.

    • Office of Management and Budget
    • Final rule
  2. OMB Memorandum M-21-31 · Superseded (as of November 14, 2026)

    M-21-31: Improving the Federal Government's Investigative and Remediation Capabilities Related to Cybersecurity Incidents

    M-21-31 set the logging, log retention and log management requirements that section 8 of Executive Order 14028 called for, built on a four-tier event logging maturity model from EL0 (not effective) to EL3 (advanced). It set minimum log data, a timestamp standard and retention periods for each log category, such as 12 months in active storage and 18 months in cold data storage for identity and credential management logs, and required agencies to give relevant logs to CISA and the FBI on request. OMB issued it on August 27, 2021, and M-26-14 rescinded it on May 22, 2026.

    • Office of Management and Budget
    • Memorandum
  3. OMB Memorandum M-22-09 · Effective (as of November 14, 2026)

    M-22-09: Moving the U.S. Government Toward Zero Trust Cybersecurity Principles

    M-22-09 sets a federal zero trust architecture strategy and requires agencies to meet specific cybersecurity standards and objectives by the end of fiscal year 2024. Its task matrix includes phishing-resistant authentication for agency users, removal of password rules that require special characters and regular rotation, encrypted DNS, authenticated HTTPS for all production HTTP traffic, and complete asset inventories using the CDM program. OMB issued it on January 26, 2022.

    • Office of Management and Budget
    • Memorandum
  4. OMB Memorandum M-24-15 · Effective (as of November 14, 2026)

    M-24-15: Modernizing the Federal Risk and Authorization Management Program (FedRAMP)

    M-24-15 sets the scope of FedRAMP, the requirements for agencies' use of it and the responsibilities of the FedRAMP Board and GSA's program office, as the FedRAMP Authorization Act of 2022 requires OMB to do. Agencies must issue or update agency-wide policy aligned with the memorandum within 180 days of issuance, and within 24 months must make their governance, risk and compliance and system inventory tools able to ingest and produce machine-readable authorization and continuous monitoring artifacts using OSCAL. OMB issued it on July 25, 2024, rescinding the Federal CIO memorandum of December 8, 2011 that created FedRAMP.

    • Office of Management and Budget
    • Memorandum
  5. OMB Memorandum M-25-21 · Effective (as of November 14, 2026)

    M-25-21: Accelerating Federal Use of AI through Innovation, Governance, and Public Trust

    M-25-21 directs agencies to accelerate their use of AI around three priorities, innovation, governance and public trust, and replaces M-24-10. Each agency must retain or designate a Chief AI Officer within 60 days of issuance, and each CFO Act agency must convene an AI governance board within 90 days and develop an AI strategy within 180 days. For high-impact AI, agencies must apply minimum risk management practices, including pre-deployment testing and an AI impact assessment, document them within 365 days, and plan to stop using high-impact AI that is not performing at an appropriate level until it complies. Each agency must also submit to OMB and post compliance plans every two years until 2036 and keep updating their annual AI use case inventories.

    • Office of Management and Budget
    • Memorandum
  6. OMB Memorandum M-25-22 · Effective (as of November 14, 2026)

    M-25-22: Driving Efficient Acquisition of Artificial Intelligence in Government

    M-25-22 sets how agencies buy AI systems and services, and replaces M-24-18. Agencies must update their acquisition procedures within 270 days, standardize how they treat data ownership and intellectual property rights, and use contract terms that address privacy, vendor lock-in, performance monitoring and the handling of agency data. Contracts must permanently prohibit vendors from using non-public agency inputs and outputs to further train publicly or commercially available AI algorithms, absent the agency's explicit consent and consistent with applicable law. The memorandum also states a policy to buy American and maximize the use of AI products and services developed and produced in the United States.

    • Office of Management and Budget
    • Memorandum
  7. OMB Memorandum M-26-04 · Effective (as of November 14, 2026)

    M-26-04: Increasing Public Trust in Artificial Intelligence Through Unbiased AI Principles

    M-26-04 implements the two Unbiased AI Principles of Executive Order 14319, truth-seeking and ideological neutrality, for large language models that agencies procure. Any solicitation or order for a large language model issued after the memorandum must include contract requirements on compliance with the principles, and agencies should modify existing contracts where practicable, at the latest before exercising an option that extends performance. By March 11, 2026, agencies had to update their procurement policies, including a way for users to report outputs that violate the principles.

    • Office of Management and Budget
    • Memorandum
  8. OMB Memorandum M-26-05 · Effective (as of November 14, 2026)

    M-26-05: Adopting a Risk-based Approach to Software and Hardware Security

    M-26-05 rescinds M-22-18 and its companion M-23-16, which required agencies to obtain a self-attestation of secure development practices from software producers before using their software. Agencies must still keep a complete inventory of software and hardware and develop assurance policies and processes that match their risk determinations and mission needs. Agencies may choose to use the government-wide secure software development resources developed under M-22-18, such as the Secure Software Development Attestation Form, and may adopt contract terms requiring a current software bill of materials on request. OMB issued the memorandum on January 23, 2026.

    • Office of Management and Budget
    • Memorandum
  9. OMB Memorandum M-26-14 · Effective (as of November 14, 2026)

    M-26-14: Ensuring Effective and Efficient Agency Logging and Network Visibility to Defend Against Evolving Cyber Threats

    M-26-14 replaces the logging requirements of M-21-31 with a risk-based approach built on two objectives: continuous event monitoring, and threat hunting, investigation, response and forensics. Agencies must submit an Agency Logging Plan within 90 days of the release of CISA's Logging Reference Architecture, then reach Basic, Intermediate and Advanced maturity across the memorandum's maturity model within 120, 180 and 320 days of that release. CISA published the reference architecture on August 20, 2026. As a minimum baseline, retained logs must be actively searchable for six months after creation and retrievable for a year.

    • Office of Management and Budget
    • Memorandum
  10. OMB Memorandum M-26-15 · Effective (as of November 14, 2026)

    M-26-15: Execution of the Migration to Post-Quantum Cryptography

    M-26-15 implements the June 22, 2026 executive order Securing the Nation Against Advanced Cryptographic Attacks and OMB's duty under the Quantum Computing Cybersecurity Preparedness Act to direct agencies' migration to post-quantum cryptography. Agencies must execute a prioritized migration of their cryptographic systems, putting high impact systems, High Value Assets and other highly sensitive systems first, with the objective of mitigating as much quantum risk as feasible by December 31, 2030. Each agency must submit a PQC Migration Plan to OMB and the Office of the National Cyber Director within 120 days of the memorandum, and must support TLS 1.3 or a successor version by January 2, 2030.

    • Office of Management and Budget
    • Memorandum
    • Next: deadline January 2, 2030
  11. OMB Memorandum M-26-18 · Effective (as of November 14, 2026)

    M-26-18: Scaling Use of Login.gov to Deliver a Universal Sign-on for Public Services

    M-26-18 makes Login.gov the universal sign-on for federal public services: agencies must offer it on every in-scope public-facing website with sign-in, or send OMB a notice, personally certified by the agency head, explaining what prevents them. Where a website also verifies identity, agencies must use Login.gov's identity verification unless it does not meet the needs of the service, and they must phase out other identity solutions that are not needed for a specific use case or to spare a large group of existing users. The memorandum is dated August 31, 2026, and its deadlines run from 60 days for an inventory of sign-in websites to two years for Login.gov on all existing in-scope websites.

    • Office of Management and Budget
    • Memorandum
  12. 2 CFR 200.216 · Effective (as of November 14, 2026)

    Prohibition on certain telecommunications and video surveillance equipment or services (Uniform Guidance)

    Recipients and subrecipients may not use loan or grant funds to procure, obtain, or enter, extend or renew a contract for covered telecommunications equipment or services as described in section 889 of Public Law 115-232. Covered items are telecommunications equipment from Huawei or ZTE, video surveillance and telecommunications equipment from Hytera, Hikvision or Dahua for public safety and national security purposes, services from those entities or using that equipment, and equipment or services from entities the Secretary of Defense believes are connected to a covered foreign country's government, including systems that use them as a substantial or essential component. By accepting a loan or grant, the recipient or subrecipient certifies that it will comply.

    • Office of Management and Budget
    • Final rule

United States Congress

  1. 44 U.S.C. 3554 · Effective (as of November 14, 2026)

    Federal Agency Responsibilities (Federal Information Security Modernization Act of 2014)

    Section 3554 makes the head of each agency responsible for information security protections commensurate with risk and for complying with OMB policies, standards issued under 40 U.S.C. 11331, and operational and emergency directives from the Secretary of Homeland Security. Each agency must run an agency-wide information security program with periodic risk assessments, security awareness training, testing of controls as often as risk requires and at least annually, remediation, incident detection and response, and continuity plans. Agencies must notify the designated congressional committees of a major incident within 7 days after there is a reasonable basis to conclude it occurred, and report each year on the adequacy and effectiveness of their information security programs.

    • United States Congress
    • Statute