Insights

Rule register

Regulations, guidance and directives that set obligations for technology, security and data at banks, health systems and public agencies. Every status and date links to the official source it was checked against.

79 rules

Financial Services

Board of Governors of the Federal Reserve System

  1. Interagency Guidance on Third-Party Relationships: Risk Management, 88 FR 37920 (Docket No. OP-1752; Docket ID OCC-2021-0011) · Effective (as of November 14, 2026)

    Interagency Guidance on Third-Party Relationships: Risk Management

    The 2023 guidance sets out the Federal Reserve, FDIC and OCC view of sound risk management for every stage in the life cycle of a banking organization's third-party relationships. It says that sound third-party risk management takes into account the level of risk, complexity and size of the banking organization and the nature of the relationship. The guidance was final as of June 6, 2023, and replaced each agency's earlier general guidance on the topic. A proposal published on September 15, 2026 would replace it, with comments due by December 16, 2026.

    • Board of Governors of the Federal Reserve System, Federal Deposit Insurance Corporation, Office of the Comptroller of the Currency
    • Guidance
    • Next: comments close December 16, 2026
  2. Federal Reserve SR letter 26-2; OCC Bulletin 2026-13 · Effective (as of November 14, 2026)

    Revised Guidance on Model Risk Management

    The revised guidance, issued on April 17, 2026, sets out principles for model development and use, model validation and monitoring, governance and controls, and vendor and other third-party models. It takes a risk-based approach tailored to each banking organization's model risk profile and the size and complexity of its operations. It is expected to matter most to banking organizations with over $30 billion in total assets, and it leaves generative AI and agentic AI models out of scope.

    • Board of Governors of the Federal Reserve System, Office of the Comptroller of the Currency, Federal Deposit Insurance Corporation
    • Guidance

Commodity Futures Trading Commission

  1. 17 CFR 1.31 · Effective (as of November 14, 2026)

    Regulatory records; retention and production (CFTC Regulation 1.31)

    Regulation 1.31 sets how long, and in what form, anyone required to keep records by the Commodity Exchange Act or CFTC regulations must retain and produce them. Swap records are kept until the transaction ends and for at least five years after, oral communications for at least one year, and other regulatory records for at least five years from creation; electronic records stay readily accessible for the whole period. A records entity keeping electronic records must have systems and controls that ensure their authenticity and reliability, keep them available during a disruption, and maintain an up-to-date inventory of the systems that hold them. Records are open to inspection by the CFTC and the Department of Justice and must be produced promptly, in the form and medium a CFTC representative requests.

    • Commodity Futures Trading Commission
    • Final rule

Consumer Financial Protection Bureau

  1. 12 CFR part 1033 · Enjoined (as of November 14, 2026)

    Personal Financial Data Rights

    The rule requires data providers to make covered data about consumer financial products and services available, on request, to consumers and to authorized third parties in an electronic form, through consumer and developer interfaces, and bars fees for that access. Third parties must meet authorization, use and retention limits to receive the data. On October 29, 2025 a federal court in Kentucky enjoined the Bureau from enforcing the rule until it completes its reconsideration, which began with an advance notice published on August 22, 2025.

    • Consumer Financial Protection Bureau
    • Final rule
  2. 12 CFR part 1016 (Regulation P) · Effective (as of November 14, 2026)

    Privacy of Consumer Financial Information (Regulation P)

    Regulation P requires a financial institution to give customers a clear and conspicuous notice of its privacy policies and practices, and to repeat it at least once in any 12 consecutive months while the customer relationship lasts. It sets the conditions under which the institution may disclose nonpublic personal information about consumers to nonaffiliated third parties and gives consumers a way to opt out of most such disclosures. Since September 17, 2018, an institution need not send the annual notice if it shares such information with nonaffiliated third parties only under the regulation's exceptions and has not changed the disclosure policies and practices described in its most recent notice.

    • Consumer Financial Protection Bureau
    • Final rule
  3. 12 CFR 1005.11 (Regulation E) · Effective (as of November 14, 2026)

    Procedures for Resolving Errors (Regulation E, Electronic Fund Transfers)

    Regulation E's error resolution section governs how a financial institution handles a consumer's notice of error about an electronic fund transfer, such as an unauthorized or incorrect transfer, received within 60 days after it sent the periodic statement on which the error first appeared. The institution must investigate and decide within 10 business days, or may take up to 45 days if it provisionally credits the account within 10 business days; the limits extend to 20 business days for transfers within 30 days after an account's first deposit, and to 90 days for those transfers, point-of-sale debit card transactions and transfers not initiated within a state. It must report the results within three business days after finishing the investigation and correct an error within one business day after finding it.

    • Consumer Financial Protection Bureau
    • Final rule

