Revolutionary Information

Here is the rule. Under the Product Security Bad Practices guidance from CISA and the FBI, a maker of software used in critical infrastructure that had no published memory safety roadmap by January 1, 2026 is, in the agencies' own word, "dangerous". The date came and went. Your firewall vendor, your hospital's imaging supplier, the firm behind your water utility's control panels: none of them owed you a thing when it passed.

The flaw is in the rule. The same document says it "is non-binding" and "imposes no requirement", so the risk of a missing plan sits with you, the customer. It should be compulsory. And the standard objection, that leaving C and C++ is too slow and too costly, no longer survives the data.

Is CISA's memory safety guidance mandatory?

No, CISA's memory safety guidance is voluntary: the agencies call a missing roadmap dangerous for critical-infrastructure software, but attach no fine and no procurement ban, so a vendor that ignored the January 2026 date faces nothing.

Washington has stayed in that register. A June 2025 NSA and CISA information sheet on memory safe languages (Rust, Go and others that stop code touching memory it does not own) says the agencies "urge organizations to consider whether adopting MSLs is practical for their circumstances." That hands every vendor two exits, "consider" and "practical". A buyer waiting for a federal push is waiting for something the government has said, in writing, it will not do.

Other regulators have been less shy. Europe wrote vulnerability handling into law, down to the 24-hour exploited-vulnerability warning the Cyber Resilience Act demands. Even NIST put calendar years on its post-quantum migration deadlines. Memory safety, the older and better-understood problem, got an adjective.

Is Rust really safer than C++?

Yes, by a margin that ends the argument. A November 2025 Google report, Rust in Android, found its roughly 5 million lines of Rust running at about 0.2 memory-safety vulnerabilities per million lines, against roughly 1,000 in its C and C++, a reduction Google puts at more than 1,000x. That kills the excuse that safer languages just move bugs elsewhere.

But the objection was always about cost: rewriting slows teams, and ship dates pay salaries. Four numbers test that. Google's Android data supplies two, measured on changes of comparable size. MITRE's CWE Top 25, released in December 2025, supplies a count of memory errors among the most dangerous weaknesses. The calendar supplies the last.

Show the rollback figure to a sceptical finance director. A rollback is a release pulled after shipping, usually an outage and a lost weekend. Fewer of those means the cost objection runs backwards.

With no regulator compelling a plan, your contract is the only lever left.

What a required memory safety roadmap changes for buyers

Requiring the plan turns a vendor's vague intention into a dated, auditable commitment that covers its riskiest code first, which gives a buyer something to enforce at renewal instead of a hope.

The flaw-rate row is my arithmetic, not Google's: Android's measured densities scaled to a 100,000-line component. At those rates a new C++ service carries latent memory flaws in triple figures, and the Rust version most likely none.

Where a compulsory roadmap gets hard

A compulsory plan gets hard in two places: products close to retirement, which the guidance already exempts, and vendors who publish a roadmap with no dates in it, which satisfies the letter while changing nothing.

Do software makers have to stop using C and C++ by 2026?

No. The CISA and FBI guidance asks existing products for a plan, not a rewrite, and only calls new critical-infrastructure product lines in C or C++ dangerous where a memory-safe alternative exists. I'd go further than CISA, or at least put it more bluntly: a roadmap without a year beside each component is a brochure.

The unresolved question, in my opinion, is embedded firmware. A substation controller will not be rewritten, and a plan for it may mean little beyond the next model. Newer guidance shares the gap, such as the NSA's May 2026 advisory on MCP security for AI agents: sound advice, no teeth. Watch for:

• Goals with no year per component.
• Memory-safe claims covering only new features.
• An end-of-support date just inside the exemption.
• Sandboxing sold as a substitute, not a stopgap.

If two of those are true, stop waiting for Washington. This week, email the vendor asking for its published plan and support end date, and tell procurement that renewal now depends on a dated commitment, cryptographic code first. Require it yourself, because nobody else will.

Here is the rule. Since 11 September 2026, any company selling software or connected hardware in the European Union that learns one of its products is being actively exploited has 24 hours to send an early warning to the authorities, and 72 hours to follow it with a full notification. That is CRA reporting, set out in the European Commission's guidance on the Cyber Resilience Act, and it is already live. A vendor in Austin that sells the same router in Berlin and Boston now owes Berlin a warning. Boston gets nothing.

