Urgent.News

What's breaking now, across thousands of outlets.

Editions

Tech

Name It, Frame It, Check It: A 3-Step Fix for Phishing

Why do employees still fall for phishing after security training? A cognitive security experiment explores how objective thinking may reduce risk.

Name It, Frame It, Check It: A 3-Step Fix for Phishing

A cognitive security researcher conducted an experiment to discover if focusing on neutral facts rather than emotions could help reduce phishing attempts. The researcher surveyed corporate workers and found that most executives considered superficial compliance as the most challenging problem. However, employees who are most familiar with security rules are sometimes still duped.

The researcher then trained 24 participants from Reddit, half on common social engineering tactics and half on those tactics plus a method for analyzing emails objectively. The objective method involved finding the command, summarizing the email in third-person language, and checking with IT/Security if uncertain. After 14 days, the researcher sent all participants a surprise phishing test email.

Six people from the control group fell for the test, while only one person from the experimental group responded. The researcher concluded that by focusing on looking for the command, summarizing the email message in third-person language, and checking with IT/Security if unsure, employees were more likely to make the right decision and avoid phishing attempts.

Written by urgent.news from HackerNoon's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.

Read the original at hackernoon.com →

More in Tech

Directus Basics Part 3 — User Roles & Permissions

This is part three of our Directus Basics series. In part one we set up our instance, and in part two we covered relationships between collections.

  • Directus access control determines user data access with Permissions, Policies, and Roles
  • Administrator role grants full access, Public role has Read access to visible data
  • Assign DataEntry role with custom policy to restrict data-entry user access

The Hard Part of Birth Chart Calculations Isn't the Zodiac. It's Time.

The most annoying bugs I’ve dealt with while building a birth-chart engine were not about zodiac signs. They were about time.

  • Calculating birth charts faces time complexity beyond zodiac signs
  • Daylight-saving transitions create ambiguity in local datetime input
  • Unknown birth times require representing incomplete data with null values

More from Friday 21 August →