Federal Deposit Insurance Corporation

  1. 12 CFR part 328, subpart A · Effective (as of November 14, 2026)

    FDIC Official Signs and Advertisement of Membership

    Subpart A requires insured depository institutions to display the FDIC official sign where deposits are received on their premises and sets sign rules for ATMs and like devices (12 CFR 328.4) and for digital deposit-taking channels (12 CFR 328.5). The 2024 amendments extended the sign requirements to digital and mobile channels and clarified the rules on misrepresenting deposit insurance coverage. After several delays, the FDIC amended the ATM and digital channel rules in January 2026 to give institutions more flexibility, with compliance required by April 1, 2027.

    • Federal Deposit Insurance Corporation
    • Final rule
    • Next: compliance date April 1, 2027

Federal Trade Commission

  1. 16 CFR part 313 · Effective (as of November 14, 2026)

    Privacy of Consumer Financial Information (FTC Privacy Rule)

    The FTC Privacy Rule requires covered motor vehicle dealers to give customers notices describing their privacy policies and practices, sets the conditions for disclosing nonpublic personal information about consumers to nonaffiliated third parties, and lets consumers opt out of most such disclosures. After the Dodd-Frank Act moved most Gramm-Leach-Bliley Act privacy rulemaking authority to the CFPB, the FTC kept rulemaking authority only for these dealers; most other financial institutions follow the CFPB's Regulation P. The 2021 amendments, effective January 10, 2022, limited the rule's scope to these dealers and updated the annual privacy notice requirement, including an exception for dealers that meet certain conditions.

    • Federal Trade Commission
    • Final rule
  2. 16 CFR part 314 · Effective (as of November 14, 2026)

    Standards for Safeguarding Customer Information (FTC Safeguards Rule)

    The Safeguards Rule requires financial institutions under the FTC's jurisdiction to develop, implement and maintain a written information security program to protect customer information. The 2021 amendments set specific elements for the program, including a Qualified Individual to oversee it, written risk assessments, access controls, encryption, multi-factor authentication and periodic reports to the board or governing body. Since May 13, 2024, an institution must notify the FTC as soon as possible, and no later than 30 days after discovery, of a notification event involving the information of at least 500 consumers.

    • Federal Trade Commission
    • Final rule

Financial Crimes Enforcement Network

  1. 31 CFR parts 1010, 1020 to 1030 (proposed; RIN 1506-AB72) · Proposed (as of November 14, 2026)

    Anti-Money Laundering and Countering the Financing of Terrorism Programs (2026 proposed rule)

    FinCEN proposes to reform the requirements for financial institutions' AML/CFT programs so that programs are effective and produce better outcomes for institutions, law enforcement and national security agencies. It would also give FinCEN a larger role in AML/CFT supervision and enforcement, in coordination with the Federal banking regulators, and make the program rules for different types of institutions clearer and more consistent. Comments closed on June 9, 2026, and FinCEN proposes that a final rule take effect 12 months after it is issued.

    • Financial Crimes Enforcement Network
    • Proposed rule
  2. 31 CFR 1032.210 · Final (as of November 14, 2026)

    Anti-money laundering/countering the financing of terrorism programs for investment advisers (FinCEN IA AML Rule)

    Section 1032.210 requires each covered investment adviser to develop and implement a written, risk-based AML/CFT program reasonably designed to prevent the adviser from being used for money laundering, terrorist financing or other illicit finance. The program must be approved in writing by the board, or by persons with similar functions, and be available for inspection by FinCEN or the SEC. At a minimum it needs internal policies, procedures and controls, independent testing, a designated person responsible for the program, ongoing training, and risk-based ongoing customer due diligence. A January 2026 FinCEN rule moved the date by which an adviser must have the program from January 1, 2026 to January 1, 2028.

    • Financial Crimes Enforcement Network
    • Final rule
    • Next: effective January 1, 2028
  3. 31 CFR 1010.230 · Effective (as of November 14, 2026)

    Beneficial Ownership Requirements for Legal Entity Customers (Customer Due Diligence Rule)

    Covered financial institutions must maintain written procedures, as part of their anti-money laundering program, reasonably designed to identify and verify the beneficial owners of legal entity customers when a new account is opened. A beneficial owner is each individual who owns, directly or indirectly, 25 percent or more of the equity interests of the customer, and a single individual with significant responsibility to control, manage or direct it. Covered financial institutions had to comply by May 11, 2018. Since February 13, 2026, a FinCEN order has excused them from repeating this at each new account opening for an existing customer, subject to conditions.

    • Financial Crimes Enforcement Network
    • Final rule
  4. 31 CFR 1010.430 · Effective (as of November 14, 2026)

    Nature of Records and Retention Period (Bank Secrecy Act Recordkeeping)

    Records that FinCEN's Bank Secrecy Act regulations require a financial institution to keep must be retained for five years and filed or stored so that they are accessible within a reasonable time. Where a check, draft, monetary instrument, investment security or similar instrument must be kept, the institution must keep a copy of both front and back, unless the back is blank or carries only standardized printed information already on file. The records may be those made in the ordinary course of business; if none is made for a transaction that must be recorded, the institution must prepare one in writing.

    • Financial Crimes Enforcement Network
    • Final rule
  5. 31 CFR 1020.320 · Effective (as of November 14, 2026)

    Reports by Banks of Suspicious Transactions (Suspicious Activity Report rule)

    A bank must file a Suspicious Activity Report with FinCEN for a transaction conducted or attempted by, at or through the bank that involves or aggregates at least $5,000 and that the bank knows, suspects or has reason to suspect involves funds from illegal activity, is designed to evade Bank Secrecy Act requirements, or has no business or apparent lawful purpose. The report is due no later than 30 calendar days after initial detection of facts that may be a basis for filing, extendable by 30 days to identify a suspect but never past 60 days, and violations that need immediate attention must also be reported to law enforcement by telephone. The bank must keep a copy of each report and its supporting documentation for five years, and a report, and any information that would reveal it exists, is confidential.

    • Financial Crimes Enforcement Network
    • Final rule

