Category: Smart Cities

  • Waymo Names Munich as Its Third City Outside the US for Driverless Ride-Hailing

    Waymo Names Munich as Its Third City Outside the US for Driverless Ride-Hailing

    Waymo announced on August 28, 2026, that Munich will become its third international city for autonomous ride-hailing, following earlier expansions to London and Tokyo, according to reporting from Euronews. The company said it is laying the operational and regulatory groundwork for a driverless service in the German city but has not set a specific public launch date.

    Waymo pointed to safety data from its US operations to make the case for expansion, citing internal analysis suggesting its autonomous vehicles are involved in significantly fewer serious-injury and fatal crashes per mile than human-driven taxis in the same markets. The company noted that Europe records roughly 20,000 road fatalities annually, with driver error cited as a factor in a majority of crashes, as part of its rationale for prioritizing European expansion.

    Part of a Broader European Push for Autonomous Driving

    The Munich announcement comes as European regulators show growing openness to autonomous and driver-assistance systems more broadly; a recent Dutch approval of Tesla’s Full Self-Driving Supervised system has been followed by similar regulatory movement in Denmark, Lithuania, and Estonia. Waymo already operates fully driverless commercial service across ten US cities, where the company has said it now completes more than half a million paid trips per week.

    Munich’s position as a major automotive-engineering hub, home to BMW and a dense supplier base, is likely to shape how quickly Waymo can secure local regulatory approval and testing partnerships. The company has not disclosed which German authorities it is engaging with or a target timeline for public rides to begin.

  • Smart Building Security Integration: Converging BMS, IoT and Physical Security Systems

    Smart Building Security Integration: Converging BMS, IoT and Physical Security Systems

    A modern commercial building typically runs several parallel digital systems: a building management system (BMS) controlling HVAC, lighting and elevators; a physical security platform handling access control and video surveillance; and a growing layer of IoT sensors monitoring everything from occupancy to air quality to energy consumption. Historically, these systems were built, procured and operated independently, often by different contractors using proprietary protocols with little interoperability. That is changing as building owners push for centralized operational visibility and as IP-based communication becomes the default across all three domains.

    What Integration Actually Enables

    • Occupancy-aware building operations. Access control and video occupancy data can inform HVAC and lighting schedules in real time, reducing energy use in unoccupied zones without requiring separate occupancy sensors purpose-built for BMS use.
    • Correlated alarm response. A door-forced-open alarm correlated with an unexpected HVAC or lighting change in the same zone can help security operators distinguish a genuine intrusion from a false alarm or scheduled maintenance activity.
    • Unified emergency response. Fire alarm, access control and BMS integration allows automated responses during emergencies — such as unlocking designated egress doors and adjusting HVAC to support smoke control — to be coordinated from a single event trigger rather than requiring separate manual actions across disconnected systems.
    • Centralized operational dashboards. Facility operators increasingly want a single interface showing security status, environmental conditions and building system health, rather than switching between multiple vendor-specific consoles.

    The Security Cost of Convergence

    Integration is not free from a risk standpoint. Building management systems have historically been built with less emphasis on cybersecurity than IT infrastructure, and connecting them to the same network as access control and video systems can create pathways for an attacker who compromises a lower-security BMS component to reach higher-value security infrastructure, or vice versa. IoT sensors, in particular, are frequently deployed in large numbers with minimal device management, making them a common weak point in an otherwise well-secured network if not properly segmented and monitored.

    Effective smart-building integration therefore requires the same network segmentation discipline applied to any converged IT/OT environment: BMS, IoT and security systems should typically sit on segmented VLANs with controlled inter-segment communication, rather than a single flat network simply because integration is technically possible.

    Governance and Organizational Challenges

    Beyond the technical architecture, smart-building integration raises questions of system ownership that many organizations have not fully resolved: does facilities management or security operations own the integrated platform? Who is responsible for patching BMS controllers that were historically outside the IT department’s purview? These governance questions frequently prove harder to resolve than the underlying technical integration, and unresolved ownership questions are a common reason integration projects stall after the initial technology deployment.

    FAQ

    Does smart building integration require replacing existing BMS or security systems?

    Not necessarily. Many integration platforms are designed to sit above existing BMS and security systems, aggregating data through APIs or middleware rather than requiring wholesale replacement of underlying infrastructure, though the degree of integration achievable depends on how open or proprietary the existing systems’ interfaces are.

    Is network segmentation still necessary if all systems are managed by the same integrated platform?

    Yes. A shared management platform does not eliminate the value of network segmentation; the two operate at different layers. Segmentation limits the blast radius of a compromised device at the network level, regardless of which platform is used to manage the devices sitting on that network.

    Conclusion

    Converging BMS, IoT and physical security in commercial buildings delivers real operational value, from energy efficiency to more coordinated emergency response, but it also expands the attack surface if approached purely as a data-integration exercise without corresponding network segmentation and governance work. Organizations that succeed at smart-building integration tend to treat it as a security architecture project with an operational-efficiency benefit, not the reverse.

  • Flock Safety Cuts License-Plate Data Retention to Seven Days Amid Surveillance Backlash

    Flock Safety Cuts License-Plate Data Retention to Seven Days Amid Surveillance Backlash

    New Guardrails Announced Amid Growing Criticism

    Flock Safety, which operates a nationwide network of more than 119,000 automated license-plate-reader (ALPR) cameras used by law enforcement agencies, announced a set of privacy and accountability reforms on August 13, 2026, according to Fox Business. The changes come as the company faces mounting criticism from privacy advocates and elected officials over mass surveillance concerns and reports of officers misusing the technology, including cases documented by Wired in which police reportedly used Flock data to track romantic partners.

    Flock CEO Garrett Langley discussed the changes publicly, telling Fox Business’s “Varney & Co.” that the reforms were a direct response to backlash the company has faced over its car-tracking cameras. Some local officials have gone further than criticism: Knox County, Tennessee, Mayor Glenn Jacobs has called for a national moratorium on further deployment of Flock’s camera network, according to Fox Business.

    Shorter Retention, Mandatory Audit Controls

    The centerpiece of the announcement is a reduction in Flock’s standard data-retention window from 30 days to seven. The company said that roughly 90% of all searches conducted on its platform already occur within a week of data capture, arguing the shorter window would have limited practical effect on law enforcement’s ability to use the system while narrowing the amount of location data stored on Flock’s servers at any given time. For cases requiring longer retention, Flock is introducing an “Evidence Mode” feature that lets agencies preserve specific data for extended periods under state or local policy.

    Flock is also making its “Audit Assistance” feature — which flags abnormal search behavior and can lock a user out of the system in real time pending administrator review — mandatory for all law enforcement customers rather than optional; the company said roughly a third of agencies had turned the feature on voluntarily before the change. Separately, Flock is making the previously optional requirement to log a case code with every search mandatory going forward, with an override reserved for emergencies such as missing-child cases. “A search without a reason is a search that shouldn’t happen in the first place, and now Flock’s system automatically treats it that way,” the company told Fox Business.

    New Controls Over Cross-Agency Data Sharing

    The company is also giving individual agencies more granular control over which types of cases they will share camera search access for with other jurisdictions. In comments to Fox Business, Flock gave the example that “City A could allow City B to search its cameras for a stolen vehicle or violent crime while blocking searches related to immigration enforcement” — an option aimed at addressing concerns that Flock’s interconnected camera network could be used for purposes individual municipalities have not authorized.

    Civil liberties groups were not satisfied by the announcement. The American Civil Liberties Union said in a statement reported by Fox Business that the reforms “seem to be a thinly veiled PR attempt to counter communities’ genuine privacy concerns with its mass surveillance system with largely hollow security promises, rather than an earnest effort to address them.” Flock, for its part, has pointed to its own figures on the technology’s investigative use, telling Fox Business that its cameras were involved in roughly 1 million investigations last year and were tied to the location of about 10,000 missing people — figures that reflect the company’s own reporting and have not been independently verified.

    Sources

  • Smart City Security: Cameras, Sensors and Public-Safety Platforms

    Smart City Security: Cameras, Sensors and Public-Safety Platforms

    Smart-city security is moving beyond large camera networks toward integrated situational awareness that combines video, environmental sensors, transport data, emergency communications and analytics.

    From surveillance to situational awareness

    A camera-only model produces large volumes of video but limited context. Modern platforms correlate video with traffic, access, environmental, acoustic and emergency-service information.

    Edge intelligence

    Running analytics at the edge can reduce bandwidth and provide faster alerts. Typical functions include object detection, crowd density, traffic incidents and unusual behavior, but deployment must be guided by clear public policy.

    Privacy and governance

    Smart-city security can affect millions of people. Data minimization, retention limits, auditability, transparency and role-based access are essential for maintaining public trust.

    Resilient communications

    City platforms depend on fiber, wireless and cloud connectivity. Architecture should assume outages and include local recording, redundant paths and graceful degradation.

    A platform, not a single product

    Successful smart-city deployments are built around interoperability. Open interfaces allow agencies to combine sensors from different vendors while preserving cybersecurity and operational control.

    Conclusion

    Smart City Security: Cameras, Sensors and Public-Safety Platforms should be evaluated as part of a broader operational architecture. The strongest deployments combine suitable sensing technology, resilient communications, clear procedures and measurable performance rather than relying on a single device or headline specification.