<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[A New Deal for Buildings - Medium]]></title>
        <description><![CDATA[Redefining how we build, manage and maintain facilities in the 21st century - Medium]]></description>
        <link>https://medium.com/new-deal?source=rss----d0a2cb45e1b---4</link>
        <image>
            <url>https://cdn-images-1.medium.com/proxy/1*TGH72Nnw24QL3iV9IOm4VA.png</url>
            <title>A New Deal for Buildings - Medium</title>
            <link>https://medium.com/new-deal?source=rss----d0a2cb45e1b---4</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 01:36:26 GMT</lastBuildDate>
        <atom:link href="https://medium.com/feed/new-deal" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Two Protocols Are Better Than NONE]]></title>
            <link>https://medium.com/new-deal/two-protocols-are-better-than-none-9af0e66357cd?source=rss----d0a2cb45e1b---4</link>
            <guid isPermaLink="false">https://medium.com/p/9af0e66357cd</guid>
            <category><![CDATA[bacnet]]></category>
            <category><![CDATA[metadata]]></category>
            <category><![CDATA[tag]]></category>
            <category><![CDATA[hvac]]></category>
            <dc:creator><![CDATA[Steve Jones]]></dc:creator>
            <pubDate>Mon, 09 Mar 2020 15:01:01 GMT</pubDate>
            <atom:updated>2020-03-09T15:01:01.112Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Ww7qObgJx6m_zOpP34gGrw.png" /></figure><p>This article was originally published in the February 2020 edition of The Gateway. It did exactly what was intended. It raised awareness of the importance of tagging technology and it got people discussing how tagging will be delivered. The feedback was important enough that I thought I should publish a revision of the article sharing what I learned. Thanks to those in the BACnet community and LinkedIn groups who have responded to the original article.</p><p>If you are looking for one communications protocol that does everything, for everyone in the BAS industry, all the time, it does not exist!</p><p>The front runner is certainly BACnet as documented by the number of installed systems. The BACnet market share is over 60% globally, and more than 80% North American market share and continues to grow rapidly. BACnet is free to use. The success of BACnet is fueled by the fact that it is an open protocol managed by ASHRAE SSPC 135 (BACnet Committee) and supported by an army of volunteers, BAS companies, and academia. The BACnet committee continues to evolve the standard to meet the ever-changing needs of the industry. The SSPC 135 committee meets quarterly to revise and expand the protocol. BACnet is an ISO standard and is independently testable and certifiable.</p><p>BACnet International is an industry association that promotes its use, provides education, testing, and certification services. BACnet International oversees the operation of the BACnet Testing Laboratories (BTL) and maintains a global listing of tested products.</p><p>Consistent meta-data for sites, devices, and points that convey the function of the objects simply did not exist in the BACnet world. Almost everything in this area was left up to the developer or installer.</p><p>Project Haystack evolved as analytics, energy management, and other value-added applications gained momentum in the marketplace. Haystack tagging provides a way of uniquely and consistently identifying objects in a building automation system at all levels of the architecture. The Haystack RESTful protocol was added as a way of extracting tagged data from an automation system for analysis by value-added applications.</p><p>With Smart Building, Smart City, and digitalization initiatives gaining momentum it is hard for the BAS industry to keep up. Cybersecurity is front and center as the most important topic. BACnet SC will address these needs.</p><p>Multiple networking transport standards are available to carry the BACnet payload. The BACnet payload is a series of objects, properties, and services that implement the mission of BACnet. The standard does not tell manufacturers how to implement their algorithms or sequences of operation behind the BACnet objects and services. So, it leaves plenty of room for innovation and competition. The BACnet services and transports can evolve independently of each other. So, as stovepiped applications in buildings converge to Smart Buildings and Smart Cities, new objects and services will be added to BACnet.</p><p>Similarly, the Haystack community has been very active. The tagging syntax, dictionary, and supporting relationship definitions have evolved as the needs of the value-added applications community have evolved and become more sophisticated. Haystack 4 represents a significant step forward in tagging technology. The most critical open issue in this community is that many value-added applications require a labor-intensive and error-prone process of manually applying Haystack tags to data before it can be processed.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*_4L_R0kx2enWyepUVqYmXA.png" /></figure><p>The latest BACnet standard ANSI/ASHRAE Standard 135–2016 introduced a new optional property to each BACnet object. The TAGS property is an array of tag names and values that describe the characteristics, restrictions, relationships, and semantics of the containing object. BACnet Standard 135–2016 also introduced Annex Y — Abstract Data Model. This Annex defines the methodology for constructing and naming TAGS within BACnet but does not include a tags dictionary. It also provides guidance on how to identify TAGS defined by organizations outside of ASHRAE.</p><p>Since the standard stopped short of providing a tagging dictionary, the adoption level appears to be quite low. However, the functionality is there and should be utilized. In an ideal world, there would be one BAS protocol and one tagging dictionary. The BACnet, Haystack, and Brick Schema communities are working together under the auspices of ASHRAE Standard 223P to define a protocol-independent TAGGING dictionary. This effort should accelerate the adoption of tagging capabilities into BACnet protocol stacks and client implementations. But this will take time. With most organizations having limited resources, it will probably take longer than anyone would like. However, it is obvious that the commitment to make this happen is there.</p><p>Recently, here at S4, we have started looking at BACnet a bit differently than we have in the past. We have been doing it a disservice by treating it only as a communications protocol. It is much more than that. It is an “environment” that enables the implementation of ASHRAE building standards in a way that is Open and Interoperable. BACnet objects and services facilitate local control of building infrastructure for real-time control operations. BACnet transport options provide multiple ways to move the BACnet objects between systems.</p><p>We believe that the community does not have to wait for this ultimate solution to evolve. With our release 2.0, we are introducing support for Haystack Tagging and the Haystack RESTful protocol, in addition, to support for BACnet. Any integration provided by S4 will automatically include Haystack tagged data. BACnet is available for local control, edge computing, and near real-time algorithms. A periodic maintenance update to our 2.0 product will support the BACnet TAGS property. We realize that only static tags can be assigned by product manufacturers. Additional tags could be assigned because of their relative positions in the networking infrastructure. Still, other tags can only be assigned by the installation engineer who defines the functionality of the device in the enterprise. Our 2.0 release supports all of these activities.</p><p>Two Protocols are better than NONE!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=9af0e66357cd" width="1" height="1" alt=""><hr><p><a href="https://medium.com/new-deal/two-protocols-are-better-than-none-9af0e66357cd">Two Protocols Are Better Than NONE</a> was originally published in <a href="https://medium.com/new-deal">A New Deal for Buildings</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[NIST Cybersecurity
