It Is December 12 and Your Analyst Asks Whether to Hit Send: A Readiness Plan for the CISA 2015 Lapse
The views expressed are my own and do not represent those of my employer.
Imagine a threat intelligence analyst at a mid sized company on Friday, December 12. She just found a command and control address in a log review. It matches a pattern her industry peer group flagged two weeks ago. The sharing portal is open. The post is half typed.
Then she stops and asks her manager a question nobody has answered: "Am I covered if I send this?"
Her manager does not know. Legal has left for the weekend. The indicator is getting older by the hour, and every other company in her sector is waiting for someone else to go first.
That scene is plausible in about a month. The Cybersecurity Information Sharing Act of 2015, known as CISA 2015, has gone through a series of short term renewals and lapses since its original 10 year sunset passed last year, and it is now set to expire again on Dec. 11 (CyberScoop, 2026). If Congress does nothing, the legal footing under every threat indicator you share changes overnight.
You cannot control what Congress does. You can control whether your team is ready for it. This post gives you a plan for that: an inventory, a list of questions for legal, a decision about how sharing will work during a lapse, and a message for your board. I would start this week.
The Law Has Done This Before, and the Pattern Matters
CISA 2015 provides liability protections for companies sharing cyber threat indicators amongst themselves and with federal agencies (Cybersecurity Dive, 2026). It has been the quiet legal foundation under ISACs, sector groups and the voluntary channels most of us use without thinking about the statute.
The timeline is worth knowing cold. The Act expired on September 30, 2025 (Mayer Brown, 2025). Congress revived it in the bill that ended the shutdown. That funding bill was enacted on November 12, 2025, and extended the protections through January 30, 2026 (Inside Privacy, 2025). Public Law 119-75 later moved the date to September 30, 2026 (Bright Defense, 2026), and the latest extension, signed in September, keeps the protections in place through Dec. 11, 2026 (CiberLATAM, 2026).
Notice the pattern. Every extension rode along on a spending bill. Every one bought weeks or months, not years. Permanent renewal remains stalled in the Senate, according to CiberLATAM in 2026.
Business groups are now pushing for a long term fix. On November 1, 35 business groups sent a letter to the leaders of the House and Senate Armed Services panels asking for a 10 year renewal in the fiscal year 2027 National Defense Authorization Act (CyberScoop, 2026). The letter backs Section 1706 of H.R. 8800, the House version of the NDAA, which would extend the law through 2035 (Operational Technology Cyber Coalition, 2026). That bill remains unfinished as Congress heads into the lame duck session (Daily Energy Insider, 2026).
Maybe Congress delivers. Maybe it passes another short patch. Maybe the date slips by. I cannot tell you which, and neither can anyone writing about it. My recommendation is to plan for the lapse and be pleasantly surprised if it never comes.
What Actually Disappears on December 12
Precision matters here, because the loudest headlines overstate the problem. A lapse does not make sharing illegal. Expiration does not necessarily foreclose information sharing with the federal government, though the statute's liability and other protections stop applying to exchanges after the sunset (Mayer Brown, 2025).
A lapse does not make sharing illegal. It removes the statute that told your lawyers sharing was safe.
So what goes away? A&O Shearman's analysis lists the pieces. The immunity for monitoring systems, deploying defensive measures and sharing cyber information will not protect new conduct after the sunset. Privilege, FOIA and regulatory use protections will not apply to new sharing, and the antitrust safe harbor for private to private sharing will expire.
That list tells you where the risk concentrates. Sharing with the government carries the liability and disclosure questions. Sharing with peers adds antitrust. MoFo's 2025 analysis notes that sharing detailed threat information with competitors could be viewed as collusion, even if cyber defense was the intent.
Two more facts keep you calm and keep you honest. First, the Act's protections still apply to relevant sharing that occurred before expiration (Mayer Brown, 2025). What you shared in 2026 stays protected. Second, the protections were never automatic for any information you happen to share, as ComplianceCISO wrote in 2026. They depend on following the statute's conditions.
Keep the scale in proportion. One law firm put it well in 2025: the expiration does not necessarily make liability a likely prospect. A lapse removes the statutory answer to a lawsuit. It does not create the lawsuit. Your general counsel still has to decide how much of that gap the company will carry.
Start With a Map of Every Place You Share
You cannot make a policy for channels you have not found. So build the inventory first. Block out a few hours with your threat intelligence lead and write down every path indicators leave your organization.
The obvious entries come first. ISAC and ISAO memberships. Your FBI field office contact. Your CISA contact or regional advisor. Then the less obvious ones. Your MSSP or managed detection provider, which may pool your telemetry across its customer base. Your incident response retainer firm. Your cyber insurance carrier. Vendor support portals where an engineer uploads a suspicious sample. Trade association working groups. Peer CISO roundtables and the group chats that grow out of them.
Then look for automation. Outbound feeds that push indicators to a platform or partner without a human reviewing each one are the channel most likely to surprise you. A scenario I have seen play out at multiple organizations: leadership knows about the formal ISAC membership, while an engineer has quietly pushed indicators to an informal peer group for two years. Nobody did anything wrong. Nobody wrote it down either.
For each channel, capture five facts: what you send, who sends it, who receives it, whether the flow is automated, and what written agreement governs it. That one page becomes the input to every decision that follows.
Do the same for inbound flows. You depend on what peers and agencies send you, and that supply can thin out fast. I will come back to that.
Ask Legal Questions They Can Answer in Writing
I am not a lawyer. What I can give you is the list of questions I would bring to one, and the habit of getting the answers in writing before the deadline instead of improvising after it.
Lead with the central question. If Congress does not act, what protections apply to sharing on December 12, channel by channel? Ask counsel to separate government sharing from private to private sharing, because the antitrust exposure differs. A&O Shearman and others flag that gap.
Then ask about privilege. If your team shares analysis that came out of an incident investigation, does that sharing put privilege at risk during a lapse? Ask about public records exposure for anything you send to a government partner. Ask what contractual protections already exist in your ISAC agreements, your MSSP contract and your NDAs, because those carry weight when the statute does not. And ask whether your current sharing process meets the statute's conditions today. ComplianceCISO's point stands: a process built years ago and never reviewed against the statute's conditions deserves a check.
Finally, ask who decides. During a lapse, someone with legal authority needs to be reachable on a Friday afternoon. Get a name and a backup.
Choose Your Posture Before the Deadline: Pause, Narrow or Continue
This is the decision most organizations will make by default, which means they will make it badly. Make it on purpose, and make it now. You have three real options.
Pause. Sharing stops until protections return. This is the cleanest legal position and the worst security position. You stop contributing, and you invite the same behavior from peers. I would only choose a full pause for a specific channel where counsel sees a concrete problem, such as an informal group with no agreement in place.
Narrow. Sharing continues for low risk content and stops for anything that carries more exposure. Technical indicators about attacker infrastructure, such as malicious domains, IP addresses and file hashes, sit at the low end. Victim details, internal system names, customer data and your own attribution commentary sit at the high end. That split is my judgment as a practitioner, not a legal safe harbor, so have counsel confirm it.
Continue under counsel review. Sharing proceeds as normal, but a defined review step sits in front of anything sensitive. This works only if the review is fast. A review process that takes three days is a pause with extra steps.
My recommendation is to narrow by default and build a fast review lane for the exceptions. Write the decision down, date it, have your general counsel approve it, and tell the people who actually press the button. Include a trigger for reversal. When Congress renews the law, the posture changes back, and your team should know exactly who announces that.
A review process that takes three days is a pause with extra steps.
Build the Fast Lane for Counsel Review
The narrow posture lives or dies on speed. Build the lane before you need it.
Start with pre approved categories. Work with counsel to define which kinds of content can go out without review, and which need a second set of eyes. Draft a short sharing template that strips what is not needed to describe the threat. Remove personal data, internal hostnames and anything that identifies a customer or a victim. That is good practice with or without a statute.
Name a reviewer and a backup, with a target turnaround measured in hours. Give your analysts a plain way to escalate, such as one mailbox or one chat channel that reaches the reviewer directly.
Keep a log. Record what you shared, when, with whom, and which channel carried it. This matters because of the date logic in the statute. Sharing before a lapse keeps its protection, and sharing during a lapse does not. ComplianceCISO put it plainly in 2026: sharing done before a lapse keeps its statutory protection, and sharing during one does not. A dated log lets you show which side of the line each exchange fell on.
This fits naturally into the external communications work you should already have in your incident process. I covered that side in my post on NIST CSF 2.0 Response Communications. Add the sharing review lane to that playbook rather than inventing a separate one.
One note on scope. CIRCIA, the incident reporting law, is a different animal. It is mandatory, one way reporting from you to the government. A Congressional Research Service product from 2025 notes that CIRCIA requires certain entities to report cybersecurity incidents and ransomware payments. CISA 2015 is voluntary and runs in both directions. A CIRCIA readiness plan does not cover your sharing exposure. Treat them as separate workstreams.
Do Not Forget What Comes In
Most lapse planning focuses on outbound sharing. The inbound side may hurt more.
When the law lapsed in 2025, lawyers and practitioners predicted that companies would pull back. One commentator quoted by The Hill that year worried that companies will share much less data because relationships built over a decade may fracture over liability concerns. Lexology's 2025 analysis warned that companies may revert to sharing limited, cherry picked or obsolete information, if they share at all.
If your peers go quiet, your early warning shrinks. Identify which of your detections rely on partner provided indicators. Then line up alternatives: commercial intelligence feeds, open source reporting, vendor advisories, and the telemetry your own tools generate.
Your MSSP deserves a direct conversation. If it pools data from many customers, ask how its sharing practices change during a lapse and what its contract says about your data. I wrote about keeping control of an outsourced function in What to Outsource (Without Losing Control). This is a good test of that control.
Machine Speed Attacks Make Sharing More Valuable Right Now
Here is the argument I would put in front of leadership, because the timing is awkward. Sharing is becoming more valuable just as its legal footing becomes less stable.
The coalition behind the November letter made the AI case directly. Advanced AI systems can identify and exploit software vulnerabilities at machine speed, and AI tools make sophisticated cyber capabilities faster, cheaper and easier to use, according to MeriTalk's 2026 report on the letter. The signers wrote that the speed and breadth with which defenders share information determines whether they keep pace with adversaries (Defense One, 2026).
Think about what that means in practice. When attackers move at machine speed, an indicator that reaches peers in an hour protects them. The same indicator arriving after three days of legal back and forth protects nobody. I explored the defender side of this speed problem in Nobody Was at the Keyboard on the Attacker's Side. Speed on offense forces speed on defense, and shared intelligence is one of the few force multipliers a mid sized company can access at low cost.
Attackers share at machine speed. Defenders who wait on legal clarity are competing with one hand tied.
That tension is your board message. Do not frame it as a political story about Congress. Frame it as a business risk story about speed, exposure and decision rights.
Getting Organizational Support: Sell the Plan in Risk Language
This plan needs help from people who do not read threat reports. Each group cares about a different part of the problem, so adjust the message for each.
The board. Lead with the business risk, not the statute. Tell directors that a federal law protecting the company when it shares threat information may lapse on December 11. Explain that management has mapped its sharing channels, asked counsel for a position, and chosen how sharing will work during a gap. Then name the tradeoff: pausing reduces legal exposure but also reduces early warning, and the company has chosen a middle path. Keep it to one page. Directors want to know that someone owns the decision and that it is already made.
The CEO and CFO. Talk about speed and cost. The value of sharing is earlier warning, which means shorter incidents and smaller losses. The cost of the plan is a few hours of legal and security time, plus a review process. That ratio is easy to defend. If you need a refresher on gaining and holding executive support, I wrote about it in Winning the Room.
The general counsel. Your counsel is the partner that matters most. Bring the inventory, bring the questions, and ask for a written position. Offer to take the operational burden by building the review lane and the log. Lawyers say yes faster when you hand them a process instead of a problem.
Business and IT leaders. Keep it short. Tell them a legal change may affect how security shares information with outside parties, that nothing changes for their daily work, and that you will ask for quick answers if a specific system or customer is involved.
Your own team and your peers. Analysts need to know what to send, what to hold and who to ask. Peers need to hear from you before the deadline. Call your ISAC contacts and ask what their legal teams plan to do. A coordinated approach across a sector beats fifty improvised ones.
Key Points
- CISA 2015 is set to expire December 11 unless Congress acts, and the pattern of short extensions means you should plan for a lapse.
- A lapse does not make sharing illegal. It removes the statutory liability, antitrust, FOIA and privilege protections for new sharing.
- Sharing done before a lapse keeps its protection, so keep a dated log of what you shared and when.
- Inventory every channel, including automated feeds, MSSP pooling and informal peer groups.
- Get counsel's position in writing, channel by channel, before December 11.
- Choose pause, narrow or continue under review. My default is narrow, with a fast review lane.
- Line up alternative intelligence sources in case peers go quiet.
- Brief the board on speed, exposure and decision rights, not on legislation.
Pro Tips
Ask your ISAC what its lawyers decided. Most ISACs went through this analysis during the 2025 lapse. Their counsel has already thought about it, and their agreements may give you language to reuse. A call costs you ten minutes.
Test the lane with a drill. Pick a fake indicator and run it through your review process on a Friday afternoon. You will learn how long it takes, who is unreachable and which step breaks. Fix that before December 11, not after.
Separate indicators from context. Analysts often send the indicator and a paragraph of narrative about how they found it. The indicator carries most of the defensive value. The narrative carries most of the exposure. Train your team to send the first without the second when the posture is narrow.
Put the reversal trigger in writing. A temporary restriction can become permanent by neglect. Assign an owner to watch the legislative calendar and an owner to announce when normal sharing resumes.
Pitfalls to Avoid
Do not wait for the deadline to ask legal. Counsel needs time to review channels and agreements, and December is a crowded month for everyone.
Do not assume the NDAA will rescue you. It remains unfinished, and no one can promise the timing. Even a successful renewal might land after the date passes.
Do not go silent by default. A blanket pause feels safe, but it starves your peers and yourself. Decide channel by channel and keep low risk sharing alive.
Do not forget automated feeds. A person can read a policy. A script cannot. Review every outbound integration and ask who owns it.
Do not frame this as a legislative drama for the board. Directors need a risk, a decision and an owner, not a civics lesson.
Final Thought
The best security teams I know treat shared intelligence as infrastructure, and infrastructure needs a plan for the day the legal ground shifts. December 11 may pass quietly with a renewal, or it may not. Either way, the work you do this month leaves you with a map of how information leaves your company, a written position from counsel and a team that knows what to do when the question comes on a Friday afternoon.
If this post helped, share it with your general counsel and your threat intelligence lead, and subscribe to InfoSec Made Easy for more practical guidance on the issues that land on a CISO's desk. Tell me in the comments how your organization plans to handle a lapse, or what your ISAC is telling you. I read every one.
Comments ()