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
Five Easiest Ways to Get Hacked Part 2
Newest First  |  Oldest First  |  Threaded View
CarricDooley
50%
50%
CarricDooley,
User Rank: Apprentice
3/6/2015 | 6:11:41 PM
Re: Vulnerability Standpoint

This is a great question and it's something Amit discusses a bit in his Low Hanging Fruits: The Top Five Easiest Ways to Hack or Get Hacked whitepaper (link in blog). In my personal experience, SMB's tend to have almost zero awareness of the threats or their vulnerabilities. They don't really have a geek culture (unless the owner happens to be one) that really participates in the community, that lives and breathes this stuff. I think you can take an affordable approach to achieve SOME level of security. It doesn't take an enterprise-level effort or tool to secure an SMB.

From a purely vulnerability standpoint SMBs would typically look for high value in return for the time and money they invest. My suggestion is to use a scan policy that performs checks only for vulnerabilities, which have an exploit available, or alternatively you can filter the results of a full vulnerability scan to only those which have exploits. This would provide a shorter and more manageable list of actionable items, and you can start with addressing the critical/high risk findings first. Also, for an SMB it will be very valuable to invest in a software for patch management (including non-Microsoft patches), otherwise it becomes too big and discouraging of a problem to solve for most organizations. Lastly, SMBs should use a maturity model based approach to plan where they currently stand and where they would like to go. This would need a thorough understanding of what an organization is trying to protect, and what people, process and technology controls they can put in place to achieve the security level they would like.

Consider the following:

  • Nessus is $1,500/ year, and a very good tool used by almost everyone at all levels of security maturity. It helps find missing patches, default configurations and accounts, etc. For a homogeneous Windows environment (typical for SMB), the "Microsoft Baseline Security Analyzer" is a reasonable start, and not so complicated that just a little IT know-how can't handle the tasks.
  • Microsoft now ships with some basic AV and anti-malware protection built-in, but it's not centrally manageable (less of a problem a problem for a small shop).

Some ISP's offer services to help filter e-mail as well so you might be subject fewer attacks on that vector as well. And, don't run or open anything you get that you don't absolutely trust... Also, having someone local (a small consultancy) help with setting baseline configurations for servers and workstations would help, and vendors provide a lot of guidance for both applications and the OS, especially since most small business these days run some version of Windows.

 

Joe Stanganelli
50%
50%
Joe Stanganelli,
User Rank: Ninja
3/2/2015 | 12:11:10 AM
Testing patches
An important yet oft overlooked aspect of a good patch management strategy: implement everything in a testbed first.  Test everything with everything.  Otherwise, you could really screw things up -- especially in a multi-vendor environment.

Verizon learned this lesson (so we might hope) the hard way last summer when its billing system suffered a multi-day outage because of its failure to test updates.
RyanSepe
50%
50%
RyanSepe,
User Rank: Ninja
2/26/2015 | 9:25:23 AM
Vulnerability Standpoint
From a vulnerability standpoint, it may be difficult to dedicate the bandwidth required for assessment and remediation.It's an ongoing process and is a multi-team faceted endeavor. What tips do you have for small to medium sized organizations that are trying to increase their security posture through their vulnerability remediation effort?


COVID-19: Latest Security News & Commentary
Dark Reading Staff 8/10/2020
Pen Testers Who Got Arrested Doing Their Jobs Tell All
Kelly Jackson Higgins, Executive Editor at Dark Reading,  8/5/2020
Researcher Finds New Office Macro Attacks for MacOS
Curtis Franklin Jr., Senior Editor at Dark Reading,  8/7/2020
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Current Issue
Special Report: Computing's New Normal, a Dark Reading Perspective
This special report examines how IT security organizations have adapted to the "new normal" of computing and what the long-term effects will be. Read it and get a unique set of perspectives on issues ranging from new threats & vulnerabilities as a result of remote working to how enterprise security strategy will be affected long term.
Flash Poll
The Changing Face of Threat Intelligence
The Changing Face of Threat Intelligence
This special report takes a look at how enterprises are using threat intelligence, as well as emerging best practices for integrating threat intel into security operations and incident response. Download it today!
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2020-17448
PUBLISHED: 2020-08-11
Telegram Desktop through 2.1.13 allows a spoofed file type to bypass the Dangerous File Type Execution protection mechanism, as demonstrated by use of the chat window with a filename that lacks an extension.
CVE-2020-17466
PUBLISHED: 2020-08-11
Turcom TRCwifiZone through 2020-08-10 allows authentication bypass by visiting manage/control.php and ignoring 302 Redirect responses.
CVE-2020-11552
PUBLISHED: 2020-08-11
An elevation of privilege vulnerability exists in ManageEngine ADSelfService Plus before build 6003 because it does not properly enforce user privileges associated with a Certificate dialog. This vulnerability could allow an unauthenticated attacker to escalate privileges on a Windows host. An attac...
CVE-2020-13124
PUBLISHED: 2020-08-11
SABnzbd 2.3.9 and 3.0.0Alpha2 has a command injection vulnerability in the web configuration interface that permits an authenticated user to execute arbitrary Python commands on the underlying operating system.
CVE-2020-15597
PUBLISHED: 2020-08-11
SOPlanning 1.46.01 allows persistent XSS via the Project Name, Statutes Comment, Places Comment, or Resources Comment field.