National Credit Union Administration

  1. 12 CFR part 748 (12 CFR 748.0 and 748.1(c)) · Effective (as of November 14, 2026)

    Security Program and Cyber Incident Notification Requirements for Federally Insured Credit Unions

    Part 748 requires each federally insured credit union to keep a written security program that protects member records and responds to unauthorized access to or use of member information that could cause substantial harm or serious inconvenience to a member. Since September 1, 2023, a federally insured credit union must notify the NCUA as soon as possible and no later than 72 hours after it reasonably believes it has experienced a reportable cyber incident, or within 72 hours of being notified by a third party of one, whichever is sooner. Reportable incidents include substantial cyber incidents that disrupt vital member services or business operations, and those caused by a compromise of a credit union service organization, cloud service provider or other third-party data hosting provider. The notice is an early alert and does not require a detailed incident assessment within the 72 hours.

    • National Credit Union Administration
    • Final rule

New York State Department of Financial Services

  1. 23 NYCRR Part 500 · Effective (as of November 14, 2026)

    Cybersecurity Requirements for Financial Services Companies (as amended by the Second Amendment)

    Part 500 requires covered entities to maintain a cybersecurity program and written policies based on a risk assessment, with a Chief Information Security Officer, access controls, encryption and incident response planning. A covered entity must notify the superintendent no later than 72 hours after determining that a cybersecurity incident has occurred, and must submit by April 15 each year either a certification of material compliance or an acknowledgment of noncompliance. The second amendment took effect on November 1, 2023 and phased in its new requirements over periods of 30 days to two years, ending with multi-factor authentication for any individual accessing any information system and the asset inventory requirements.

    • New York State Department of Financial Services
    • Final rule

Office of Foreign Assets Control

  1. 31 CFR 501.603 and 501.604 · Effective (as of November 14, 2026)

    Reports of Blocked, Unblocked or Transferred Blocked Property and of Rejected Transactions (OFAC Reporting, Procedures and Penalties Regulations)

    A U.S. person holding property blocked under OFAC's regulations must report it within 10 business days of the blocking and file an annual report by September 30 of all blocked property held as of June 30. Unblocking or transferring blocked property must also be reported within 10 business days, with exceptions such as transfers explicitly authorized by a license and unblocking after a removal from the SDN List. A U.S. person that rejects a transaction that is not blocked but would violate OFAC's regulations must report it within 10 business days, giving the information available when it rejected the transaction. Initial, annual and rejected transaction reports go through the OFAC Reporting System; unblocking and transfer reports may go by email or through that system.

    • Office of Foreign Assets Control
    • Final rule

Office of the Comptroller of the Currency

  1. 12 CFR part 53; 12 CFR part 225, subpart N; 12 CFR part 304, subpart C · Effective (as of November 14, 2026)

    Computer-Security Incident Notification Requirements for Banking Organizations and Their Bank Service Providers

    A banking organization must notify its primary federal regulator of a notification incident as soon as possible and no later than 36 hours after it determines that one has occurred. A bank service provider must notify each affected banking organization customer as soon as possible when it determines that a computer-security incident has caused, or is reasonably likely to cause, a material service disruption or degradation for four or more hours. The OCC, the Federal Reserve Board and the FDIC issued the rule jointly, and compliance has been required since May 1, 2022.

    • Office of the Comptroller of the Currency, Board of Governors of the Federal Reserve System, Federal Deposit Insurance Corporation
    • Final rule
  2. 12 CFR 4.6 and 4.7; 12 CFR 208.64 and 211.26; 12 CFR 337.12 and 347.211 · Effective (as of November 14, 2026)

    Expanded Examination Cycle for Certain Small Insured Depository Institutions and U.S. Branches and Agencies of Foreign Banks

    A full-scope, on-site examination is required at least once every 12 months, but the agencies may use an 18-month cycle for an institution that is well capitalized, was rated 1 or 2 for management and composite condition at its most recent examination, is not subject to a formal enforcement proceeding or order, and has had no change in control in the preceding 12-month period. The joint interim final rule, effective September 14, 2026, raises the asset limit for the 18-month cycle from $3 billion to $6 billion, implementing section 903 of the 21st Century ROAD to Housing Act, which became law on July 11, 2026. It makes parallel changes for U.S. branches and agencies of foreign banks.

    • Office of the Comptroller of the Currency, Board of Governors of the Federal Reserve System, Federal Deposit Insurance Corporation
    • Interim final rule
  3. 12 CFR part 30, appendix B (with supplement A) · Effective (as of November 14, 2026)

    Interagency Guidelines Establishing Information Security Standards (OCC)

    Each national bank and federal savings association must implement a comprehensive written information security program, with administrative, technical and physical safeguards suited to its size, complexity and activities, designed to ensure the security and confidentiality of customer information, protect against anticipated threats and unauthorized access, and ensure the proper disposal of customer and consumer information. The board or a board committee must approve the program, and the institution must assess and control risk, oversee service providers by contract and, where its risk assessment indicates, by monitoring, adjust the program, and report to the board at least annually. Supplement A says an institution's response program should include notifying its primary federal regulator as soon as possible of an incident involving unauthorized access to or use of sensitive customer information, and notifying affected customers when warranted.

    • Office of the Comptroller of the Currency
    • Final rule

