Application Security

5/9/2018
04:00 PM
Dark Reading
Dark Reading
Products and Releases
50%
50%

Black Box Debuts New Secure KVM Switches

PITTSBURGH, May 09, 2018 -- Black Box Corporation now offers a comprehensive line of Secure KVM Switches that safeguard against accidental transfer, unauthorized access or compromise of critical data.

“Black Box was a pioneer in KVM technology back in the 1990s and has continued to lead the KVM market over the quarter-century since,” said John Hickey, R&D & KVM Systems Director, at Black Box. “It’s a natural evolution in our history that we’re bringing to market new secure KVM switches with cybersecurity features that customers have been demanding but that didn’t previously exist.”

New features meet customer demands for secure KVM switching

Examples of innovations that will be soon available from Black Box include secure KVM switches with up to 16 direct computer connections controlled from a single user console. These come with DVI-I, DisplayPort, or HDMI video supporting 4K Ultra HD resolution, stereo audio, USB and an optional smart card reader (CAC-Port).

The secure KVM switches provide complete mechanical, electrical and optical signal isolation to ensure that absolutely no data is leaked between the ports. Each connection uses its own isolated data channel excluding the outside world. For added security, the switches also feature an always-on tamper-proof hardware design, including external hologram tamper-evident seals and long-life internal anti-tampering batteries, as well as keyboard/internal cache wiping and non-reprogrammable ROM.

Secure access solution for information assurance

All Black Box secure KVM switches comply with PSS PP v3.0 (Protection Profile for Peripheral Sharing Switch, Version 3.0) and are being certified by the National Information Assurance Partnership (NIAP), making them suitable for use in government, medical, banking, insurance, secure control rooms, educational administration, corporate, industrial and other environments with cyber-security, hacking and data leakage concerns. They are TAA compliant and made in the U.S.

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
Want Your Daughter to Succeed in Cyber? Call Her John
John De Santis, CEO, HyTrust,  5/16/2018
New Mexico Man Sentenced on DDoS, Gun Charges
Dark Reading Staff 5/18/2018
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Write a Caption, Win a Starbucks Card! Click Here
Latest Comment: This comment is waiting for review by our moderators.
Current Issue
Flash Poll
[Strategic Security Report] Navigating the Threat Intelligence Maze
[Strategic Security Report] Navigating the Threat Intelligence Maze
Most enterprises are using threat intel services, but many are still figuring out how to use the data they're collecting. In this Dark Reading survey we give you a look at what they're doing today - and where they hope to go.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2018-11354
PUBLISHED: 2018-05-22
In Wireshark 2.6.0, the IEEE 1905.1a dissector could crash. This was addressed in epan/dissectors/packet-ieee1905.c by making a certain correction to string handling.
CVE-2018-11355
PUBLISHED: 2018-05-22
In Wireshark 2.6.0, the RTCP dissector could crash. This was addressed in epan/dissectors/packet-rtcp.c by avoiding a buffer overflow for packet status chunks.
CVE-2018-11356
PUBLISHED: 2018-05-22
In Wireshark 2.6.0, 2.4.0 to 2.4.6, and 2.2.0 to 2.2.14, the DNS dissector could crash. This was addressed in epan/dissectors/packet-dns.c by avoiding a NULL pointer dereference for an empty name in an SRV record.
CVE-2018-11357
PUBLISHED: 2018-05-22
In Wireshark 2.6.0, 2.4.0 to 2.4.6, and 2.2.0 to 2.2.14, the LTP dissector and other dissectors could consume excessive memory. This was addressed in epan/tvbuff.c by rejecting negative lengths.
CVE-2018-11358
PUBLISHED: 2018-05-22
In Wireshark 2.6.0, 2.4.0 to 2.4.6, and 2.2.0 to 2.2.14, the Q.931 dissector could crash. This was addressed in epan/dissectors/packet-q931.c by avoiding a use-after-free after a malformed packet prevented certain cleanup.