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
10% of Small Businesses Breached Shut Down in 2019
Newest First  |  Oldest First  |  Threaded View
Dr.T
50%
50%
Dr.T,
User Rank: Ninja
10/27/2019 | 3:19:58 PM
Re: On small business support
"..they do not have the resources for a full CSirt department...."

This is a common problem in the industry, unfortunately.

 

 

 
Dr.T
50%
50%
Dr.T,
User Rank: Ninja
10/27/2019 | 3:09:17 PM
37?
"As a result of cybercrime, 69% of small organizations were forced offline for a limited time and 37% experienced financial loss."   37% seems to be a little bit small to me. We keep hearing about breaches. I would have expected a little bit bigger number.
REISEN1955
50%
50%
REISEN1955,
User Rank: Ninja
10/24/2019 | 8:23:08 AM
On small business support
I provided managed service support for small accounts a few years ago -- they do not have the resources for a full CSirt department of course or really an on-staff engineer skilled in the field.  So they are vulneable by default.  A real opening for consulting is to provide such support to clients with more emphasis on the cyber side than simple and relatively dull server management and workstation management.  The latter are endpoints of course but also good TEACHING AND INSTRUCTION to staff is a fine thing too.  That would solve a ton of problems right there.    Small firms have almost no financial depth too, so lack of income or hit to perception can drive business away real fast and their cashflow cannot tolerate that.  They also do not see the need for tech protection as miuch as larger organizations do that have, after all, a runnning CSirt department.  Smal business sees risk as small - so goes their name.  Risk = large but their size mitigates against that perception.  They ARE small so who would be interested in them?   Well, any hacker is interested ---- any one of them. 


Data Leak Week: Billions of Sensitive Files Exposed Online
Kelly Jackson Higgins, Executive Editor at Dark Reading,  12/10/2019
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Write a Caption, Win a Starbucks Card! Click Here
Latest Comment: Our Endpoint Protection system is a little outdated... 
Current Issue
The Year in Security: 2019
This Tech Digest provides a wrap up and overview of the year's top cybersecurity news stories. It was a year of new twists on old threats, with fears of another WannaCry-type worm and of a possible botnet army of Wi-Fi routers. But 2019 also underscored the risk of firmware and trusted security tools harboring dangerous holes that cybercriminals and nation-state hackers could readily abuse. Read more.
Flash Poll
Rethinking Enterprise Data Defense
Rethinking Enterprise Data Defense
Frustrated with recurring intrusions and breaches, cybersecurity professionals are questioning some of the industrys conventional wisdom. Heres a look at what theyre thinking about.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2019-19767
PUBLISHED: 2019-12-12
The Linux kernel before 5.4.2 mishandles ext4_expand_extra_isize, as demonstrated by use-after-free errors in __ext4_expand_extra_isize and ext4_xattr_set_entry, related to fs/ext4/inode.c and fs/ext4/super.c, aka CID-4ea99936a163.
CVE-2019-19768
PUBLISHED: 2019-12-12
In the Linux kernel 5.4.0-rc2, there is a use-after-free (read) in the __blk_add_trace function in kernel/trace/blktrace.c (which is used to fill out a blk_io_trace structure and place it in a per-cpu sub-buffer).
CVE-2019-19769
PUBLISHED: 2019-12-12
In the Linux kernel 5.3.10, there is a use-after-free (read) in the perf_trace_lock_acquire function (related to include/trace/events/lock.h).
CVE-2019-19770
PUBLISHED: 2019-12-12
In the Linux kernel 4.19.83, there is a use-after-free (read) in the debugfs_remove function in fs/debugfs/inode.c (which is used to remove a file or directory in debugfs that was previously created with a call to another debugfs function such as debugfs_create_file).
CVE-2019-19771
PUBLISHED: 2019-12-12
The lodahs package 0.0.1 for Node.js is a Trojan horse, and may have been installed by persons who mistyped the lodash package name. In particular, the Trojan horse finds and exfiltrates cryptocurrency wallets.