# Compliance Deadlines | Why So Many Are Wrong, and How to Check Any One in 10 Minutes

- Link: https://secithub.com/compliance-deadlines-how-to-check/
- Published: 2026-11-19T10:12:18+02:00
- Author: SECITHUB

Reading Time:   5 min

Compliance deadlines are a moving target, and most published content never moves
with them. Search for what any cybersecurity regulation requires today and you will
find confident articles citing dates that have since changed. The author was usually
right on the day they wrote it. The problem is that the date slipped, the page stayed
the same, and someone is now budgeting against it.

This guide is not another list of deadlines that will expire next quarter. It is
a method. We will show why compliance content goes stale, walk through four real
examples where the date moved in 2026, and give you a way to check any deadline 
yourself in about ten minutes. The date on an article matters as much as the claim
inside it.

Table of Contents

 [Toggle](https://secithub.com/compliance-deadlines-how-to-check/#)

 * [Why Compliance Content Goes Stale](https://secithub.com/compliance-deadlines-how-to-check/#Why_Compliance_Content_Goes_Stale)
    - [It Is Written at Peak Urgency](https://secithub.com/compliance-deadlines-how-to-check/#It_Is_Written_at_Peak_Urgency)
    - [It Is Never Revisited](https://secithub.com/compliance-deadlines-how-to-check/#It_Is_Never_Revisited)
    - [The Errors Point One Way](https://secithub.com/compliance-deadlines-how-to-check/#The_Errors_Point_One_Way)
 * [Four Compliance Deadlines That Moved in 2026](https://secithub.com/compliance-deadlines-how-to-check/#Four_Compliance_Deadlines_That_Moved_in_2026)
    - [CMMC Phase II: A Deadline That Passed With Nothing](https://secithub.com/compliance-deadlines-how-to-check/#CMMC_Phase_II_A_Deadline_That_Passed_With_Nothing)
    - [EU AI Act: Right When Written, Wrong Now](https://secithub.com/compliance-deadlines-how-to-check/#EU_AI_Act_Right_When_Written_Wrong_Now)
    - [HIPAA Security Rule: A Proposal Cited as Law](https://secithub.com/compliance-deadlines-how-to-check/#HIPAA_Security_Rule_A_Proposal_Cited_as_Law)
    - [NIST IR 8547: A Draft That Became Final](https://secithub.com/compliance-deadlines-how-to-check/#NIST_IR_8547_A_Draft_That_Became_Final)
 * [How to Check Any Compliance Deadline Yourself](https://secithub.com/compliance-deadlines-how-to-check/#How_to_Check_Any_Compliance_Deadline_Yourself)
 * [Three Questions Before You Trust a Date](https://secithub.com/compliance-deadlines-how-to-check/#Three_Questions_Before_You_Trust_a_Date)
 * [The Real Lesson](https://secithub.com/compliance-deadlines-how-to-check/#The_Real_Lesson)
    - [Sources](https://secithub.com/compliance-deadlines-how-to-check/#Sources)

## **Why Compliance Content Goes Stale**

### **It Is Written at Peak Urgency**

Articles about a regulation appear when a deadline looks imminent. That is when 
readers search and when the topic earns traffic. The piece is accurate the day it
goes out, and it describes a future that still looks fixed.

### **It Is Never Revisited**

Then the deadline slips, as regulatory deadlines often do. Nobody updates the article,
because there is no reward for editing a page to say a rule receded. So it keeps
ranking, and readers keep finding it, now quietly wrong.

### **The Errors Point One Way**

Stale compliance content almost always overstates urgency. The version that says“
you must act now” is the one someone had a commercial reason to write. The result
is a layer of dated, confident, one-directional pressure that can push a security
budget toward the wrong year.

    ```wp-block-verse
    Nobody lied. The article simply stayed still while the rule moved on.
    ```

## **Four Compliance Deadlines That Moved in 2026**

### **CMMC Phase II: A Deadline That Passed With Nothing**

For two years, US defense contractors marked November 10, 2026, as the day third-
party CMMC Level 2 assessments became a condition of award. On July 13, 2026, the
Department of Defense suspended Phase II and all later milestones pending a review.
The November date passed with nothing taking effect. Note the trap in both directions:
the certification requirement is on hold, but the underlying obligations, including
Phase I self-assessment and the existing DFARS clause, remain fully in force.

### **EU AI Act: Right When Written, Wrong Now**

Countless articles state that high-risk AI obligations under Annex III apply from
August 2, 2026. That was correct until mid-2026. The Digital Omnibus on AI moved
those obligations to December 2, 2027, and product-embedded high-risk rules to August
2, 2028. The prohibited practices and general-purpose AI rules that were already
live did not move. Anything telling you high-risk compliance was due in August 2026
was accurate when written and is wrong today.

### **HIPAA Security Rule: A Proposal Cited as Law**

You will read that HIPAA now requires encryption and multi-factor authentication
for health data. It does not. Those changes live in a proposed rule published in
January 2025, which would remove the “addressable” category and make such controls
mandatory. Regulators projected final action for May 2026, then pushed it to July
2027 and moved the rulemaking to long-term actions. The 2003 Security Rule, amended
in 2013, is still the law in force.

### **NIST IR 8547: A Draft That Became Final**

This one moved the other way, which is just as instructive. For almost two years,
people cited NIST’s post-quantum transition dates from a document marked as a draft.
On October 27, 2026, NIST published the final NIST IR 8547. It keeps the headline
dates, deprecating quantum-vulnerable public-key cryptography after 2030 and disallowing
it after 2035, and the final text is stricter than the draft. It is now fair to 
cite those dates as NIST’s position, though they bind federal systems directly and
reach everyone else through procurement.

    ```wp-block-verse
    A date can move later, move earlier, or harden from draft to law. Only the source tells you which.
    ```

## **How to Check Any Compliance Deadline Yourself**

None of the examples above needed inside knowledge. They needed the primary source,
and the sources are public and free. Here is where to look.

 * **EU law:** EUR-Lex carries the text and status of every regulation and directive.
   A reference that starts with “COM” is a proposal, not law.
 * **US federal rules:** the Unified Agenda shows the stage of each rulemaking and
   the date the agency currently projects. A rule listed as “under review” has not
   been published, and those projections change often.
 * **UK law:** the Parliament bills site shows every stage a bill has passed. If
   Royal Assent is missing, it is a bill, not an act.
 * **NIST publications:** the status sits on the publication page. Anything marked“
   ipd” is an initial public draft, not a final requirement.

The pattern is simple. Go one layer below the headline article to the instrument
itself, and read its status line. That single step would correct most of the confident,
dated claims in circulation.

## **Three Questions Before You Trust a Date**

When you meet a compliance claim, three quick questions resolve most of them.

 1. **Is it in force, or proposed?** A proposal is not an obligation, no matter how
    detailed it is or how firmly it is written.
 2. **What is the date of the source?** A claim from a year ago may describe a deadline
    that has since moved. Check when it was written, not just what it says.
 3. **Has anyone actually been penalized?** Real enforcement tells you a regime has
    teeth and a timeline. Its absence can mean the mechanism is still being built.

These questions also protect your budget. Spending to meet a suspended deadline 
wastes money, and so does ignoring a rule that quietly became final. We saw real
enforcement land in our coverage of **_[the Hertz privacy fine](https://secithub.com/hertz-ccpa-fine/)_**,
which shows how fast “proposed” becomes “penalty” once a rule is actually in force.

## **The Real Lesson**

None of this means regulation should be taken less seriously. DORA is in force, 
PCI’s future-dated requirements are now assessed, and the first fines are appearing.
It means the opposite of complacency: treat every date as something to verify, because
the confident ones are the ones most likely to be stale.

Build the ten-minute check into how your team plans. Before a deadline drives a 
purchase or a project, open the primary source and read its status. It is the cheapest
control you will ever run, and it keeps you from spending real money on a date that
moved. For a broader primer on the regimes themselves, see our **_[cybersecurity FAQ](https://secithub.com/guides-insights/cybersecurity-faq-2025/)_**.

    ```wp-block-verse
    Check the source, check its date, check for a real penalty. Then plan.
    ```

![SECITHUB FAQ banner for checking cybersecurity compliance deadlines](https://secithub.
com/wp-content/uploads/2025/12/SECITHUB-FAQ-1.jpg)

**Why are so many compliance deadline articles wrong?**

They are written when a deadline looks imminent and are accurate that day, but they
are rarely updated. When the deadline later slips, the page stays the same and keeps
presenting an old date as current.

**Did CMMC Phase II start in November 2026?**

No. The US Department of Defense suspended CMMC Phase II on July 13, 2026, and the
November 10 date passed with nothing taking effect. Phase I self-assessment and 
existing DFARS obligations remain in force.

**When do EU AI Act high-risk rules apply?**

The Digital Omnibus on AI moved standalone high-risk obligations under Annex III
from August 2, 2026 to December 2, 2027, and product-embedded high-risk rules to
August 2, 2028. Prohibited practices and general-purpose AI rules were not delayed.

**Does HIPAA now require encryption and MFA?**

Not yet. Those requirements are in a proposed rule from January 2025, not final 
law. Final action has been pushed to around July 2027. The existing 2003 Security
Rule remains in force.

**Is NIST IR 8547 final?**

Yes. NIST published the final NIST IR 8547 on October 27, 2026. It deprecates quantum-
vulnerable public-key cryptography after 2030 and disallows it after 2035, and the
final version is stricter than the 2024 draft.

**How can I verify a compliance deadline myself?**

Go to the primary source and read its status: EUR-Lex for EU law (a COM reference
is a proposal), the US Unified Agenda for federal rules, the UK Parliament bills
site, and NIST publication pages (ipd means draft).

### **Sources**

 * _[NIST IR 8547: Transition to Post-Quantum Cryptography Standards (final)](https://csrc.nist.gov/pubs/ir/8547/final)_
 * _[HHS OCR: HIPAA Security Rule NPRM fact sheet](https://www.hhs.gov/hipaa/for-professionals/security/hipaa-security-rule-nprm/factsheet/index.html)_
 * _[EUR-Lex: official text and status of EU regulations and directives](https://eur-lex.europa.eu/)_