Securities and Exchange Commission

  1. 17 CFR 240.17a-4(f), (i) and (j); 17 CFR 240.18a-6(e), (f) and (g) · Effective (as of November 14, 2026)

    Electronic Recordkeeping Requirements for Broker-Dealers, Security-Based Swap Dealers, and Major Security-Based Swap Participants (2022 amendments to Rule 17a-4)

    The 2022 amendments let a broker-dealer keep electronic records either in a non-rewriteable, non-erasable (WORM) format or on a system with an audit trail that allows an original record to be recreated if it is modified or deleted. They removed the requirement to notify the designated examining authority before using an electronic recordkeeping system and let a designated executive officer, instead of a third party, sign the undertakings to provide records to regulators. Firms must also be able to produce electronic records in a reasonably usable electronic format. Broker-dealers had to comply by May 3, 2023, and security-based swap dealers and major security-based swap participants by November 3, 2023.

    • Securities and Exchange Commission
    • Final rule
  2. 17 CFR 248.201-248.202 (Regulation S-ID); 17 CFR part 162, subpart C · Effective (as of November 14, 2026)

    Regulation S-ID: Identity Theft Red Flags Rules

    A broker-dealer, investment company or investment adviser that is a financial institution or creditor under the Fair Credit Reporting Act and offers or maintains covered accounts must develop and implement a written Identity Theft Prevention Program designed to detect, prevent and mitigate identity theft when a covered account is opened and for existing covered accounts. The program must identify relevant red flags, detect them, respond to them appropriately and be updated periodically, and the board of directors or one of its committees must approve the initial written program. A card issuer must also assess the validity of a change of address when, within a short period after it, the issuer receives a request for an additional or replacement card for the same account. Compliance has been required since November 20, 2013.

    • Securities and Exchange Commission, Commodity Futures Trading Commission
    • Final rule
  3. 17 CFR 248.30 · Effective (as of November 14, 2026)

    Regulation S-P: Privacy of Consumer Financial Information and Safeguarding Customer Information (2024 amendments)

    The 2024 amendments require covered institutions to adopt written policies and procedures for an incident response program that is reasonably designed to detect, respond to and recover from unauthorized access to or use of customer information. The program must include notice to individuals whose sensitive customer information was, or is reasonably likely to have been, accessed or used without authorization, given as soon as practicable and no later than 30 days after the institution becomes aware of it, with limited exceptions. Covered institutions must also oversee their service providers, including making sure each one notifies the institution no later than 72 hours after becoming aware of a breach that gave unauthorized access to a customer information system it maintains. Larger entities had to comply by December 3, 2025 and smaller entities by June 3, 2026.

    • Securities and Exchange Commission
    • Final rule
  4. 17 CFR 242.1000-242.1007 (Regulation SCI) · Effective (as of November 14, 2026)

    Regulation Systems Compliance and Integrity (Regulation SCI)

    Regulation SCI requires SCI entities, including national securities exchanges, registered securities associations, registered clearing agencies, the MSRB and alternative trading systems that meet its volume thresholds, to keep written policies and procedures reasonably designed to give their SCI systems adequate capacity, integrity, resiliency, availability and security. When responsible SCI personnel have a reasonable basis to conclude that an SCI event (a systems disruption, systems compliance issue or systems intrusion) has occurred, the entity must begin corrective action and, unless the event has no or a de minimis impact, notify the Commission immediately and in writing within 24 hours. Each entity must also report material systems changes quarterly, conduct an SCI review at least once each calendar year, and require designated members or participants to test its business continuity and disaster recovery plans at least once every 12 months. SCI entities have had to comply since November 3, 2015.

    • Securities and Exchange Commission
    • Final rule

Healthcare

