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.

Risk

11/26/2018
09:00 AM

7 Real-Life Dangers That Threaten Cybersecurity

Cybersecurity means more than bits and bytes; threats are out there IRL, and IT pros need to be prepared.
2 of 8

Etiquette
We've all seen the case of the accidental doorman: One person opens a door, holds it for the next person - and then the next dozen or so who follow. What we rarely see is that human doorstop asking each person walking through for a badge to verify access privileges.
It takes very little for a threat actor to observe entry patterns around meals, shift changes, and breaks, and to join a large group of people as they habitually walk through a door without individually triggering the lock mechanism. There are technology fixes to the issue, but restricting flow through exterior doors carries its own safety issues, so behavioral and procedural remediation may be best.
A procedural fix is straightforward: Require each employee and guest to badge in and out so that every in and out can be tracked (and the two activities can be balanced for each person). The behavioral component may be a greater challenge, but employees can be educated to know that every person walking through a door must use a badge. And if they see someone trying to enter without properly doing so, then saying something is a must.
(Image: igorovsyannykov VIA Pixabay

Etiquette

We've all seen the case of the accidental doorman: One person opens a door, holds it for the next person and then the next dozen or so who follow. What we rarely see is that human doorstop asking each person walking through for a badge to verify access privileges.

It takes very little for a threat actor to observe entry patterns around meals, shift changes, and breaks, and to join a large group of people as they habitually walk through a door without individually triggering the lock mechanism. There are technology fixes to the issue, but restricting flow through exterior doors carries its own safety issues, so behavioral and procedural remediation may be best.

A procedural fix is straightforward: Require each employee and guest to badge in and out so that every in and out can be tracked (and the two activities can be balanced for each person). The behavioral component may be a greater challenge, but employees can be educated to know that every person walking through a door must use a badge. And if they see someone trying to enter without properly doing so, then saying something is a must.

(Image: igorovsyannykov VIA Pixabay

2 of 8
Comment  | 
Print  | 
Comments
Newest First  |  Oldest First  |  Threaded View
mattsweet
50%
50%
mattsweet,
User Rank: Apprentice
11/28/2018 | 12:15:00 PM
Re: USB tracking
We track files being written and read on USB drives through an agent connected to our SIEM server (we use Solarwinds LEM, but there are others as well.) We can also monitor machines that have restricted USB access.
REISEN1955
100%
0%
REISEN1955,
User Rank: Ninja
11/27/2018 | 9:53:55 AM
Re: USB tracking
Last year, my wife - daughter and 3 year old grand-daughter, Cariana, visited my office.  She had pizza in the cafeteria, met my colleagues and WHEN LEAVING ..... Cariana pulled all of our security badges, save mine, and said THESE MUST BE RETURNED.   She then walked them to the security desk to hand them in.  Staff there was delighted!!!   Lesson - A THREE YEAR OLD understood perimeter security BETTER than most employees do. 
lakers85
100%
0%
lakers85,
User Rank: Strategist
11/26/2018 | 1:14:46 PM
USB tracking
We have a domain policy that forces BitLocker to be used before saving data to any usb drive, otherwise its will be read only. I guess my questions is, how do you track or monitor usb activity on our 1500 end clients?

Thanks
Florida Town Pays $600K to Ransomware Operators
Curtis Franklin Jr., Senior Editor at Dark Reading,  6/20/2019
Pledges to Not Pay Ransomware Hit Reality
Robert Lemos, Contributing Writer,  6/21/2019
Register for Dark Reading Newsletters
White Papers
Video
Cartoon
Current Issue
Building and Managing an IT Security Operations Program
As cyber threats grow, many organizations are building security operations centers (SOCs) to improve their defenses. In this Tech Digest you will learn tips on how to get the most out of a SOC in your organization - and what to do if you can't afford to build one.
Flash Poll
The State of IT Operations and Cybersecurity Operations
The State of IT Operations and Cybersecurity Operations
Your enterprise's cyber risk may depend upon the relationship between the IT team and the security team. Heres some insight on what's working and what isn't in the data center.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2019-12280
PUBLISHED: 2019-06-25
PC-Doctor Toolbox before 7.3 has an Uncontrolled Search Path Element.
CVE-2019-3961
PUBLISHED: 2019-06-25
Nessus versions 8.4.0 and earlier were found to contain a reflected XSS vulnerability due to improper validation of user-supplied input. An unauthenticated, remote attacker could potentially exploit this vulnerability via a specially crafted request to execute arbitrary script code in a users browse...
CVE-2019-9836
PUBLISHED: 2019-06-25
Secure Encrypted Virtualization (SEV) on Advanced Micro Devices (AMD) Platform Security Processor (PSP; aka AMD Secure Processor or AMD-SP) 0.17 build 11 and earlier has an insecure cryptographic implementation.
CVE-2019-6328
PUBLISHED: 2019-06-25
HP Support Assistant 8.7.50 and earlier allows a user to gain system privilege and allows unauthorized modification of directories or files. Note: A different vulnerability than CVE-2019-6329.
CVE-2019-6329
PUBLISHED: 2019-06-25
HP Support Assistant 8.7.50 and earlier allows a user to gain system privilege and allows unauthorized modification of directories or files. Note: A different vulnerability than CVE-2019-6328.