Category: Industrial Safety & Monitoring

  • Aviation Cybersecurity Survey Reports Average Annual Losses of $1.4 Million

    Aviation Cybersecurity Survey Reports Average Annual Losses of $1.4 Million

    A survey commissioned by cybersecurity company Bridewell reports average breach losses of $1.4 million among U.S. aviation organizations during the previous 12 months. Censuswide surveyed 250 cybersecurity professionals working across the sector.

    Common attacks reached operationally sensitive organizations

    Phishing was the most frequently reported attack in the study. Respondents also described malware, credential theft and distributed denial-of-service incidents. The findings show that aviation cyber risk extends across business systems, airport operations, service providers and supply-chain connections.

    Financial impact varied, but a large share of respondents placed losses between hundreds of thousands and several million dollars. Concern was particularly high around operational infrastructure and third parties, where one compromised connection can affect several organizations.

    Spending must translate into tested resilience

    More respondents reported increasing cybersecurity budgets, while specialist recruitment remained difficult. Aviation operators should therefore measure whether investment improves asset visibility, identity controls, segmentation, recovery time and supplier assurance rather than treating spending alone as a maturity indicator.

    The results are relevant to SectechMedia’s Industrial Safety & Monitoring coverage. Airports and aviation service providers should exercise degraded operations, verify backup communications and require suppliers to report incidents promptly. A defensible program links cyber monitoring with physical operations so that a digital outage does not create an unmanaged safety or access-control condition.

    Sources

  • Michigan Plastics Plant Fire Disrupts Power Near South Haven

    Michigan Plastics Plant Fire Disrupts Power Near South Haven

    A major fire at East Jordan Plastics near South Haven, Michigan, spread from plastic pallets stored outside the facility into the factory and disrupted electrical service in parts of the community. Local reporting said smoke was visible for miles as multiple fire agencies responded.

    Propane explosions complicated the response

    South Haven Area Emergency Services said early propane explosions threw tanks into the air while crews worked the third-alarm incident. At least six agencies participated in the response. Employees evacuated safely, and no injuries had been reported in the initial public information.

    The fire’s proximity to critical electrical infrastructure added a second operational problem. The City of South Haven said an electric transmission feed was cut because the incident threatened a municipal utility substation. Power restoration depended on progress toward containment, and the public was asked to stay away from the area.

    Industrial incidents can cross system boundaries

    The event illustrates why industrial emergency planning must account for stored materials, pressurized containers, utility dependencies and access for mutual-aid crews. Detection and suppression systems are important, but pre-incident surveys, isolation plans and coordination with energy providers can determine how far consequences spread beyond a facility. SectechMedia follows related engineering risks in its fire and safety coverage.

    Sources

  • NIST Draft Updates OT Security Guidance With CSF 2.0 and Zero Trust

    NIST Draft Updates OT Security Guidance With CSF 2.0 and Zero Trust

    The U.S. National Institute of Standards and Technology has published an initial public draft of Special Publication 800-82 Revision 4, its updated guide to operational technology security. Dated September 21, the draft retains the central requirement to protect industrial systems without ignoring their safety, reliability and availability constraints.

    What changes in the draft

    NIST reorganizes the guidance around Cybersecurity Framework 2.0 and expands coverage of asset management, monitoring, system administration, risk assessment and zero-trust concepts. The publication addresses operational environments that include industrial control systems, building automation, transportation systems and other technologies whose physical consequences make conventional IT-only security assumptions inadequate.

    The draft does not imply that every zero-trust control can be copied directly into a plant or utility network. Instead, organizations are expected to adapt identity, segmentation, policy enforcement and monitoring practices to equipment lifecycles, deterministic communications and safety requirements. NIST has opened the document for public comment through November 30, 2026.

    Why it matters

    Asset owners can use the draft as a review framework for inventories, remote access, network architecture and incident response. Those subjects also intersect with industrial safety and monitoring, where cybersecurity decisions must support rather than disrupt safe operations.

    Sources

  • Power Resilience and Battery Autonomy for Electronic Security Systems

    Power Resilience and Battery Autonomy for Electronic Security Systems

    Electronic security systems depend on power at cameras, controllers, locks, servers, network switches, communications links and operator workstations. A central uninterruptible power supply may keep the server running while field devices fail. Power resilience therefore begins with the complete operational path, not a single battery specification.

    Define the required security state

    The design team should decide what must remain operational during an outage and for how long. The answer may differ by function. Perimeter detection might need continuous coverage, while selected cameras can move to a reduced frame rate. Access-controlled doors may need to follow life-safety release rules while controllers and event logging remain powered.

    Document the protected loads, acceptable degradation and recovery priorities. Include supporting equipment such as PoE switches, wireless bridges, time servers and monitoring gateways. A device that has power but no network path may still be operationally unavailable.

    Calculate with measured loads and aging

    Battery autonomy should be based on realistic load measurements, conversion losses, temperature and expected aging. Nameplate maximums can overstate normal demand, while a snapshot taken during quiet operation can miss heaters, illuminators, charging or peak lock activity. Use a conservative design method and record the assumptions.

    Battery chemistry, enclosure ventilation and maintenance requirements affect the installation. Capacity normally declines over time, so a system that barely passes at handover may fail before the next planned replacement. Distributed field supplies also need identification and service access.

    Coordinate UPS, generator and network recovery

    Where a generator is available, the battery must bridge startup and transfer without dropping critical loads. Test actual transfer behavior, not only the calculated interval. Some devices reboot after a short disturbance even when average voltage appears acceptable. Network equipment and servers may recover in the wrong sequence, leaving cameras or controllers disconnected.

    A recovery plan should define how services restart, how configuration is preserved and which alarms indicate degraded power. Remote monitoring of battery and supply health is useful only when thresholds are maintained and someone owns the response.

    Test failure modes safely

    Acceptance testing should simulate loss of normal power under controlled conditions. Verify runtime, alarms, transfer, reduced-operation modes and restoration. Inspect event timestamps and confirm that evidence is not lost or corrupted. If the full outage cannot be tested, document the limitation and use component tests with a clear engineering justification.

    Trend results over successive tests rather than recording only pass or fail. A shortening runtime can reveal battery deterioration, increased load or poor environmental conditions before the system falls below its required autonomy.

    Repeat testing after battery replacement, load expansion or major network change. Power resilience is part of industrial safety and monitoring, not a one-time electrical calculation. A reliable design makes the degraded state visible and ensures that restoration does not create a second outage.

    Reference sources

  • Boston Dynamics Positions Mobile Robots for Enterprise Security

    Boston Dynamics Positions Mobile Robots for Enterprise Security

    Boston Dynamics is presenting mobile robots as tools for enterprise inspection and security operations, extending sensor coverage into locations that may be repetitive, remote or hazardous for personnel. International Security Journal examined the shift on 21 September.

    From patrol visibility to repeatable inspection

    A mobile robot can carry cameras, thermal sensors or environmental instruments along a defined route. The security value is not simply movement: the platform must collect consistent observations, transmit them reliably and flag deviations that a human operator can assess. Repeatable inspection can be useful around industrial assets, utility spaces and large campuses.

    Robots do not remove the need for a response team. Stairs, doors, crowds, weather and communications gaps can limit coverage, while an ambiguous alert still requires judgment. Operators also need rules for privacy, recording and interaction with employees or visitors.

    Integration and governance

    Before deployment, organizations should map safe routes, define no-go areas, test loss-of-communications behavior and secure the robot’s credentials. Video and telemetry should enter the existing command workflow rather than create a separate unmonitored console. Mobile robots can strengthen industrial safety and monitoring when their role, limitations and escalation process are explicit.

    Sources

  • Google Cloud Publishes Secure Agentic AI Blueprint for Manufacturing

    Google Cloud Publishes Secure Agentic AI Blueprint for Manufacturing

    Google Cloud has published a blueprint for deploying agentic artificial intelligence in manufacturing while preserving physical safety, operational resilience and human authority. The framework addresses agents that can move beyond analysis to plan tasks or propose actions across enterprise, engineering and plant-floor workflows.

    Three connected operating domains

    The blueprint groups opportunities into business operations, engineering and industrial operations, and unified cybersecurity and resilience. Examples include procurement checks, predictive-maintenance analysis and the triage of security telemetry across IT and operational technology. Google emphasizes targeted pilots, data readiness, governance and access controls rather than unrestricted deployment.

    That distinction matters because an error in a factory can have physical consequences. An agent that summarizes maintenance records presents a different risk from one that can change a production schedule or interact with control infrastructure. The latter requires constrained permissions, tested rollback paths and a human decision point for consequential actions.

    Security architecture before scale

    Manufacturers should separate deterministic control from experimental AI services, validate data flows and monitor agent activity as a privileged workload. Digital twins and isolated environments can support testing without exposing production equipment. The blueprint reinforces a wider industrial monitoring principle: faster automation is valuable only when teams can explain, authorize and reverse its actions.

    Sources

  • HKCERT Warns VPNs, Firewalls and Remote Access Devices Face Rising Attacks

    HKCERT Warns VPNs, Firewalls and Remote Access Devices Face Rising Attacks

    Hong Kong’s computer emergency response team is warning organizations that VPN appliances, firewalls, routers and remote-access systems remain high-value entry points for attackers. The guidance, issued on 15 September and reported by Industrial Cyber, stresses that installing a patch does not prove an already-exposed device is clean.

    Why patching may be only the first step

    An attacker can exploit an edge device before remediation, steal credentials, create an account or establish another persistence mechanism. Closing the original vulnerability does not automatically remove those access paths. HKCERT therefore recommends reviewing accounts, active sessions, privilege changes, logs and suspicious data transfers after patching, particularly when a vulnerability is known to have been exploited.

    The issue matters in industrial environments because remote-access systems often bridge corporate and operational networks. An edge compromise can expose credentials or routes that would otherwise remain unavailable from the public internet. Asset owners need an accurate inventory of external interfaces, including systems installed by contractors or retained after projects end.

    Operational response

    Defenders should prioritize exploited vulnerabilities, enforce multifactor authentication, revoke suspect sessions and investigate for unauthorized accounts or backdoors. Monitoring should continue after the immediate incident. These measures fit a broader cyber-physical security program that treats identity, network architecture and recovery planning as connected controls.

    Sources

  • Agility Robotics Unveils Digit 5, a Humanoid Built to Work Without Safety Cages

    Agility Robotics Unveils Digit 5, a Humanoid Built to Work Without Safety Cages

    Agility Robotics unveiled Digit 5, the fifth generation of its general-purpose humanoid robot and the company’s first designed for what it calls “cooperatively safe work at scale” — operating alongside people without the physical safety cages traditional industrial robots require. The robot uses sensors, human-detection and independent motion control to stop or reposition itself when a person moves into its workspace, rather than relying on fixed barriers to keep people out.

    Digit 5 stands 5 feet 11 inches tall, weighs 284 pounds and can reach up to 7.2 feet, with grippers that let it lift up to 50 pounds repeatedly and recharge in nine minutes for shifts the company says can run more than 20 hours a day. Agility reports more than $300 million in multi-year customer orders as of May 2026 and says it plans to make Digit available for commercial deployment outside North America for the first time, starting with the EU and UK, with CE and other regional certification marks.

    Why it matters

    Most humanoid and industrial robots still depend on fenced-off work cells to keep people safe; a robot engineered to share floor space with workers without that barrier changes the layout calculus for warehouses and factories, and shifts more of the safety burden onto the robot’s own sensing and control systems rather than the facility’s physical design.

    Sources

  • Coast Guard and FBI Board Oil Tankers After Cyberattacks Reach Engine-Room Systems

    Coast Guard and FBI Board Oil Tankers After Cyberattacks Reach Engine-Room Systems

    The US Coast Guard and FBI boarded at least two foreign-flagged, US-bound oil tankers in the Gulf of Mexico — including the Liberian-flagged VL Prosperity — on August 21 and August 24, 2026, after detecting evidence that the vessels’ onboard networks had been compromised. Coast Guard Rear Adm. Amy Grable confirmed “evidence of a malicious cyber actor” on the ship’s IT/OT systems, though the Coast Guard has not attributed the intrusion to any state actor. A joint team of Coast Guard cyber specialists, a vessel inspector and an FBI Cyber Action Team spent four days aboard the VL Prosperity.

    Iran’s Mehr News Agency separately reported that the VL Prosperity suffered a cyberattack on August 7 while transiting the Strait of Gibraltar, alleging the intrusion reached engine-room systems — altering coolant flow, engine speed and fuel delivery — and knocked out communications for roughly 30 hours; those specific technical claims have not been confirmed by the Coast Guard. Officials say there is no evidence the vessels operated unsafely, and the Coast Guard says it has conducted an estimated 40-50 similar cyber-related boardings over the past year.

    Why it matters

    Commercial vessels increasingly run networked engine, navigation and fuel-management systems that were not designed with the same threat model as IT networks — an attacker reaching those systems mid-voyage, even briefly, raises the kind of physical-safety stakes that a typical office network breach does not.

    Sources

  • Ransomware Attacks on Manufacturers Rose Nearly 40% in First Half of 2026, Report Finds

    Ransomware Attacks on Manufacturers Rose Nearly 40% in First Half of 2026, Report Finds

    Cyber-risk intelligence firm Black Kite reported 1,183 manufacturing-sector ransomware victims in the first seven months of 2026, a nearly 40% increase year-over-year, with attacks on the sector more than doubling since 2023. Manufacturing accounted for 22% of all 7,551 ransomware disclosures the firm tracked across all industries in the period.

    The report found newer ransomware groups — including The Gentlemen, which alone claimed 142 manufacturing victims, along with Qilin, Akira, DragonForce and INC Ransom — have displaced the threat-actor groups that previously dominated the sector. Black Kite said 73% of attacks hit mid-market companies, with a median victim revenue of $42.9 million, and that European victim counts rose 85.4% year-over-year while the US share of global victims fell from 52.3% to 34.8%.

    Why it matters

    The shift toward mid-market manufacturers suggests attackers are increasingly targeting companies that may have less mature security operations than large enterprises but still enough revenue — and enough dependence on continuous production — to make ransom payment attractive.

    Sources