Centers for Medicare & Medicaid Services

  1. 42 CFR parts 422, 431, 435, 438, 440 and 457; 45 CFR part 156 (CMS-0057-F) · Effective (as of November 14, 2026)

    Advancing Interoperability and Improving Prior Authorization Processes (CMS Interoperability and Prior Authorization final rule)

    CMS-0057-F requires impacted payers to add prior authorization information to the Patient Access API and to build Provider Access, Payer-to-Payer and Prior Authorization APIs. Impacted payers other than QHP issuers on the Federally-facilitated Exchanges must decide prior authorization requests within 72 hours for expedited and 7 calendar days for standard requests, and all impacted payers must give a specific reason for a denial and publicly report prior authorization metrics. The process requirements apply from January 1, 2026 and most API requirements from January 1, 2027.

    • Centers for Medicare & Medicaid Services
    • Final rule
    • Next: compliance date January 1, 2027
  2. 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
  3. 42 CFR 482.24 · Effective (as of November 14, 2026)

    Hospital Condition of Participation: Medical Record Services

    A hospital must keep an accurately written, promptly completed, properly filed and accessible medical record for every inpatient and outpatient, retain records for at least 5 years, and ensure that unauthorized individuals cannot gain access to or alter them. Entries must be legible, complete, dated, timed and authenticated, and records must be completed within 30 days after discharge. Since May 1, 2021, a hospital whose electronic records system conforms to the required content exchange standard must send electronic patient event notifications at emergency department registration or inpatient admission, and at or just before discharge or transfer, to applicable post-acute care providers and suppliers and to the patient's established primary care practitioner or another practitioner the patient identifies.

    • Centers for Medicare & Medicaid Services
    • Final rule
  4. 45 CFR part 180 · Effective (as of November 14, 2026)

    Hospital Price Transparency

    Each hospital must publish a machine-readable file of its standard charges for all items and services, including gross charges, discounted cash prices, payer-specific negotiated charges and de-identified minimum and maximum negotiated charges, and a consumer-friendly display of at least 300 shoppable services or a qualifying price estimator tool. Since January 1, 2026, where a negotiated charge is based on a percentage or algorithm, the file must report the 10th percentile, median and 90th percentile allowed amounts, and every file must carry an attestation, the name of a senior official and the hospital's Type 2 NPIs; CMS delayed enforcement of these changes to April 1, 2026. CMS may impose daily civil monetary penalties of up to $300 for hospitals with 30 or fewer beds, $10 per bed for 31 to 550 beds, and $5,500 for more than 550 beds, amounts that part 180 says are adjusted annually for inflation under 45 CFR part 102.

    • Centers for Medicare & Medicaid Services
    • Final rule
  5. 42 CFR 422.122 · Effective (as of November 14, 2026)

    Medicare Advantage Prior Authorization Requirements

    Since January 1, 2026, a Medicare Advantage organization that denies a prior authorization request for an item or service other than a drug must give the provider a specific reason for the denial, however the decision is communicated. Each year, by March 31, the organization must post on its website prior authorization metrics for the previous calendar year, including the list of items and services that require prior authorization, approval and denial rates, and average and median decision times. Beginning January 1, 2027, it must run a Prior Authorization API that lists the items and services needing prior authorization, identifies the documentation required, supports a HIPAA-compliant request and response, and says whether a request is approved, denied or needs more information.

    • Centers for Medicare & Medicaid Services
    • Final rule
    • Next: compliance date January 1, 2027
  6. 42 CFR 424.515 and 424.516 · Effective (as of November 14, 2026)

    Medicare enrollment: periodic revalidation (424.515) and requirements for maintaining active enrollment, including change reporting and documentation (424.516)

    To keep Medicare billing privileges, a provider or supplier other than a DMEPOS supplier must resubmit and recertify its enrollment information every 5 years, and must send a complete application within 60 calendar days of CMS's notice to revalidate; CMS may also order off-cycle revalidations and site visits. Physicians, nonphysician practitioners and their organizations report a change of ownership, an adverse legal action or a practice location change within 30 days and all other changes within 90 days, and other providers and suppliers follow similar 30- and 90-day timeframes. Providers and suppliers that order, certify, refer or prescribe, or furnish such services, keep the related documentation for 7 years from the date of service and give CMS or its contractor access on request. A final rule published November 9, 2026 adds a duty, effective January 1, 2027, for covered entities to submit documentation on covered Part D drugs they write or order.

    • Centers for Medicare & Medicaid Services
    • Final rule
    • Next: effective January 1, 2027
  7. 42 CFR 411.357(bb); 42 CFR 1001.952(jj) · Effective (as of November 14, 2026)

    Physician self-referral exception and anti-kickback safe harbor for cybersecurity technology and related services

    The physician self-referral exception at 42 CFR 411.357(bb) and the anti-kickback safe harbor at 42 CFR 1001.952(jj) protect donations of technology and services necessary and used predominantly to implement, maintain or reestablish cybersecurity. The donor may not directly take into account the volume or value of referrals, the recipient may not make the donation a condition of doing business, and the arrangement must be in writing. The safe harbor also bars the donor from shifting the costs to any Federal health care program. Both took effect on January 19, 2021.

    • Centers for Medicare & Medicaid Services, HHS Office of Inspector General
    • Final rule

