Dark Reading is part of the Informa Tech Division of Informa PLC

This site is operated by a business or businesses owned by Informa PLC and all copyright resides with them.Informa PLC's registered office is 5 Howick Place, London SW1P 1WG. Registered in England and Wales. Number 8860726.

Database Security
Authentication
Mobile
Privacy
Compliance
Careers and People
Identity & Access Management
Security Monitoring
Advanced Threats
Insider Threats
Vulnerability Management
Comments
NIST Issues IoT Risk Guidelines
Newest First  |  Oldest First  |  Threaded View
ylwspd
ylwspd,
 User Rank: Apprentice
7/1/2019 | 12:03:15 PM
Re: Protect Individuals Privacy
I agree that creating a policy where BYOD isn't allowed is the "easiest", however it's definitely not the most practical or reasonable.  Businesses want and need employees to be as up to date and responsive as possible, and expecting someone to carry multiple devices is impractical. More things to lose, keep powered up, etc.  It's what makes the dance of IT such an interesting one.
tdsan
tdsan,
 User Rank: Ninja
6/30/2019 | 5:17:41 PM
Interesting Article about IoT Devices
Look at the security risk aspects of the NIST Publication:
  • Page 8 (Addresses Risk)
  • Page 12 (Device, Data, and Individual risks)
  • Page 15 (Mgmt, Monitoring Features)
  • Page 21 (Challenges to IT Security)
  • Page 27 (Cannot modify software - cannot remove known vulnerabilities, Expectation 5-6)
  • Page 34 (Expectation 17 - May not be able to detect internal threats)
  • Page 33 (Expectation 21, Sect. 34-35) - Does not verify endpoint and does not perform encryption
  • Page 35 (Section 43) - Remote accessibility, Risk Consideration 2
  • Page 41 (Appendix B)

 
In addition, an organization may need to determine how to manage risk not just by device type, but also by device usage. The way a device is to be used may indicate that one security objective, such as integrity, is more important than another, such as confidentiality, and that in turn may necessitate different mechanisms to risk mitigation. Similarly, a device might be used in such a way that some of its capabilities are not needed and can be disabled, which could reduce the device's risk.

This is probably one of the most important aspects of the document because why would a refrigerator want to communicate with a DB or Web application. If the hacker accessed an IoT device, that device tries to communicate with a server or DB that is not part of its original communication stream (baseline), then we can determine if the device is working outside of its normal function. This could lead to addressing problems before they occur; however, we need to address issues with the manufacturer; one solution would need to create a consortium where minimal security aspects are added to the device to ensure some level of compliance or at least a way to thwart attacks.

Later we found out (from Dark Reading), the FTC has increased the minimal standards for device security (DLink Case), so it may not be a consortium but at least someone is paying attention.

Todd

 
RyanSepe
RyanSepe,
 User Rank: Ninja
6/28/2019 | 10:19:56 AM
Protect Individuals Privacy
I'm interested to read more into the 3rd pillar of the report because typically if you are concerned about security you will infringe on someones privacy. Noticeably in an Acceptable Use Policy you'll find that people wave their right to privacy by utilizing a corporate asset. For a personally owned asset, it's my belief that you are better off stating that BYOD is not allowed so you don't have to navigate the sticky waters of trying to maintain best practice security while being cognizant of an individuals privacy.


Edge-DRsplash-10-edge-articles
I Smell a RAT! New Cybersecurity Threats for the Crypto Industry
David Trepp, Partner, IT Assurance with accounting and advisory firm BPM LLP,  7/9/2021
News
Attacks on Kaseya Servers Led to Ransomware in Less Than 2 Hours
Robert Lemos, Contributing Writer,  7/7/2021
Commentary
It's in the Game (but It Shouldn't Be)
Tal Memran, Cybersecurity Expert, CYE,  7/9/2021
Register for Dark Reading Newsletters
White Papers
Video
Cartoon
Current Issue
Everything You Need to Know About DNS Attacks
It's important to understand DNS, potential attacks against it, and the tools and techniques required to defend DNS infrastructure. This report answers all the questions you were afraid to ask. Domain Name Service (DNS) is a critical part of any organization's digital infrastructure, but it's also one of the least understood. DNS is designed to be invisible to business professionals, IT stakeholders, and many security professionals, but DNS's threat surface is large and widely targeted. Attackers are causing a great deal of damage with an array of attacks such as denial of service, DNS cache poisoning, DNS hijackin, DNS tunneling, and DNS dangling. They are using DNS infrastructure to take control of inbound and outbound communications and preventing users from accessing the applications they are looking for. To stop attacks on DNS, security teams need to shore up the organization's security hygiene around DNS infrastructure, implement controls such as DNSSEC, and monitor DNS traffic
Flash Poll
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2023-33196
PUBLISHED: 2023-05-26
Craft is a CMS for creating custom digital experiences. Cross site scripting (XSS) can be triggered by review volumes. This issue has been fixed in version 4.4.7.
CVE-2023-33185
PUBLISHED: 2023-05-26
Django-SES is a drop-in mail backend for Django. The django_ses library implements a mail backend for Django using AWS Simple Email Service. The library exports the `SESEventWebhookView class` intended to receive signed requests from AWS to handle email bounces, subscriptions, etc. These requests ar...
CVE-2023-33187
PUBLISHED: 2023-05-26
Highlight is an open source, full-stack monitoring platform. Highlight may record passwords on customer deployments when a password html input is switched to `type="text"` via a javascript "Show Password" button. This differs from the expected behavior which always obfuscates `ty...
CVE-2023-33194
PUBLISHED: 2023-05-26
Craft is a CMS for creating custom digital experiences on the web.The platform does not filter input and encode output in Quick Post validation error message, which can deliver an XSS payload. Old CVE fixed the XSS in label HTML but didn’t fix it when clicking save. This issue was...
CVE-2023-2879
PUBLISHED: 2023-05-26
GDSDB infinite loop in Wireshark 4.0.0 to 4.0.5 and 3.6.0 to 3.6.13 allows denial of service via packet injection or crafted capture file