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
A 2014 Lookback: Predictions vs. Reality
Newest First  |  Oldest First  |  Threaded View
Marilyn Cohodas
50%
50%
Marilyn Cohodas,
User Rank: Strategist
1/6/2015 | 9:21:44 AM
Re: 2015 Predictions
Adding the live link to the Hitoshi Kokumai page on LI. Some interesting content there. Thanks for sharing @HAnatomi!

https://www.linkedin.com/today/author/141508358?trk=pulse-det-athr_posts
HAnatomi
50%
50%
HAnatomi,
User Rank: Apprentice
1/1/2015 | 7:49:44 PM
Re: 2015 Predictions
I am supporting the thought and theory of Expanded Password System advocated by Hitoshi Kokumai whose writings are posted on LinkedIn at

https://www.linkedin.com/today/author/141508358?trk=pulse-det-athr_posts

 
RyanSepe
50%
50%
RyanSepe,
User Rank: Ninja
12/31/2014 | 11:34:21 AM
Re: 2015 Predictions
Very interesting post. I agree with many of the statements you made.

People have difficulty remembering intricate strings, hence principles behind DNS. But I think with items such as tokens and devices, Security professionals have the right to hold people accountable to not lose the token. In an environment that requires this type of authentication being responsible is not a lofty request. That being said I understand mistakes happen.

Biometric is ideal but a very expensive means of authentication. This may not be feasible for implementation. What is your advice for a happy medium?
HAnatomi
50%
50%
HAnatomi,
User Rank: Apprentice
12/31/2014 | 2:40:56 AM
Re: 2015 Predictions
The two-factor authentication, though not a silver bullet, could be reliable when it comes with a reliable password. 2 is larger than 1 on paper, but two weak boys in the real world may well be far weaker than a toughened guy.  Physical tokens and phones are easily lost, stolen and abused. Then the password would be the last resort.  It should be strongly emphasized that a truly reliable 2-factor solution needed for important accounts requires the use of the most reliable password.  

Using a strong password does help a lot even against the attack of cracking the leaked/stolen hashed passwords back to the original passwords.  The problem is that few of us can firmly remember many such strong passwords.  It is like we cannot run as fast and far as horses however strongly urged we may be.  We are not built like horses.

 At the root of the password headache is the cognitive phenomena called "interference of memory", by which we cannot firmly remember more than 5 text passwords on average.  What worries us is not the password, but the textual password.  The textual memory is only a small part of what we remember.  We could think of making use of the larger part of our memory that is less subject to interference of memory.  More attention could be paid to the efforts of expanding the password system to include images, particularly KNOWN images, as well as conventional texts.

 By the way, some people shout that the password is dead or should be killed dead.  The password could be killed only when there is an alternative to the password.  Something belonging to the password(PIN, passphrase, etc)and something dependent on the password (ID federations, 2/multi-factor, etc) cannot be the alternative to the password.  Neither can be something that has to be used together with the password (biometrics, auto-login, etc). What could be killed is the text password, not the password.  

 
RyanSepe
50%
50%
RyanSepe,
User Rank: Ninja
12/29/2014 | 1:37:43 PM
2015 Predictions
Have you compiled predictions for the year 2015? If so, do you plan on creating another article to denote them?

I would be interested to see how your predictions align with the roadmapped enterprise initiatives.


Why Cyber-Risk Is a C-Suite Issue
Marc Wilczek, Digital Strategist & CIO Advisor,  11/12/2019
DevSecOps: The Answer to the Cloud Security Skills Gap
Lamont Orange, Chief Information Security Officer at Netskope,  11/15/2019
Unreasonable Security Best Practices vs. Good Risk Management
Jack Freund, Director, Risk Science at RiskLens,  11/13/2019
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Current Issue
Navigating the Deluge of Security Data
In this Tech Digest, Dark Reading shares the experiences of some top security practitioners as they navigate volumes of security data. We examine some examples of how enterprises can cull this data to find the clues they need.
Flash Poll
Rethinking Enterprise Data Defense
Rethinking Enterprise Data Defense
Frustrated with recurring intrusions and breaches, cybersecurity professionals are questioning some of the industrys conventional wisdom. Heres a look at what theyre thinking about.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2019-19040
PUBLISHED: 2019-11-17
KairosDB through 1.2.2 has XSS in view.html because of showErrorMessage in js/graph.js, as demonstrated by view.html?q= with a '"sampling":{"value":"<script>' substring.
CVE-2019-19041
PUBLISHED: 2019-11-17
An issue was discovered in Xorux Lpar2RRD 6.11 and Stor2RRD 2.61, as distributed in Xorux 2.41. They do not correctly verify the integrity of an upgrade package before processing it. As a result, official upgrade packages can be modified to inject an arbitrary Bash script that will be executed by th...
CVE-2019-19012
PUBLISHED: 2019-11-17
An integer overflow in the search_in_range function in regexec.c in Oniguruma 6.x before 6.9.4_rc2 leads to an out-of-bounds read, in which the offset of this read is under the control of an attacker. (This only affects the 32-bit compiled version). Remote attackers can cause a denial-of-service or ...
CVE-2019-19022
PUBLISHED: 2019-11-17
iTerm2 through 3.3.6 has potentially insufficient documentation about the presence of search history in com.googlecode.iterm2.plist, which might allow remote attackers to obtain sensitive information, as demonstrated by searching for the NoSyncSearchHistory string in .plist files within public Git r...
CVE-2019-19035
PUBLISHED: 2019-11-17
jhead 3.03 is affected by: heap-based buffer over-read. The impact is: Denial of service. The component is: ReadJpegSections and process_SOFn in jpgfile.c. The attack vector is: Open a specially crafted JPEG file.