Comments
Report: Only 2 in 3 Cyber Attacks Can Be Stopped with Current Defenses
Newest First  |  Oldest First  |  Threaded View
macker490
50%
50%
macker490,
User Rank: Ninja
3/1/2017 | 7:38:22 AM
1.2m phishings
according to an essay published this morning on Help Net Security:

With 1.2 million phishing attacks, 2016 was a success for cybercriminals

while converting to a more secure o/s may not be immediately practicle nonetheless people can move ahead with AUTHENTICATION for e/mail, current term

consider using Symantec/PGP Desktop with Outlook,   or -- use ENIGMAIL with Thunderbird

note that this can be phased in -- as users and correspondents can acquire training and software step-wise. 

while this will be seen as a burden cost the potential for blocking tragedy is significant.

all e/mail should be authenticated and encrypted.

Link to article
Jet Hedon
50%
50%
Jet Hedon,
User Rank: Apprentice
3/1/2017 | 7:11:06 AM
Re: "Hope is not a method"
Thanks for your comment, helped me out to learn more
macker490
50%
50%
macker490,
User Rank: Ninja
3/1/2017 | 6:36:10 AM
"Hope is not a method"
between the cubes today employees are admonished to read incomming e/mails carefully and not to click on "anything funny"

there was an article on this this morning   on ComputerWorld

see A better security strategy than 'know your enemy': Know your co-workers

THINK

(1) are employees going to be highly successful in examining input mails for signs of fraud?    are they even capable of doing that ?   or are there going to be a few click-firsts and then ooooops errors ?

(2) why are your computer systems vulnerable to "phishing" messages that are loaded with malware?

---

a. start using PGP with Outlook to validate e/mails.   Or Thunderbird/ENIGMAIL .   It isn't hard; you can do it.

b. use a secure o/s.   we may not have any that are 100% secure -- but some are MUCH better than others.

 


White House Cybersecurity Strategy at a Crossroads
Kelly Jackson Higgins, Executive Editor at Dark Reading,  7/17/2018
Lessons from My Strange Journey into InfoSec
Lysa Myers, Security Researcher, ESET,  7/12/2018
What's Cooking With Caleb Sima
Kelly Jackson Higgins, Executive Editor at Dark Reading,  7/12/2018
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Current Issue
Flash Poll
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2018-14339
PUBLISHED: 2018-07-19
In Wireshark 2.6.0 to 2.6.1, 2.4.0 to 2.4.7, and 2.2.0 to 2.2.15, the MMSE dissector could go into an infinite loop. This was addressed in epan/proto.c by adding offset and length validation.
CVE-2018-14340
PUBLISHED: 2018-07-19
In Wireshark 2.6.0 to 2.6.1, 2.4.0 to 2.4.7, and 2.2.0 to 2.2.15, dissectors that support zlib decompression could crash. This was addressed in epan/tvbuff_zlib.c by rejecting negative lengths to avoid a buffer over-read.
CVE-2018-14341
PUBLISHED: 2018-07-19
In Wireshark 2.6.0 to 2.6.1, 2.4.0 to 2.4.7, and 2.2.0 to 2.2.15, the DICOM dissector could go into a large or infinite loop. This was addressed in epan/dissectors/packet-dcm.c by preventing an offset overflow.
CVE-2018-14342
PUBLISHED: 2018-07-19
In Wireshark 2.6.0 to 2.6.1, 2.4.0 to 2.4.7, and 2.2.0 to 2.2.15, the BGP protocol dissector could go into a large loop. This was addressed in epan/dissectors/packet-bgp.c by validating Path Attribute lengths.
CVE-2018-14343
PUBLISHED: 2018-07-19
In Wireshark 2.6.0 to 2.6.1, 2.4.0 to 2.4.7, and 2.2.0 to 2.2.15, the ASN.1 BER dissector could crash. This was addressed in epan/dissectors/packet-ber.c by ensuring that length values do not exceed the maximum signed integer.