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
Phishing Your Employees for Schooling & Security
Newest First  |  Oldest First  |  Threaded View
<<   <   Page 2 / 2
CNACHREINER981
CNACHREINER981,
User Rank: Author
3/23/2017 | 11:32:44 PM
Re: Positive feedback also
That is a very good and interesting point. I agree that it would be very cool for you employees to have "immediate" feedback when the delete a suspect email. Technical, I think it's harder to do. It's much easier to track when they click and interact on things in the email, since you can use HTML script without needing to interact with the email server or client. However, for the administrator to know when the user didn't interact with the email, but simply dragged it to the trash or deleted it would take more interaction with the email server and client itself (at least as far as I know). So I think the only reason you don't see this much is it would be a hard technical thing to do.

That said, the admin can easily keep track of all the folks that didn't click, and later send a follow up saying congratulations. It would be as immediate feedback as the click, but at least it would be the positive feedback, that I agree would be good to validate the behavior for your users. 

 

Great comment. 
ALINDERHOLM670
ALINDERHOLM670,
User Rank: Apprentice
3/23/2017 | 11:23:30 PM
Positive feedback also
You only mentioned situations where people did the wrong thing by clicking the link. Something good needs to happen if the employee deletes the email, moves it to the company spam folder, forwards it to IT or does whatever the company policy is.
<<   <   Page 2 / 2


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
White Papers
Video
Cartoon
Current Issue
Incorporating a Prevention Mindset into Threat Detection and Response
Threat detection and response systems, by definition, are reactive because they have to wait for damage to be done before finding the attack. With a prevention-mindset, security teams can proactively anticipate the attacker's next move, rather than reacting to specific threats or trying to detect the latest techniques in real-time. The report covers areas enterprises should focus on: What positive response looks like. Improving security hygiene. Combining preventive actions with red team efforts.
Flash Poll
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2022-22497
PUBLISHED: 2022-05-24
IBM Aspera Faspex 4.4.1 and 5.0.0 could allow unauthorized access due to an incorrectly computed security token. IBM X-Force ID: 226951.
CVE-2022-29334
PUBLISHED: 2022-05-24
An issue in H v1.0 allows attackers to bypass authentication via a session replay attack.
CVE-2022-29337
PUBLISHED: 2022-05-24
C-DATA FD702XW-X-R430 v2.1.13_X001 was discovered to contain a command injection vulnerability via the va_cmd parameter in formlanipv6. This vulnerability allows attackers to execute arbitrary commands via a crafted HTTP request.
CVE-2022-29333
PUBLISHED: 2022-05-24
A vulnerability in CyberLink Power Director v14 allows attackers to escalate privileges via a crafted .exe file.
CVE-2021-3597
PUBLISHED: 2022-05-24
A flaw was found in undertow. The HTTP2SourceChannel fails to write the final frame under some circumstances, resulting in a denial of service. The highest threat from this vulnerability is availability. This flaw affects Undertow versions prior to 2.0.35.SP1, prior to 2.2.6.SP1, prior to 2.2.7.SP1,...