{"id":216,"date":"2026-10-25T13:32:18","date_gmt":"2026-10-25T12:32:18","guid":{"rendered":"https:\/\/www.lifee.ai\/blog\/2026\/10\/25\/smart-building-cybersecurity-risks\/"},"modified":"2026-10-25T15:24:41","modified_gmt":"2026-10-25T14:24:41","slug":"smart-building-cybersecurity-risks","status":"publish","type":"post","link":"https:\/\/www.lifee.ai\/blog\/2026\/10\/25\/smart-building-cybersecurity-risks\/","title":{"rendered":"6 Smart Building Cybersecurity Risks That Operators Often Miss"},"content":{"rendered":"<p>Your smart building&#8217;s greatest vulnerability isn&#8217;t the front door; it&#8217;s the network connecting every sensor, thermostat, and access control system inside. As automation deepens across commercial and residential properties, cybersecurity gaps widen in places most operators never think to check. Lifee, a French leader in AI-powered home automation and energy efficiency solutions, has seen firsthand how interconnected systems create blind spots that hackers exploit with alarming ease.<\/p>\n<p>This guide walks you through six overlooked cybersecurity risks in intelligent buildings and shows you practical steps to lock them down before they become costly breaches.<\/p>\n<h2>1. Shadow IoT Devices and Unmanaged Endpoints<\/h2>\n<p><a href=\"https:\/\/www.lifee.ai\/en\/iot.php\" target=\"_blank\" rel=\"noopener\">Smart buildings contain air-quality<\/a> sensors, smart locks, occupancy counters, cameras, thermostats, gateways, and connected energy meters. Each device can become an entry point when it is installed outside the approved process, retains factory credentials, lacks current firmware, or disappears from the operator\u2019s asset register. Building automation is operational technology, not ordinary office IT: a compromised endpoint can affect comfort, energy use, physical access, or safety-related operations.<\/p>\n<p>The problem often begins innocently. A contractor adds a wireless camera during a renovation, a maintenance technician connects a diagnostic gateway, or a tenant installs a connected appliance on a shared network. The device may remain active after the project ends, while nobody knows its owner, purpose, software version, or removal date.<\/p>\n<ul>\n<li><strong>Discover every endpoint continuously.<\/strong> Use passive network discovery and switch, wireless, and gateway logs to identify devices without disrupting sensitive building controls. Record the manufacturer, model, location, owner, network zone, firmware version, communication protocols, and business purpose.<\/li>\n<li><strong><a href=\"https:\/\/www.lifee.ai\/en\/audit.php\" target=\"_blank\" rel=\"noopener\">Control the full device<\/a> lifecycle.<\/strong> Require approval before installation, verify security settings during commissioning, schedule firmware reviews, and document secure removal. A device that is no longer needed should be disconnected, credentials revoked, and data erased according to policy.<\/li>\n<li><strong>Separate unknown equipment immediately.<\/strong> Place newly detected or unidentified devices in a restricted quarantine network until facilities and IT confirm their legitimacy. This prevents an unauthorised thermostat or contractor gateway from reaching BMS servers while preserving evidence for investigation.<\/li>\n<\/ul>\n<div class=\"tip\">\n<p>Lifee can support a security-by-design approach for AI-powered home automation and energy-efficiency projects by helping teams map connected devices, data flows, and control dependencies before deployment. For larger sites, combine this project inventory with passive monitoring, vulnerability management, and a named owner for every endpoint.<\/p>\n<\/div>\n<p>NIST\u2019s 2026 building automation guidance recommends practical measures such as asset identification, risk assessment, monitoring, incident response, and tested backup and restoration procedures. Its operational-technology guidance also treats building automation systems as systems that interact with the physical environment, where availability and safety matter alongside confidentiality.<\/p>\n<h2>2. Insecure Building Management System Integrations<\/h2>\n<p>A Building Management System can coordinate HVAC, lighting, elevators, access control, fire-related interfaces, metering, and energy management. Its value comes from integration, but every API, remote-access path, protocol converter, cloud connector, and legacy bridge expands the attack surface.<\/p>\n<p>Older controllers may rely on protocols that were designed for trusted networks rather than hostile environments. A modern analytics platform can also create risk if it receives broad permissions, uses long-lived credentials, exposes an internet-facing interface, or allows a vendor to connect through an unmanaged remote-access tool.<\/p>\n<ul>\n<li><strong>Map trust relationships before connecting systems.<\/strong> Document which platform initiates communication, what data crosses the boundary, which commands are permitted, and whether the connection is required continuously. Remove unused integrations rather than accepting them as permanent features.<\/li>\n<li><strong>Restrict interfaces to the minimum necessary.<\/strong> Use allowlists, mutual authentication where supported, short-lived credentials, encrypted connections, and role-based permissions. An energy dashboard should not automatically receive permission to change access-control settings or safety-critical parameters.<\/li>\n<li><strong>Make vendors part of the control environment.<\/strong> Contracts should define patch responsibilities, vulnerability disclosure, logging, remote-access approval, incident notification, secure development practices, and end-of-service obligations. Review these conditions whenever a system is upgraded or a supplier changes.<\/li>\n<\/ul>\n<table>\n<thead>\n<tr>\n<th>Integration point<\/th>\n<th>Typical exposure<\/th>\n<th>Practical control<\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td>Cloud analytics platform<\/td>\n<td>Excessive API permissions or exposed credentials<\/td>\n<td>Use scoped tokens, encryption, access logging, and periodic permission reviews<\/td>\n<\/tr>\n<tr>\n<td>Legacy controller gateway<\/td>\n<td>Unsupported software or insecure protocol translation<\/td>\n<td>Isolate the gateway, restrict traffic, monitor commands, and plan replacement<\/td>\n<\/tr>\n<tr>\n<td>Vendor remote access<\/td>\n<td>Persistent accounts and uncontrolled support sessions<\/td>\n<td>Require approval, MFA, time-limited access, session logging, and immediate revocation<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<p>NIST\u2019s 2026 revision of its OT security guidance explicitly includes building automation and control systems, physical access control, environmental monitoring, and cloud convergence. That scope reflects the reality that BMS security cannot be delegated entirely to a facilities vendor or treated as a conventional office-network issue.<\/p>\n<h2>3. Weak Authentication and Access Control Policies<\/h2>\n<p>Default passwords, shared administrator accounts, reused credentials, and excessive privileges allow attackers to turn a small foothold into control over valuable systems. A password may be strong and still create risk if it is shared among contractors, never expires when staff leave, or grants access to every building in a portfolio.<\/p>\n<ul>\n<li><strong><a href=\"https:\/\/www.lifee.ai\/en\/best-password-managers-2026.php\" target=\"_blank\" rel=\"noopener\">Replace shared access with named identities<\/a>.<\/strong> Give employees and suppliers individual accounts tied to a role, site, and business need. This improves accountability and makes it possible to disable one person without interrupting every maintenance relationship.<\/li>\n<li><strong>Apply phishing-resistant MFA where possible.<\/strong> Protect BMS consoles, cloud dashboards, VPNs, privileged accounts, and remote-support portals with MFA. If a legacy controller cannot support MFA, place it behind a hardened jump host and restrict access to approved administrative paths.<\/li>\n<li><strong>Use least privilege and time-limited permissions.<\/strong> A technician troubleshooting HVAC does not need access to tenant video feeds or door-controller administration. Grant elevated rights only for the maintenance window, then review and remove them automatically.<\/li>\n<li><strong>Test emergency access without creating permanent back doors.<\/strong> Maintain a controlled break-glass procedure for outages, store credentials securely, log every use, and rotate them after an incident or emergency intervention.<\/li>\n<\/ul>\n<div class=\"tip\">\n<p>For Lifee projects, access design should be discussed alongside automation workflows. A secure AI-powered system should distinguish occupants, facilities staff, installers, administrators, and service providers, ensuring that convenience does not become unrestricted control.<\/p>\n<\/div>\n<p>Perimeter protection alone is insufficient because compromised credentials can appear legitimate. Identity governance, device authentication, privileged-access management, and regular access reviews create a stronger barrier between an exposed endpoint and a high-impact building command.<\/p>\n<h2>4. Overlooked Data Privacy and Compliance Risks<\/h2>\n<p>Smart buildings collect more than energy readings. Occupancy patterns, badge events, video, indoor-environment data, mobile identifiers, tenant preferences, and automation histories can reveal when people enter, where they move, and how spaces are used. Even data that appears anonymous may become identifying when combined with access logs, calendars, or camera systems.<\/p>\n<ul>\n<li><strong>Minimize collection at the design stage.<\/strong> Use the least precise sensor data that can achieve the operational goal. If a zone-level count is sufficient for ventilation, storing individual movement histories creates unnecessary privacy exposure.<\/li>\n<li><strong>Set retention limits that operators can enforce.<\/strong> Define how long each data category is kept, where it is stored, who can retrieve it, and how deletion is verified. Retention should reflect operational, legal, and contractual needs rather than unlimited storage capacity.<\/li>\n<li><strong>Control secondary use and supplier access.<\/strong> An analytics provider should not automatically reuse occupancy or energy data for unrelated purposes. Contracts should identify processing roles, permitted uses, subprocessors, security measures, breach notification duties, and deletion requirements.<\/li>\n<li><strong>Protect data throughout its lifecycle.<\/strong> Encrypt information in transit and at rest, separate identifiers from operational datasets, restrict exports, and monitor unusual downloads. Privacy protection must cover backups, test environments, support tickets, and system logs as well as production databases.<\/li>\n<\/ul>\n<p>Privacy and cybersecurity overlap but are not identical. A system may remain available while exposing sensitive movement data, or it may protect tenant records while attackers manipulate temperature or access settings. Operators should therefore conduct privacy impact assessments and operational-security reviews as separate but connected activities.<\/p>\n<table>\n<thead>\n<tr>\n<th>Data type<\/th>\n<th>Potential impact<\/th>\n<th>Recommended treatment<\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td>Occupancy and movement data<\/td>\n<td>Inference about individuals, routines, or vulnerable spaces<\/td>\n<td>Minimize precision, limit retention, restrict access, and aggregate where practical<\/td>\n<\/tr>\n<tr>\n<td>Video and access events<\/td>\n<td>Identity exposure and physical-security consequences<\/td>\n<td>Use strict role controls, encryption, audit logs, and documented retention periods<\/td>\n<\/tr>\n<tr>\n<td>Energy and environmental data<\/td>\n<td>Disclosure of business activity or building usage patterns<\/td>\n<td>Separate tenants where appropriate, control exports, and define permitted analytics uses<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<p><a href=\"https:\/\/www.lifee.ai\/en\/projects.php\" target=\"_blank\" rel=\"noopener\">Lifee\u2019s intelligent energy audits and predictive automation<\/a> can deliver greater efficiency when data governance is built into the project from the beginning. Clear purposes, limited collection, and transparent tenant communication help preserve trust while still enabling useful optimization.<\/p>\n<div class=\"youtube-video-embed\" style=\"margin: 20px 0\">\n <iframe loading=\"lazy\" title=\"Security and Safety in a Smart Building\" width=\"640\" height=\"360\" src=\"https:\/\/www.youtube.com\/embed\/WZTR1TykXYA?feature=oembed\" frameborder=\"0\" allow=\"accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture; web-share\" referrerpolicy=\"strict-origin-when-cross-origin\" allowfullscreen><\/iframe><\/p>\n<p class=\"video-caption\" style=\"font-style: italic;text-align: center;margin-top: 10px\">Related video: Security and Safety in a Smart Building<\/p>\n<\/div>\n<h2>5. Insufficient Network Segmentation and Monitoring<\/h2>\n<figure class=\"in-article-image\" style=\"margin: 24px 0\"><img decoding=\"async\" src=\"https:\/\/s01.swdrive.fr\/index.php\/s\/ziLLpfcpoorSgzz\/download\" alt=\"6 Smart Building Cybersecurity Risks That Operators Often Miss , 5. Insufficient Network Segmentation and Monitoring\" style=\"width: 100%;height: auto;border-radius: 8px;display: block\" loading=\"lazy\" \/><\/figure>\n<p>A flat network allows an attacker who compromises a low-value device to search for more valuable systems. Digital signage, guest Wi-Fi, cameras, tenant networks, BMS servers, access control, and safety-related interfaces should not share unrestricted connectivity.<\/p>\n<ul>\n<li><strong>Segment by function and consequence.<\/strong> Create distinct zones for corporate IT, building controls, physical security, tenant services, guest access, and vendor connections. The boundaries should reflect what could happen if a zone were compromised, not merely how devices are manufactured.<\/li>\n<li><strong>Control traffic between zones explicitly.<\/strong> Use deny-by-default rules, approved conduits, protocol restrictions, and monitored jump hosts. A VLAN alone does not provide meaningful protection if routing and administrative access remain unrestricted.<\/li>\n<li><strong>Monitor behavior, not only signatures.<\/strong> Alert on unusual controller commands, new outbound connections, unexpected protocol use, repeated authentication failures, and activity outside maintenance windows. Baselines should account for seasonal changes so that energy optimization does not generate constant false alarms.<\/li>\n<li><strong>Prepare for safe containment.<\/strong> Operators need a tested procedure for isolating a compromised device without disabling ventilation, access, fire interfaces, or other essential functions. Manual operating procedures and fallback controls should be documented before an incident occurs.<\/li>\n<\/ul>\n<div class=\"tip\">\n<p>NIST\u2019s building automation materials emphasize monitoring and tested recovery. For Lifee deployments, include network diagrams, data-flow maps, alert ownership, escalation contacts, and manual fallback procedures in the project handover package.<\/p>\n<\/div>\n<p>Effective segmentation is a living design. Renovations, new tenants, cloud services, and contractor connections can silently weaken it, so rules and diagrams should be reviewed whenever the building\u2019s technology or operational dependencies change.<\/p>\n<h2>6. Neglecting Cybersecurity in Energy Efficiency and Automation Projects<\/h2>\n<figure class=\"in-article-image\" style=\"margin: 24px 0\"><img decoding=\"async\" src=\"https:\/\/s01.swdrive.fr\/index.php\/s\/nPpxKxisiYiPmPY\/download\" alt=\"6 Smart Building Cybersecurity Risks That Operators Often Miss , 6. Neglecting Cybersecurity in Energy Efficiency and Automation Projects\" style=\"width: 100%;height: auto;border-radius: 8px;display: block\" loading=\"lazy\" \/><\/figure>\n<p>Energy-efficiency initiatives increasingly combine smart meters, predictive HVAC, contextual automation, cloud analytics, and AI models. These systems can reduce waste and improve comfort, but they also create new dependencies on data quality, software updates, external platforms, and automated commands.<\/p>\n<ul>\n<li><strong>Start with threat modeling, not procurement.<\/strong> Identify what happens if sensor data is falsified, an optimization platform becomes unavailable, or an automated command is manipulated. This helps teams select safe defaults, approval thresholds, and fallback modes before installation.<\/li>\n<li><strong>Protect model inputs and automated decisions.<\/strong> Validate unusual sensor readings, limit the range and frequency of automated commands, and require human approval for high-impact changes. An AI system should not respond to one corrupted occupancy signal by making unsafe or costly building-wide adjustments.<\/li>\n<li><strong>Measure security alongside efficiency.<\/strong> Track patch age, unresolved vulnerabilities, privileged accounts, backup-test results, alert response time, and vendor-access activity alongside energy consumption and carbon performance. A project that saves energy but cannot recover from a cyber incident is not operationally resilient.<\/li>\n<li><strong>Test failure and recovery scenarios.<\/strong> Confirm that HVAC, lighting, access, and monitoring can operate safely if the cloud platform, network, or automation controller is unavailable. Maintain secure backups of configurations and test restoration under realistic conditions.<\/li>\n<\/ul>\n<p><a href=\"https:\/\/www.lifee.ai\/en\/ai-powered-autonomous-gate.php\" target=\"_blank\" rel=\"noopener\">Lifee\u2019s combination of AI-powered LLM automation<\/a>, custom energy-efficiency solutions, intelligent energy audits, and contextual automation makes cybersecurity a core design requirement rather than a separate technical task. Cross-functional reviews between IT, OT, facilities, sustainability, and privacy teams can preserve the benefits of automation without creating invisible operational dependencies.<\/p>\n<h2>From Detection to Recovery: The Missing Layer in Building Security<\/h2>\n<h3>Incident response must include facilities operations<\/h3>\n<p>A cyber incident in a smart building can affect temperature, doors, elevators, lighting, alarms, or tenant communications. The response plan should therefore combine security analysts with facilities managers, electricians, vendors, building owners, and communications staff, with clear authority for isolating systems and switching to safe manual operation.<\/p>\n<h3>Backups are useful only when restoration is tested<\/h3>\n<p>Keep protected backups of BMS configurations, controller programs, network diagrams, credentials, and critical operating procedures. NIST\u2019s building automation guidance highlights backup and restoration planning, but operators should also test whether backups are complete, unaltered, accessible during an outage, and compatible with replacement hardware.<\/p>\n<h3>Supply-chain assurance continues after installation<\/h3>\n<p>Security should be reviewed throughout the equipment and software lifecycle, including vulnerability notifications, end-of-support dates, subcontractors, firmware signing, component provenance, and secure disposal. A vendor questionnaire at purchase cannot compensate for years of unmonitored remote access or unsupported controllers.<\/p>\n<h3>Measure resilience in terms operators can act on<\/h3>\n<p>Useful indicators include the percentage of inventoried devices, time to remove former-user access, coverage of MFA, age of critical patches, number of unapproved remote connections, time to detect unusual activity, and time to restore tested configurations. These measures turn cybersecurity from a one-time compliance exercise into an operating discipline.<\/p>\n<h2>A Practical Smart Building Cybersecurity Baseline<\/h2>\n<table>\n<thead>\n<tr>\n<th>Control area<\/th>\n<th>Minimum baseline<\/th>\n<th>Evidence to retain<\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td>Asset management<\/td>\n<td>Continuously maintained inventory with owner, location, firmware, purpose, and network zone<\/td>\n<td>Asset register, discovery reports, change approvals, removal records<\/td>\n<\/tr>\n<tr>\n<td>Identity<\/td>\n<td>Named accounts, MFA for privileged access, least privilege, and rapid offboarding<\/td>\n<td>Access reviews, authentication logs, vendor session records<\/td>\n<\/tr>\n<tr>\n<td>Architecture<\/td>\n<td>Separated IT, OT, tenant, guest, physical-security, and vendor pathways<\/td>\n<td>Current diagrams, firewall rules, approved data flows<\/td>\n<\/tr>\n<tr>\n<td>Vulnerability management<\/td>\n<td>Risk-based patching, compensating controls for legacy systems, and documented exceptions<\/td>\n<td>Patch reports, risk acceptances, remediation plans<\/td>\n<\/tr>\n<tr>\n<td>Detection<\/td>\n<td>Centralized logs and alerts for abnormal commands, access, traffic, and remote sessions<\/td>\n<td>Alert rules, incident tickets, escalation records<\/td>\n<\/tr>\n<tr>\n<td>Recovery<\/td>\n<td>Offline or protected backups, manual procedures, supplier contacts, and restoration tests<\/td>\n<td>Backup inventories, test results, recovery time records<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<h2>Key Takeaways<\/h2>\n<ul>\n<li><strong>Visibility comes first.<\/strong> Continuous asset discovery and ownership records expose shadow IoT devices before they become forgotten access points.<\/li>\n<li><strong>Integration requires boundaries.<\/strong> APIs, cloud services, legacy gateways, and vendor connections should use limited permissions, monitored pathways, and explicit security responsibilities.<\/li>\n<li><strong>Identity is a control surface.<\/strong> Named accounts, MFA, least privilege, and time-limited supplier access reduce the chance that stolen credentials become building-wide control.<\/li>\n<li><strong>Privacy belongs in the design.<\/strong> Occupancy, access, video, and energy data require purpose limitation, retention rules, encryption, and controlled third-party use.<\/li>\n<li><strong>Resilience goes beyond prevention.<\/strong> Segmentation, monitoring, incident response, secure backups, and tested restoration determine how safely a building can continue operating after compromise.<\/li>\n<li><strong>Sustainability and cybersecurity reinforce each other.<\/strong> Lifee\u2019s automation and energy-efficiency projects can deliver lasting value when threat modeling, governance, and recovery are built into the project lifecycle.<\/li>\n<\/ul>\n<h2>Frequently Asked Questions<\/h2>\n<h3>What is the most overlooked smart building cybersecurity risk?<\/h3>\n<p>Unmanaged devices and forgotten remote-access paths are among the most frequently overlooked risks because they are introduced during maintenance, renovation, or vendor work rather than through formal IT projects. Continuous discovery, ownership records, and immediate quarantine of unknown equipment provide a practical first defense.<\/p>\n<h3>How should a BMS be separated from the corporate network?<\/h3>\n<p>Place building controls in dedicated operational zones, restrict communication to approved conduits, use hardened administrative access, and monitor commands and remote sessions. The exact design should reflect safety, availability, legacy constraints, and the consequences of losing or manipulating each function.<\/p>\n<h3>Can AI-powered energy management create cybersecurity risks?<\/h3>\n<p>Yes. AI and predictive energy systems depend on sensors, APIs, cloud services, models, and automated commands. Validate inputs, limit permissions, protect training and operational data, require approval for high-impact changes, and maintain a safe fallback mode when the platform or network is unavailable.<\/p>\n<h3>What should operators do first if resources are limited?<\/h3>\n<p>Begin with an accurate asset inventory, remove default credentials, protect privileged and remote access with MFA, segment the most consequential systems, and create tested backups. These controls establish visibility and reduce the likelihood that a single compromised device can affect the entire building.<\/p>\n<p>Smart building cybersecurity is an ongoing operational responsibility, not a one-time technology purchase. Risks can emerge from a forgotten sensor, a poorly governed integration, a former contractor account, an exposed data store, or an automation project that lacks a recovery path. By combining NIST-aligned OT practices with disciplined identity management, segmentation, privacy controls, monitoring, and tested restoration, operators can protect occupants, assets, and essential services. Lifee\u2019s intelligent automation and energy-efficiency solutions are strongest when sustainability, comfort, and cyber resilience are designed together from the start.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Protect your smart building from hidden cybersecurity risks. Discover 6 common vulnerabilities operators often miss and secure your network today.<\/p>\n","protected":false},"author":1,"featured_media":227,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[1,14],"tags":[],"class_list":["post-216","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-non-classe","category-smart-buildings-commercial-real-estate"],"_links":{"self":[{"href":"https:\/\/www.lifee.ai\/blog\/wp-json\/wp\/v2\/posts\/216","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.lifee.ai\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.lifee.ai\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.lifee.ai\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.lifee.ai\/blog\/wp-json\/wp\/v2\/comments?post=216"}],"version-history":[{"count":2,"href":"https:\/\/www.lifee.ai\/blog\/wp-json\/wp\/v2\/posts\/216\/revisions"}],"predecessor-version":[{"id":226,"href":"https:\/\/www.lifee.ai\/blog\/wp-json\/wp\/v2\/posts\/216\/revisions\/226"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.lifee.ai\/blog\/wp-json\/wp\/v2\/media\/227"}],"wp:attachment":[{"href":"https:\/\/www.lifee.ai\/blog\/wp-json\/wp\/v2\/media?parent=216"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.lifee.ai\/blog\/wp-json\/wp\/v2\/categories?post=216"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.lifee.ai\/blog\/wp-json\/wp\/v2\/tags?post=216"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}