Framework and BAS (White Paper)]]></title>
            <link>https://medium.com/new-deal/nist-cybersecurity-framework-and-bas-white-paper-fc5ff3b83542?source=rss----d0a2cb45e1b---4</link>
            <guid isPermaLink="false">https://medium.com/p/fc5ff3b83542</guid>
            <category><![CDATA[facility-it]]></category>
            <category><![CDATA[nist-framework]]></category>
            <category><![CDATA[smart-buildings]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[white-papers]]></category>
            <dc:creator><![CDATA[Anto Budiardjo]]></dc:creator>
            <pubDate>Mon, 24 Feb 2020 14:02:08 GMT</pubDate>
            <atom:updated>2020-02-27T16:54:40.912Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/547/1*sJ9ukiOOZ0qGmXJmwdGcvQ.png" /></figure><p>The second annual New Deal for Buildings Cybersecurity Summit at AHR Expo happened on Tuesday, February 4, 2020, in Orlando, Florida,<br>BAS leaders and facility practitioners gathered there around the topic of cybersecurity policies, practices, and technologies.</p><p>Panelists included spokespeople for leading companies and organizations advocating for better cybersecurity in building automation systems.</p><p>The conversation was organized around the NIST Cybersecurity Framework, with each speaker delving into the important aspects of each step. For this whitepaper, Anto Budiardjo and the panelists merge their voices to tell the story of how cybersecurity touches buildings, from identifying components, all the way to responding and recovering following an attack.</p><figure><a href="https://cdn.shopify.com/s/files/1/1193/5206/files/NewDeal_CyberSummitCollection_22320.pdf?623"><img alt="Download White Paper here" src="https://cdn-images-1.medium.com/max/400/1*oJ9zNH6ZfxEZWdobY5VLVg.png" /></a><figcaption>Download the White Paper here.</figcaption></figure><h3>Summit Speakers and White Paper Contributors</h3><p><strong>Dave Bohlmann, </strong>VP of Technology at KMC Controls, currently working on IoT and Cybersecurity.<br><strong>Jim Butler</strong>, CTO of Cimetrics, and Convener at BACnet IT WG.<br><strong>Steve Fey</strong>, CEO of Totem Building Cybersecurity. <br><strong>Chris Kwong</strong>, Chief Technology Officer at Delta Controls<br><strong>James Lee</strong>, CEO at Cimetrics, Inc.<br><strong>Carol Lomonaco</strong>, Senior Product Manager for Johnson Controls Metasys BAS mission-critical products.<br><strong>Andy McMillan</strong>, President &amp; Managing Director at BACnet International<br><strong>Jerry Reeves</strong>, VP of Technology at Tosibox, Inc.<br><strong>Hans-Joerg Schweinzer</strong>, Managing Director at LOYTEC electronics GmbH<br><strong>Kevin Smith</strong>, CTO of Tridium. Inc. Author of seven books focused on Cybersecurity, the IoT, and Building Automation.</p><p><strong>Anto Budiardjo</strong>, (Summit Moderator) Editor at New Deal for Buildings.<br><strong>Therese Sullivan</strong>, (White Paper Curator) Customer Marketing Leader, Tridium, Inc.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=fc5ff3b83542" width="1" height="1" alt=""><hr><p><a href="https://medium.com/new-deal/nist-cybersecurity-framework-and-bas-white-paper-fc5ff3b83542">NIST Cybersecurity