Department of Health and Human Services

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

    Confidentiality of Substance Use Disorder Patient Records (2024 final rule)

    The 2024 rule implements section 3221 of the CARES Act by aligning the substance use disorder confidentiality rules more closely with HIPAA. A patient can give a single consent for all future uses and disclosures of their records for treatment, payment and health care operations, and a covered entity or business associate that receives records under that consent may redisclose them as the HIPAA rules permit, except for certain proceedings against the patient. Breaches of part 2 records are subject to the HIPAA breach notification requirements, and violations to the HIPAA civil and criminal penalties. Persons subject to the rule had to comply by February 16, 2026.

    • Department of Health and Human Services, Substance Abuse and Mental Health Services Administration
    • Final rule
  2. 45 CFR part 160 · Effective (as of November 14, 2026)

    HIPAA General Administrative Requirements (applicability, definitions, preemption, compliance and enforcement)

    Part 160 holds the general provisions shared by the HIPAA Administrative Simplification rules: who they apply to, common definitions such as protected health information, and when a HIPAA standard preempts contrary state law. Its enforcement subparts let any person file a complaint with the Secretary, generally within 180 days of when the complainant knew or should have known of the act or omission, and set the tiers of civil money penalties by level of culpability. The Secretary must begin a penalty action within 6 years of the violation, and the penalty amounts are adjusted for inflation each year and published at 45 CFR part 102.

    • Department of Health and Human Services
    • Final rule
  3. 45 CFR parts 160 and 164 (proposed; RIN 0945-AA22) · Proposed (as of November 14, 2026)

    HIPAA Security Rule To Strengthen the Cybersecurity of Electronic Protected Health Information (proposed rule)

    The proposal would revise the HIPAA Security Rule to better protect the confidentiality, integrity and availability of electronic protected health information. Regulated entities would have to keep a written inventory of technology assets and a network map, encrypt electronic protected health information at rest and in transit with limited exceptions, run vulnerability scans at least every six months and set written procedures to restore critical systems and data within 72 hours. Comments closed on March 7, 2025, and the rule has not been finalized.

    • Department of Health and Human Services
    • Proposed rule
  4. 45 CFR 92.210 · Effective (as of November 14, 2026)

    Nondiscrimination in the Use of Patient Care Decision Support Tools (Section 1557 rule)

    Section 92.210 bars covered entities from discriminating on the basis of race, color, national origin, sex, age or disability through the use of patient care decision support tools in their health programs or activities. Covered entities have an ongoing duty to make reasonable efforts to identify tools that use input variables or factors measuring those characteristics, and to make reasonable efforts to mitigate the risk of discrimination from each one. The identification and mitigation duties applied within 300 days of the July 5, 2024 effective date.

    • Department of Health and Human Services
    • Final rule
  5. 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
  6. 45 CFR part 164, subpart D (45 CFR 164.400 to 164.414) · Effective (as of November 14, 2026)

    Notification in the Case of Breach of Unsecured Protected Health Information (HIPAA Breach Notification Rule)

    Covered entities must notify affected individuals of a breach of unsecured protected health information without unreasonable delay and in no case later than 60 calendar days after discovery. A breach involving more than 500 residents of a state or jurisdiction must also be reported to prominent media outlets, and a breach of 500 or more individuals to the Secretary at the same time as the notice to individuals; smaller breaches are logged and reported within 60 days after the end of each calendar year. An impermissible use or disclosure is presumed to be a breach unless a risk assessment shows a low probability that the information has been compromised.

    • Department of Health and Human Services
    • Final rule
  7. 45 CFR part 164, subpart C (45 CFR 164.302 to 164.318) · Effective (as of November 14, 2026)

    Security Standards for the Protection of Electronic Protected Health Information (HIPAA Security Rule)

    The Security Rule requires covered entities and business associates to ensure the confidentiality, integrity and availability of the electronic protected health information they create, receive, maintain or transmit. It sets administrative, physical and technical safeguards whose implementation specifications are either required or addressable, and requires policies, procedures and documentation to be kept for 6 years. Covered entities other than small health plans had to comply by April 21, 2005, and the 2013 modifications made business associates directly liable for compliance, with a compliance date of September 23, 2013.

    • Department of Health and Human Services
    • Final rule
  8. 45 CFR 147.211 and 147.212; 29 CFR 2590.715-2715A2 and 2590.715-2715A3; 26 CFR 54.9815-2715A2 and 54.9815-2715A3 · Effective (as of November 14, 2026)

    Transparency in Coverage

    Group health plans and health insurance issuers must give participants, beneficiaries and enrollees cost-sharing information on request through an internet-based self-service tool and on paper, and must publish machine-readable files of in-network rates and historical out-of-network allowed amounts. Final rules published on October 6, 2026 add contextual files and data elements such as product type and provider network, lengthen the out-of-network reporting period while lowering its claims threshold, reduce the reporting cadence, and require the cost-sharing information by phone as well. The amended cost-sharing rules apply for plan years beginning on or after January 1, 2027, and the amended file rules from March 6, 2027, with contextual files and website footers from September 6, 2027.

    • Department of Health and Human Services, Department of Labor, Department of the Treasury
    • Final rule
    • Next: effective December 7, 2026

