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
New Federal Report Gives Guidance on Beating Botnets
Oldest First  |  Newest First  |  Threaded View
BrianN060
50%
50%
BrianN060,
User Rank: Ninja
6/9/2018 | 10:31:19 AM
Guidance on Beating Botnets - report
While the report and the executive order are meaningful, a number of the points mentioned in the article are questionable, if not downright head-scratching.  Those referenced in the article summary are perplexing - but recourse to the full report doesn't resolve the ambiguities or provide actionable and effective guidance. 

Reading the full report is a challenge (if you take the time to consider what's said - started with hip-boots, switched to chest waders, and may need to go with a snorkel). 

As just one example of the politico-bureaucrat-esse muck, are the references to "the IoT community".  There are a number of things the report says this community must do or should do, such as "The IoT community must work collaboratively [my emphasis] to identify and adopt existing best practices, frameworks, and guidelines that are...".  When the authors of this report compile a comprehensive and authoritative list of the individuals members of this community, then they can assign the responsibilities of identifying, and adopting best practices, frameworks and guidelines...; at which point I'm sure they'll form a committee, to assess how well the community is doing, and suggest new ways to make their work more effective.  Not only is the idea of an IoT community ludicrous; any list of best practices, frameworks, etc. would be out of date before it could be published, let alone implemented.  The only comedy relief is contemplating who will emerge as their spokes(person): Amazon Echo, or Google Home

Sadly, the IoT community gibberish is but one example; you can hardly take a step through the report without splatting into another. 


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
Video
Cartoon
Current Issue
How Enterprises are Attacking the Cybersecurity Problem
Concerns over supply chain vulnerabilities and attack visibility drove some significant changes in enterprise cybersecurity strategies over the past year. Dark Reading's 2021 Strategic Security Survey showed that many organizations are staying the course regarding the use of a mix of attack prevention and threat detection technologies and practices for dealing with cyber threats.
Flash Poll
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2021-43056
PUBLISHED: 2021-10-28
An issue was discovered in the Linux kernel for powerpc before 5.14.15. It allows a malicious KVM guest to crash the host, when the host is running on Power8, due to an arch/powerpc/kvm/book3s_hv_rmhandlers.S implementation bug in the handling of the SRR1 register values.
CVE-2021-43057
PUBLISHED: 2021-10-28
An issue was discovered in the Linux kernel before 5.14.8. A use-after-free in selinux_ptrace_traceme (aka the SELinux handler for PTRACE_TRACEME) could be used by local attackers to cause memory corruption and escalate privileges, aka CID-a3727a8bac0a. This occurs because of an attempt to access th...
CVE-2021-3904
PUBLISHED: 2021-10-27
grav is vulnerable to Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')
CVE-2021-3906
PUBLISHED: 2021-10-27
bookstack is vulnerable to Unrestricted Upload of File with Dangerous Type
CVE-2021-3903
PUBLISHED: 2021-10-27
vim is vulnerable to Heap-based Buffer Overflow