That gap should close by law, and the usual objection is mostly answered by how the rule is written.

Why CRA reporting should be the global floor

A vendor knows first when its product is being exploited, so the duty to warn belongs with the vendor, and a rule that protects only EU customers leaves every other buyer of the same product exposed.

The manufacturer sees the crash reports, the researcher emails and the telemetry spike days before customers notice anything. The Act makes that knowledge travel: manufacturers must also inform impacted users, according to Hogan Lovells' 11 September 2026 briefing. An EU hospital running a VPN appliance gets told. A clinic in Ohio running the identical box does not.

The American answer is thinner. CIRCIA puts the reporting duty on critical-infrastructure operators, the victims, not on the vendor whose code let the attacker in. CISA's Secure by Design pledge is voluntary, so a US buyer holds no enforceable promise unless it sits in the contract. Treating a pledge as a rule is outdated advice.

Anyone who tracked the DPDP consent manager deadline in India or post-quantum migration deadlines under NIST IR 8547 knows the pattern: a regulator sets a clock, and vendors discover how little of their process was built for one.

Run the clock on a real calendar. Confirm exploitation at 5pm on a Friday and the early warning is due by 5pm Saturday, the full notification by 5pm Monday. That is our own arithmetic, and it means someone with authority to file must be reachable all weekend. The four numbers below, from the Commission and Article 64 of the Act, decide whether vendors take that seriously.

The revenue-linked ceiling is what changes behaviour at large vendors. A flat cap is a budget line; a share of global revenue grows with the company, so the suppliers in the most networks carry the steepest exposure.

Does the Cyber Resilience Act apply to US companies?

Yes, the Cyber Resilience Act applies to any manufacturer placing products on the EU market, wherever it is based, so a US vendor selling into Europe already owes EU buyers warnings its home customers never receive.

US figures below come from Ballard Spahr's Byte Back analysis of CIRCIA (February 2026) and CISA's pledge page.

The vendor builds the triage desk for Europe anyway, so American customers pay for output they never see. Vendors treating 2027 as the start date have the calendar wrong.

Won't a 24-hour rule crush small vendors?

No, because the 24-hour step is an early warning to a national security team, not a public disclosure or a finished report, and the fuller detail follows on a structured, longer schedule.

At its strongest, the objection says a ten-person firm has no security team and a panicked filing could leak. Filings go through ENISA's Single Reporting Platform to the CSIRT of the manufacturer's main establishment, so the warning never touches the open internet. Attackers learn nothing from a message they cannot read.

The burden is real but scoped: a written threshold for "actively exploited" and a named Sunday filer. Plus a rehearsal. Two, honestly, because the first always finds the gap nobody wrote down. AI tooling vendors have more ground to cover, with flaws surfacing in MCP servers flagged in the NSA's advisory and in AI agent credentials nobody has inventoried.

The genuine grey area is the word "aware". In our view the clock should start at credible evidence of exploitation, not legal sign-off, but enforcement will settle it. Watch for these:

• Community-maintained components sit outside the clock until open-source stewards join.
• Severe incidents run a different final-report schedule, so check which your contract names.
• US buyers hold no right to the EU notice, even for identical firmware.

Do not wait for Washington. This week, pull your three largest software contracts and add one clause: the vendor notifies you within 24 hours of confirming active exploitation, on the same terms it already owes EU regulators. A vendor that refuses a promise it already keeps in Europe has told you what you need to know.

Related: why a memory safety roadmap should be compulsory for software vendors

Your consent flow works. A user taps accept, a row lands in your database, marketing gets its audience, and nobody thinks about it again. Now picture a platform your company has never integrated with, never signed a contract with, sending a withdrawal instruction on that same user's behalf and expecting your systems to honour it. That is the shape of the DPDP consent manager deadline landing on 13 November 2026. Most Indian data teams are still treating consent as something they own, when the law is about to treat it as something they receive.

Why the DPDP consent manager deadline lands early

The DPDP consent manager deadline lands early because your obligation is not to register a consent manager, it is to accept instructions from one, and that capability takes far longer to build than a vendor contract takes to sign.

