The House’s 2015 cyber-sharing bill tied protection to the channel; the law that followed runs on extensions
The bill the House passed on April 22, 2015 protected organizations that shared threat data with several federal agencies under its rules. The December 2015 law narrowed the federal channel to DHS, set a 2025 end date, and has since run on short extensions.
Looking Back revisits past weeks one at a time, up to the most recent, and asks what it meant for the banks, health systems and public agencies we serve. The series was written in 2026, with the benefit of hindsight, and each article says which week it looks back on.
Two-minute summaryThe dek and the first sentence of each section, quoted from the article
The bill the House passed on April 22, 2015 protected organizations that shared threat data with several federal agencies under its rules. The December 2015 law narrowed the federal channel to DHS, set a 2025 end date, and has since run on short extensions.
- The week The engrossed bill had two halves.
- What was shared: indicators, not records Both the House bill and the enacted law protected the sharing of “cyber threat indicators” and “defensive measures.” [1] [2] They did not protect the sharing of everything an incident responder sees.
- Who received it: the channel that earned protection The House bill’s channel was broad.
- What recipients could do with it: use limits and the regulatory bar A sharer’s second worry is what the recipient does next.
- How long the protection lasted: the sunset The House bill set a clock.
- Where the argument is weakest The strongest objection is that the House bill is not the law.
- Checks for banks, health systems and public agencies These checks follow the four conditions.
- With hindsight The House text did not become law as passed.
The week
The House of Representatives passed H.R. 1560 on April 22, 2015, according to the engrossed text. [1] Its long title described the aim: to improve cybersecurity “through enhanced sharing of information about cybersecurity threats.” [1] It also proposed amending the Homeland Security Act of 2002 to strengthen privacy and civil liberties protections. [1]
The engrossed bill had two halves. The first was the Protecting Cyber Networks Act. [1] The second was the National Cybersecurity Protection Advancement Act, which worked through amendments to the Homeland Security Act. [1] Each half carried its own end date. [1]
The first half let private companies, “notwithstanding any other provision of law,” monitor their own information systems for a cybersecurity purpose. [1] They could monitor another organization’s systems with written authorization. [1] They could also operate defensive measures on the same terms. [1] The bill excluded defensive measures that destroy or substantially harm systems the operator does not own or is not authorized to protect. [1]
Companies, states and localities could pass threat data to each other, or to an “appropriate Federal entity,” other than the Department of Defense or its components, including the National Security Agency. [1] The bill listed those agencies as Commerce, Defense, Energy, Homeland Security, Justice, Treasury and the Office of the Director of National Intelligence. [1]
Before passing on threat data, an organization had to take “reasonable efforts” to review it and remove personal information. [1] The duty reached information it “reasonably believes at the time of sharing” to identify a specific person and not to be directly related to a threat. [1] An organization could instead run a technical capability configured to remove such information. [1]
The bill’s liability section set out what participants would get in return. It said “no cause of action shall lie or be maintained in any court” against a private entity for monitoring done in accordance with the bill. [1] It gave the same protection for exchanges under the bill, “or a good faith failure to act” based on them. [1] It preserved suits for willful misconduct, with the plaintiff bearing a clear and convincing evidence burden. [1]
The first half also told the Attorney General to write privacy and civil liberties guidelines for federal use of the data. [1] It required the President to set policies so that data received by one listed agency reached the others in real time. [1] It created a Cyber Threat Intelligence Integration Center in the Office of the Director of National Intelligence. [1] Its end date was written as “the date that is 7 years after the date of the enactment of this title.” [1]
The second half centered on the National Cybersecurity and Communications Integration Center at DHS. [1] It added its own protections from suit, a limit on state and local regulatory use of the data received, and a damages remedy against the federal government for willful misuse. [1] It extended the Homeland Security Act’s provisions on information sharing and analysis organizations to cybersecurity risks and incidents. [1]
The bill’s definitions framed all of this. It defined “cyber threat indicator” as information or a physical object necessary to describe or identify listed threats, such as malicious reconnaissance or command and control. [1] It defined a defensive measure as an action, device, procedure or technique that prevents or mitigates a known or suspected threat. [1]
The April 2015 House bill is easy to remember as the start of a familiar law. The Cybersecurity Information Sharing Act of 2015 became law in December that year. [2] Banks, health systems and agencies can share indicators under it, and sharing agreements and policies can cite its protections.
Our argument is that the House bill shows what the protections were conditional on from the start. Protection for sharing depended on following the statute’s rules: what was shared, with whom, under what limits, and for how long. [1] [2] The enacted law kept that structure and tightened one condition: the channel. [2] And the time condition, a sunset, has since become, in our reading, the most uncertain of the four. [3] [4] [5]
That matters to a compliance officer more than to a threat analyst. An analyst cares whether an indicator reaches a partner. Counsel cares whether that sharing is protected if a customer or patient later sues. Under both the 2015 House bill and the enacted law, the answer depends on facts that sit in the sharing record. [1] [2]
We take the conditions in four parts, each a question the statute asked:
- What was shared: the definition of a cyber threat indicator and the duty to remove personal information.
- Who received it: the federal entities that counted, and the route that earned protection.
- What recipients could do with it: the limits on use, disclosure and regulation.
- How long the protection lasted: the sunset, and what happened when it arrived.
The parts do not overlap. The first is about content, the second about the recipient, the third about later use and the fourth about time. Together they cover the conditions on which the liability protection turned. After them we take the strongest objections, and end with checks for banks, health systems and public agencies.
What was shared: indicators, not records
Both the House bill and the enacted law protected the sharing of “cyber threat indicators” and “defensive measures.” [1] [2] They did not protect the sharing of everything an incident responder sees. A packet capture, a mailbox or a database extract is broader than an indicator. The protection followed the defined term. [1] [2]
What the definition reached
The definition was broad within its frame. In the House bill, an indicator was “information or a physical object” necessary to describe or identify listed things. [1] They included malicious reconnaissance, methods of defeating a security control, security vulnerabilities and malicious command and control. [1] They included a method of causing a legitimate user to unwittingly enable an attack, which covers phishing lures. [1]
One item matters to organizations that suffer data theft. Both texts included “the actual or potential harm caused by an incident, including a description of the information exfiltrated.” [1] [2] A health system could describe the kind of records taken without sharing the records. A bank could describe the account data an attacker sought. In our reading, the definition invited sharing about impact as well as technique.
The enacted law dropped “or a physical object” and added “any combination thereof.” [1] [2] It also widened defensive measures to include signatures and measures that detect threats, as well as those that prevent or mitigate them. [2] In our reading, that made detection rules plainly shareable under the statute for a security operations team. [2]
That distinction matters for sectors that hold personal data. A bank’s fraud investigation, a health system’s ransomware review or an agency’s intrusion analysis will gather customer, patient or citizen information along the way. The statute’s protection covered what was distilled from that work. [1] [2]
The personal information duty in the House bill
The House bill required “reasonable efforts” before sharing. [1] An entity could review the indicator and remove information it “reasonably believes at the time of sharing” to be personal and unrelated to the threat. [1] Or it could use a technical capability configured to remove such information. [1]
“Reasonably believes” is an objective standard in our reading. A plaintiff could argue that a careful analyst should have spotted a name or account number. The House text made the sharing entity’s diligence a question of reasonableness. [1]
The duty in the enacted law
The December 2015 law changed the standard. It required a review of whether the indicator contained information “that the non-Federal entity knows at the time of sharing” to be personal information of a specific individual and not directly related to a threat. [2] Or it required a technical capability configured to remove such information. [2]
In our reading, “knows” is a narrower duty than “reasonably believes.” It turns on actual knowledge at the moment of sharing. [2] That eases the burden on the sharer. It also puts more weight on the review step being real and recorded, since a sharer claiming protection will need to show the review happened. [2]
What that means in a sharing program
A sharing program is a series of small decisions. An analyst decides what to send, strips fields and pushes it to a partner or portal. The statute’s protection depends on that decision being made in accordance with the title. [2] The record of the decision is the evidence.
For a hospital, the risk is that an indicator carries patient data by accident: a file name, an email address, a record number in a URL. For a bank, it is an account number or a customer name in a phishing lure. For an agency, it is a citizen’s address in a malicious attachment. Each sector’s privacy rules apply to what slips through. The statute’s removal step is the control that keeps sharing inside the protection. [2]
Automated sharing raises the stakes. The enacted law allowed a technical capability configured to remove personal information instead of a manual review. [2] An organization that relies on automation needs to show what the tool removes and how it was configured. [2] In our reading, the configuration file becomes a compliance record.
A hypothetical share, step by step
Consider a hypothetical regional bank that finds a credential-phishing site aimed at its customers. Its analysts collect the site’s address, the sending domains, the lure’s text and the list of customers who clicked. Some of that is an indicator; some of it is customer data.
The statute’s content condition sorts the pile. The site address, sending domains and lure technique describe a threat and a method of causing users to enable an attack. [2] The list of customers who clicked is personal information not directly related to the threat, in the sense the statute uses. [2] A description of the kind of data the attackers sought can be shared as harm. [2]
The bank’s record should show the review, who did it and what was removed. [2] If the share goes to DHS, the route matters for protection. [2] If the bank also tells its own regulator about the campaign, that is a separate communication the statute preserved. [2] The same steps would apply to a hospital facing a lure aimed at patients, with patient data in place of account data.
Monitoring and defensive measures
Content conditions also applied to the activities behind sharing. The House bill authorized monitoring of an entity’s own systems and of others’ with written authorization. [1] The enacted law did the same, with written consent for others’ systems. [2] Both excluded defensive measures that destroy or substantially harm systems the operator does not own or is not authorized to protect. [1] [2]
Those authorizations matter to managed service arrangements. A security provider monitoring a credit union’s or a county’s network acts under that entity’s written authorization. [2] The authorization document is part of what makes the monitoring protected. [2] In our reading, a managed security contract should state that authorization in terms the statute recognizes.
Who received it: the channel that earned protection
The House bill’s channel was broad. A non-Federal entity could share with any other non-Federal entity, or with an appropriate Federal entity other than the Defense Department and its components. [1] That left Commerce, Energy, Homeland Security, Justice, Treasury and the Office of the Director of National Intelligence. [1] The bill still allowed lawful sharing with Defense and NSA; it simply did not authorize it under its sharing section. [1]
The bill relied on policy to spread information among agencies. It required presidential policies so that an indicator shared with one appropriate Federal entity was shared “in real-time” with the others. [1] It required that this sharing not be delayed or modified without good cause. [1] In our reading, the House design let companies pick a familiar agency and relied on the government to route the rest.
Why the channel mattered to sectors with regulators
Banks share with Treasury and their regulators. Health systems deal with HHS. Utilities deal with Energy. A broad channel let each sector share with the agency it already knew. [1] The House bill’s definition of appropriate Federal entities did not name the bank regulators or HHS. [1] The protected federal channel was the listed departments, not the sector’s own regulator.
The House bill addressed regulators in another way. It said nothing in the title authorized regulatory actions that would duplicate or conflict with other federal requirements. [1] It also said the title did not establish regulatory authority beyond what it specifically provided. [1] Those are limits on the statute, not a protected route to a regulator.
The enacted law’s single front door
The December 2015 law narrowed the federal channel. It required DHS to develop a capability and process that “shall accept from any non-Federal entity in real time” indicators and defensive measures. [2] Once certified, that capability would be the process by which the government receives indicators shared by email, web form or automated feed, with exceptions. [2]
Liability protection followed the channel. For sharing with the federal government, the law protected a private entity only if the sharing was “consistent with section 105(c)(1)(B),” the DHS process provision. [2] It also set a start: after the earlier of the submission of interim policies and guidelines, or “the date that is 60 days after the date of the enactment of this Act.” [2]
The exceptions mattered for regulated sectors. The DHS process did not displace communications between a federal entity and a non-Federal entity about a previously shared indicator. [2] It did not displace “communications by a regulated non-Federal entity with such entity’s Federal regulatory authority regarding a cybersecurity threat.” [2] It did not limit reporting of suspected crimes or participation in investigations. [2]
In our reading, the enacted law separated two kinds of sharing. Sharing indicators with the federal government for protection ran through DHS. [2] Talking with one’s own regulator about a threat was preserved as a separate path. [2] A bank or health system had to know which path a given message traveled.
How the government routed what it received
The enacted law also bound the government. The DHS process had to ensure that all appropriate federal entities received indicators shared through it “in an automated manner.” [2] It had to comply with the policies, procedures and guidelines the law required. [2] In our reading, the law made DHS the front door and the other agencies the rooms behind it.
The House bill took a different path to the same end. It required presidential policies so that an indicator shared with one listed agency reached all of them “in real-time.” [1] It also created the Cyber Threat Intelligence Integration Center within the Office of the Director of National Intelligence, to analyze and integrate intelligence on cyber threats. [1] The two designs differed in where a sharer knocked, not in whether the government shared internally.
Sharing among private and public peers
Both texts protected sharing among non-Federal entities. [1] [2] The House bill’s liability protection covered a non-Federal entity’s sharing or receipt under its sharing section. [1] The enacted law covered a private entity’s sharing or receipt with any entity, subject to the DHS condition only for federal sharing. [2] Information sharing and analysis centers and organizations are one setting for this peer sharing.
The House’s Title II extended the Homeland Security Act’s information sharing and analysis organization provisions to cybersecurity risks and incidents. [1] In our reading, that language recognized peer-sharing bodies as part of the national structure. The enacted law’s antitrust exemption for exchanges between private entities supported the same activity. [2]
Public agencies are a special case. The enacted law’s liability section protected “private” entities. [2] State and local governments are non-Federal entities that can share. [2] The House’s Title II excluded state, local and tribal governments from its liability provision’s definition of non-Federal entity. [1] A county or a state health department should not assume the liability shield runs to it.
The enacted definitions add a twist for public bodies. “Private entity” includes “a State, tribal, or local government performing utility services, such as electric, natural gas, or water services.” [2] A municipal water or power utility can therefore fall within the private-entity protections. [2] A county health department or a state benefits agency does not fit that inclusion on its face. [2]
How the channel question differs by organization
A broker-dealer, a credit union and a regional bank share differently. A large firm may run a threat intelligence team that feeds automated indicators to several partners. A small credit union may rely on its sector body, its core processor and its regulator’s alerts. The statute’s channel rules apply to each sharing route, whoever runs it. [2]
Health care divides the same way. An academic health system may have its own analysts and a direct feed to DHS. An ambulatory network may share through a vendor or a regional sharing group. When a vendor shares on a client’s behalf, the client should know which route the vendor uses and under what authority. [2]
Agencies differ again. A federal agency shares with DHS as a fellow federal entity, under different rules from those for non-Federal sharers. [2] A state or county shares as a non-Federal entity. [2] Its protections depend on whether it counts as a private entity for the liability section, which turns on the utility inclusion. [2]
What recipients could do with it: use limits and the regulatory bar
A sharer’s second worry is what the recipient does next. The House bill and the enacted law both answered with limits on use, disclosure and regulation. [1] [2] Those limits can matter to a regulated organization as much as the liability shield.
Use and disclosure limits
The House bill required the Attorney General’s guidelines to limit receipt, retention, use and dissemination of indicators containing personal information. [1] It called for prompt destruction of information known not to be directly related to a cybersecurity purpose, and limits on retention periods. [1] It called for sanctions for officials who misused shared information. [1]
The enacted law set out permitted federal uses. Indicators provided to the government could be used “solely for” a cybersecurity purpose, identifying threats or vulnerabilities, responding to specific threats of death or serious harm, protecting minors, or prosecuting listed offenses. [2] They could not be used for any other purpose. [2]
The enacted law also provided that sharing with the government does not waive privilege or trade secret protection. [2] Indicators designated as proprietary are treated as commercial, financial and proprietary information. [2] Shared indicators are exempt from disclosure under the Freedom of Information Act and state disclosure laws. [2]
Two more provisions bear on regulated sharers. The enacted law said providing indicators to the government is not subject to agency rules or judicial doctrine on ex parte communications with a decision-making official. [2] For an organization with a matter pending before an agency, that removes one procedural worry about sharing. [2] It also said shared indicators are “deemed voluntarily shared information.” [2]
The enacted law also addressed duties that receiving might create. It said nothing in the title should be construed to create a duty to share, or “a duty to warn or act based on the receipt” of an indicator. [2] For a hospital or bank that receives thousands of indicators, that limits one theory of liability for failing to act on each one. [2] The House bill reached a similar point by protecting “a good faith failure to act” based on sharing or receipt. [1]
The regulatory use bar
For banks and health systems, a central provision is a limit on regulation. The enacted law said indicators provided to the federal government “shall not be used by any Federal, State, tribal, or local government to regulate, including an enforcement action, the lawful activities of any non-Federal entity.” [2]
There is an exception. Shared indicators may inform the development or implementation of regulations under authority “specifically relating to the prevention or mitigation of cybersecurity threats.” [2] In our reading, that lets a regulator learn from shared data in writing rules, while barring use of the shared data to bring an enforcement action over lawful activity.
The House bill had a narrower version in its Title II. It said indicators shared with state, local or tribal governments under that title may not be used by them to regulate a lawful activity of a non-Federal entity. [1] It also exempted them from state public disclosure laws. [1] The enacted law’s bar reached federal regulators too. [2]
What the bar does not cover
The bar applies to indicators and defensive measures provided to the federal government under the title. [2] It does not turn an incident into a protected secret. A bank’s regulator can still examine the bank’s controls, using its own examination authority. [2] A health system’s breach is still a breach under its own rules. The protection covers the shared data, not the underlying facts.
That limit shapes how organizations should write their sharing policies. Sharing an indicator does not discharge any reporting duty to a regulator or to affected people. Nor does it shield the controls that failed. In our reading, the regulatory bar is a reason to share, not a reason to report less.
Antitrust and the federal government’s own liability
The enacted law also said exchanging indicators between private entities for cybersecurity purposes is not an antitrust violation, within limits. [2] That matters to competitors in one sector, such as banks in a payments network or hospitals in one region. [2]
The House’s Title II went further on government accountability. It made the federal government liable to a person injured by an intentional or willful violation of its use restrictions, for actual damages or $1,000, whichever was greater, plus fees. [1] That remedy illustrates how the House bill tried to give sharers recourse against the recipient as well as protection from third parties. [1]
Title I of the House bill had a parallel remedy. If a federal department or agency intentionally or willfully violated the Attorney General’s privacy and civil liberties guidelines, the United States would be liable to a person injured. [1] Damages were actual damages or $1,000, whichever was greater, plus reasonable fees. [1] An action had to be commenced “not later than 2 years after the date on which the cause of action arises.” [1]
In our reading, those remedies mattered for the people whose data might be in an indicator. A patient or customer named in a shared file was the person a misuse would injure. The House bill gave that person a claim against the government, alongside the sharer’s protection from suit. [1]
How long the protection lasted: the sunset
The House bill set a clock. Title I would “terminate on the date that is 7 years after the date of the enactment of this title.” [1] Title II had its own sunset section with the same seven-year term. [1] In our reading, the House treated the bill as an experiment to be revisited.
The enacted law chose a date instead. Its effective period section said the title “shall be effective during the period beginning on the date of the enactment of this Act and ending on September 30, 2025.” [2] An exception kept the title in effect for any action authorized by it, or information obtained through such an action, that occurred before the end date. [2]
Why the exception matters
The exception protected the past. Sharing done while the law was in effect kept its protection after the end date, under that subsection. [2] What the exception did not do was protect new sharing after the end date. [2] An organization sharing on October 1, 2025 had to ask whether any extension was in force.
The exception makes dating important. An organization that wants to rely on it must be able to show when a share occurred and what it contained. [2] Logs from a sharing platform, with timestamps and the content sent, are the natural evidence. In our reading, retention rules for those logs should run at least as long as the period in which a related suit could be brought.
That is the condition that became uncertain. The law reached its end date without a long-term reauthorization. [2] [3] Congress then extended it in appropriations laws, each time for months. [3] [4] [5] Each extension was a separate fact that counsel had to check. [3] [4] [5]
The extensions as written
The first extension came in a continuing resolution approved on November 12, 2025. [3] Its section 149 said the end date “shall be applied by substituting the date specified in section 106(3) of this Act for ’September 30, 2025.’” [3] Section 106(3) of that Act was January 30, 2026. [3]
The same Act contained a section saying the time covered by its first four divisions “shall be considered to have begun on October 1, 2025.” [3] Whether that language reached sharing between the original end date and approval of the Act is a question for counsel. In our reading, the text invites it.
The second extension came in the Consolidated Appropriations Act, 2026, approved on February 3, 2026. [4] Its section 5008 amended the end date by striking “September 30, 2025” and inserting “September 30, 2026.” [4] Neighboring sections did the same for the federal intrusion detection authority and the state and local cybersecurity grant program. [4]
The third came in the Continuing Appropriations and Extensions Act, 2027, approved on September 2, 2026. [5] Its section 2011 struck “September 30, 2026” and inserted “December 11, 2026.” [5] The Act’s continuing appropriations were available until December 11, 2026, among other conditions. [5]
What the sunset does to a sharing program
A sunset changes the risk calculation for every new share, whatever the sector. A bank’s legal team approving a sharing agreement needs to know the protection will still be in force when indicators flow. [2] A health system’s privacy office deciding whether to share an indicator with patient-adjacent data needs the same assurance. [2]
Short extensions make that a calendar task. Each end date is a fact to track, and each extension is a statute to read. [3] [4] [5] In our reading, the 2015 House bill’s sunset was a design for periodic review. The enacted law’s fixed date has become a series of deadlines tied to appropriations.
What a lapse does to contracts and policies
Sharing agreements can cite the statute. A memorandum with a sector body, a contract with a managed security provider or a policy for analysts may say sharing is done “pursuant to” the law. If the law lapses, those documents describe a protection that is not in force for new sharing. [2]
A lapse does not end the contract. Parties may still share, relying on other law, confidentiality terms and their own judgment. The enacted law said nothing in it limited otherwise lawful disclosures, including reporting suspected crimes. [2] What changes is the statutory shield for new activity. [2]
The practical answer is drafting. A policy can state which sharing continues if the statute lapses, which pauses, and who decides. A contract can allocate risk for sharing done in a gap. In our reading, the cost of writing those clauses is small compared with deciding them during a lapse.
Where the argument is weakest
The strongest objection is that the House bill is not the law. Its text changed before enactment, and organizations rely on the enacted version. [2] Comparing them may seem academic. We use the House text because it shows which conditions were contested and which survived. [1] [2] The survival of the four conditions, in changed form, is the evidence for our reading.
A second objection is that liability protection was not the main reason organizations shared. Some organizations may share because peers share back, or because sector bodies ask them to. That may be so. The statute’s protections still shape what counsel approves, and they are what policies cite. [2] We make no claim about how often organizations relied on them.
A third objection is that the sunset uncertainty has been managed. Congress extended the law three times in the record we reviewed. [3] [4] [5] But the record also shows the original end date passing before the first extension was approved. [2] [3] A protection that depends on each appropriations law passing on time is weaker than one that does not.
A fourth objection is that the DHS channel was a reasonable choice. A single front door can route indicators quickly and apply privacy scrubbing once. [2] We agree. Our point is that protection followed the door, so organizations had to build their federal sharing around it. [2] The exception for communications with one’s own regulator kept a familiar path open. [2]
A last objection concerns public agencies. The enacted liability section speaks of private entities, so the shield matters less to a state or county. [2] That is true. Agencies still benefit from the disclosure exemptions and use limits when they share with the federal government. [2] The four conditions apply to them differently, which is a reason to read the statute rather than rely on a summary.
One further objection is that our four conditions overstate the role of the House bill’s text. The House passed a bill; the final law came through an appropriations act, in different form. [1] [2] We do not claim the House text caused the final design. We use it to show which conditions were present from the start and how each later changed.
Checks for banks, health systems and public agencies
These checks follow the four conditions. Organizations should confirm with counsel how the law applies, and whether it is in force on the day they share. [2] [5]
Content
- Write down how analysts review indicators for personal information before sharing, and keep the record of each review. [2]
- If a tool strips personal information automatically, document its configuration and test what it removes. [2]
- Keep written authorization for any monitoring of systems the organization does not own. [2]
Channel
- List every route the organization uses to share indicators, including DHS, sector bodies, vendors and peers. [2]
- Separate threat discussions with the organization’s own regulator from indicator sharing with the federal government, and label each. [2]
- For public agencies, confirm with counsel which protections apply to a government sharer. [2]
Use limits
- Mark proprietary indicators as such when sharing with the government, as the law allows. [2]
- Do not treat sharing as a substitute for regulatory, contractual or breach notification duties.
- Know the regulatory use bar and its exception for rules that specifically address cybersecurity threats. [2]
Time
- Track the current end date in the statute, which was December 11, 2026 as checked on November 16, 2026. [5]
- Name an owner to confirm, before each end date, whether an extension has been enacted. [3] [4] [5]
- Decide in advance what sharing continues if the law lapses again, and what pauses.
Contracts and agreements
- Find every sharing agreement, vendor contract and policy that cites the statute, and note what each says happens if it lapses. [2]
- Require managed security providers to state which routes they use to share on the organization’s behalf. [2]
- Keep sharing logs with timestamps long enough to show when each share occurred. [2]
With hindsight
The House text did not become law as passed. The law that emerged was the Cybersecurity Act of 2015, Division N of the Consolidated Appropriations Act, 2016, approved on December 18, 2015. [2] Its first title is the Cybersecurity Information Sharing Act of 2015. [2]
The enacted title kept the House bill’s main structure. It authorized monitoring, defensive measures and sharing for cybersecurity purposes, with a duty to remove personal information. [2] It protected private entities from suits over monitoring and sharing done in accordance with the title. [2] It preserved common law and statutory defenses, and said it created no duty to share or to act on what is received. [2]
It changed the conditions in ways that matter to sharers. The personal information standard moved from what an entity “reasonably believes” to what it “knows at the time of sharing.” [1] [2] Federal sharing earned protection through the DHS capability and process. [2] Federal, state, tribal and local governments were barred from using shared indicators to regulate lawful activities, with an exception for cybersecurity rules. [2]
It replaced the House’s seven-year sunset with a fixed end date of September 30, 2025. [1] [2] It kept actions taken before that date in effect afterward. [2]
That date arrived without a long-term reauthorization. On November 12, 2025, a continuing appropriations law applied the end date as January 30, 2026. [3] The same law said the time covered by its first four divisions was considered to have begun on October 1, 2025. [3]
On February 3, 2026, the Consolidated Appropriations Act, 2026 amended the statute to end on September 30, 2026. [4] It extended other cybersecurity authorities in the same way, including the National Cybersecurity Protection System authorization and the state and local cybersecurity grant program. [4]
On September 2, 2026, the Continuing Appropriations and Extensions Act, 2027 moved the end date to December 11, 2026. [5] It made the same change for the federal intrusion detection authority in the Federal Cybersecurity Enhancement Act of 2015. [5]
Each extension we read changed only the end date. The November 2025 law applied a substitute date; the February and September 2026 laws struck one date and inserted another. [3] [4] [5] None of the three provisions changed the definitions, the channel, the use limits or the liability section. [3] [4] [5] The 2015 bargain ran unchanged on new dates.
As checked on November 16, 2026, that was the most recent change we found in public laws published on govinfo, through Public Law 119-138. The statute’s end date stood at December 11, 2026. [5] Whether Congress acts before then, and for how long, was not known when we checked. Organizations should confirm the status on the day they rely on it.
What held up from April 2015 is the bargain: protection from suits in return for sharing according to the statute’s rules. [1] [2] What changed is the channel, narrowed to DHS for federal sharing, and the clock, turned from a seven-year review into a fixed date and then into short extensions. [1] [2] [3] [4] [5]
For banks, health systems and public agencies, the result is a protection that is real and conditional. The conditions are content, channel, use and time. [2] The first three are in the organization’s control. The fourth has depended on Congress, extension by extension. [3] [4] [5]
Spotted an error? Tell us and we will check it and correct the article where needed.