Critical

Communicating Under Pressure: Best Practices for Service Providers

All CISA Advisories

Overview

The guidance developed by CISA and the FBI outlines how organizations should communicate during IT and operational technology outages. These outages can stem from various causes like cyberattacks, human error, or natural disasters and can lead to significant disruption and public concern. The recommendations stress the importance of clear, accountable, and transparent communication to keep stakeholders informed and to prevent misinformation. Organizations are encouraged to have crisis communication plans that include backup communication methods to ensure reliability during outages. This is particularly critical for critical infrastructure providers, as disruptions can affect interconnected systems and ultimately impact public trust.

Key Takeaways

  • Affected Systems: Critical infrastructure organizations, telecommunications services
  • Action Required: Organizations should develop and implement crisis communication plans that include backup communication methods.
  • Timeline: Newly disclosed

Original Article Summary

Developed by CISA, the Federal Bureau of Investigation, and international partners, this guidance describes how organizations can plan and execute clear, timely, accurate, and audience-appropriate communications during IT and operational technology (OT) outages. Whether caused by cyber threat actors, human error, equipment failure, or natural hazards, service outages can create disruption and societal panic even without speculation from end users and the public as added factors. Outages at one organization may cascade across interconnected systems, increasing uncertainty and alarm. The guidance emphasizes clarity, accountability, and transparency as core principles and details key elements of effective crisis messaging to inform affected stakeholders and the public while aligning with legal requirements, operational security, law enforcement, and containment efforts. CISA’s CI Fortify initiative provides information and resources that help critical infrastructure organizations prepare to isolate and recover vital OT systems during a major cyber incident or crisis. Changes in service availability, whether from outages or isolation as a defensive strategy, require transparent and ongoing communication to help end users minimize operational impact, limit speculation, and preserve trust. For emergency planning purposes, critical infrastructure owners and operators should assume that telecommunications services may be disrupted or otherwise unreliable, making it crucial for organizations to have crisis communications plans in place that integrate backup communication methods and understand the type of communication they should expect from their service providers.

Impact

Critical infrastructure organizations, telecommunications services

Exploitation Status

No active exploitation has been reported at this time. However, organizations should still apply patches promptly as proof-of-concept code may exist.

Timeline

Newly disclosed

Remediation

Organizations should develop and implement crisis communication plans that include backup communication methods.

Additional Information

This threat intelligence is aggregated from trusted cybersecurity sources. For the most up-to-date information, technical details, and official vendor guidance, please refer to the original article linked below.

Related Topics: This incident relates to Critical.

Related Coverage

Leaked LiteLLM Master Key Let Attackers Steal GitHub Tokens and Hijack Release Pipeline

The Hacker News

LiteLLM has reported a serious security incident stemming from the accidental exposure of a master key in a public GitHub repository. This key, which was found in a configuration file committed on May 27, 2026, enabled an attacker to manipulate the release pipeline of the popular Python package. As a result, the attacker was able to push a malicious version of the software, potentially compromising users who downloaded it. This incident raises significant concerns about the security practices surrounding sensitive information in open-source projects, particularly how such keys are managed and stored. Developers and organizations using LiteLLM's tools should review their security protocols to prevent similar incidents in the future.

Oct 24, 2026

Researchers Push Over 2 Million Updates to Remotely Disable Popcorn Time Updater That Could Fuel a Botnet

The Hacker News

In a significant cybersecurity move, the Dutch security firm Eye Security has remotely pushed over 2 million updates to computers to disable a background updater associated with Time4Popcorn, a discontinued version of the Popcorn Time app known for streaming pirated content. This updater posed a potential risk as it could allow unauthorized users to take control of affected machines. The updates were carried out between November 2025 and March 2026, targeting devices that did not belong to the firm. The action underscores the ongoing risks linked to abandoned software and highlights the need for users to be cautious about outdated applications. This incident serves as a reminder of the vulnerabilities that can arise from using unsupported software, especially those associated with illegal activities.

Oct 24, 2026

CISA Flags Two Actively Exploited Critical Flaws in Collabora Online and Arista VeloCloud

The Hacker News

The U.S. Cybersecurity and Infrastructure Security Agency (CISA) has flagged two critical vulnerabilities that are actively being exploited. These vulnerabilities affect the Collabora Online Built-in CODE Server and the Arista VeloCloud Orchestrator (VCO). The first vulnerability, identified as CVE-2026-110447, carries a CVSS score of 9.2, indicating its severity. Organizations using these products need to take immediate action, as attackers are actively exploiting these flaws. Prompt remediation is essential to protect sensitive data and maintain system integrity.

Oct 24, 2026

Exposed to PHP2Shell? Cyber Experts Weigh in With Advice

darkreading

Recent vulnerabilities in PHP, known as PHP2Shell, have raised concerns among cybersecurity experts. These flaws pose risks to numerous web applications that rely on PHP, potentially allowing attackers to exploit these weaknesses for unauthorized access or data manipulation. Users and administrators of PHP-based systems are advised to assess their exposure and implement protective measures. Simply updating software may not suffice, as the vulnerabilities require careful evaluation and tailored remediation strategies. This situation underscores the need for vigilance in maintaining web application security and keeping software up to date.

Oct 23, 2026

Microsoft Teams to get AI-powered, context-aware phishing detection

BleepingComputer

Microsoft is set to enhance its Teams messaging platform with AI-driven phishing detection capabilities starting in early November 2026. This new feature aims to identify and flag potential phishing attempts within Teams messages, helping users avoid falling victim to scams. The integration of AI is expected to improve the accuracy of phishing detection by analyzing the context of messages. This is particularly important as phishing attacks continue to rise, targeting both individuals and organizations. By implementing this technology, Microsoft hopes to bolster security for its users and reduce the risk of data breaches associated with phishing.

Oct 23, 2026

Ruby Fixes Three Regex Engine Bugs Responsible for Four Critical GitLab RCE Flaws

The Hacker News

Ruby has released updates to versions 4.0.9, 3.4.12, and 3.3.13 to address three bugs in the Onigmo regular expression engine. These bugs are linked to four critical vulnerabilities that GitLab recently patched. The vulnerabilities could allow attackers to craft specific patterns that may corrupt memory during the compilation process, potentially enabling remote code execution on affected servers. This issue is particularly concerning for GitLab users, as it puts their systems at risk if the vulnerabilities are exploited. Users are encouraged to update to the latest Ruby versions to mitigate these risks.

Oct 23, 2026