RSVP Now
by Kyle Hussey
by Kyle Hussey
Over the past several months, the National Cybersecurity Center of Excellence (NCCoE) at the National Institute of Standards and Technology (NIST) has been working on a cybersecurity project involving asset management to help energy utilities and the oil the gas industry develop an automated solution to better manage their industrial control system (ICS) assets.
The NCCoE is a collaborative hub where industry organizations, government agencies, and academic institutions work together to address businesses’ most pressing cybersecurity challenges. The NCCoE has just released draft practice guide NIST Special Publication 1800-23, Energy Sector Asset Management.
This project explores methods for managing, monitoring, and baselining assets and includes information to help identify threats to these OT assets. Both standards and best practices were used to develop reference designs leveraging commercially available technologies. The guide also maps capabilities to NIST guidance and control families, including the NIST Cybersecurity Framework.
TDi’s flagship product, ConsoleWorks Cybersecurity & Operations Platform, is one of the solutions along with others in the NIST cybersecurity framework for this project.
To complete this guide, the NCCoE collaborated with other technology vendors, including Dragos, Forescout, FoxGuard Solutions, KORE Wireless Group, Splunk, and Tripwire. The NCCoE believes the guide helps meet a critical cybersecurity and economic need, but we want to hear from you. Please share your thoughts on this step-by-step guide to enhance it. Download the draft guide and provide your feedback on the NCCoE comment page. The public comment period closes on November 25, 2019.
FAQ’s related to ESAM
Below are a set of FAQs specific to NIST SP 1800-23, Energy Sector Asset Management (ESAM) Practice Guide. Please share this information with your communications/public relations departments as they may use them as a basis for personalized talking points. If significant changes will be made to better appeal to your primary audience, please send to Lauren Acierto (lacierto@mitre.org) for review, allowing for a five-business-day turnaround.
Why did the National Cybersecurity Center of Excellence (NCCoE) create this guide?
Industrial control system assets provide command and control information as well as key functions on OT networks. These assets are primary targets of cyber attacks and any vulnerabilities in these assets can present opportunities for malicious actors to disrupt both the electric grid and oil and natural gas infrastructure. Such disruptions can result in economic loss and interruption of critical services to millions of people. This guide was created to provide a reference architecture and an example solution for managing, monitoring, and baselining assets, and includes information to help identify threats to these OT assets.
What is this practice guide about?
This guide describes methods for managing, monitoring, and baselining assets and also includes information to help identify threats to these OT assets. The guide includes a reference design and uses commercially available technologies in an example solution that will help energy organizations address the security challenges of OT asset management.
What is energy sector asset management?
Asset management is defined in the NIST Cybersecurity Framework as the identification and management of data, personnel, devices, systems, and facilities that enable the organization to achieve business purposes, consistent with their relative importance to business objectives and the organization’s risk strategy. In this guide we are addressing the following characteristics of asset management in the energy sector:
Will energy sector executives find value in this practice guide?
Yes! The NCCoE’s Energy Sector Asset Management Practice Guide can help an organization:
Will energy sector technology (IT) professionals find value in this practice guide?
Yes! This guide assumes that IT professionals have experience implementing security products within the enterprise. The practice guide builds on this knowledge, so that IT professionals who opt to implement ESAM in their organizations will find practical and actionable information throughout the entire guide. Here’s why:
*While the example implementation uses certain products, NIST and the NCCoE do not endorse these products. The guide presents the characteristics and capabilities of those products, which an organization’s security experts can use to identify similar standards-based products that will fit within with their organization’s existing tools and infrastructure.
by Kyle Hussey
Advancements in medical imaging technology are helping patients get diagnosed and treated more quickly and effectively. But unsecured systems can open the door to breaches of patient data and could potentially risk patient safety. Our Securing Picture Archiving and Communication System guidance shows how healthcare delivery organization can take advantage of these technologies while also ensuring patient data is protected.
Jennifer Cawthra, NIST NCCoE Healthcare Sector Lead
The National Cybersecurity Center of Excellence (NCCoE) at the National Institute of Standards and Technology (NIST) is proud to release a new practice guide – NIST Special Publication 1800-24, Securing Picture Archiving and Communication System (PACS) – to help healthcare delivery organizations (HDOs) protect patient images and other pertinent medical data. The NCCoE is a collaborative hub where industry organizations, government agencies, and academic institutions work together to address businesses’ most pressing cybersecurity challenges. This practice guide represents the NCCoE’s dedication to the public interest and the critical cybersecurity matters within the healthcare sector.
The guide can be used by any organization that is deploying PACS and medical imaging systems, and that is willing to perform its own risk assessment and implement controls based on its risk posture. Both standards and best practices were used to develop two reference designs leveraging commercially available technologies. The guide also maps capabilities to NIST guidance and control families, including the NIST Cybersecurity Framework.
TDi’s flagship product, ConsoleWorks Cybersecurity & Operations Platform, is one of the solutions along with others in the NIST cybersecurity framework for this project.
To complete this guide, the NCCoE collaborated with other technology vendors, including Cisco, Clearwater Compliance, Digicert, Forescout, Hyland, Philips, Symantec, Tempered Networks, Tripwire, Virta Labs, and Zingbox.
The NCCoE believes the guide helps meet critical cybersecurity and economic need, but we want to hear from you. Please share your thoughts on this step-by-step guide to enhance it. Download the draft guide and provide your feedback on the NCCoE comment page. The public comment period closes on November 18, 2019.
FAQ’s related to PACS
Why did the National Cybersecurity Center of Excellence (NCCoE) create this guide?
Healthcare is a part of the nation’s critical infrastructure and vulnerabilities within this sector have the potential to result in breaches inpatient data or risks to patient safety. These vulnerabilities could also expose an HDO to risks of significant data loss, malware and ransomware attacks, and unauthorized access to other parts of an HDO enterprise network. The NCCoE’s mission is to accelerate the adoption of secure technologies to address critical cybersecurity challenges in key industry sectors. To learn more about the NCCoE’s cybersecurity efforts in healthcare, visit nccoe.nist.gov/healthcare.
What is this practice guide about?
This guide provides practical, real-world guidance to healthcare providers interested in implementing an example solution to securely configure and deploy PACS ecosystem. The guide also contains several risk-based scenarios detailing the approach with risk assessment and analysis; logical design; example build development, functional test and evaluation; and security control mapping.
What is the scope of this project?
The NCCoE project focused on securing the environment of the PACS ecosystem, but not on reengineering medical devices or altering medical imaging processes themselves. This project has led to a standards-based practice guide that is applicable to the wider healthcare ecosystem. This practice guide has been derived from the implementation of a secure PACS in a laboratory environment at the NCCoE that seeks to replicate parts of a typical HDO environment. The project considers PACS users internal to the HDO as well as external users and partners needing access to certain components of the HDO environment.
Will healthcare executives find value in this practice guide?
Yes! The NCCoE’s Securing Picture Archiving and Communication System (PACS) Practice Guide can help an organization:
Will healthcare information technology (IT) professionals find value in this practice guide?
*While the example implementation uses certain products, NIST and the NCCoE do not endorse these products. The guide presents the characteristics and capabilities of those products, which an organization’s security experts can use to identify similar standards-based products that will fit within with their organization’s existing tools and infrastructure.
by Kyle Hussey
Many IT/OT professionals are very concerned about configuration port management. Configuration ports are often on a separate network, typically called an out-of-band or maintenance network. Many use the out-of-band network extensively for break/fix, patching, the build process, configuration changes, and asset redeployment.
From a user (admin) perspective, configuration ports can be problematic because access often involves directly connecting to the ports with telnet or ssh, using a terminal server for serial configuration points, and multiple tools that may be in place for networked configuration port access. There is a lot to know and remember making it cumbersome, time-consuming and often difficult to get to a particular device easily.
From a management perspective configuration, ports are a gaping security and compliance hole. Configuration ports are always highly privileged interfaces. Security policies are typically in place calling for configuration ports to be under tightly controlled security, with all changes made over them documented. That is so difficult to do with most operations tools that the issue gets shoved under a rug and everyone avoids talking about it.
This puts the organization at significant risk. In the past, the issue has been tabled due to the lack of a useful tool that will meet management needs without impacting the performance of the ops team.
ConsoleWorks Privileged Interactive Access eliminates this risk. Using ConsoleWorks all privileged user activity from users, 3rd-party vendors and contractors are logged as a forensic record of activity performed on assets, a persistent connection is maintained to ensure nothing is missed (no buffers; no polling cycles), and a comprehensive security model with granular permissions for access control is provided. Performance is improved rather than being degraded.
Improved security and compliance with improved performance is a winner. It dramatically reduces risk (breaches, fines) while reducing the work required for the operations team to get their job done.
ConsoleWorks Privileged Interactive Access (configuration port management)
by Kyle Hussey
What is persistent security with ConsoleWorks? Traditional security practices focus primarily on normal operations and require documentation to be performed manually. ConsoleWorks achieves full security and automated documentation in all modes, including maintenance, configuration, and system failure. This “always-on” connection, which covers many of the traditional approach’s “blind spots,” is what we mean when we talk about persistent security. ConsoleWorks remains in a persistent state of security by retaining its connection in all states, locking out unauthorized access, and automatically capturing forensic records of all User activity.
Persistent Security in Action
A leader in healthcare technology chose ConsoleWorks to help them ensure the protection of patient records, delivery of mission-critical healthcare services, and compliance with HIPAA regulations.
This company didn’t want to risk leaving their systems vulnerable to potential security risks through the “blind spots” of traditional security practices – that is, anyone accessing devices or systems through a means other than the normal network, such as through a serial or configuration port.
ConsoleWorks monitors these ports and establishes a persistent connection that detects and reports on events in real-time. It also creates forensic records of all actions taken, in all operating modes, down to the keystroke – invaluable in protecting the organization from litigation and HIPAA violations.
by Kyle Hussey
Many of today’s monitoring solutions depend on polling at predefined intervals, using agents that are only capable of responding when the operating system and network stack are functioning normally. Because polling a large number of systems frequently can be resource intensive, polling intervals are commonly 10 to 20 minutes or even longer, which can result in delayed problem detection.
When an operating system fails, for example, polling solutions depend on time-outs to alert the user that an application or device is down. It often takes more than one polling cycle to generate a problem notification, and warning events that occur between polls may be detected too late to prevent failures.
While decreasing the polling interval may help a little, the cost would be more network traffic and more CPU utilization on the monitored system.
ConsoleWorks has a different approach maintaining a persistent connection to ensure nothing is missed. No buffers; no polling cycles.
Persistent monitoring with ConsoleWorks for IT/OT environments, monitors the hardware management interfaces, such as serial console, iLO, Baseboard Management Controller, etc. constantly and in real time. Advance warning error messages are received, immediately identifying the root cause and allowing administrators to address problems before they become failures.
Anticipating and addressing problems before they occur and identifying them instantly in real-time results in improved system oversight and a significant reduction in mean-time-to-repair.
Reach out today, and we'll talk through how we might be able to help!
sales@tditechnologies.com
info@tditechnologies.com
support@tditechnologies.com
TDI Technologies, Inc.
8751 Collin McKinney Pkwy
Suite 1102, Box 1155
McKinney, TX 75070
Toll Free (US): 800-695-1258
Main Office: 972-881-1553