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.

Comments
Internet of Things: 4 Security Tips From The Military
Newest First  |  Oldest First  |  Threaded View
<<   <   Page 2 / 2
Thomas Claburn
Thomas Claburn,
User Rank: Ninja
7/25/2014 | 6:39:25 PM
Re: What not to learn from the military
We can also learn something from the fictional military, as depicted in the recent remake of Battlestar Galactica: Networked equipment will be your doom.
Marilyn Cohodas
Marilyn Cohodas,
User Rank: Strategist
7/25/2014 | 4:16:44 PM
Re: What not to learn from the military
Good point, Thanks. I've heard that voiced as a "poor practice" with enterprises deaiing with BYOD... a precursor of what is coming with IoT.
MichaelKDaly
MichaelKDaly,
User Rank: Author
7/25/2014 | 4:13:00 PM
Re: What not to learn from the military
One good lesson to learn (that is, what we should not do) comes from the poor practice of bringing multiple sources of information back to a centralized repository, particularly one that does not have data element security controls.  We often see data sets, for which we have diligently applied access controls, later connected to other systems using a privileged account. It then pulls the data out and into these secondary systems, which aggregate and correlate, failing to maintain the original access controls and retention policies of the source data set.  This can be repeated through several chains, fully confusing "originator control", and permitting excessive access by the privileged users of these aggregator systems.
Marilyn Cohodas
Marilyn Cohodas,
User Rank: Strategist
7/25/2014 | 3:53:09 PM
What not to learn from the military
Good blog, Michael. Thanks for your insight. Curious to know what you think is the one thing that InfoSec can learn from the military about what NOT to do with the IoT. 
<<   <   Page 2 / 2


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
Practical Network Security Approaches for a Multicloud, Hybrid IT World
The report covers areas enterprises should focus on for their multicloud/hybrid cloud security strategy: -increase visibility over the environment -learning cloud-specific skills -relying on established security frameworks -re-architecting the network
Flash Poll
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2022-30333
PUBLISHED: 2022-05-09
RARLAB UnRAR before 6.12 on Linux and UNIX allows directory traversal to write to files during an extract (aka unpack) operation, as demonstrated by creating a ~/.ssh/authorized_keys file. NOTE: WinRAR and Android RAR are unaffected.
CVE-2022-23066
PUBLISHED: 2022-05-09
In Solana rBPF versions 0.2.26 and 0.2.27 are affected by Incorrect Calculation which is caused by improper implementation of sdiv instruction. This can lead to the wrong execution path, resulting in huge loss in specific cases. For example, the result of a sdiv instruction may decide whether to tra...
CVE-2022-28463
PUBLISHED: 2022-05-08
ImageMagick 7.1.0-27 is vulnerable to Buffer Overflow.
CVE-2022-28470
PUBLISHED: 2022-05-08
marcador package in PyPI 0.1 through 0.13 included a code-execution backdoor.
CVE-2022-1620
PUBLISHED: 2022-05-08
NULL Pointer Dereference in function vim_regexec_string at regexp.c:2729 in GitHub repository vim/vim prior to 8.2.4901. NULL Pointer Dereference in function vim_regexec_string at regexp.c:2729 allows attackers to cause a denial of service (application crash) via a crafted input.