{"id":564,"date":"2026-10-12T10:25:36","date_gmt":"2026-10-12T10:25:36","guid":{"rendered":"https:\/\/managedt.com\/blog\/fbi-cisa-third-party-ics-integrator-guidance\/"},"modified":"2026-10-12T12:53:08","modified_gmt":"2026-10-12T12:53:08","slug":"fbi-cisa-third-party-ics-integrator-guidance","status":"publish","type":"post","link":"https:\/\/managedt.com\/blog\/fbi-cisa-third-party-ics-integrator-guidance\/","title":{"rendered":"FBI and CISA Guidance for Critical Infrastructure Operators Working With Third-Party ICS Integrators"},"content":{"rendered":"<p>Critical infrastructure owners and operators can reduce their exposure to cyber risk by applying the principle of least privilege, vetting integrator access, and building the ability to operate independently when working with third-party industrial control system (ICS) integrators, according to a joint fact sheet from the FBI and CISA published on September 29, 2026.<\/p>\n<h2>Why third-party ICS integrator access creates risk<\/h2>\n<p>Industrial control systems are integrated networks of hardware and software designed to monitor and automate physical processes. They include supervisory control and data acquisition (SCADA) systems and programmable logic controllers. Third-party ICS integrators provide services such as control system design, installation, operational data analysis, device and service support, and daily operational control.<\/p>\n<p>Granting outside firms extensive access to industrial processes can expose operators to malicious actors, who may use it to disrupt equipment.<\/p>\n<p>The principle of least privilege (PoLP) is designed to counter that risk. In operational technology (OT) environments, PoLP grants users, processes, and systems only the minimum access necessary to perform their assigned tasks.<\/p>\n<h2>Documented exploitation of an integrator&#8217;s network<\/h2>\n<p>Between March and April 2025, malicious foreign cyber actors gained access to the network of a U.S. industrial automation solutions company that provided services, including system integration, engineering consulting, and SCADA programming, for industrial customers such as power utilities and transportation entities. While inside the network, the actors searched for terms including &#8220;customers&#8221; and &#8220;SCADA,&#8221; and assembled nine .zip files containing approximately 800 files for presumed exfiltration. The files included customer SCADA information, ICS device details, and other schematics.<\/p>\n<p>Exfiltrated data could later disrupt operations and interrupt services.<\/p>\n<h2>Questions operators should include in their risk assessments<\/h2>\n<p>The guidance lists questions for critical infrastructure organizations to consider before letting a third-party integrator into their networks and operations.<\/p>\n<ul>\n<li><strong>What organizational data does the integrator store or have access to?<\/strong> Network designs, device specifications, and logs can each be useful to a malicious actor, and any of that data could be reached through the integrator&#8217;s own network.<\/li>\n<li><strong>Where is the data stored?<\/strong> If the integrator is foreign-owned, utility data may sit inside the United States or abroad. Data held outside the United States can fall under the laws of that country, even when the integrator is a U.S. subsidiary.<\/li>\n<li><strong>Does the integrator have remote access for operational support?<\/strong> Remote access creates a path that an attacker who has compromised the integrator could use to pivot into the utility&#8217;s network and take control of systems.<\/li>\n<li><strong>Can the organization operate independently if the integrator is compromised?<\/strong> Redundancies, recovery capability, and secure offline backups of all software required to run equipment can keep operationally critical processes running if the integrator is lost.<\/li>\n<\/ul>\n<h2>Steps to reduce risk when contracting with integrators<\/h2>\n<p>The agencies recommend specific controls that owners and operators can include in service agreements and daily operations.<\/p>\n<ul>\n<li><strong>Include cybersecurity and supply chain security in service agreements.<\/strong> Contracts should cover data storage locations, information protection agreements, protection of ICS data and design documentation, remote access capabilities, the integrator&#8217;s cybersecurity program, change and patch management, securing deployed components such as by changing default passwords and disabling unused ports, listing authorized personnel, and processes that enable local engineering support when needed.<\/li>\n<li><strong>Evaluate devices with external internet exposure.<\/strong> Work with integrators to understand where devices are hosted and minimize exposure by disconnecting devices from the public-facing internet.<\/li>\n<li><strong>Monitor and log remote access.<\/strong> Ensure integrators reach equipment only along routes that operators can monitor. Use on-demand remote access so operators must proactively grant each session.<\/li>\n<li><strong>Request a full inventory of supplied hardware and software.<\/strong> The inventory should include documentation of how each component connects to existing infrastructure and how it will be updated.<\/li>\n<li><strong>Practice manual operations and recovery.<\/strong> Procedures should show where third parties fit into the environment and how recovery will work if they are unavailable.<\/li>\n<\/ul>\n<h2>Reporting and supporting resources<\/h2>\n<p>Operators are urged to report suspicious cyber activity to a local FBI field office, the Internet Crime Complaint Center (IC3), or CISA&#8217;s 24\/7 Operations Center at contact@cisa.dhs.gov or 1-844-Say-CISA (1-844-729-2472). Reports of suspected criminal activity can also go to 1-800-CALL-FBI (1-800-225-5324).<\/p>\n<p>Additional cited resources include CISA&#8217;s Foundations for OT Cybersecurity: Asset Inventory Guidance for Owners and Operators, CISA&#8217;s 2026 Minimum Elements for a Software Bill of Materials (SBOM), the Communications Sector Coordinating Council and IT Sector Coordinating Council&#8217;s Supplier, Products, and Services Threat Evaluation, and NIST&#8217;s Cybersecurity Supply Chain Risk Management guidance. For ICS cybersecurity advisories, the agencies point to CISA&#8217;s Industrial Control Systems pages.<\/p>\n<h2>FAQ<\/h2>\n<h3>What did the joint fact sheet recommend for working with third-party ICS integrators?<\/h3>\n<p>It recommends applying the principle of least privilege, vetting what data and remote access integrators receive, including cybersecurity and supply chain requirements in contracts, monitoring remote sessions, inventorying supplied hardware and software, and maintaining the ability to operate manually if an integrator is compromised.<\/p>\n<h3>What real-world incident is referenced to show integrator compromise risk?<\/h3>\n<p>Between March and April 2025, foreign cyber actors compromised a U.S. industrial automation solutions company that provided system integration, engineering consulting, and SCADA programming services to power utilities and transportation entities. The actors searched for terms such as &#8220;customers&#8221; and &#8220;SCADA&#8221; and assembled roughly 800 files across nine .zip archives, including customer SCADA information, ICS device details, and schematics, for exfiltration.<\/p>\n<h3>Where should critical infrastructure operators report suspicious cyber activity involving an integrator?<\/h3>\n<p>Reports can be made to a local FBI field office, the Internet Crime Complaint Center, or CISA&#8217;s 24\/7 Operations Center at contact@cisa.dhs.gov or 1-844-Say-CISA (1-844-729-2472). Suspected criminal activity can also be reported at 1-800-CALL-FBI (1-800-225-5324).<\/p>\n<p><script type=\"application\/ld+json\">{\"@context\":\"https:\/\/schema.org\",\"@graph\":[{\"@type\":\"FAQPage\",\"mainEntity\":[{\"@type\":\"Question\",\"name\":\"What did the joint fact sheet recommend for working with third-party ICS integrators?\",\"acceptedAnswer\":{\"@type\":\"Answer\",\"text\":\"It recommends applying the principle of least privilege, vetting what data and remote access integrators receive, including cybersecurity and supply chain requirements in contracts, monitoring remote sessions, inventorying supplied hardware and software, and maintaining the ability to operate manually if an integrator is compromised.\"}},{\"@type\":\"Question\",\"name\":\"What real-world incident is referenced to show integrator compromise risk?\",\"acceptedAnswer\":{\"@type\":\"Answer\",\"text\":\"Between March and April 2025, foreign cyber actors compromised a U.S. industrial automation solutions company that provided system integration, engineering consulting, and SCADA programming services to power utilities and transportation entities. The actors searched for terms such as \\\"customers\\\" and \\\"SCADA\\\" and assembled roughly 800 files across nine .zip archives, including customer SCADA information, ICS device details, and schematics, for exfiltration.\"}},{\"@type\":\"Question\",\"name\":\"Where should critical infrastructure operators report suspicious cyber activity involving an integrator?\",\"acceptedAnswer\":{\"@type\":\"Answer\",\"text\":\"Reports can be made to a local FBI field office, the Internet Crime Complaint Center, or CISA's 24\/7 Operations Center at contact@cisa.dhs.gov or 1-844-Say-CISA (1-844-729-2472). Suspected criminal activity can also be reported at 1-800-CALL-FBI (1-800-225-5324).\"}}]}]}<\/script><\/p>\n","protected":false},"excerpt":{"rendered":"<p>A joint fact sheet lays out how critical infrastructure owners can assess and reduce the risks that come with giving third-party ICS integrators access to<\/p>\n","protected":false},"author":3,"featured_media":563,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[1],"tags":[],"class_list":["post-564","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-uncategorized"],"_links":{"self":[{"href":"https:\/\/managedt.com\/blog\/wp-json\/wp\/v2\/posts\/564","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/managedt.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/managedt.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"replies":[{"embeddable":true,"href":"https:\/\/managedt.com\/blog\/wp-json\/wp\/v2\/comments?post=564"}],"version-history":[{"count":2,"href":"https:\/\/managedt.com\/blog\/wp-json\/wp\/v2\/posts\/564\/revisions"}],"predecessor-version":[{"id":566,"href":"https:\/\/managedt.com\/blog\/wp-json\/wp\/v2\/posts\/564\/revisions\/566"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/managedt.com\/blog\/wp-json\/wp\/v2\/media\/563"}],"wp:attachment":[{"href":"https:\/\/managedt.com\/blog\/wp-json\/wp\/v2\/media?parent=564"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/managedt.com\/blog\/wp-json\/wp\/v2\/categories?post=564"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/managedt.com\/blog\/wp-json\/wp\/v2\/tags?post=564"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}