Drug Enforcement Administration

  1. 21 CFR 1307.41; 42 CFR 12.1 (Fourth Temporary Extension, 90 FR 61301; Docket No. DEA-407) · Effective (as of November 14, 2026)

    Fourth Temporary Extension of COVID-19 Telemedicine Flexibilities for Prescription of Controlled Medications

    DEA and HHS extended, through December 31, 2026, the telemedicine flexibilities in place since the COVID-19 public health emergency for prescribing controlled medications. Until then, a DEA-registered practitioner may prescribe schedule II-V controlled substances via telemedicine to a patient without an in-person medical evaluation, if the prescription is for a legitimate medical purpose, uses an interactive telecommunications system and meets the other conditions of 21 CFR 1307.41(c). The rule took effect on January 1, 2026.

    • Drug Enforcement Administration, Department of Health and Human Services
    • Final rule
    • Next: deadline December 31, 2026

Federal Trade Commission

  1. 16 CFR part 318 · Effective (as of November 14, 2026)

    Health Breach Notification Rule

    The Health Breach Notification Rule requires vendors of personal health records and related entities that HIPAA does not cover to notify affected individuals, the FTC and, in some cases, the media after a breach of unsecured identifiable health information. Notices to individuals and the media are due without unreasonable delay and no later than 60 calendar days after discovery, and notice to the FTC of a breach involving 500 or more individuals is due at the same time as the notice to individuals. The 2024 amendments, effective July 29, 2024, clarify that the rule covers developers of many health apps and that a breach of security includes an unauthorized disclosure.

    • Federal Trade Commission
    • Final rule

Food and Drug Administration

  1. FDA guidance, Cybersecurity in Medical Devices: Quality Management System Considerations and Content of Premarket Submissions (February 3, 2026; docket FDA-2021-D-1158) · Effective (as of November 14, 2026)

    Cybersecurity in Medical Devices: Quality Management System Considerations and Content of Premarket Submissions

    The guidance sets out FDA's recommendations on cybersecurity in device design and labeling and on the cybersecurity documentation to include in premarket submissions, and covers its recommendations under section 524B for cyber devices, including the software bill of materials. It treats cybersecurity as part of device safety and of the Quality Management System Regulation, and describes a secure product development framework as one way to satisfy that regulation. The February 3, 2026 version supersedes the June 27, 2025 version and aligns the text with the amended 21 CFR part 820, which took effect on February 2, 2026.

    • Food and Drug Administration
    • Guidance

HHS Office of Inspector General

  1. 42 CFR part 1003, subpart N (42 CFR 1003.1400 to 1003.1420) · Effective (as of November 14, 2026)

    Civil Money Penalties for Information Blocking

    The HHS Office of Inspector General may impose a civil money penalty of not more than $1,000,000 per violation (adjusted for inflation to $1,327,209 in 45 CFR 102.3) on a health IT developer of certified health IT, health information network or health information exchange that commits information blocking as defined in 45 CFR part 171. Each practice that constitutes information blocking is a violation. In setting the amount, OIG takes into account the nature and extent of the information blocking and the harm it caused, including the number of patients and providers affected and the number of days it persisted. The penalties took effect on September 1, 2023, and OIG has said it will not impose them for conduct before the final rule's effective date.

    • HHS Office of Inspector General
    • Final rule

Office of the National Coordinator for Health Information Technology

  1. 45 CFR parts 170 and 172 (RIN 0955-AA09) · Final (as of November 14, 2026)

    Health Data, Technology, and Interoperability: ONC Deregulatory Actions To Unleash Prosperity (HTI-5 final rule)

    The final rule removes 14 of the 60 certification criteria in effect in the ONC Health IT Certification Program, revises seven and leaves 39 unchanged. One revision narrows the decision support interventions criterion by removing the source attribute requirements in 45 CFR 170.315(b)(11)(iv) and (v). The rule takes effect on December 28, 2026, except for three amendatory instructions, including the removal of the family health history criterion, which take effect on January 1, 2027.

    • Office of the National Coordinator for Health Information Technology
    • Final rule
    • Next: effective December 28, 2026
  2. 45 CFR part 171 · Effective (as of November 14, 2026)

    Information Blocking

    Information blocking is a practice that, unless required by law or covered by an exception, is likely to interfere with access, exchange or use of electronic health information; a developer, network or exchange is liable if it knows or should know this, and a health care provider if it knows the practice is unreasonable. Part 171 sets out exceptions for preventing harm, privacy, security, infeasibility, health IT performance, protecting care access, manner, fees, licensing and the TEFCA manner of fulfilling requests. Actors have been subject to the part since April 5, 2021, and the full definition of electronic health information has applied since October 6, 2022.

    • Office of the National Coordinator for Health Information Technology
    • Final rule

