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.

Breaking The Security Fail Cycle
Newest First  |  Oldest First  |  Threaded View
aziza bond
aziza bond,
User Rank: Apprentice
5/4/2015 | 1:52:49 PM
Re: Simplify, rethink, simplify, rethink
You are totally true , there is a difference there
User Rank: Ninja
5/3/2015 | 7:25:07 AM
Re: Simplify, rethink, simplify, rethink
there is a fundamental difference between an old "dumb head" terminal like a VT-100 or a 3270 -- and a PC: the PC can have multiple applications open at the same time -- AND -- the PC User's credentials apply to all the open apps.   this is wrong from the get-go and promotes leakage of secure data between apps: while memory may be protected: file systems are not.   this may be rectified by using NAMED SPACES so that application programs do NOT have free run of all the data resources on the user workstation combined with free use of the user's credentials.
User Rank: Ninja
5/1/2015 | 12:45:02 AM
"Stop Doing"
A kernel of wisdom in this article notes "the question you should always ask is 'What is this going to help let me stop doing?'"  That is because every security solution "is an addition, but never a subtraction."

It is always amazing to me the amount of overhead on man hours applications specially designed to "help" the Enterprise actually ingest.  In particular, security software (of which I've had the pleasure of managing two, so I know from experience) seems to take the cake.  

Being able to assess an application, the time it will require to implement and whether its features once live will save or incur time cost is a great skill and an important part of procurement. 

Joe Stanganelli
Joe Stanganelli,
User Rank: Ninja
4/30/2015 | 11:32:29 PM
Simplify, simplify, simplify
Security simplification may indeed be the most important InfoSec step we can take -- across the board.  Most security mishaps, I daresay, happen because of laziness and/or an overpermissiveness so as to not compromise accessibility and functionality (security's mortal foes).  The less conflict security innovations can present between security and accessibility, the more security we can expect to see.

7 Old IT Things Every New InfoSec Pro Should Know
Joan Goodchild, Staff Editor,  4/20/2021
Cloud-Native Businesses Struggle With Security
Robert Lemos, Contributing Writer,  5/6/2021
Defending Against Web Scraping Attacks
Rob Simon, Principal Security Consultant at TrustedSec,  5/7/2021
Register for Dark Reading Newsletters
White Papers
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
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
PUBLISHED: 2021-05-11
** UNSUPPORTED WHEN ASSIGNED ** An issue was discovered on Zebra (formerly Motorola Solutions) Fixed RFID Reader FX9500 devices. An unauthenticated attacker can upload arbitrary files to the filesystem that can then be accessed through the web interface. This can lead to information disclosure and c...
PUBLISHED: 2021-05-11
The 802.11 standard that underpins Wi-Fi Protected Access (WPA, WPA2, and WPA3) and Wired Equivalent Privacy (WEP) doesn't require that received fragments be cleared from memory after (re)connecting to a network. Under the right circumstances, when another device sends fragmented frames encrypted us...
PUBLISHED: 2021-05-11
The 802.11 standard that underpins Wi-Fi Protected Access (WPA, WPA2, and WPA3) and Wired Equivalent Privacy (WEP) doesn't require that all fragments of a frame are encrypted under the same key. An adversary can abuse this to decrypt selected fragments when another device sends fragmented frames and...
PUBLISHED: 2021-05-11
The 802.11 standard that underpins Wi-Fi Protected Access (WPA, WPA2, and WPA3) and Wired Equivalent Privacy (WEP) doesn't require that the A-MSDU flag in the plaintext QoS header field is authenticated. Against devices that support receiving non-SSP A-MSDU frames (which is mandatory as part of 802....
PUBLISHED: 2021-05-11
An issue was discovered in the kernel in NetBSD 7.1. An Access Point (AP) forwards EAPOL frames to other clients even though the sender has not yet successfully authenticated to the AP. This might be abused in projected Wi-Fi networks to launch denial-of-service attacks against connected clients and...