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.

Endpoint

4/16/2015
05:00 PM
Connect Directly
Twitter
RSS
E-Mail

7 Deadly Sins That Get Users Hacked

How users and their endpoints are leveraged by the bad guys to eventually find their way to critical data
1 of 8

Image: (Pixabay)
Image: (Pixabay)

1 of 8
Comment  | 
Print  | 
Comments
Newest First  |  Oldest First  |  Threaded View
Page 1 / 2   >   >>
pawan14
50%
50%
pawan14,
User Rank: Apprentice
6/8/2015 | 4:21:42 AM
Re: Username/password is main problem
The long we continue to user Username/password combination the worse these situation will get. 
SashKhe
50%
50%
SashKhe,
User Rank: Apprentice
4/23/2015 | 7:27:30 AM
Re: Username/password is main problem
If people would start using key-patterns instead of letter patterns as password, that would help too.
Example, "draw" a circle on your keyboard, every second key pressed is with shift - you just made a strong password that's as easy to remember as looking at your keyboard.
SashKhe
50%
50%
SashKhe,
User Rank: Apprentice
4/23/2015 | 7:24:54 AM
Re: Username/password is main problem
Don't forget the salt.
MarkSitkowski
50%
50%
MarkSitkowski,
User Rank: Moderator
4/20/2015 | 11:40:45 PM
Re: Username/password is main problem
I agree - and so do thousands of others, probably.

Thing is, it's not even necessary to send anything meaningful. Imagine, that you have a secret word, which only you know. Now imagine you are presented with an alphabet, under which is a random array of 0's and 1's. You enter the pattern corresponding to your secret word, which won't be the same next time you login, as the 0's and 1's are random.

Oh, yes, just in case anyone is listening on the network, you don't send the solution, you just send its SHA256 hash.

Isn't that better than passwords?
cyclepro
50%
50%
cyclepro,
User Rank: Strategist
4/20/2015 | 9:07:04 AM
hacking
One other way that was not mentioned is through Instant Messaging.

 

I always just delete any messages where I do not recognize the person.

 
Dr.T
50%
50%
Dr.T,
User Rank: Ninja
4/18/2015 | 11:11:24 AM
Re: Fake phone calls
Nice tactic. You can also tell them what a good service they acre providing and you want to send kudos to their bosses if they can provide phone number for that. You never know, they may be providing real number of their boss.
Dr.T
50%
50%
Dr.T,
User Rank: Ninja
4/18/2015 | 11:07:50 AM
Re: Fake phone calls
I tend to do the same thing, not answering any unknown and waiting for voice message for the number I do not recognize. It is safer and saving time that way.
Dr.T
50%
50%
Dr.T,
User Rank: Ninja
4/18/2015 | 11:05:40 AM
Re: Fake phone calls
I like the idea, keeping them on the line until they hang up. Or giving the all the fake information so they can continue their effort.
Dr.T
50%
50%
Dr.T,
User Rank: Ninja
4/18/2015 | 11:02:35 AM
Username/password is main problem
The long we continue to user Username/password combination the worse these situation will get. Today, most common attacks are phishing and social engineering attacks on the end-users side, even these attacks are the results of the fact tags we use username/password combination. We need to find out a way to get rid of it or move the next level such as two or three factor authentication.
SmarterThanTheAverageBear
50%
50%
SmarterThanTheAverageBear,
User Rank: Apprentice
4/17/2015 | 7:55:31 PM
Re: Fake phone calls
Tell them your boss wants to hear more about their services and you are going to forward their call to him then forward them to the FBI/NSA or one of the otgher alphabet soups :)
Page 1 / 2   >   >>
News
FluBot Malware's Rapid Spread May Soon Hit US Phones
Kelly Sheridan, Staff Editor, Dark Reading,  4/28/2021
Slideshows
7 Modern-Day Cybersecurity Realities
Steve Zurier, Contributing Writer,  4/30/2021
Commentary
How to Secure Employees' Home Wi-Fi Networks
Bert Kashyap, CEO and Co-Founder at SecureW2,  4/28/2021
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Current Issue
2021 Top Enterprise IT Trends
We've identified the key trends that are poised to impact the IT landscape in 2021. Find out why they're important and how they will affect you today!
Flash Poll
How Enterprises are Developing Secure Applications
How Enterprises are Developing Secure Applications
Recent breaches of third-party apps are driving many organizations to think harder about the security of their off-the-shelf software as they continue to move left in secure software development practices.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2020-35519
PUBLISHED: 2021-05-06
An out-of-bounds (OOB) memory access flaw was found in x25_bind in net/x25/af_x25.c in the Linux kernel version v5.12-rc5. A bounds check failure allows a local attacker with a user account on the system to gain access to out-of-bounds memory, leading to a system crash or a leak of internal kernel i...
CVE-2021-20204
PUBLISHED: 2021-05-06
A heap memory corruption problem (use after free) can be triggered in libgetdata v0.10.0 when processing maliciously crafted dirfile databases. This degrades the confidentiality, integrity and availability of third-party software that uses libgetdata as a library. This vulnerability may lead to arbi...
CVE-2021-30473
PUBLISHED: 2021-05-06
aom_image.c in libaom in AOMedia before 2021-04-07 frees memory that is not located on the heap.
CVE-2021-32030
PUBLISHED: 2021-05-06
The administrator application on ASUS GT-AC2900 devices before 3.0.0.4.386.42643 allows authentication bypass when processing remote input from an unauthenticated user, leading to unauthorized access to the administrator interface. This relates to handle_request in router/httpd/httpd.c and auth_chec...
CVE-2021-22209
PUBLISHED: 2021-05-06
An issue has been discovered in GitLab CE/EE affecting all versions starting from 13.8. GitLab was not properly validating authorisation tokens which resulted in GraphQL mutation being executed.