United States Congress

  1. 21 U.S.C. 360n-2 (section 524B of the Federal Food, Drug, and Cosmetic Act) · Effective (as of November 14, 2026)

    Ensuring Cybersecurity of Devices (FD&C Act section 524B)

    Section 524B requires a sponsor that submits a premarket submission for a cyber device to include the information FDA requires to show that the device meets four cybersecurity requirements. The sponsor must submit a plan to monitor, identify and address postmarket cybersecurity vulnerabilities and exploits, including coordinated vulnerability disclosure; maintain processes that give a reasonable assurance the device and related systems are cybersecure, with updates and patches on a reasonably justified regular cycle for known unacceptable vulnerabilities and as soon as possible for critical ones; provide a software bill of materials; and meet any further requirements FDA sets by regulation. The section took effect on March 29, 2023.

    • United States Congress
    • Statute

Government

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

Cross-sector

Bureau of Industry and Security

  1. 15 CFR 734.13; 15 CFR 734.18(a)(5) · Effective (as of November 14, 2026)

    Export, including deemed exports, and the encrypted-storage exclusion for technology and software (Export Administration Regulations)

    Under the Export Administration Regulations an export is an actual shipment or transmission out of the United States, or a release of technology or source code, but not object code, to a foreign person in the United States, which is a deemed export to that person's most recent country of citizenship or permanent residency. Section 734.18(a)(5) says that sending, taking or storing unclassified technology or software is not an export when it is secured with end-to-end encryption, protected by FIPS 140-2 compliant or equally effective cryptography, and not intentionally stored in a Country Group D:5 country. The definitions took effect on September 1, 2016.

    • Bureau of Industry and Security
    • Final rule

Cybersecurity and Infrastructure Security Agency

  1. 6 CFR part 226 (proposed; RIN 1670-AA04; Docket No. CISA-2022-0010) · Proposed (as of November 14, 2026)

    Cyber Incident Reporting for Critical Infrastructure Act (CIRCIA) Reporting Requirements

    The proposed rule would implement CIRCIA by requiring covered entities to report covered cyber incidents to CISA no later than 72 hours after they reasonably believe one has occurred, and ransom payments no later than 24 hours after the payment is disbursed. CISA published the proposal on April 4, 2024, and comments closed on July 3, 2024, after a 30-day extension. As checked on November 14, 2026, it had not been finalized.

    • Cybersecurity and Infrastructure Security Agency, Department of Homeland Security
    • Proposed rule

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

Department of Justice

  1. 28 CFR part 202 · Effective (as of November 14, 2026)

    Preventing Access to U.S. Sensitive Personal Data and Government-Related Data by Countries of Concern or Covered Persons (the Data Security Program)

    The Data Security Program bars or restricts U.S. persons from data transactions that would give countries of concern or covered persons access to government-related data or bulk U.S. sensitive personal data. Data brokerage with those countries or persons, and transactions giving them access to bulk human ’omic data or to human biospecimens from which it could be derived, are prohibited, while vendor, employment and investment agreements are allowed only if the U.S. person meets CISA's security requirements and the rule's other applicable requirements. The rule took effect on April 8, 2025, and its data compliance program and audit duties for restricted transactions, along with two reporting duties, apply from October 6, 2025.

    • Department of Justice
    • Final rule

Federal Trade Commission

  1. 16 CFR part 312 · Effective (as of November 14, 2026)

    Children's Online Privacy Protection Rule (COPPA Rule)

    The COPPA Rule requires operators of child-directed websites and online services, and operators with actual knowledge that they collect or maintain personal information from a child under 13, to give notice and obtain verifiable parental consent before collecting, using or disclosing that information. As amended in 2025, it also requires separate parental consent before disclosing a child's information to third parties unless the disclosure is integral to the service, a written information security program, and a written data retention policy that sets a timeframe for deletion. The amended rule took effect on June 23, 2025, and regulated entities had until April 22, 2026 to comply, with earlier dates for FTC-approved safe harbor programs.

    • Federal Trade Commission
    • Final rule
  2. 16 CFR part 318 · Effective (as of November 14, 2026)

    Health Breach Notification Rule

    The Health Breach Notification Rule requires vendors of personal health records and related entities that HIPAA does not cover to notify affected individuals, the FTC and, in some cases, the media after a breach of unsecured identifiable health information. Notices to individuals and the media are due without unreasonable delay and no later than 60 calendar days after discovery, and notice to the FTC of a breach involving 500 or more individuals is due at the same time as the notice to individuals. The 2024 amendments, effective July 29, 2024, clarify that the rule covers developers of many health apps and that a breach of security includes an unauthorized disclosure.

    • Federal Trade Commission
    • 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. 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

Securities and Exchange Commission

  1. 17 CFR 229.106 (Regulation S-K Item 106); Form 8-K Item 1.05 · Effective (as of November 14, 2026)

    Cybersecurity Risk Management, Strategy, Governance, and Incident Disclosure

    Public companies must disclose on Form 8-K Item 1.05 any cybersecurity incident they determine to be material, describing its nature, scope and timing and its material or reasonably likely material impact, generally within four business days of that determination. Regulation S-K Item 106 requires annual-report disclosure of the processes for assessing, identifying and managing material cybersecurity risks, the board's oversight of those risks, and management's role. Item 1.05 has applied since December 18, 2023 for most registrants and since June 15, 2024 for smaller reporting companies.

    • Securities and Exchange Commission
    • Final rule