Framework and BAS (White Paper)</a> was originally published in <a href="https://medium.com/new-deal">A New Deal for Buildings</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[After The Breach — How Can My Building Recover from a Cyberattack?]]></title>
            <link>https://medium.com/new-deal/after-the-breach-how-can-my-building-recover-from-a-cyberattack-7280dc1de1a6?source=rss----d0a2cb45e1b---4</link>
            <guid isPermaLink="false">https://medium.com/p/7280dc1de1a6</guid>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[smart-buildings]]></category>
            <category><![CDATA[ndsummit]]></category>
            <category><![CDATA[facility-it]]></category>
            <category><![CDATA[building-automation]]></category>
            <dc:creator><![CDATA[Kevin Smith]]></dc:creator>
            <pubDate>Thu, 23 Jan 2020 22:39:05 GMT</pubDate>
            <atom:updated>2020-01-23T22:39:04.945Z</atom:updated>
            <content:encoded><![CDATA[<h3>After The Breach — How Can My Building Recover from a Cyberattack?</h3><p><em>This article is one of a series of articles published to coincide with the </em><a href="https://newdeal.blog/cybersecurity-summit-2020-2500e4a28024"><em>New Deal Cybersecurity Summit at AHR Expo 2020 in Orlando</em></a><em>.</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*airbC6-wvW9bE3qlc1Sd5w.png" /></figure><p><strong><em>And one day it happens to you — the cyberattack you were warned about. You’ve attended trade shows where they talked about this. You’ve read articles about how to prevent attacks. You’ve put safeguards in place. But inevitably, one day you wake up to discover that your organization has been hacked and your Building Automation System (BAS) has been affected. Regardless of where it came from and how the attack happened, it’s time to recover from that attack. What do you do now?</em></strong></p><p>Hopefully, none of you are in that situation as you are reading this. At Tridium, we’ve written <a href="https://www.tridium.com/~/media/tridium/library/documents/collateral/white%20papers/white%20paper%20%20cybersecurity%20and%20the%20iot%20%20threats%20best%20practices%20and%20lessons%20learnedjan%202019-1.ashx?la=en">white papers</a> and <a href="https://www.tridium.com/~/media/tridium/library/documents/niagara%204%20hardening%20guide_2019.ashx?la=en">product hardening guides</a> that provide guidance on cybersecurity best practices and cybersecurity strategies that you can use to help <em>prevent and thwart</em> cyberattacks — but what should you do if it ever happens?</p><p>Luckily, the National Institute of Standards and Technology (NIST) Cybersecurity Framework has you covered. For those not familiar with this, it is a standard that offers a flexible and customizable security approach for any organization, and it lends itself well to the BAS business area. Focused on five key functions (Identify, Protect, Detect, Respond, and Recover), it provides guidance for maintaining security and managing security risk for critical infrastructure.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/624/1*ewPIA2dLHh9kOzDBdMPkLA.png" /><figcaption>Figure 1: The National Institute of Standard and Technology (NIST) Cybersecurity Framework</figcaption></figure><p>In a few weeks, I’ll be speaking at the <a href="https://newdeal.blog/cybersecurity-summit-2020-2500e4a28024">New Deal Cybersecurity Summit at AHR Expo 2020 in Orlando</a>, where the other speakers and I will focus specifically on applying the NIST Cybersecurity Framework to the BAS domain. It may seem difficult to discuss the “Recover” function of the NIST Cybersecurity Framework without explaining those other four functions, so I will refer to <a href="https://newdeal.blog/nist-cybersecurity-framework-and-bas-832ddda58ad">this recent article</a> that provides a good overview, and I will let you reference the graphic in Figure 1 to give a sense of the first four areas.</p><p>The Recover function is a key element of the NIST Cybersecurity Framework that should help building owners understand the necessity of applying the other four functions. To put this into perspective, let me give you a scenario that building owners and facility managers can appreciate.</p><p>In the middle of a hot summer day, you are notified that your building has gone “haywire” — all the rooms in your building are unbearably hot and the tenants are complaining. Adding to that, the building security system is no longer working, and tenant badges are not working with the badge readers, leaving them locked out of key areas of the building. Finally, specialized cooling for a data center in your building has been turned off, shutting down critical cloud services hosted by one of your business tenants. After a quick investigation, you discover that your network and your BAS has been infected with ransomware, and you realize that you need to quickly recover the normal operations of your building. Your phone is ringing off the hook, your tenants are outraged, and a local news reporter wants answers. How do you respond?</p><p>Some of the questions that might go through your mind are the following.</p><p>- <strong>Now that we know that the integrity of our building system has been compromised, what do we do first? </strong>Does your organization have a plan that addresses this type of scenario?</p><p>- <strong>Of all the systems that are affected by this cyberattack, what systems should we recover first?</strong> Has your organization done an analysis of all your systems, their inter-dependencies, and the Service Level Agreements(SLAs) you have with your customers so that you know what systems take priority and what systems you will need to restore first?</p><p>- <strong>How, specifically, will we recover all systems to normal operations?</strong> Are there temporary workarounds that will get systems working quickly? Did your organization routinely back up the logic of your BAS systems (e.g., controllers and supervisors)? Did your organization routinely back up all other relevant systems on your network that will need to be restored? Has your organization developed a disaster recovery plan that provides step-by-step instructions for restoring these systems? Who, specifically, will need to be involved?</p><p>- <strong>How do we respond to our tenants, customers, and the media?</strong> Does your organization have a communication and crisis response plan? How and when should your organization communicate with your tenants, customers and key stakeholders related to the outage and when things will be restored? Are communication systems also compromised, and if so, do you have an alternate mechanism for communicating? How do you respond to media queries? How will you communicate with your tenants and customers after the fact? What are the legal and regulatory implications of how you communicate? Who needs to be involved in your communications?</p><p>This scenario conveys the reality of today’s cybersecurity threat landscape, and it demonstrates the necessity of the Recover function of the NIST Cybersecurity Framework. Answers to these questions can be complex, many team members and stakeholders will need to be involved in decision making, and you will be expected to respond quickly. Making <em>any</em> of those decisions without a plan is a recipe for disaster and can lead to a host of horrible technical, legal and public relations issues.</p><p>The Recover function provides a helpful guide for recovery planning and allows your organization to proactively develop a playbook for recovering from cybersecurity incidents by helping you answer those questions above and more. The NIST Cybersecurity Framework provides a well-defined playbook in place for you to execute, allowing your organization to address items such as recovery prioritization, communication plans, and the tactical steps necessary to recover functions to normal operations. By doing this planning in advance, you will have a plan that can be followed during a stressful but critical time.</p><p>The most well-prepared organizations go through this recovery planning process and “tabletop exercises” where participants in your recovery process walk through the plan in various scenarios and talk through each process to identify gaps in planning details. These exercises can be a helpful, cost-effective means of testing your preparedness ahead of time.</p><p>When a cybersecurity incident does happen, it’s important to know that even well-prepared organizations can make mistakes during their recovery process. Because of this reality, the Recover function of the NIST Cybersecurity Framework also includes an improvement phase, where you are advised to take lessons learned and incorporate them into improving your recovery process and plans, and when you can send improvement feedback into the other four functions of the framework. For example, we’ve seen many situations where organizations have recovered from an attack without addressing the root cause of the problem, only to have it happen again! Many times, incidents will identify weaknesses in your current processes. After each incident, your organization should always look at your entire process (identify, protect, detect, respond, and recover) to identify what went right, what went wrong, and ways to improve your cybersecurity process.</p><p>I look forward to the discussion that we’ll be having on this topic at <a href="https://newdeal.blog/cybersecurity-summit-2020-2500e4a28024">New Deal Cybersecurity Summit at AHR Expo 2020 in Orlando</a>, and we hope to see you there!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7280dc1de1a6" width="1" height="1" alt=""><hr><p><a href="https://medium.com/new-deal/after-the-breach-how-can-my-building-recover-from-a-cyberattack-7280dc1de1a6">After The Breach — How Can My Building Recover from a Cyberattack?</a> was originally published in <a href="https://medium.com/new-deal">A New Deal for Buildings</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Response]]></title>
            <link>https://medium.com/new-deal/response-87b8e105ad58?source=rss----d0a2cb45e1b---4</link>
            <guid isPermaLink="false">https://medium.com/p/87b8e105ad58</guid>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[ndsummit]]></category>
            <category><![CDATA[facility-it]]></category>
            <category><![CDATA[smart-buildings]]></category>
            <dc:creator><![CDATA[Carol Lomonaco]]></dc:creator>
            <pubDate>Thu, 23 Jan 2020 22:38:56 GMT</pubDate>
            <atom:updated>2020-01-23T22:38:56.674Z</atom:updated>
            <content:encoded><![CDATA[<h3>Respond</h3><p><em>This article is one of a series of articles published to coincide with the </em><a href="https://newdeal.blog/cybersecurity-summit-2020-2500e4a28024"><em>New Deal Cybersecurity Summit at AHR Expo 2020 in Orlando</em></a><em>.</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*sR9238e9fXkCn-Som2JOcw.png" /></figure><p>One of the best ways to help prevent a cybersecurity incident is to follow IT/OT best practices and prevent it from happening in the first place. However, we all know that we cannot possibly prevent all cyber incidents so we must have a plan in order to be able to respond reasonably and in a timely fashion.</p><p>A better approach is to have a “Response Plan” in place, per the National Institute of Standards and Technology (NIST) Cybersecurity Framework v1.1. The Framework describes how cybersecurity risk is managed by an organization and how to enable communication of cyber risk across an organization. Five Functions are identified as part of the Framework:</p><p>1. Identify</p><p>2. Protect</p><p>3. Detect</p><p>4. Respond</p><p>5. Recover</p><p>The NIST Cybersecurity Framework v1.1 defines “Respond” as “Develop and implement appropriate activities to take action regarding a detected cybersecurity incident”.</p><p>The NIST framework encourages one to focus on what techniques can contain or possibly lessen the impacts of incidents. The recommendation is that a customer, and even BAS vendors, will have a formal Response Plan in place.</p><p>In addition, the NIST Framework recommends that one focuses on response planning by reviewing and including the following outcome Categories as an element in one’s response plan:</p><p>-Response Planning</p><p>-Communications</p><p>-Analysis</p><p>-Mitigation</p><p>-Improvements</p><h3>Response Planning:</h3><p>For effective Response Planning, response processes and procedures are executed and maintained, to ensure timely response to detected cybersecurity events. This may even entail having a playbook of scenarios and exercising the Response Plan by completing tabletop exercises from the playbook once or twice every year. Having a playbook in place allows one to track and measure metrics based on actual incidents. This, in turn, helps to drive down the total response times, because you have assembled the proper incident response team, with cross-functional representatives from all the vested parties.</p><h3>Communications:</h3><p>Response activities are coordinated with internal and external stakeholders, as appropriate, to include external support from law enforcement agencies.</p><p>Example letters that follow the playbook of cybersecurity scenarios will be drafted to have an initial set of draft letters. The list of roles in the company or organization that need to review and sign off on those letters is also identified. Note: pre-prepared social media responses could also be included, for posting to the company’s Twitter handle and other social media channels. Publishing appropriate information to the company’s website could also be considered (and reviewed and approved).</p><h3>Analysis:</h3><p>Analysis is conducted to ensure adequate response and support recovery activities. Specific team members need to be available to do the analysis. Also, internal stakeholders may need to be contacted to free up resources to get local subject matter experts (SMEs) involved to complete or to support recovery activities.</p><h3>Mitigation:</h3><p>Activities are performed to prevent the expansion of an event, mitigate its effects, and eradicate the incident. Having the right SMEs available 24/7/365 will greatly help with the mitigation activities, along with the exercising the playbook of possible cyber incidents.</p><h3>Improvements:</h3><p>Organizational response activities are improved by incorporating lessons learned from current and previous detection/response activities. Results from Table Top exercises will greatly help, as well as any other lesson learned items captured from past experiences.</p><p>Having a formal cybersecurity incident response plan in place is critical to be able to respond reasonably and in a timely fashion! There are consultants available to help you write an initial response plan. Then it is highly recommended that one apply continuous improvement methods to keep the response plan up to date annually.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=87b8e105ad58" width="1" height="1" alt=""><hr><p><a href="https://medium.com/new-deal/response-87b8e105ad58">Response</a> was originally published in <a href="https://medium.com/new-deal">A New Deal for Buildings</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Detection: Yes, Trees and Groundhogs Do Make Sounds]]></title>
            <link>https://medium.com/new-deal/detection-yes-trees-and-groundhogs-do-make-sounds-fc730b703ad2?source=rss----d0a2cb45e1b---4</link>
            <guid isPermaLink="false">https://medium.com/p/fc730b703ad2</guid>
            <category><![CDATA[smart-buildings]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[detection]]></category>
            <category><![CDATA[ndsummit]]></category>
            <category><![CDATA[facility-it]]></category>
            <dc:creator><![CDATA[dbohlmann]]></dc:creator>
            <pubDate>Thu, 23 Jan 2020 22:38:53 GMT</pubDate>
            <atom:updated>2020-01-23T22:38:53.323Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*KMR8gIjHg0v70mUjG83Izg.png" /></figure><p>And so do cyber hackers running around in our systems.</p><p><em>This article is one of a series of articles published to coincide with the </em><a href="https://newdeal.blog/cybersecurity-summit-2020-2500e4a28024"><em>New Deal Cybersecurity Summit at AHR Expo 2020 in Orlando</em></a><em>.</em></p><p>The age-old question: If a tree falls in the forest and no one is around to hear it, does it make a sound? As an engineer, I’ve never understood why this was even debatable — the laws of classical physics scream, with audio decibels: “Yes!”. Various philosophers and quantum physicists would say “maybe, maybe not”. But none of the trees in my yard, as far as I’ve measured, have a dimensional scale on the order of a quantum particle/wave. And the tree-climbing groundhogs eating my mulberries consistently verify that.</p><p>We do not have the luxury of debate when it comes to our information or controls systems; bad actors actively work hard to <em>not </em>make a sound, to not be <em>detected. </em>And we all are definitely under attack<em>. </em>Kaspersky <a href="https://securelist.com/threat-landscape-for-industrial-automation-systems-in-h2-2018/90041/">reported that in H2 2018</a>, their tools stopped malicious activity on more than 40% of industrial control systems.<em> 40%</em>. And that’s just what they managed to stop, just on systems properly using their tools.</p><p>When the attackers do get in, it takes on average <a href="https://www.itgovernanceusa.com/blog/how-long-does-it-take-to-detect-a-cyber-attack">200 days</a> for US companies to notice, a statistic that is not improving. That is more than <em>six months</em> for bad actors to be rummaging through our information/controls systems, gathering whatever they want, before we even know it. We might think we could detect an attack in a controls system faster than a data system (would it not be obvious that equipment is failing?) but it took <a href="https://www.wired.com/2014/11/countdown-to-zero-day-stuxnet/">two years for Stuxnet to be discovered</a> after it was planted in Iran’s Natanz nuclear facility.</p><h3>Detection: When the Fun Begins</h3><p>Cyber-security is not a one-shot “fire and forget” kind of game, where we simply <em>identify </em>what we want to safe-guard, then purchase the automated tools or predefined procedures to <em>protect </em>our systems, and then “turn on the switch” and think we’re safe. That’s just when the fun begins. We must continually work to <em>detect </em>attacks, to get a sense (think <em>sensor</em>) of what we and our systems are up against, the type and scale of their attacks. Without sensors, how do we know what is going on? In order to protect, we must detect. And in our world, what we don’t know may already be hurting us.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/472/1*7HJe93W5_1GTZp48e0osQg.jpeg" /><figcaption><a href="https://syslog.com/~jwilson/pics-i-like/kurios119.jpg">https://syslog.com/~jwilson/pics-i-like/kurios119.jpg</a></figcaption></figure><p>As with everything else in cyber security, we must defend in depth. I suppose a gate across a road can be the first level of defense (and snow on the ground the detector for a gate breach), but let’s do better.</p><p>Common software-based detectors are anti-virus, anti-spyware, or in general, anti-malware tools. These are typically installed on PCs and servers, and detect if malware is installed or executing on the host machine. Similar types of software are installed on email servers, to detect if an attachment is suspicious-looking, or the source of the email has a history of being suspicious, before it gets into users’ inboxes.</p><p>The biggest problem here is when we don’t configure or use the tools properly, or keep them up to date. This appears to have been the case with the infamous <a href="https://krebsonsecurity.com/2014/02/email-attack-on-vendor-set-up-breach-at-target/comment-page-2/">Target breach</a> in 2014. The attackers used a phishing campaign to send emails to Target vendors. Someone at one of the vendors, a small HVAC business, opened the attachment or link with the malware. They were apparently using a free version of <em>Malwarebytes</em>, which needed to manually be updated and executed, and so it did not detect the malware until it was too late. The attackers got that vendor’s credentials, and using Target’s vendor portal tool <em>Ariba</em>, got onto Target’s point-of-sales network. There is no evidence that they ever touched any HVAC system; no need to.</p><p>Our lesson from the Target breach, as HVAC people, is our attack detection tools and methods should not only be in the systems we install and maintain, but also within our own organizations. And that’s just for starters.</p><h3>Detection Methods</h3><p>IT-minded people have been building detection tools for data systems for a long time (almost as long as hackers have been around).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/564/1*ZTp_I-T0rLRXAIX4FVYCcg.png" /><figcaption>NIST Cyber Security Framework</figcaption></figure><p>Such software tools are designed specific to the type of data a computer is being used to access, or how it is accessed. Some tools are installed on the computers themselves, while others live within specialized networking devices so they can detect attacks running through the network.</p><p>How do the tools detect; what do they look for? Basically, anything out of the ordinary, or anything (or anyone) that “shouldn’t be there”.</p><p>Perhaps the “simplest” method is to use <em>signatures </em>— a sequence of bits and bytes that are known to be the code for a particular piece of malware. The tool scans memory to see if something matches any of these signatures… millions and millions of known signatures. The problem, though, is signatures must be known ahead of time to be used by the tools, and the bad actors are changing, hiding or creating variants of signatures and malware faster than we can keep up — some estimate close to a million variants <em>a day</em>.</p><p><a href="https://www.cynet.com/blog/a-guide-to-malware-detection-techniques-av-ngav-and-beyond/">Next method</a>: look for patterns of behavior of a program, seeing if it is doing things it should not. “Misbehaving” include trying to use memory or resources that is not allowed, trying to change operating system parameters, and trying to register for auto-start. Detection tools must dynamically and continuously look for these (and thousands of other) patterns, rather than simply check for static signatures. Operating systems that <em>sandbox </em>programs to execute within certain parameters of the system try to detect malware by watching behavior. But yet again, attackers have made sophisticated malware that can detect the detector — detect that they are in a sandbox — and behave “nicely” until it can exploit blind spots and work its way out of the box.</p><p>On the network side, <em>firewalls </em>attempt to protect networks by detecting traffic coming from known malicious web sites, or incoming messages destined for service ports that should not be in use by that outside server. Ports can be dynamically opened by the firewall if it performs <a href="https://www.sciencedirect.com/topics/computer-science/stateful-inspection"><em>stateful-inspection</em></a> of legitimate messages between an internal user and and external server, basically reading the messages, understanding the handshaking between server and client, and temporarily open ports to support the traffic.</p><p>Well and good… sort of. Bad actors use <a href="https://www.securityweek.com/targets-data-breach-commercialization-apt"><em>advanced-persistent threat</em></a> methods to “stay quiet”, avoiding detection. One technique: trickle out the collected stolen data so that detectors looking for high outbound traffic rates don’t notice. One of the pieces of malware used in Target’s case slowly exfiltrated some 100 million records over the course of a month or so.</p><h3>Know Your System</h3><p>This gets to one of the major differences between data systems and control systems: attack purpose and how to achieve it. Attacks on data systems are generally to retrieve data that can be sold, or held for ransom by encrypting it so we cannot read it. For controls and infrastructure systems, the attackers want to interrupt or even damage physical services or equipment. And they can accomplish this by infiltrating key devices with just a few malicious commands, rather than exfiltrating millions of records.</p><p>That’s how Stuxnet works — methodically and slowly issuing bogus commands to devices to ultimately damage the equipment they control. Even in the cyberwar Russia has brought against Ukraine’s national grid since 2015, the attackers utilize a <a href="https://www.wired.com/story/russian-hackers-attack-ukraine/">small fraction of attacks</a> against targeted devices, compared to what we see with data or denial-of-service attacks, in order to bring down the grid for a city. For controls, “just a few bytes” of control data can wreak much havoc.</p><p>In these types of attacks, besides the other protection and detection methods normally used (remember: defense in depth!), knowledge of our control system and its components are specified and required to operate can be used to create focused detection rules… if we had software tools and devices that could utilize such rules. Until then, examination of activity logs and implementing schemes to continually verify proper operation or setpoint limits can be done to sense malicious behavior.</p><h3>Conclusion</h3><p>Cyber threats and attacks continue to increase in quantity and sophistication, and our ability to counter them must keep up. The work to bring to bear more and better tools to detect attacks, to listen as bad actors try to go after their targets, is critical in safe-guarding the systems we build and need.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=fc730b703ad2" width="1" height="1" alt=""><hr><p><a href="https://medium.com/new-deal/detection-yes-trees-and-groundhogs-do-make-sounds-fc730b703ad2">Detection: Yes, Trees and Groundhogs Do Make Sounds</a> was originally published in <a href="https://medium.com/new-deal">A New Deal for Buildings</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Protecting BAS from Cybersecurity Threats]]></title>
            <link>https://medium.com/new-deal/protecting-bas-from-cybersecurity-threats-3c5ab0f6d822?source=rss----d0a2cb45e1b---4</link>
            <guid isPermaLink="false">https://medium.com/p/3c5ab0f6d822</guid>
            <category><![CDATA[nist-framework]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[ndsummit]]></category>
            <category><![CDATA[facility-it]]></category>
            <category><![CDATA[building-automation]]></category>
            <dc:creator><![CDATA[Jim Butler]]></dc:creator>
            <pubDate>Thu, 23 Jan 2020 22:38:50 GMT</pubDate>
            <atom:updated>2020-01-23T22:38:50.178Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*FXTdG_aCbZ_L2bm76CfcTA.png" /></figure><p>This article is one of a series of articles that have been published to coincide with the <a href="https://newdeal.blog/cybersecurity-summit-2020-2500e4a28024">New Deal Cybersecurity Summit at AHR Expo 2020 in Orlando</a>.</p><p>For an overview of the relevance of the NIST Cybersecurity Framework to BAS, and links to other articles, read this story: “<a href="https://newdeal.blog/nist-cybersecurity-framework-and-bas-832ddda58ad">NIST Cybersecurity Framework and BAS</a>”.</p><h3>Why do we need to protect building automation systems?</h3><p>Buildings are critical infrastructure, and building automation systems (BAS) have a key role in ensuring that commercial and industrial buildings can be used for their intended purposes. BAS systems are evolving; for example, TCP/IP and Ethernet communication are increasingly being used within BAS systems, and BAS systems increasingly share IT-managed network infrastructure with other systems. A consequence of this evolution is that BAS systems are facing new and increasing cybersecurity threats.</p><p>Here are some of the types of attacks that BAS systems could face today:</p><ol><li>Ransomware. This is a popular way for cybercriminals to profit from their hacking, and BAS systems might be seen as vulnerable.</li><li>Lateral attacks. Poorly protected BAS systems can be a stepping stone to facilitate attacks against other systems to which they are connected. One example of a lateral attack is described in <a href="https://www.casino.org/news/hackers-stole-las-vegas-casino-high-roller-database-via-its-fish-tank/">this news article</a> about how hackers apparently stole valuable data from a casino by first attacking a network-connected device in a fish tank.</li><li>Denial of service. BAS devices are potentially vulnerable to such attacks and compromised BAS devices could be used in botnets to carry out such attacks.</li></ol><p>Protecting BAS systems from cyberattacks is the joint responsibility of building owners, building managers, IT networking and cybersecurity personnel, BAS integrators, and BAS manufacturers. In order to work together effectively, we should use a common playbook. One such playbook that is in widespread use in IT is the NIST Cybersecurity Framework.</p><h3>Leveraging the NIST Cybersecurity Framework</h3><p>The <a href="https://www.nist.gov/cyberframework">NIST Cybersecurity Framework version 1.1</a> defines a structured approach for managing and reducing cybersecurity risk in critical infrastructure, and <a href="https://newdeal.blog/nist-cybersecurity-framework-and-bas-832ddda58ad">we can apply the Framework to BAS systems</a>.</p><p>The following table shows the five functions of the Framework (Identify, Protect, Detect, Respond and Recover). Each function has a corresponding set of outcomes/actions, which are referred to as categories; for example, Asset Management is a category within the Identify function.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*BjmxtoUxQsZYjcOS7DE0ww.png" /></figure><p>The Protect function of the Framework is where we can look for guidance about protecting BAS systems. But before we go about developing a strategy for protecting assets in a particular system, we need to identify the BAS assets and determine the most critical risks to those assets. These activities fall into the Identify function of the NIST framework, which is discussed in the article “<a href="https://newdeal.blog/b774e3911aa6">Understanding NIST’s Identify Function</a>”.</p><p>In the table shown above, the Protect column lists several categories of desirable outcomes and activities that go into protecting a system.</p><p><strong>Identity Management and Access Control:</strong> Access to BAS assets should be limited to authorized users, processes, and devices. This includes all manner of access, including physical access and remote access. Managing credentials used for authentication (e.g. usernames and their corresponding passwords) is an integral part of this activity.</p><p><strong>Awareness and Training:</strong> All BAS users and other stakeholders should receive cybersecurity awareness education and role-appropriate training about their cybersecurity responsibilities.</p><p><strong>Data Security:</strong> The three primary goals are maintaining the confidentiality of sensitive data, the integrity of data, and the availability of data necessary for building operation. Data stored within BAS devices should be protected, as well as data transmitted on a communication channel (e.g. a network).</p><p><strong>Information Protection Processes and Procedures: </strong>This includes baseline BAS system and device configurations that reflect good cybersecurity practices, procedures for conducting backups of important data, and incident response and recovery plans.</p><p><strong>Maintenance: </strong>When maintenance of BAS assets is required, it should be done using approved tools. All BAS maintenance should be logged. Remote maintenance requires prior approval and must be done in a way that prevents unauthorized access.</p><p><strong>Protective Technology:</strong> Technical security solutions should be managed in such a way as to ensure that BAS systems are secure and resilient. Such solutions include audit logging and network security controls.</p><p>The degree to which an organization implements the Protection recommendations in the Framework should be determined by the organization based on its assessment of the expected costs and potential benefits of implementation.</p><h3>How does BACnet/SC protect BAS systems?</h3><p>BACnet/SC, which was officially added to the BACnet standard (ANSI/ASHRAE Standard 135) in November 2019, is a new communication technology for use on TCP/IP networks that are built upon widely used network protocols (TCP, TLS, and WebSocket). BACnet/SC requires peer authentication of devices and encryption of all network traffic.</p><p>In terms of the NIST Cybersecurity Framework, BACnet/SC contributes to Identity Management and Access Control by requiring devices to be authenticated and by limiting BACnet/SC network access to authorized devices. As well, BACnet/SC contributes to Data Security by using a reliable transport protocol and encryption.</p><p><a href="https://newdeal.blog/cybersecurity-summit-2020-2500e4a28024"><strong>Learn more about BAS cybersecurity from the panel of experts at the New Deal Cybersecurity Summit on February 4, 2020.</strong></a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3c5ab0f6d822" width="1" height="1" alt=""><hr><p><a href="https://medium.com/new-deal/protecting-bas-from-cybersecurity-threats-3c5ab0f6d822">Protecting BAS from Cybersecurity Threats</a> was originally published in <a href="https://medium.com/new-deal">A New Deal for Buildings</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Understanding NIST’s Identify function]]></title>
            <link>https://medium.com/new-deal/understanding-nists-identify-function-b774e3911aa6?source=rss----d0a2cb45e1b---4</link>
            <guid isPermaLink="false">https://medium.com/p/b774e3911aa6</guid>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[facility-it]]></category>
            <category><![CDATA[smart-buildings]]></category>
            <category><![CDATA[ndsummit]]></category>
            <dc:creator><![CDATA[Steve Fey]]></dc:creator>
            <pubDate>Thu, 23 Jan 2020 22:38:31 GMT</pubDate>
            <atom:updated>2020-01-23T22:38:31.169Z</atom:updated>
            <content:encoded><![CDATA[<h3>Understanding NIST’s Identify Function</h3><p><em>This article is one of a series of articles published to coincide with the </em><a href="https://newdeal.blog/cybersecurity-summit-2020-2500e4a28024"><em>New Deal Cybersecurity Summit at AHR Expo 2020 in Orlando</em></a><em>.</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*omb9El23_V2o8ysglmk8Xg.png" /></figure><p>The first of the NIST functions is Identify. NIST describes Identify as the need to “develop an organizational understanding to manage cybersecurity risk to systems, people, assets, data, and capabilities.” In the world of building control systems, it means <em>you must know what you have before you can decide how best to protect it.</em></p><p>As an industry, our number one concern is around the functionality of the mechanical and electrical systems that we use to regulate the environment of our buildings. Building control systems play an enormous role in operating these systems to achieve the comfort, efficiency and safety objectives that we demand. To achieve these requirements, the design of control systems have benefited from the evolution of IT technology both in hardware and software.</p><p>New systems going into buildings today communicate over conventional wired and wireless IP networks, utilize standard operating systems such as Microsoft Windows and Linux and are accessed remotely over the Internet. In other words, these systems are subject to the same cybersecurity threats that every Enterprise IT system must contend with.</p><p>Arguably the adoption of these technologies has been approximately a decade behind the IT industry, but virtually all facilities built since the beginning of this century have systems facing these threats. The fundamental question remains — do we know what is in our buildings?</p><p>Unfortunately in many, many cases, the answer is no. This is why the starting point for following the NIST guidelines starts with Identify. Identify asks us to approach the problem in five ways:</p><p>1. <em>Prepare an accurate inventory of the control systems in your building</em>. This needs to be comprehensive going beyond building automation to include lighting control, elevators, access control, video surveillance, and parking systems and often many more.</p><p>2. <em>Understand the importance of control systems to the success of the organization</em>. For example, hospitals, data centers and manufacturers are highly dependent on the operation of their control systems, where a cybersecurity breach can have serious economic and safety consequences as well as damage the organization’s reputation.</p><p>3. <em>Establish policies and procedures for the organization to follow in managing cybersecurity risk</em>. It’s easy to get caught up in managing cybersecurity through an emphasis on technology. Industry studies, on the other hand, point out that 80% of cybersecurity breaches result from a lack of basic processes, policies, and procedures as well as employee and vendor mistakes.</p><p>4. <em>Assess each system to identify the risk areas and the potential business impact.</em> Protecting against cybersecurity threats begins with conducting an assessment of the vulnerabilities in each control system. Most systems today are connected to the Internet which presents obvious risks from both trusted and untrusted users.</p><p>5. <em>Move from assessment to risk management</em>. The nature of cybersecurity threats is one that requires constant diligence, adherence to the organization’s policies and procedures and will also require continuous improvement to keep pace with the ever-evolving threat landscape (i.e. the bad guys are always finding new ways to exploit systems).</p><p>6. <em>Vendor Risk Management is the single biggest priority for this industry.</em> Unlike Enterprise IT, managing facilities requires substantial engagement of contractors, systems integrators, property management firms, and consultants in the delivery and ongoing support of control systems. By its nature, it introduces many non-employee users that need access and often on a 24 / 7 basis. Managing this supply chain from a cybersecurity perspective is uniquely demanding for our industry and requires substantial attention in the area of policies and procedures.</p><p>In summary, the Identify function instructs us to know what systems we have, uncover the risks, understand their impact to the organization, and manage these risks over time with a strong emphasis on engaging the many suppliers that we depend upon as active participants in the process.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b774e3911aa6" width="1" height="1" alt=""><hr><p><a href="https://medium.com/new-deal/understanding-nists-identify-function-b774e3911aa6">Understanding NIST’s Identify function</a> was originally published in <a href="https://medium.com/new-deal">A New Deal for Buildings</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[NIST Cybersecurity Framework and BAS]]></title>
            <link>https://medium.com/new-deal/nist-cybersecurity-framework-and-bas-832ddda58ad?source=rss----d0a2cb45e1b---4</link>
            <guid isPermaLink="false">https://medium.com/p/832ddda58ad</guid>
            <category><![CDATA[ndsummit]]></category>
            <category><![CDATA[smart-buildings]]></category>
            <category><![CDATA[hvac]]></category>
            <category><![CDATA[facility-it]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <dc:creator><![CDATA[Anto Budiardjo]]></dc:creator>
            <pubDate>Wed, 01 Jan 2020 17:01:02 GMT</pubDate>
            <atom:updated>2020-01-01T17:01:02.196Z</atom:updated>
            <content:encoded><![CDATA[<p>This article is one of a series of articles published to coincide with the <a href="https://newdeal.blog/cybersecurity-summit-2020-2500e4a28024">New Deal Cybersecurity Summit at AHR Expo 2020 in Orlando</a>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*pwIHtpEUmddH53_Vbk5gzg.png" /></figure><p>The BAS industry is currently in the midst of transforming its posture with respect to cybersecurity. This move comes after years of the reality that BAS systems are secure mostly because they are stand-alone, and thus have little or no impact on digital information systems relied on by building owners.</p><p>With the rapid transformation of BAS systems into an integral part of corporate networks and ultimately falling under the scope of IT and CISO organizations, the BAS industry as a whole has the opportunity to transform its image and make sure it is not regarded as the security hazard on the digital infrastructure.</p><p>Many who understand the workings of the BAS industry will quickly make two points: first, that many vendors are already working on solving this challenge by implementing IT-centric technologies in their products and services. Second, that BAS serves many different roles in buildings; it is not just for automation, but for a range of stakeholders including architects, designers, construction, mechanical equipment, operations, real-estate ownership/leasing, IT, and many others. Many people touch buildings; a significant number of them are typically not very IT/security savvy. In other words, cybersecurity is a massive challenge not just to BAS but to all those involved with buildings and facilities.</p><p>That vendors are implementing IT-centric technologies is welcomed indeed, keep up the great work. As to the breadth of the players involved, that’s unlikely to change due to the nature of buildings. What we can do, however, is understand BAS’s role with respect to cybersecurity in buildings, something that can only be looked at in a holistic manner. To do this, it is critical for BAS professionals to understand how their role impacts not only what they do and deliver, but how it impacts what others have to deal with, often long after they have left the project.</p><p>The tendency of BAS to be product-, contract-, and project-centric makes this hard since our financial incentives are generally tied to delivering a specific product or project to specification, and not on their impact outside of those specs, nor on issues that may surface years hence. This business model has led us to be blind to issues outside of our “responsibilities”, and in cybersecurity, this is not acceptable. This model may have served us well in the past, but will not serve us well in the new future we face.</p><h3>The rationale for the NIST Framework</h3><p>Fortunately for us, when it comes to cybersecurity, we are not alone with this problem. Other industries are made up of a similarly lengthy and diverse supply chain, though not lasting decades as buildings do, making our task that much harder.</p><p>In February 2013, the Obama White House issued an <a href="https://obamawhitehouse.archives.gov/the-press-office/2013/02/12/executive-order-improving-critical-infrastructure-cybersecurity">executive order</a> instructing the National Institute of Standards and Technology (NIST) to develop a framework to reduce cyber risks of critical infrastructures. Specifically to include “standards, methodologies, procedures, and processes that align policy, business, and technological approaches to address cyber risks”. Out of this, the NIST Cybersecurity Framework was created, with version 1.0 released in 2014 and an updated version 1.1 released in 2018.</p><p>The purpose of the NIST Framework fits exactly with the need for different buildings-focused stakeholder groups to be aligned when it comes to creating secure buildings. It thus makes sense for us to use the Framework to map out how the BAS industry should view its role.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*cIue0fbBoG9IP9G0" /></figure><p>The core of the NIST Framework revolves around five functions that trace the activities across the scope of securing digital systems; these perfectly relate to how we should view buildings in a holistic manner. The five functions are Identify, Protect, Detect, Respond, and Recover.</p><p>We’ll dig in a little on these five functions here, and additional authors will provide more on each in subsequent articles. These functions will be at the core of the discussions at the New Deal Cybersecurity Summit in Orlando, February 4, 2020, at the sidelines of the annual, industry-gathering AHR Expo and ASHRAE Winter Meeting.</p><h3>Identify</h3><p>The first function in the NIST Framework is knowing what needs to be secured, specifically to Identify them.</p><p>In the NIST Framework, the Identify function is broken down into asset management (knowing what system components exist, from devices to software versions and more), knowing the business environment (a retail property is different from a school), understanding governance (how the building is managed), risk assessment and management, and finally, understanding the supply chain.</p><p>Without an understanding of these issues, it’s easy to see how securing a BAS could be hard to get right. While many building automation systems manage their direct assets (device management of supervisory systems), we need to broaden this scope to all components that could affect the building’s security, including infrastructure, users, external systems, integrations, and other IoT devices and systems performing supplementary tasks to controls and automation. Understanding the risks associated with each of these components is critical.</p><h3>Protect</h3><p>Once the system components are known and understood, they need to be protected. This is the second function in the NIST Framework. In this context, protecting needs to be viewed in broader terms than just protecting devices and systems with usernames and passwords (which, incidentally BAS generally doesn’t do well).</p><p>NIST breaks this down to protecting through an identity and access management system (of people and devices); the need for awareness and training of users; the need to protect data (both in-situ and in-motion); understanding the processes and procedures of how the data is being protected; what happens when systems are maintained (with many temporary users and activities); and lastly, understanding all of the protective technologies that are being used so risks can be assessed.</p><p>BAS readers should be able to relate most to this function area, though maybe not as broadly to the scope of protection illustrated above. The new BACnet/SC addendum is a good example of a specification for protecting BACnet nodes.</p><h3>Detect</h3><p>Detecting breaches is probably a most basic function that needs to be performed in BAS, but it’s probably also the least understood since as a discipline, BAS has not, generally, had to deal with cyber breaches. It is important that we think about the detection of breaches so they can be dealt with systematically.</p><p>NIST breaks the detection function into three parts: detecting anomalies and events, continuous monitoring, and understanding the detection processes. As most BAS readers know, building systems are very much event-driven, so in many ways, this is part of our DNA. The question is which events should be detected as a security incident?</p><p>This is where we can start to understand the sequence of the NIST Framework functions. Having identified all of the components (Identify), and with adequate protection technologies and processes (Protect), a system stands a better chance of detecting an anomaly from normal events. Without knowing what is in the system, and without knowing how it is being protected, it would be hard to know the good from the bad.</p><p>With this, we should start to see how the framework works, and it’s not hard to map this to BAS use cases.</p><h3>Respond</h3><p>While most of us assume that no bad incidents happen, the NIST Framework assumes that an incident WILL occur at some point. When an incident is detected, as per above, how do the building and the people operating the building respond?</p><p>As you would expect, the NIST Framework starts with planning, anticipating that incidents will happen and laying out a plan to respond. It’s easy to see how important this is for buildings with the many players involved from occupants, owners, facility managers, IT/security professionals as well as system and mechanical service providers that may need to be consulted WHEN something happens.</p><p>A key part of the response is communication between the stakeholders. Who is notified, how do they respond in their respective responsibility area? This is quickly followed by analysis. What happened? Should the building be evacuated? In certain types of buildings (see Identify), different responses would be in order.</p><p>Under a continuous improvement banner, the NIST Framework also provides consideration of mitigation and improvement to the response process. In BAS terms, this may well involve some changes in system configuration or other operating parameters.</p><p>Bear in mind that an incident could occur a day after the building’s commissioning or five years hence; the expectation of a speedy response by the owners and occupants is the same.</p><h3>Recover</h3><p>After an incident and response, it is important to think about recovery, the last of NIST Framework’s five functions. While many may think this is well beyond the scope of BAS, the reality is otherwise.</p><p>Again as you expect, the NIST Framework starts with recovery planning. Consider the situation that the incident involved one or more BAS components. Do we simply turn the power back on, or maybe reboot or reset everything? How about the configuration of all of the BAS devices? Does the system have secured and correct backups of EVERYTHING? What is the process of restoring these, or does the BAS need to be reprogrammed and recommissioned?</p><p>Yet again we see the value of the Framework. Having identified, protected, and detected incidents in a controlled and managed manner would provide a much safer way to recover the building’s operation with confidence. The speed of recovery is also an economic issue; if a building is deemed unsafe for occupation following an incident, the daily cost to the building owner/tenant can mount up fast! Who is responsible for this?</p><p>Discovering improvements from incidents is yet again important here, which is a key part of the Recover function. And finally, as part of recovery is communication, here we’re talking about internal communication of improvements between operations, vendors and service providers, communication to occupants, and in many cases extending to public relations, especially with public buildings.</p><h3>Conclusions</h3><p>When we step back and look at the full picture of defending against cybersecurity breaches in buildings, we see that the role of BAS is vital. There are many implications to this; the industry should certainly not just ignore them and push the responsibility to someone else.</p><p>Some would regard this as an additional burden to an already narrow margin business, while the more progressive would see this as an opportunity to provide additional value from services to make sure the buildings we work on remain secure across their lifetime.</p><p>The question is how the industry will organize itself to deal with this trend, in terms of technology, products, and services. This is the discussion we should be having moving forward.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=832ddda58ad" width="1" height="1" alt=""><hr><p><a href="https://medium.com/new-deal/nist-cybersecurity-framework-and-bas-832ddda58ad">NIST Cybersecurity Framework and BAS</a> was originally published in <a href="https://medium.com/new-deal">A New Deal for Buildings</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Cybersecurity Summit 2020]]></title>
            <link>https://medium.com/new-deal/cybersecurity-summit-2020-2500e4a28024?source=rss----d0a2cb45e1b---4</link>
            <guid isPermaLink="false">https://medium.com/p/2500e4a28024</guid>
            <category><![CDATA[facility-it]]></category>
            <category><![CDATA[hvac]]></category>
            <category><![CDATA[ndsummit]]></category>
            <category><![CDATA[summit]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <dc:creator><![CDATA[Anto Budiardjo]]></dc:creator>
            <pubDate>Fri, 20 Dec 2019 15:29:04 GMT</pubDate>
            <atom:updated>2019-12-21T00:57:39.255Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*5vYcix4x2XqnH2d50OX8Cw.png" /></figure><h3>A Summit to advance BAS cybersecurity</h3><p>For the second year, the New Deal for Buildings is organizing a Cybersecurity Summit at AHR Expo. The event is designed to gather BAS leaders and facility practitioners to discuss and chart the way forward for the adoption of comprehensive cybersecurity policies, practices, and technologies in the BAS industry. Sponsors of this event are made up of the leading companies and organizations advocating for better cybersecurity in building automation systems.</p><p>The Summit comes at the heels of the release of BACnet/SC, a critical component to securing BAS networks. Those interested in the deployment of BACnet/SC should definitely attending this event.</p><p>Date: <strong>Tuesday, February 4, 2020</strong><br>Time: <strong>8:00 am - 12:00 Noon</strong><br>Venue: <strong>W311G Orlando County Convention Center, Orlando, FL</strong></p><h3>NOTE: No registration or badge is required.</h3><p>For more information, contact <a href="/service/mailto:anto@budiardjo.com">summit@newdeal.blog</a>.</p><h3>Who Should Attend</h3><p>Addressing cybersecurity in BAS is critical for the broad adoption of products and services delivering the value promised from intelligent and smart buildings. This Summit is specifically designed for:</p><ul><li>Business leaders in BAS, automation, and controls</li><li>Product managers, service managers, and developers</li><li>Integrators and contractors delivering smart solutions</li><li>The leadership of facility managers and building owners</li><li>Consultants, media, bloggers, and others around smart buildings</li></ul><h3>Agenda</h3><ul><li>8:00 am <strong>Breakfast &amp; Networking</strong></li><li>8:30 am <strong>Welcome &amp; Keynote</strong></li><li>9:00 am <strong>Identify</strong></li><li>9:30 am <strong>Protect</strong></li><li>10:30 am <strong>Detect</strong></li><li>11:00 am <strong>Respond</strong></li><li>11:20 am <strong>Recover</strong></li><li>11:40 am <strong>Closing Comments</strong></li><li>12:00 Noon <strong>Summit Ends</strong></li></ul><p>Agenda subject to change.</p><h3>Confirmed Speakers</h3><ul><li><a href="https://www.linkedin.com/in/james-lee-605072139/">Jim Lee</a>, Cimetrics, Inc. (Chair)</li><li><a href="https://www.linkedin.com/in/andymcm/">Andy McMillan</a>, BACnet International</li><li><a href="https://www.linkedin.com/in/james-butler-16b29b12/">James Butler</a>, BACnet IT Working Group</li><li><a href="https://www.linkedin.com/in/hans-joerg-schweinzer-2166b134/">Hans-Joerg Schweinzer</a>, LOYTEC Electronics, GmbH</li><li><a href="http://linkedin.com/in/r-chris-kwong-fec-p-eng-5a41b713">Chris Kwong</a>, Delta Controls, Inc.</li><li><a href="http://linkedin.com/in/jhreeves">Jerry Reeves</a>, Tosibox</li><li><a href="http://linkedin.com/in/kevintsmith">Kevin Smith</a>, Tridium, Inc.</li><li><a href="http://linkedin.com/in/steve-fey-8988005">Steve Fey</a>, Totem Building Cybersecurity</li><li><a href="https://www.linkedin.com/in/carol-lomonaco-21a14315/">Carol Lomonaco</a>, Johnson Controls.</li><li><a href="https://www.linkedin.com/in/dave-bohlmann-5575b0/">Dave Bohlmann</a>, KMC Controls.</li><li><a href="https://www.linkedin.com/in/antobud/">Anto Budiardjo</a>, New Deal for Buildings</li></ul><h3>Sponsored by</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*n134mguGooY1wgr7jY87JA.png" /></figure><h3>Attendance Information</h3><ul><li>Attendance to the Summit is open to all AHR Expo ticket holders.</li><li>Breakfast is available on a first-come basis. Come early!</li><li>The Summit is organized as a discussion forum, come with your questions, comments, and thoughts on BAS cybersecurity.</li><li>For more information, contact <a href="/service/mailto:summit@newdeal.blog">summit@newdeal.blog</a>.</li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2500e4a28024" width="1" height="1" alt=""><hr><p><a href="https://medium.com/new-deal/cybersecurity-summit-2020-2500e4a28024">Cybersecurity Summit 2020</a> was originally published in <a href="https://medium.com/new-deal">A New Deal for Buildings</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Cybersecurity is Everyone’s Business]]></title>
            <link>https://medium.com/new-deal/cybersecurity-is-everyones-business-2243152a3e05?source=rss----d0a2cb45e1b---4</link>
            <guid isPermaLink="false">https://medium.com/p/2243152a3e05</guid>
            <category><![CDATA[iot]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[hvac]]></category>
            <category><![CDATA[building-automation]]></category>
            <category><![CDATA[meetings]]></category>
            <dc:creator><![CDATA[Anto Budiardjo]]></dc:creator>
            <pubDate>Tue, 03 Sep 2019 13:06:01 GMT</pubDate>
            <atom:updated>2019-09-03T13:06:01.633Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*L2XBGdJpmj2obNh9S473xg.png" /></figure><p>It is easy to think of cybersecurity as just another challenge for the tech people since that is typically how we think of other challenges that technology solves; think computing power, digital audio, smartphones, etc.</p><p>The above sentiment is especially true in the BAS industry, the focus of this scribe. The “everyone’s business” mantra applies all the way from sales to maintenance, product development to distribution, and from the boardroom to the boiler room. Cybersecurity is everyone’s business.</p><p>Why is this the case? Why is cybersecurity any different than other technologies that the BAS industry has adopted in the past? I am arguing here that over the next few decades, addressing cybersecurity will be a key subject in the evolution of the digital world. In our personal lives, we will make decisions based on it, but those decisions are <em>relatively </em>simple; it comes down to which smartphone you buy or where you do online shopping. The heavy lifting will mostly be done by large tech vendors behind the scenes. As with all things consumer, it will come down to brand reputation. We are seeing this play out with the large tech companies’ positioning around security.</p><p>BAS is a B2B space, and building systems are never a “standard product” per se. This is because each building is different; they are engineered systems in the truest sense of the term. Thus, each building is financed, specified (even if using a template), designed, planned, built (using standard components), commissioned, maintained, and operated according to its own specific needs.</p><p>The one thing we know about cybersecurity is that what the bad actors look for is a weakness in the system. As the defender of BAS, we as an industry must be 100% secure 100% of the time, whereas a potential intruder only needs to be successful once. And, they get to try as many times as their economic motivation justifies. The odds are on their side.</p><p>This is where the concept of holistic cybersecurity makes complete sense and should be the battle cry of all players in the BAS industry.</p><p>As a <strong>sales executive</strong>, it’s imperative that your prospects understand the need to include cybersecurity tools and services as part of what you propose to them.</p><p>As a <strong>board director</strong> of a BAS company, it is imperative to know the cybersecurity profile of the company you oversee and to allocate adequate resources for the company to address security fully.</p><p>As a <strong>maintenance engineer</strong>, it is critical that you abide by the cybersecurity policies and procedures in place at any facility you maintain, and you must demand them if they are not forthcoming.</p><p>As a <strong>product developer</strong>, you must ensure that any product you work on addresses all of the requirements and best practices necessary such that the products are secure.</p><p>As a <strong>mechanical engineer</strong>, it is important to use the right tools and procedures to do your work and be extra careful in potentially vulnerable areas such as user credentials.</p><p>Basically, as a <strong>[add your role here]</strong>, you must consider how your actions could expose the building in which you are working and do everything necessary to prevent a vulnerability from being exposed by malicious actors.</p><p>Yes, I know, we all have a whole bunch of other, more pressing priorities to deal with; project completion, budget numbers, profits, getting home to your family, and so on. How do you add yet another issue in today’s crazy and hectic work environment?</p><p>I have a few suggestions that should make this easier.</p><ol><li><strong>Add “Cybersecurity” to all project meeting agendas</strong>. And, don’t just add it as the last item that can be skipped as the meeting concludes, add it as the first item! The point isn’t to spend much time on it; it’s to remind everyone to think about cybersecurity.</li><li><strong>Don’t do business with anyone that does not take cybersecurity seriously</strong>. Would you buy a car without breaks or seat belts? Ask your vendors and clients about their cybersecurity policies and expectations. If they don’t have one, you are possibly exposed.</li><li><strong>Expose risks when they are obvious</strong>. Many times, we see flagrant breaches of the most fundamental cybersecurity hygiene principles; visiting a client that has passwords on a post-it note, a co-worker setting a new password as “password”. How you expose these risks depends on you. Be sensitive and kind, but not doing so makes you culpable.</li><li><strong>Use basic security tools always</strong>. Responsible systems will enable the use of <a href="https://en.wikipedia.org/wiki/Multi-factor_authentication">Multi/Two Factor Authentication</a> to make sure your credentials are not abused, and technologies such as VPN/VLANs are widely available. Use them in the normal course of business.</li><li><strong>Don’t plug in the USB memory stick you found in the parking lot</strong>. Be very wary of introducing any unknown devices, software or other digital assets into any of your, or your client’s equipment. This is how <a href="https://www.wired.com/2011/06/the-dropped-drive-hack/">Stuxnet was said to have been deployed</a>.</li></ol><p>It’s really easy to sweep cybersecurity under a rug. The BAS industry has not had to address this issue in the past as most of the systems we have installed have been disconnected from the rest of the world. With the move to IP, this is no longer the case.</p><p>Stay safe and secure out there.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2243152a3e05" width="1" height="1" alt=""><hr><p><a href="https://medium.com/new-deal/cybersecurity-is-everyones-business-2243152a3e05">Cybersecurity is Everyone’s Business</a> was originally published in <a href="https://medium.com/new-deal">A New Deal for Buildings</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>