Read the commencement schedule and it looks generous. MeitY notified the Digital Personal Data Protection Rules, 2025 on 13 November 2025. Rule 4 and the First Schedule, which carry the consent manager machinery, take effect exactly a year later. The operative duties on data fiduciaries wait until 13 May 2027. Eighteen months of runway. Plenty of time.

That reading is wrong, and it is the most common mistake in Indian compliance roadmaps right now. The 2027 date governs what you must tell people. The 2026 date governs what your systems must be able to hear. Those are different engineering problems, and the second one is harder, because it means an external party you did not choose gets to change the state of a record inside your platform. Anyone who has watched India's telecom sector fight over whether operators should display verified KYC names to the people they call already knows how slowly identity plumbing moves once it has to work across companies.

What is a consent manager under the DPDP Act?

A consent manager is an Indian-incorporated company, registered with the Data Protection Board, that gives a person one interface to grant, review, manage and withdraw consent across every business holding their data.

The First Schedule sets the bar deliberately high. The applicant must be incorporated in India. It must hold a minimum net worth of two crore rupees. Personal data routed through its platform must not be readable by it, which rules out the obvious architecture where a broker sits in the middle and inspects payloads. Consent records must be retained for seven years. Together those conditions describe an entity closer to a depository than to a SaaS product, and the capital test alone will keep the field small. Four numbers frame the problem.

The third cell is the one that should bother you. The Board is established in law under Section 18 of the Act, and MeitY has invited applications for its Chairperson and Members, with a search panel headed by the Cabinet Secretary. It is not fully constituted. No registry exists, so no company has been registered to do the job the rule assumes will be done. Meanwhile the DPDP Act's own schedule of penalties sets a ceiling of 250 crore rupees for a single failure to take reasonable security safeguards, and that ceiling is not waiting for anyone to be appointed. The same pattern shows up in AI agent governance, where the enterprises that moved before the rules landed are the ones now setting the terms.

Key highlights: what switches on, and when

India's DPDP Rules, 2025 commence in three tranches between November 2025 and May 2027, and only the consent manager tranche carries a build requirement that reaches outside your own systems.

The table below is the version of the schedule worth pinning above a sprint board, because it separates dates that create paperwork from dates that create engineering. Two of these rows describe conditions, not deadlines, and those are the ones that decide your architecture.

Rows four through six are the ones your architects should argue about. Eligibility decides whether your current privacy vendor can hold the role at all. Data blindness decides your integration shape. Retention decides the storage tier, and seven years is long enough that the answer is probably not your transactional database.

Do Indian companies have to use a consent manager?

No, a data fiduciary is not required to appoint a consent manager, but it must be able to receive and act on consent given, reviewed or withdrawn through one, which makes the integration mandatory even when the appointment is not.

This is where the common advice goes wrong. Plenty of teams have filed the consent manager work under procurement, expecting a vendor to arrive in 2027 with a connector. That gets the direction of the obligation backwards. The consent manager works for the individual, not for you. When it sends a withdrawal, your platform is the party that has to prove it acted, and proving it means an auditable trail that survives seven years and several system migrations. This is the same long-horizon storage problem that shows up in harvest now, decrypt later planning, where data you keep for a decade has to survive threats that do not exist yet.

What happens if no consent manager is registered by November 2026?

Nothing visible happens, and that is the trap. My read is that a quiet Phase 2 will be treated by most boards as evidence that the whole thing slipped, and the build will be deferred into the same quarter as the May 2027 duties. That is a bad bet. The Board can be constituted in weeks once appointments clear, registrations can follow quickly after that, and the first fiduciary asked to honour an external withdrawal will not get a runway. Watch for these before you defer:

• Legacy consent captured before the Rules, with no purpose string attached, which cannot be mapped to a machine-readable record.
• Withdrawal propagation that stops at the primary database and never reaches warehouses, exports, ad platforms or vendor copies.
• Consent state held in a table with no history, so you can show what is true today but not what was true on the day of a complaint.
• Vendor contracts that treat consent as your problem, with no obligation on the processor to accept a withdrawal signal you pass down.

Pick the ingestion endpoint and the audit log first, because both are slow and neither depends on a registry existing. The registry is the visible part. The unglamorous part, and honestly the part that will eat your quarter, is propagation. Start the design review this month, freeze it by mid-October, and let the Board catch up to you.