Comparison tables
Rules, deadlines and programs side by side. Every cell links to the primary source it was checked against, with the date it was checked.
79 tables
Financial Services
Comparison table · Reviewed November 14, 2026
AI and model guidance for banks compared: issuers, instruments and binding status
The Federal Reserve, OCC and FDIC replaced their 2011 model risk guidance on April 17, 2026 (SR 26-2, OCC Bulletin 2026-13); it is not binding, is expected to be most relevant to banking organizations with over $30 billion in total assets, and leaves generative and agentic AI models outside its scope. On November 4, 2026 the OCC issued a Super Intelligence supervisory framework for examiners that does not establish supervisory expectations for banks. Treasury's AI work for the sector includes two 2024 reports and the February 2026 AI Lexicon and FS AI RMF, resources Treasury says focus on practical implementation rather than prescriptive requirements. The CFPB withdrew its two adverse action circulars on complex algorithms and AI as of May 12, 2025, and FinCEN's 2026 AML/CFT program proposal would weigh a bank's effective use of artificial intelligence in enforcement decisions.
Comparison table · Reviewed November 14, 2026
Anti-money laundering program rules compared by type of financial institution
Banks, savings associations and credit unions need an anti-money laundering program with internal controls, independent testing, a person or people responsible for day-to-day compliance, training and risk-based customer due diligence (31 CFR 1020.210), and the OCC, Federal Reserve, FDIC and NCUA rules add that the program be written, approved by the board of directors and recorded in the minutes. Broker-dealers, futures commission merchants and insurance companies need senior management approval instead, while the casino and money services business rules name no approving body. FinCEN's April 10, 2026 proposal to reform program rules across institution types was still a proposal as of 2026-11-14, and the investment adviser rule's effective date is delayed until January 1, 2028.
Comparison table · Reviewed November 14, 2026
Bank and credit union cybersecurity assessment tools after the FFIEC CAT: status and what regulators say
The FFIEC Cybersecurity Assessment Tool sunset on August 31, 2025; the FFIEC chose not to update it for NIST CSF 2.0 or CISA's Cybersecurity Performance Goals and said institutions can refer to those resources directly. The Federal Reserve says it does not endorse any particular self-assessment tool, and the FDIC says its institutions may consider industry-developed resources. NCUA still offers its voluntary ACET toolbox, derived from the CAT and mapped to the FFIEC IT Handbook and the NIST CSF. The FFIEC Information Security booklet of September 2016 remained among the current IT Handbook booklets in March 2026.
Comparison table · Reviewed November 14, 2026
Bank supervision changes in 2026 compared: unsafe or unsound practice, MRAs, reputation risk, exam cycles and CAMELS
The OCC and FDIC final rule defining an unsafe or unsound practice and limiting matters requiring attention took effect on November 2, 2026. Their rule barring supervisory use of reputation risk took effect on June 9, 2026, and NCUA's own reputation risk rule on July 27, 2026; the Federal Reserve Board's reputation risk proposal closed for comment on April 27, 2026. An interim final rule of the OCC, Federal Reserve Board and FDIC, effective September 14, 2026, lets qualifying institutions with less than $6 billion in total assets, up from $3 billion, have an 18-month exam cycle. The FFIEC's proposed CAMELS revisions closed for comment on August 17, 2026; a Federal Register search on 2026-11-14 found no final version.
Comparison table · Reviewed November 14, 2026
BSA/AML and sanctions obligations for banks: deadlines, thresholds and records
A bank must file a suspicious activity report on a transaction involving or aggregating at least $5,000 no later than 30 calendar days after initial detection of facts that may constitute a basis for filing, and in no case more than 60 calendar days after initial detection when it delays filing because no suspect was identified. A report of a transaction in currency of more than $10,000 is filed within 15 days following the day on which the transaction occurred, and records required by the Bank Secrecy Act rules are retained for a period of five years. Initial reports of blocked property are filed with OFAC within 10 business days from the date the property becomes blocked. FinCEN's April 10, 2026 proposal to reform AML/CFT program rules was still a proposal as of 2026-11-14.
Comparison table · Reviewed November 14, 2026
CFPB personal financial data rights rule (12 CFR part 1033): parties, compliance dates and status
Under 12 CFR 1033.121 as codified, the compliance date for the largest data providers (depository institutions with at least $250 billion in total assets and nondepositories with at least $10 billion in total receipts in 2023 or 2024) is April 1, 2026, with later tiers on April 1 of 2027, 2028, 2029 and 2030. On October 29, 2025 the federal court in Forcht Bank v. CFPB (E.D. Ky.) ordered that the CFPB is enjoined from enforcing the rule until it has completed its reconsideration of the rule; no later court opinion in the case was found as of 2026-11-14. The CFPB opened that reconsideration with an advance notice of proposed rulemaking released August 22, 2025, and its agenda published August 14, 2026, which states that its information is current as of January 13, 2026, says it plans a rulemaking to reconsider certain aspects of the November 2024 rule.
Comparison table · Reviewed November 14, 2026
CFTC system safeguards testing and recovery rules compared across exchanges, SEFs, clearing houses and swap data repositories
CFTC rules set fixed minimum testing frequencies for derivatives clearing organizations, swap data repositories and covered designated contract markets: vulnerability testing no less frequently than quarterly, external and internal penetration testing and incident response plan testing no less frequently than annually, and key controls testing every three years, with independent contractors doing the annual external penetration test and the three-year key controls assessment. Swap execution facilities and designated contract markets that are not covered test at a frequency set by their own risk analysis. Recovery targets range from the next business day for most entities to two hours for systemically important and subpart C clearing organizations.
Comparison table · Reviewed November 14, 2026
Consumer financial data sharing rules compared: part 1033, Regulation P, FCRA and Regulation E
The CFPB's personal financial data rights rule (12 CFR part 1033) gives consumers and authorized third parties a right to get covered account data from data providers, but as of 2026-11-14 the CFPB is enjoined from enforcing it until it completes its reconsideration, under the October 29, 2025 order in Forcht Bank v. CFPB. Regulation P lets consumers opt out of a financial institution's sharing of nonpublic personal information with nonaffiliated third parties, with listed exceptions. The FCRA allows consumer reports only for listed permissible purposes, including the consumer's written instructions. Regulation E requires a signed or similarly authenticated writing for preauthorized transfers from a consumer's account and lets the consumer stop one by notice at least three business days before the scheduled date.
Comparison table · Reviewed November 14, 2026
Credit union and bank cyber rules compared: NCUA and the federal banking agencies
A federally insured credit union must report a reportable cyber incident to NCUA no later than 72 hours after it reasonably believes one occurred, while a bank must notify its federal regulator no later than 36 hours after determining a notification incident occurred. Both follow information security guidelines that list the same three service-provider steps: due diligence, contract terms and monitoring. The banking agencies say that, when circumstances warrant, they can examine functions a third party performs for a bank, while NCUA's examiner guide says NCUA does not have authority to examine third-party vendors.
Comparison table · Reviewed November 14, 2026
Customer notice duties in financial services compared: breaches, privacy notices and error disputes
Under Regulation S-P, covered institutions must notify individuals whose sensitive customer information was, or is reasonably likely to have been, accessed or used without authorization as soon as practicable and no later than 30 days after becoming aware of the unauthorized access or use, unless a reasonable investigation finds the information is not reasonably likely to be used in a way that would result in substantial harm or inconvenience. A financial institution relying on the Regulation P exception to the annual privacy notice must send an annual notice within 100 days of a policy change that ends its eligibility, unless the change required a revised notice. Regulation E gives an institution 10 business days to decide whether an electronic fund transfer error occurred, or up to 45 days with provisional credit. Regulation Z requires a creditor to acknowledge a billing error notice within 30 days and resolve it within two complete billing cycles and no more than 90 days.
Comparison table · Reviewed November 14, 2026
Cybersecurity duties for virtual currency businesses and money transmitters: Louisiana, Washington and the FTC Safeguards Rule
Louisiana requires board-approved written policies covering cybersecurity and information security and asks for a description of any data security breach in the annual renewal report. Washington requires an information security program and a written business resumption plan, and an information security audit report from applicants engaged in virtual currency storage. The FTC Safeguards Rule counts a business that regularly wires money to and from consumers as a financial institution; absent effective continuous monitoring it requires annual penetration testing and vulnerability assessments at least every six months, and it requires notice to the FTC no later than 30 days after discovery of a notification event involving at least 500 consumers.
Comparison table · Reviewed November 14, 2026
Electronic communications recordkeeping: SEC, FINRA and CFTC rules compared
SEC Rule 17a-4(b)(4) has broker-dealers keep all communications relating to their business as such for not less than three years, the first two in an easily accessible place, and FINRA Rule 3110 requires a registered principal to review correspondence and internal communications and evidence the review in writing. Investment advisers keep listed written communications for not less than five years from the end of the fiscal year of the last entry (Rule 204-2). CFTC rules name the channels, from telephone and instant messaging to chat rooms, email and mobile devices: futures commission merchants, larger introducing brokers and swap dealers keep oral and written pre-trade communications, with oral records kept not less than one year and other records not less than five years (17 CFR 1.31).
Comparison table · Reviewed November 14, 2026
FFIEC IT Examination Handbook booklets compared: release dates and scope
As shown in the Internet Archive's copy of the FFIEC's booklet page captured March 25, 2026, the handbook has ten booklets: Audit, Business Continuity Management, Development, Acquisition, and Maintenance, Information Security, Management, Architecture, Infrastructure, and Operations, Outsourcing Technology Services, Retail Payment Systems, Supervision of Technology Service Providers, and Wholesale Payment Systems. Of the booklet releases announced in OCC bulletins, the most recent is Development, Acquisition, and Maintenance, announced on September 5, 2024; the FFIEC's archived booklets page says the April 2004 Development and Acquisition booklet it replaced was superseded on August 29, 2024. The latest OCC bulletins found for the Wholesale Payment Systems and Outsourcing Technology Services booklets date from 2004.
Comparison table · Reviewed November 14, 2026
Identity theft Red Flags rules compared across seven federal regulators
Seven regulators (OCC, Federal Reserve Board, FDIC, NCUA, FTC, SEC and CFTC) each publish their own Red Flags rule, with near-identical text and different scope: which one applies depends on the type of financial institution or creditor. Each requires a written Identity Theft Prevention Program whose initial version is approved by the board of directors or an appropriate committee of the board, and each points to its own guidelines appendix (J for the banking agencies and NCUA, A for the FTC and SEC, B for the CFTC). A card issuer must assess the validity of a change of address before issuing an additional or replacement card requested during at least the first 30 days after the notice; the SEC version requires written policies and procedures for this.
Comparison table · Reviewed November 14, 2026
Insurance data security laws in nine selected states: notice to the regulator and small-licensee exemptions
This table covers nine selected states whose insurance data security statutes we opened; it is not a complete list, and other states may have similar laws. Of the nine, South Carolina gives licensees 72 hours to notify the regulator after determining a cybersecurity event occurred; Ohio, New Hampshire, Delaware, Connecticut, Virginia, Iowa and North Dakota allow three business days, and Minnesota five business days. Employee-count exemptions from the information security program range from fewer than ten employees (South Carolina, Connecticut) to fewer than 25 (Minnesota); Ohio and Iowa add revenue and asset tests, North Dakota uses revenue and assets only, and Virginia sets no size exemption.
Comparison table · Reviewed November 14, 2026
Operational resilience guidance for US banks compared: the 2020 sound practices and how each agency issued them
The OCC, Federal Reserve Board and FDIC released Sound Practices to Strengthen Operational Resilience on October 30, 2020, written for the largest domestic banking organizations: $250 billion or more in average total consolidated assets, or $100 billion or more with $75 billion or more in specified risk measures. The paper brings together existing regulations, guidance and industry standards and sets no new ones. The Fed's SR 20-24 page and the FDIC's FIL-103-2020 page show the attached paper revised on June 2, 2026 to remove references to reputation risk. NCUA has joined the agencies' proposed third-party risk management guidance, which mentions operational resilience plans; a November 13, 2026 joint release extended its comment period to December 16.
Comparison table · Reviewed November 14, 2026
SEC and FINRA cybersecurity rules compared: who is covered, duties and deadlines
Under amended Regulation S-P, broker-dealers, investment companies, registered investment advisers, funding portals and transfer agents must notify individuals whose sensitive customer information was, or is reasonably likely to have been, accessed without authorization no later than 30 days after becoming aware of the incident, unless a reasonable investigation finds it is not reasonably likely to be used to cause substantial harm or inconvenience; larger entities had to comply by December 3, 2025 and smaller entities by June 3, 2026. Public companies file Form 8-K Item 1.05 within four business days of determining that a cybersecurity incident is material. SCI entities must notify the SEC immediately, and in writing within 24 hours, of an SCI event with more than a de minimis impact. The SEC's 2023 proposals to expand Regulation SCI and add cybersecurity risk management rules for broker-dealers and others were withdrawn in June 2025.
Comparison table · Reviewed November 14, 2026
SEC and FINRA recordkeeping and retention rules compared
Broker-dealers keep core records under SEC Rule 17a-4 for at least 6 years and other listed records, including communications, for at least 3 years, the first 2 easily accessible in both cases; security-based swap entities that are not broker-dealers follow the same 6-year and 3-year pattern under Rule 18a-6. Advisers keep most records for at least 5 years under Rule 204-2, and funds keep some records permanently and others for at least 6 years under Rule 31a-2. Rules 17a-4 and 18a-6 allow electronic recordkeeping systems with a time-stamped audit trail or non-rewriteable, non-erasable storage (under Rule 18a-6, for entities without a prudential regulator); Rules 204-2 and 31a-2 allow electronic storage media with indexing, duplicate copies and safeguards. FINRA Rule 4511 sets at least 6 years where FINRA and Exchange Act rules specify no period and requires 17a-4 compliant format and media.
Comparison table · Reviewed November 14, 2026
Technology duties in broker-dealer and investment adviser rules compared
Since the SEC's 2022 amendments (compliance date May 3, 2023), Rule 17a-4 lets broker-dealers keep electronic records either with a complete time-stamped audit trail that permits re-creation of the original record or in non-rewriteable, non-erasable format, with automatic verification, export in usable formats and a backup or other redundancy. Rule 15c3-5 requires brokers or dealers with market access to keep pre-trade controls that reject orders exceeding credit, capital, price or size limits under their direct and exclusive control and to restrict access to trading systems to authorized persons. Regulation S-ID requires a written identity theft program for firms in its scope that offer or maintain covered accounts. Advisers Act Rule 204-2(g) allows electronic storage if records are indexed, duplicated, protected from loss or alteration and access-limited.
Comparison table · Reviewed November 14, 2026
US banking regulators compared: who they supervise, exam cycles and technology rules
The OCC, Federal Reserve and FDIC must give the banks they supervise a full-scope, on-site exam at least once every 12 months, or every 18 months for qualifying banks under $6 billion in assets. NCUA's scheduling table puts most credit unions under $15 billion on a cycle of 8 to under 24 months depending on condition, size and net worth, and supervises those at $15 billion and above continuously. The banking agencies examine technology using the FFIEC IT Examination Handbook, while NCUA uses its Information Security Examination procedures. The CFPB has authority to examine banks and credit unions with more than $10 billion in assets for compliance with Federal consumer financial law.
Comparison table · Reviewed November 14, 2026
US payment rails modernization compared: FedNow, Fedwire ISO 20022 and Same Day ACH
The FedNow Service went live on July 20, 2023; on September 9, 2025 Federal Reserve Financial Services announced that its network limit for customer credit transfers would rise from $1 million to $10 million, effective November 2025. Federal Reserve Financial Services announced on July 15, 2025 that the Fedwire Funds Service had completed its move to the ISO 20022 message format; the next ISO 20022 release is set for November 22, 2027, with mandatory testing for named groups. The Board has announced that Fedwire will run 22 hours a day, Sunday through Friday, expected in 2028 or 2029. The Same Day ACH limit rose to $1 million per payment on March 18, 2022.
Healthcare
Comparison table · Reviewed November 14, 2026
42 CFR part 2 and HIPAA compared: consent, redisclosure, proceedings, breaches and penalties
Substance use disorder records from federally assisted substance use disorder programs still need written patient consent under 42 CFR part 2, but since the 2024 rule a patient can give one consent for all future treatment, payment and health care operations, and covered entities and business associates that receive records for those purposes may redisclose them as HIPAA allows, except for proceedings against the patient. HIPAA itself needs no authorization for those purposes, except for psychotherapy notes and other uses that require one. Part 2 records still may not be used in civil, criminal, administrative or legislative proceedings against the patient without consent or a court order. Part 2 programs now follow HIPAA's breach notification rule (no later than 60 calendar days after discovery), the enforcement provisions of 45 CFR part 160 and a complaint route to the HHS Secretary, and compliance with the 2024 rule was required by February 16, 2026.
Comparison table · Reviewed November 14, 2026
AI rules and guidance in US health care: FDA device and decision support guidance, section 1557, ONC certification and Medicare Advantage
Of the federal instruments on AI in health care compared here, the binding ones are 45 CFR 92.210, which bars discrimination through patient care decision support tools, the ONC decision support certification criterion for certified health IT, and the Medicare Advantage rules on medical necessity determinations. The ONC rule of October 28, 2026 removes the criterion's source attribute ('model card') and risk management requirements from December 28, 2026. FDA's AI-enabled device guidance is still a January 2025 draft, and its clinical decision support guidance, reissued January 29, 2026, is nonbinding. CMS told Medicare Advantage plans in a February 6, 2024 memo that algorithms or AI alone cannot be the basis to deny admission, and in April 2025 it did not finalize proposed AI guardrails.
Comparison table · Reviewed November 14, 2026
CMS programs with security and interoperability conditions compared
From the EHR reporting period in CY 2026, eligible hospitals and CAHs in the Medicare Promoting Interoperability Program must attest yes to a security risk analysis and to security risk management, and yes to an annual self-assessment using all eight 2025 SAFER Guides. The CY 2027 physician fee schedule final rule removes the Security Risk Analysis measure from the MIPS Promoting Interoperability category starting with the CY 2027 performance period. Hospital Conditions of Participation require medical record systems that protect the security of record entries and an emergency communication plan reviewed at least every 2 years, without mentioning cybersecurity. Medicare Advantage organizations, Medicaid and CHIP programs and plans, and QHP issuers on the federally-facilitated exchanges must have Provider Access, Payer-to-Payer and Prior Authorization APIs in 2027.
Comparison table · Reviewed November 14, 2026
Health data exchange standards named in federal rules
As of 2026-11-14, ONC certification lists USCDI Version 3 (adoption of Version 1 expired on January 1, 2026) and HL7 FHIR Release 4.0.1 as the API base standard. CMS-0057-F requires Medicare Advantage organizations' Provider Access, Payer-to-Payer and Prior Authorization APIs to conform to FHIR-based standards at 45 CFR 170.215 beginning January 1, 2027, but only recommends the Da Vinci and CARIN implementation guides. X12 278 remains the HIPAA standard for prior authorization; under enforcement discretion announced February 28, 2024, HHS will not take enforcement action against covered entities that do not use it as part of a FHIR prior authorization process under CMS-0057-F. CMS-0057-F lets payers use TEFCA exchange where it meets the rule, but says TEFCA participation does not necessarily do so.
Comparison table · Reviewed November 14, 2026
Health data interoperability programs compared: TEFCA, certification, information blocking and CMS APIs
TEFCA rules in 45 CFR part 172 set qualifications for QHINs and let ASTP/ONC or the RCE suspend or terminate them. Information blocking rules have applied to providers, developers of certified health IT, exchanges and networks since April 5, 2021, with OIG civil money penalties of up to $1,000,000 per violation for developers, networks and exchanges and, since the July 1, 2024 rule, CMS disincentives for providers. CMS-0057-F requires Medicare Advantage organizations to run Provider Access, Payer-to-Payer and Prior Authorization APIs from January 1, 2027. An ONC final rule of October 28, 2026 removes 14 certification criteria.
Comparison table · Reviewed November 14, 2026
Health privacy and breach penalties compared: HIPAA tiers, part 2, the FTC rule and state attorneys general
HIPAA civil money penalties run in four tiers by culpability; at the 2025 inflation-adjusted amounts HHS still uses in 2026, the per-violation range is $145 to $73,011 for violations the entity did not know about and $73,011 to $2,190,294 for uncorrected willful neglect; the regulation's calendar-year cap is $2,190,294 for every tier, although HHS's 2019 enforcement discretion notice set lower annual limits for the first three tiers. Since the February 2024 rule, 42 CFR part 2 violations carry the same HIPAA penalty structure, at $103 to $1,538,970 in the 2025 table. The FTC's Health Breach Notification Rule treats a violation as a breach of an FTC trade regulation rule, with a maximum of $53,088 per violation for penalties assessed after January 17, 2025. State attorneys general can sue under HITECH for up to $100 per violation, capped at $25,000 a year for identical violations.
Comparison table · Reviewed November 14, 2026
HHS Healthcare and Public Health Cybersecurity Performance Goals: the 10 essential and 10 enhanced goals
HHS lists 20 voluntary Cybersecurity Performance Goals for the Healthcare and Public Health sector on its HHS Cyber Gateway: 10 essential goals, which set a floor of safeguards against cyber attacks, and 10 enhanced goals, which help organizations mature their capabilities against additional attack vectors. The essential goals cover known vulnerabilities, email security, multifactor authentication, basic training, strong encryption, revoking departing workers' credentials, basic incident planning, unique credentials, separate privileged accounts and vendor requirements. The enhanced goals cover asset inventory, third-party vulnerability disclosure and incident reporting, testing and mitigation, threat detection, network segmentation, central log collection, incident response plans and configuration management. HHS lists one or more matching CISA performance goal IDs for each goal.
Comparison table · Reviewed November 14, 2026
HIPAA individual rights compared: response deadlines, extensions and fees
Under the HIPAA Privacy Rule a covered entity must act on a request for access no later than 30 days after receipt, and on a request for amendment or for an accounting of disclosures no later than 60 days after receipt; each allows one extension of no more than 30 days with a written statement of reasons. Access copies may carry only a reasonable, cost-based fee, and the first accounting in any 12-month period is free. Requests for restrictions and confidential communications have no deadline in the rule text, but a covered entity must agree to restrict a disclosure to a health plan for payment or health care operations, not otherwise required by law, about an item or service paid for in full, and covered health care providers must accommodate reasonable requests for confidential communications (health plans must when the individual states that disclosure could endanger them).
Comparison table · Reviewed November 14, 2026
HIPAA Security Rule: current rule against the January 2025 proposal
The HIPAA Security Rule in force still treats many implementation specifications, including encryption, as addressable, and its administrative and technical safeguards name no asset inventory, vulnerability scanning or penetration testing. The proposed rule published January 6, 2025 would remove the addressable distinction and require encryption of ePHI at rest and in transit, multi-factor authentication, restoration of critical systems within 72 hours and a compliance audit every 12 months. As of 2026-11-14 it is still a proposal: the latest Unified Agenda entry lists it as a long-term action with final action dated 07/00/2027.
Comparison table · Reviewed November 14, 2026
HIPAA, the FTC Health Breach Notification Rule and Washington's My Health My Data Act compared
HIPAA covers health plans, clearinghouses, providers that transact electronically and their business associates; the FTC Health Breach Notification Rule covers vendors of personal health records and related entities that HIPAA does not. Both require breach notice to individuals no later than 60 calendar days after discovery. Washington's My Health My Data Act covers consumer health data outside HIPAA, has no breach notification section, and makes a violation an unfair or deceptive act under the state Consumer Protection Act, under which an injured person may sue for damages.
Comparison table · Reviewed November 14, 2026
Hospital price transparency and Transparency in Coverage compared
Hospitals must post one machine-readable file of all standard charges, updated at least once a year, plus at least 300 shoppable services in a consumer-friendly display or an online price estimator (45 CFR part 180). Health plans and issuers must post in-network rate, out-of-network allowed amount and prescription drug files monthly and give members cost-sharing estimates (45 CFR 147.211 and 147.212). The hospital rules gained percentile allowed amounts, Type 2 NPIs and a named-official attestation from January 1, 2026, with CMS enforcement from April 1, 2026. The October 6, 2026 Transparency in Coverage rule applies from March 6, 2027, with in-network and allowed-amount files then posted quarterly, and adds contextual files, a .txt file and a website footer link from September 6, 2027.
Comparison table · Reviewed November 14, 2026
How fast patients and payers must get health data: HIPAA access, information blocking and CMS API deadlines compared
A HIPAA covered entity has up to 30 days (plus one 30-day extension) to act on a patient's access request, while CMS requires Medicare Advantage organizations, state Medicaid and CHIP agencies and QHP issuers on individual market Federally-facilitated Exchanges to put claims and clinical data in the Patient Access API no later than one business day after a claim is processed or data are received. From January 1, 2027, Medicare Advantage organizations must also show prior authorization information within 1 business day and answer Provider Access and Payer-to-Payer API requests within 1 business day. Under the information blocking manner exception an actor that cannot use the requested manner must use an alternative one without unnecessary delay, with no number of days stated, while an actor declining a request as infeasible must say why in writing within ten business days.
Comparison table · Reviewed November 14, 2026
Medical device cybersecurity duties compared: manufacturers and hospitals
Section 524B of the FD&C Act requires anyone who submits a premarket application for a cyber device to give FDA a plan to monitor and address postmarket vulnerabilities, maintain processes for cybersecurity updates and patches, and provide a software bill of materials. FDA's premarket guidance, issued February 3, 2026, and its 2016 postmarket guidance add nonbinding recommendations, such as penetration test reports and 30-day and 60-day steps for vulnerabilities with uncontrolled risk. On the hospital side, HIPAA covered entities must run an accurate and thorough risk analysis of the ePHI they hold, and FDA recommends that health care delivery organizations work closely with manufacturers when they patch or update devices.
Comparison table · Reviewed November 14, 2026
Medicare and DEA telehealth flexibilities: what is extended, and to when
Under the Consolidated Appropriations Act, 2026, Medicare's main telehealth flexibilities (no geographic limits, the expanded list of originating sites, more practitioner types, non-behavioral telehealth from rural health clinics and federally qualified health centers, and audio-only telehealth to the home for any service) run through December 31, 2027, and the in-person requirements for telehealth mental health services are delayed to January 1, 2028. DEA's temporary rule letting practitioners prescribe schedule II-V controlled substances by telemedicine without an in-person medical evaluation runs to the end of December 31, 2026, as of 2026-11-14. Two permanent DEA rules, for opioid use disorder medications and for VA patients, took effect on December 31, 2025.
Comparison table · Reviewed November 14, 2026
Medicare and Medicaid enrollment revalidation and change reporting deadlines compared
Most Medicare providers and suppliers revalidate their enrollment every 5 years and DMEPOS suppliers every 3 years; once CMS sends a revalidation notice, the application is due within 60 calendar days. Physicians, practitioners and most other providers report a change of ownership, an adverse legal action or a practice location change within 30 days and all other changes within 90 days, while DMEPOS suppliers report any change within 30 days. State Medicaid agencies revalidate every provider at least every 5 years, and providers disclose a change in ownership within 35 days.
Comparison table · Reviewed November 14, 2026
Prior authorization decision times and API duties by payer type (CMS-0057-F)
Under the CMS-0057-F rules, Medicare Advantage organizations, state Medicaid and CHIP agencies, and Medicaid and CHIP managed care plans must decide standard prior authorization requests within 7 calendar days and expedited requests within 72 hours, from January 1, 2026 or the rating period starting on or after that date. Qualified health plan issuers on Federally-facilitated Exchanges were left out of the shorter timeframes; CMS states that under existing rules they must give notice within 15 days for standard and 72 hours for expedited requests. All six payer types must run a Prior Authorization API from January 1, 2027, or the rating period or plan year beginning on or after that date.
Comparison table · Reviewed November 14, 2026
Recurring reporting and file-update deadlines for hospitals, clinicians and health plans
HIPAA covered entities report the year's breaches affecting fewer than 500 people to HHS within 60 days after the calendar year ends, MIPS data is due March 31 after the performance period, and Medicare Advantage organizations post prior authorization metrics and report Patient Access API usage by March 31 each year from 2026. Health plans update Transparency in Coverage files monthly until the October 2026 rule applies from March 6, 2027, when in-network rate and allowed amount files move to quarterly. Hospitals update price transparency files at least once a year.
Comparison table · Reviewed November 14, 2026
Using patient data for research and analytics: HIPAA and Common Rule routes compared
A HIPAA covered entity can use or disclose patient data for research without each patient's authorization if it de-identifies the data, by removing 18 kinds of identifiers or by an expert's documented finding that the risk of identification is very small, if it shares a limited data set under a data use agreement for research, public health or health care operations, or if an IRB or privacy board approves a waiver of authorization. Otherwise research needs a signed authorization, whose expiration may read "end of the research study", "none" or similar language. Under the Common Rule, secondary research on HIPAA-regulated information for health care operations, research or public health is exempt, broad consent is an alternative for storing and reusing identifiable data, and an IRB may waive consent only if it finds and documents, among other criteria, no more than minimal risk and that the research could not practicably be carried out without the waiver.
Government
Comparison table · Reviewed November 14, 2026
CISA binding operational and emergency directives: what each requires and whether it is in force
BOD 26-04, issued June 10, 2026, revokes BOD 19-02 and BOD 22-01 and sets risk-based remediation timelines, with clocks that start when CISA adds a vulnerability to the KEV catalog or the agency identifies it on an asset, whichever comes first. BOD 26-02 requires agencies to decommission all identified end-of-support edge devices within 18 months of issuance. CISA formally closed ten emergency directives issued between 2019 and 2024, announced January 8, 2026; ED 24-01, 25-02, 25-03, 26-01 and 26-03 remain on its Active Directives list with no Closed label as of 2026-11-14.
Comparison table · Reviewed November 14, 2026
Cloud security baselines by level: FedRAMP, FedRAMP 20x classes, DoW (DoD) cloud impact levels and GovRAMP
FedRAMP Rev5 sets Low, Moderate and High baselines on NIST SP 800-53 Rev. 5, assessed by FedRAMP Recognized independent assessment services. FedRAMP 20x Classes A, B and C are available now and Class D will be developed in Phase 4; FedRAMP says classes describe how much assurance information a provider supplies and are not one-for-one replacements for impact levels. The Cloud Service Provider SRG's Impact Levels 2, 4, 5 and 6 start from FedRAMP Moderate (Level 2), Moderate or High (Level 4) or High (Levels 5 and 6); Levels 4 to 6 add FedRAMP+ controls and CNSSI 1253 overlays, and Levels 5 and 6 add national security system controls. GovRAMP's verification steps run from Core (60 controls, checked by its program office) through Ready (80 controls) to Authorized (300+ controls, 3PAO-assessed and government-approved).
Comparison table · Reviewed November 14, 2026
CMMC levels compared: requirements, assessments and affirmations under 32 CFR part 170
CMMC Level 1 uses the 15 FAR 52.204-21 safeguarding requirements and an annual self-assessment; Level 2 is identical to the 110 requirements of NIST SP 800-171 Revision 2 and is assessed every three years by the contractor or a C3PAO; Level 3 adds 24 selected NIST SP 800-172 requirements assessed by DCMA DIBCAC. Every level needs an affirmation in SPRS. Phase 1 began when the DFARS rule took effect on November 10, 2025, and from November 10, 2028 the clause is used when the program office or requiring activity determines that contractor systems will process, store or transmit FCI or CUI. As of 2026-11-14, DFARS Class Deviation 2026-O0025, Revision 3 tells contracting officers to remove or revise CMMC requirements under a July 13, 2026 Department of War CIO memorandum that suspends the November 2026 Phase 2 transition.
Comparison table · Reviewed November 14, 2026
Criminal justice and federal tax data: CJIS Security Policy and IRS Publication 1075 compared
The CJIS Security Policy (version 6.1, June 25, 2026) applies to every entity that accesses criminal justice information or runs systems that process it; IRS Publication 1075 (Rev. 11-2021) applies to agencies that receive federal tax information. Both require multi-factor authentication for privileged and non-privileged accounts and encryption built on FIPS standards: FIPS 140-3 certified modules or FIPS 197 (AES) under CJIS, the latest FIPS 140 validated encryption under Publication 1075. Incident clocks differ: CJIS requires personnel to report suspected incidents internally within one hour of discovery, while Publication 1075 requires a report to TIGTA within 24 hours, with the IRS Office of Safeguards notified concurrently.
Comparison table · Reviewed November 14, 2026
Cybersecurity and data terms in federal grants: Uniform Guidance, DHS and NIH compared
Under the Uniform Guidance (2 CFR part 200, as revised effective October 1, 2024), every recipient and subrecipient must take reasonable cybersecurity and other measures to safeguard protected PII and other sensitive information, may not spend award funds on covered telecommunications or video surveillance equipment or services under section 889, and must keep award records for three years from the final financial report. Agencies add their own terms: DHS's FY 2026 standard terms require a public privacy policy from recipients that collect PII and a research security program certification, with a cybersecurity element, from research institutions receiving federal R&D science and engineering support "in excess of $50 million per year". Since January 25, 2025, NIH has expected users of its controlled-access genomic data to attest to NIST SP 800-171 and its repositories to adopt the NIST SP 800-53 Moderate baseline.
Comparison table · Reviewed November 14, 2026
Federal agency zero trust, logging and asset visibility duties: deadlines compared
OMB M-22-09 set zero trust goals for the end of fiscal year 2024 and is still cited: in OMB M-26-18 (August 31, 2026) as existing OMB policy, in BOD 26-02 and in the FY 2026 and FY 2027 CIO FISMA metrics. OMB M-26-14 (May 22, 2026) rescinded M-21-31 and requires an Agency Logging Plan within 90 days of the release of CISA's Logging Reference Architecture (publish date August 20, 2026, per CISA), then logging maturity Level 1, 2 and 3 within 120, 180 and 320 days of that release. BOD 23-01 requires asset discovery every 7 days and vulnerability enumeration every 14 days; BOD 26-04 sets remediation timelines from 3 days to 60 days or fix on system upgrade; BOD 26-02 requires end-of-support edge devices to be decommissioned within 12 and 18 months of its issuance on February 5, 2026.
Comparison table · Reviewed November 14, 2026
Federal AI governance duties compared: Chief AI Officers, boards, inventories, high-impact AI and LLM contracts
OMB M-25-21 required each agency to retain or designate a Chief AI Officer within 60 days of April 3, 2025 and to post a compliance plan within 180 days, each CFO Act agency to convene an AI governance board within 90 days, AI use case inventories at least annually, and documented minimum practices for high-impact AI within 365 days. M-25-22 applies its AI acquisition rules to contracts under solicitations issued on or after the date 180 days after issuance, and M-26-04 requires LLM solicitations and orders issued after December 11, 2025 to include Unbiased AI Principles terms, with agency policies updated by March 11, 2026. Executive Order 14434 of September 29, 2026 directs agencies, to the maximum extent permitted by law, to use "Super Intelligence" and "SI" in place of "Artificial Intelligence" and "AI" in official correspondence, public communications, websites, reports, policy documents and other non-statutory documents.
Comparison table · Reviewed November 14, 2026
Federal cloud and AI buying rules compared: M-25-22, M-26-04, M-24-15, OneGov and the FAR part 39 proposal
OMB M-25-22 (April 3, 2025) governs agency AI acquisition; agency processes should ensure contracts permanently bar use of non-public agency data and outputs to further train publicly or commercially available AI without explicit agency consent. M-26-04 (December 11, 2025) requires new solicitations and orders for large language models to include contract terms on two Unbiased AI Principles. M-24-15 (July 25, 2024) requires agencies to obtain and maintain a FedRAMP authorization for in-scope cloud services. GSA's OneGov negotiates government-wide software agreements, and a FAR Council proposed rule of June 23, 2026 would retitle FAR part 39 to cover information and communication technology.
Comparison table · Reviewed November 14, 2026
Federal cloud and SaaS security requirements compared
BOD 25-01 makes federal civilian agencies inventory in-scope cloud tenants, run CISA's SCuBA assessment tools and apply the mandatory SCuBA policies, with deadlines in 2025. M-24-15 requires FedRAMP authorization for in-scope cloud services, including SaaS, and a presumption that an existing FedRAMP package is adequate. FedRAMP's 2026 20x Class B rules require providers to send Ongoing Certification Reports every 3 months and agencies to review them, required to maintain certification from January 1, 2027. The DoD SRG requires a SaaS offering used by DoD to be assessed for its own provisional authorization, even on an authorized IaaS or PaaS, and M-26-14 applies logging duties to systems third parties operate for agencies, with deadlines counted from the release of CISA's Logging Reference Architecture, published August 20, 2026.
Comparison table · Reviewed November 14, 2026
Federal cyber grants for state, local and Tribal governments: SLCGP and TCGP compared
Both programs rest on 6 U.S.C. 665g, which defines an eligible entity as a State or a Tribal government and authorized appropriations of $200 million, $400 million, $300 million and $100 million for FY 2022 to FY 2025. CISA's pages put FY 2025 funding at $91.7 million under the State and Local Cybersecurity Grant Program and $12,164,971 under the Tribal Cybersecurity Grant Program, each with a 40 percent non-federal cost share (30 percent for multi-entity projects). The FY 2025 SLCGP listing calls FY 2025 the final year of funding, and Pub. L. 119-75 moved the section's termination date to September 30, 2026.
Comparison table · Reviewed November 14, 2026
Federal electronic records duties: email, texts, collaboration platforms and cloud
Federal employees who use a personal or other non-official messaging account for agency business must copy their official account or forward a complete copy within 20 days (44 U.S.C. 2911). NARA's rules in 36 CFR part 1236 require email records to keep sender, addressees, date and integral attachments, and bar using system backups as the recordkeeping system. Under GRS 6.1 the email and messages of Capstone officials are permanent, while those of most other staff may be deleted at 7 years, and OMB and NARA memorandum M-23-07 set June 30, 2024 as the date by which agencies must manage permanent records electronically.
Comparison table · Reviewed November 14, 2026
Federal privacy compliance documents: PIAs, SORNs, routine uses and matching agreements
A federal agency must complete a privacy impact assessment before it develops or procures IT that handles information in identifiable form (E-Government Act, section 208). When it creates or changes a system of records it publishes a SORN in the Federal Register, which takes effect on publication except for new or changed routine uses, which need at least 30 days; it reports the proposal to OMB and Congress at least 30 days before sending the notice to the Federal Register. Computer matching agreements cannot take effect until 30 days after they go to Congress, last no more than 18 months and can be renewed for not more than one additional year, and the annual matching activity report is due to OMB by June 1.
Comparison table · Reviewed November 14, 2026
Federal public sign-in and identity assurance: M-26-18, NIST SP 800-63-4 and Login.gov
OMB M-26-18 (August 31, 2026) requires agencies to offer Login.gov as a sign-on option on in-scope public-facing websites within two years, and within one year on High Impact Service Provider websites, or to send OMB a notice. NIST SP 800-63-4 (July 2025) defines three identity, authentication and federation assurance levels and sets no compliance date itself; M-26-18 gives agencies 240 days to run its risk management process. Login.gov offers authentication only, basic identity verification aligned to IAL1, and enhanced verification with a facial match at IAL2.
Comparison table · Reviewed November 14, 2026
Federal software security attestation after M-26-05: what replaced M-22-18 and M-23-16
OMB M-26-05, dated January 23, 2026, rescinded M-22-18 and its companion M-23-16. 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; they may choose to use the Secure Software Development Attestation Form and may adopt contract terms that require a current SBOM on request. NIST SP 800-218 (SSDF Version 1.1, February 2022) is final; Version 1.2 (SP 800-218 Rev. 1) is an initial public draft whose comment period closed January 30, 2026. CISA's Secure by Design Pledge is voluntary and not legally binding.
Comparison table · Reviewed November 14, 2026
Federal zero trust models compared: OMB M-22-09, CISA ZTMM 2.0 and the DoD strategy
OMB M-22-09 is addressed to the heads of executive departments and agencies and set zero trust goals for the end of FY2024, aligned with five pillars taken from CISA. CISA's Zero Trust Maturity Model 2.0 presents itself as one of many paths for agencies' zero trust plans: five pillars, three cross-cutting capabilities, and a journey from a Traditional starting point through the Initial, Advanced and Optimal stages. The DoD Zero Trust Strategy uses seven pillars and requires DoD Components to reach the Target Level outcomes by the end of FY2027.
Comparison table · Reviewed November 14, 2026
FISMA reporting: who reports what, to whom and when
Under FISMA 2014, each agency reports annually on the effectiveness of its information security program, its Inspector General or an independent auditor evaluates that program each year, and OMB reports to Congress by March 1 of each year. Agencies must notify the named congressional committees of a major incident not later than 7 days after there is a reasonable basis to conclude it occurred. For FY2026, CIO and SAOP FISMA metrics were due through CyberScope on October 30, 2026; OMB's memoranda page lists no FY2026 edition of its annual FISMA guidance memorandum as of 2026-11-14.
Comparison table · Reviewed November 14, 2026
Government cloud authorization programs compared: FedRAMP, GovRAMP, TX-RAMP and the DoD cloud SRG
FedRAMP is set in law at 44 U.S.C. 3608 for cloud services used by federal agencies; FedRAMP 20x took applications for Classes A to C from August 2026, and FedRAMP will no longer accept applications for new Rev5 certifications from June 11, 2027. GovRAMP is a nonprofit whose participating governments and education institutions adopt it, while TX-RAMP applies to Texas state agencies, institutions of higher education and public community colleges, and accepts FedRAMP Low or Moderate evidence. DISA's Cloud Service Provider SRG (Version 1, Release 7, June 2026) builds on FedRAMP baselines, requiring the FedRAMP High baseline plus DoD FedRAMP+ controls for impact levels 5 and 6.
Comparison table · Reviewed November 14, 2026
OMB cybersecurity, identity, AI and IT memoranda listed on OMB's memoranda page
This table covers eight memoranda listed on OMB's memoranda page that deal with cybersecurity, identity, software, logging, AI or IT, issued between April 3, 2025 and August 31, 2026. Four replace earlier policy: M-25-21 and M-25-22 rescind and replace M-24-10 and M-24-18, M-26-05 rescinds M-22-18 and M-23-16, and M-26-14 rescinds M-21-31. Dated duties include a post-quantum migration plan no later than 120 days from the date of M-26-15, and Login.gov on all in-scope public websites within two years under M-26-18, or a notice to OMB.
Comparison table · Reviewed November 14, 2026
Prohibited technology clauses in federal contracts: Kaspersky, section 889, TikTok and FASCSA orders
Four FAR clauses bar federal contractors from supplying or using named technology: Kaspersky Lab (52.204-23), section 889 covered telecommunications and video surveillance equipment or services, including Huawei and ZTE equipment (52.204-25), TikTok and other ByteDance applications (52.204-27) and sources and articles named in FASCSA orders (52.204-30). The section 889 clause has the shortest report deadline, one business day; the Kaspersky and FASCSA clauses allow 3 business days, each followed by further information within 10 business days, and the ByteDance clause sets no reporting duty. From August 13, 2020, section 889 also bars agencies from contracting with an entity that uses covered equipment, whether or not the use is in performance of a Federal contract; that part is not flowed down to subcontracts.
Comparison table · Reviewed November 14, 2026
Public sector web accessibility rules compared: Section 508, ADA Title II and HHS section 504
Federal agencies have had to meet WCAG 2.0 Level A and AA under the Section 508 Standards since January 18, 2018. State and local governments must meet WCAG 2.1 Level A and AA for web content and mobile apps under the ADA Title II rule from April 26, 2027 (50,000 or more people) or April 26, 2028. Recipients of HHS funding must meet WCAG 2.1 Level A and AA under the section 504 rule from May 11, 2027 (15 or more employees) or May 10, 2028. Interim final rules effective April 20 and May 7, 2026 set those later dates.
Cross-sector
Comparison table · Reviewed November 14, 2026
AI governance rules and frameworks compared: NIST, OMB, Colorado and the EU AI Act
The NIST AI RMF 1.0 and its Generative AI Profile are voluntary, OMB memoranda M-25-21 and M-25-22 set requirements for federal agencies using and buying AI, and Colorado SB 26-189 and the EU AI Act are binding law. The EU AI Act reaches providers outside the EU that place AI systems on the EU market, and providers and deployers whose system output is used in the EU; its Annex III high-risk rules apply from December 2, 2027. Colorado SB 26-189, signed May 14, 2026, repeals and reenacts SB 24-205, and its developer documentation duty starts January 1, 2027.
Comparison table · Reviewed November 14, 2026
AI rules and guidance by sector compared: banking, health care, federal agencies and Colorado
Banks have new interagency model risk management guidance (Fed SR 26-2, OCC Bulletin 2026-13, April 17, 2026) that is not enforceable and leaves generative and agentic AI out of scope. In health care, 45 CFR 92.210 requires covered entities to make reasonable efforts to identify and mitigate discrimination risk in patient care decision support tools, while ONC's October 28, 2026 rule removes the model card and risk management requirements from its decision support certification criterion from December 28, 2026. Federal agencies must apply minimum practices to high-impact AI under OMB M-25-21 and buy AI under M-25-22, and Colorado SB 26-189 sets developer and deployer duties for automated decision-making in consequential decisions across sectors.
Comparison table · Reviewed November 14, 2026
Biometric privacy laws compared: Illinois, Texas, Washington, Colorado and the FTC
Illinois BIPA gives a private right of action, with $1,000 or $5,000 per violation, and requires written notice and a written release before collection and destruction within 3 years of the last interaction at most. Texas requires notice and consent, destruction by the first anniversary of the date the purpose expires, and lets the attorney general seek up to $25,000 per violation. Washington, where only the attorney general enforces, and Colorado also limit sale and set retention rules, Colorado deleting at most 24 months after the last interaction. The FTC's policy statement sets no fixed rule but lists biometric practices it will scrutinize under Section 5 of the FTC Act.
Comparison table · Reviewed November 14, 2026
Board and senior-official cybersecurity reporting duties compared
Most of these rules set an annual minimum: the NYDFS CISO and the FTC Safeguards Rule's Qualified Individual report in writing at least annually, national banks and federal savings associations under the OCC guidelines report to the board or a board committee at least annually, and NCUA's guidelines say federally insured credit unions should do the same. Federal agency CIOs report annually to the agency head on the effectiveness of the information security program, and each agency files an annual report that goes to congressional committees and the Comptroller General, among others. Regulation S-K Item 106(c) works the other way: registrants describe in their annual report on Form 10-K how the board oversees cybersecurity risk and how it is informed.
Comparison table · Reviewed November 14, 2026
Children's and student data rules compared
The amended COPPA Rule took effect June 23, 2025, with compliance required by April 22, 2026: operators of child-directed services, or those with actual knowledge they collect from a child under 13, need verifiable parental consent, separate consent for third-party disclosures not integral to the service, a written information security program and a written data retention policy. FERPA governs education records held by institutions funded under Department of Education programs, and lets an outsourced contractor receive records as a school official if it is under the institution's direct control. PPRA limits required surveys and examinations on protected topics and requires school districts to adopt policies on using student data for marketing. Illinois's Student Online Personal Protection Act adds duties for K-12 online services, including breach notice to the school within 30 calendar days.
Comparison table · Reviewed November 14, 2026
Cloud storage under export controls and the DOJ Data Security Program: EAR, ITAR and 28 CFR part 202
Under both the EAR and the ITAR, sending or storing unclassified controlled technology or technical data is not an export if it is end-to-end encrypted with FIPS 140-2 (or successor) modules or equivalent means and is not intentionally stored in a Country Group D:5 country (EAR) or a country proscribed in 22 CFR 126.1 (ITAR); access to data encrypted that way is not a release. The Justice Department's Data Security Program works the other way: bulk U.S. sensitive personal data is covered even when encrypted, cloud-computing services count as vendor agreements, and such agreements with China, Cuba, Iran, North Korea, Russia, Venezuela or covered persons are allowed only under CISA's security requirements. Its data compliance program, audit and reporting duties applied from October 6, 2025.
Comparison table · Reviewed November 14, 2026
Data location and residency requirements compared
FedRAMP's Class D parameters, the DoD Cloud Computing SRG and IRS Publication 1075 keep in-scope data in the United States, its territories or places under U.S. jurisdiction (the SRG allows exceptions the authorizing official approves), and Publication 1075 also bars offshore access to and maintenance of systems holding federal tax information. The CJIS Security Policy allows criminal justice information to be stored only in cloud environments within APB-member countries, which include Canada. The DOJ rule at 28 CFR part 202 is not a storage-location rule: it governs covered data transactions that give six countries of concern or covered persons access to government-related or bulk U.S. sensitive personal data, prohibiting data brokerage with them and allowing vendor, employment and investment agreements only under CISA security requirements.
Comparison table · Reviewed November 14, 2026
Encryption requirements at rest and in transit compared
The FTC Safeguards Rule and the NYDFS Cybersecurity Regulation require encryption at rest and in transit over external networks, with approved compensating controls where encryption is infeasible (FTC: at rest or in transit; NYDFS: at rest only). The current HIPAA Security Rule makes encryption addressable rather than required, but breach notification applies only to unsecured data, so encryption that meets HHS guidance, with the key not breached, takes data outside it; the proposed update would require encryption but is not final as of 2026-11-14. FIPS 140-3 applies to federal agencies that use cryptography to protect sensitive information, and IRS Publication 1075 requires the latest FIPS 140 validated encryption for federal tax information; the CJIS Security Policy requires FIPS 140-3 certified modules or FIPS 197 (AES) for criminal justice information outside physically secure locations.
Comparison table · Reviewed November 14, 2026
Identity proofing and authentication levels: NIST SP 800-63-4 and the rules that use them
NIST SP 800-63-4 defines three identity assurance levels (IAL1 to IAL3), three authentication assurance levels (AAL1 to AAL3) and three federation assurance levels (FAL1 to FAL3); AAL3 requires a phishing-resistant public-key authenticator with a non-exportable private key. OMB M-26-18 sets no single level and gives agencies 240 days to run a Digital Identity Risk Management process, including selection of assurance levels, for public-facing services, consistent with NIST SP 800-63-4. IRS Publication 1075 requires IAL2 and AAL2 for public-facing systems with federal tax information and AAL2 devices for remote access, and the CJIS Security Policy sets assessment criteria for providers authenticating at AAL2. The FTC Safeguards Rule and NYDFS section 500.12 require multi-factor authentication without naming a NIST level.
Comparison table · Reviewed November 14, 2026
Incident and breach reporting deadlines compared
The clocks run from one hour (federal civilian agencies to CISA) and 36 hours (banks to their federal regulator) to 72 hours (NYDFS and NCUA), four business days (SEC Form 8-K Item 1.05), 30 days (FTC Safeguards Rule) and 60 calendar days (HIPAA and the FTC Health Breach Notification Rule). Most clocks start when the organization determines or discovers the incident, not when it began. CIRCIA reporting to CISA is not yet required as of 2026-11-14, because the final rule has not been issued.
Comparison table · Reviewed November 14, 2026
Incident response frameworks compared: NIST SP 800-61 Rev. 3, CISA playbooks and federal notification
NIST SP 800-61 Rev. 3 (April 2025) replaces the incident life cycle of Rev. 2 with the six CSF 2.0 Functions and may be used voluntarily by nongovernmental organizations. CISA's 2021 federal playbooks, for civilian executive branch agencies, still follow the Rev. 2 phases: preparation, detection and analysis, containment, eradication and recovery, and post-incident activity. Civilian agencies must notify CISA within one hour of identifying an incident under the 2017 Federal Incident Notification Guidelines, which CISA says it is updating for a new reporting form published November 9, 2026.
Comparison table · Reviewed November 14, 2026
Multi-factor authentication requirements compared
The FTC Safeguards Rule and the NYDFS Cybersecurity Regulation both require MFA for any individual accessing an information system, unless equivalent or more secure controls are approved in writing; NYDFS entities with a limited exemption need MFA only for remote access and privileged accounts. For federal agencies, Executive Order 14028 requires MFA to the maximum extent consistent with law, and OMB M-22-09 requires phishing-resistant MFA for staff, contractors and partners. IRS Publication 1075 requires MFA for privileged and non-privileged accounts on systems handling federal tax information. The current HIPAA Security Rule does not explicitly require MFA; the proposed update would, but as of 2026-11-14 it has not been finalized.
Comparison table · Reviewed November 14, 2026
Penetration testing and vulnerability scanning requirements compared
The FTC Safeguards Rule requires annual penetration testing and vulnerability assessments at least every six months unless the institution has effective continuous monitoring, and NYDFS Part 500 requires penetration testing at least annually by a qualified internal or external party. The proposed HIPAA Security Rule update would require scans at least every six months and penetration testing at least every 12 months, but it is not final as of 2026-11-14. IRS Publication 1075 sets vulnerability scans every 30 days and penetration testing every 3 years for the FTI environment. CISA BOD 26-04, which replaced BOD 22-01 on June 10, 2026, sets remediation deadlines of 3, 14 or 60 calendar days, or the next system upgrade, for federal civilian agencies, depending on exposure, KEV listing, automatability and technical impact.
Comparison table · Reviewed November 14, 2026
Post-quantum cryptography deadlines compared: NIST IR 8547, EO 14412, OMB M-26-15 and CNSA 2.0
NIST IR 8547, final in October 2026, says NIST will deprecate quantum-vulnerable signatures (ECDSA, EdDSA, RSA) and key establishment (Diffie-Hellman, MQV, RSA) after 2030 and disallow them under NIST standards and guidelines after 2035. Executive Order 14412 directs OMB guidance requiring federal agencies to move high value assets and high impact systems to post-quantum key establishment by December 31, 2030 and to post-quantum signatures by December 31, 2031, and directs a proposed FAR rule requiring covered contractors to comply with NIST FIPS, including post-quantum FIPS, by December 31, 2030. The replacement algorithms are in FIPS 203, 204 and 205, published August 13, 2024.
Comparison table · Reviewed November 14, 2026
Ransomware payment, sanctions and reporting rules compared
OFAC's 2021 advisory, which says it does not have the force of law, warns that U.S. persons who make or facilitate a ransom payment to a sanctioned person or embargoed jurisdiction can face civil penalties on a strict liability basis, that license applications for such payments face a presumption of denial, and that reporting the attack to law enforcement or CISA as soon as possible is a significant mitigating factor. FinCEN's 2021 advisory reminds financial institutions that a suspicious transaction involving or aggregating to $5,000 or more needs a SAR, and that ransomware-related ones require immediate attention. CIRCIA's 24-hour ransom payment report to CISA is not required until CISA's final rule takes effect, which had not happened as of 2026-11-14. North Carolina and Florida statutes bar state agencies and local governments from paying ransoms.
Comparison table · Reviewed November 14, 2026
Retention periods for records technology teams hold
Retention periods differ by rule and by record: HIPAA Security Rule documentation is kept 6 years, Bank Secrecy Act records 5 years and hospital medical records at least 5 years. Broker-dealers keep core books and records at least 6 years and Regulation S-P records of unauthorized access to customer information 3 years, while NYDFS Part 500 sets 5 years for transaction-reconstruction records and 3 years for cybersecurity audit trails. Federal agencies follow NARA's General Records Schedules, and OMB M-26-14 (May 22, 2026) requires agency logs to stay searchable for at least 6 months and retrievable for a year. The FTC Safeguards Rule works the other way, with a disposal deadline 2 years after customer information was last used, subject to exceptions.
Comparison table · Reviewed November 14, 2026
Security frameworks compared: who must use them and how they are checked
Only some of these are required by rule: federal agencies must use NIST SP 800-53 controls to meet FIPS 200, DoD contractors with covered contractor information systems must apply NIST SP 800-171 under DFARS 252.204-7012, and CMMC applies to DoD contracts involving FCI or CUI. NIST CSF 2.0 may be adopted voluntarily or through government policies and mandates, and CISA describes its Cross-Sector Cybersecurity Performance Goals as voluntary. For CMMC, Level 2 certification assessments are done by an authorized or accredited C3PAO and Level 3 by DCMA DIBCAC, and Level 2 and Level 3 assessments repeat every three years.
Comparison table · Reviewed November 14, 2026
Third-party and service provider risk rules compared
The 2023 interagency guidance on third-party relationships has not been replaced as of 2026-11-14: the OCC, Federal Reserve, FDIC and NCUA proposed replacement guidance on 2026-09-15, and their notice dated November 12, 2026 extended the comment deadline from November 16, 2026 to December 16, 2026. HIPAA, the FTC Safeguards Rule and NYDFS Part 500 set binding duties on selecting and contracting with service providers, and the FTC and NYDFS rules also require periodic assessment based on risk. Federal agencies must obtain and maintain a FedRAMP authorization for in-scope cloud services under OMB M-24-15. NCUA said in its June 2024 report to Congress that it lacks statutory authority over third-party vendors.
Comparison table · Reviewed November 14, 2026
U.S. privacy laws compared: GLBA, HIPAA, FERPA, COPPA, FCRA and state laws
Each federal law covers one sector or kind of data: GLBA covers financial institutions, HIPAA covers health plans, health care clearinghouses and certain health care providers, FERPA covers educational agencies and institutions that receive funds under Department of Education programs, COPPA covers operators of websites and online services directed to children under 13, or that knowingly collect their personal information, and FCRA covers consumer reporting agencies and those who use or furnish consumer reports. Virginia's Consumer Data Protection Act, shown as one example of a state comprehensive law, applies by volume (personal data of at least 100,000 consumers a year, or 25,000 with over half of gross revenue from selling personal data) and exempts GLBA financial institutions and HIPAA covered entities. Virginia's law is enforced only by its Attorney General, while FCRA also allows private suits.
Comparison table · Reviewed November 14, 2026
Vulnerability disclosure policy requirements compared
CISA's BOD 20-01, issued September 2, 2020, requires federal executive branch agencies to publish a vulnerability disclosure policy that authorizes good-faith research and to bring all internet-accessible systems into scope within two years. Under section 524B of the FD&C Act, effective for premarket submissions from March 29, 2023, sponsors of cyber devices must give FDA a plan that includes coordinated vulnerability disclosure. The IoT Cybersecurity Improvement Act of 2020 required NIST to publish disclosure guidelines for agencies and their contractors (NIST SP 800-216, May 2023) and bars agencies from buying or using IoT devices that prevent compliance with them, and Executive Order 14412 (June 22, 2026) directs the FAR Council to propose a rule, within 270 days, under which covered contractors implement VDPs.