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
AppSec Is Dead, but Software Security Is Alive & Well
Newest First  |  Oldest First  |  Threaded View
John160
50%
50%
John160,
User Rank: Apprentice
1/22/2019 | 6:08:19 AM
Ignorance
The author clearly has no idea about what he is writing. Application security is much more than the author described and it is just a silly thing to discard what has already been done in the area (and it successfully done). there is nothing worth reading and taking into consideration in this article. Hopefully experts like Matt Rose won't be affecting the state of application security
scarabeetle
50%
50%
scarabeetle,
User Rank: Author
11/8/2018 | 8:52:36 AM
S-SDLC is key
Software security IS the right path.  I agree with the previous commenter that having the static and dynamic testing built-in to the build process that keeps security testing proactive, rather than reactive (after deployment) is key.  
username007
100%
0%
username007,
User Rank: Strategist
10/29/2018 | 12:33:37 PM
Wait what?
I stopped doing Application Security about a year ago mostly due to the burn out of working with new kids being taught in school the insecure way to code all the way to the old school dev that has been coding since the Com64 thinking "if it ain't broke don't fix it"; however the point here is I have been doing this for some time too.

Now, Matt Rose seems to think that for whatever reason the industry should shake what it has already worked so hard on and just throw it away. Software Security is not the same thing as Application Security. They can NOT be intermingled and they are in so way similiar. Building an application, something an end-user actually uses, should not be treated the same way the back end database gets built. One gets handled with configuration management, I.E. company policies on how something should be configured and can be audited easily, while the other is handled with vulnerability management, I.E. with reactive response such as code review, penetration testing, or vulnerability scanning.

DevOps and Agile do not have the time that security needs to do all of our checking. So with that, Security needs to be baked into the SDLC process, not bolted on like some crap Captcha. Individuals that show the aptitude, need to be dubed security champions within their team, to help make sure best coding practices are followed.

We, as senior staff, need to stop trying to change things just for the sake of change or because we learned new words and think they need to go in a different order. This post wreaks of someone living in the Waterfall days, knowing just enough about security to cause more harm than good.

AppSec is not dead, but arrogance over how it should be handled needs to be.


Data Leak Week: Billions of Sensitive Files Exposed Online
Kelly Jackson Higgins, Executive Editor at Dark Reading,  12/10/2019
Intel Issues Fix for 'Plundervolt' SGX Flaw
Kelly Jackson Higgins, Executive Editor at Dark Reading,  12/11/2019
Register for Dark Reading Newsletters
White Papers
Video
Cartoon
Current Issue
The Year in Security: 2019
This Tech Digest provides a wrap up and overview of the year's top cybersecurity news stories. It was a year of new twists on old threats, with fears of another WannaCry-type worm and of a possible botnet army of Wi-Fi routers. But 2019 also underscored the risk of firmware and trusted security tools harboring dangerous holes that cybercriminals and nation-state hackers could readily abuse. Read more.
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-5252
PUBLISHED: 2019-12-14
There is an improper authentication vulnerability in Huawei smartphones (Y9, Honor 8X, Honor 9 Lite, Honor 9i, Y6 Pro). The applock does not perform a sufficient authentication in a rare condition. Successful exploit could allow the attacker to use the application locked by applock in an instant.
CVE-2019-5235
PUBLISHED: 2019-12-14
Some Huawei smart phones have a null pointer dereference vulnerability. An attacker crafts specific packets and sends to the affected product to exploit this vulnerability. Successful exploitation may cause the affected phone to be abnormal.
CVE-2019-5264
PUBLISHED: 2019-12-13
There is an information disclosure vulnerability in certain Huawei smartphones (Mate 10;Mate 10 Pro;Honor V10;Changxiang 7S;P-smart;Changxiang 8 Plus;Y9 2018;Honor 9 Lite;Honor 9i;Mate 9). The software does not properly handle certain information of applications locked by applock in a rare condition...
CVE-2019-5277
PUBLISHED: 2019-12-13
Huawei CloudUSM-EUA V600R006C10;V600R019C00 have an information leak vulnerability. Due to improper configuration, the attacker may cause information leak by successful exploitation.
CVE-2019-5254
PUBLISHED: 2019-12-13
Certain Huawei products (AP2000;IPS Module;NGFW Module;NIP6300;NIP6600;NIP6800;S5700;SVN5600;SVN5800;SVN5800-C;SeMG9811;Secospace AntiDDoS8000;Secospace USG6300;Secospace USG6500;Secospace USG6600;USG6000V;eSpace U1981) have an out-of-bounds read vulnerability. An attacker who logs in to the board m...