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
Don't Blame It On The Web Programming Platform
Oldest First  |  Newest First  |  Threaded View
anon6230542982
100%
0%
anon6230542982,
User Rank: Apprentice
4/15/2014 | 9:40:20 PM
It all starts with the C-Level
Anyone in this industry knows that the development language is not the issue, that it is the implementation is the issue, and it all starts with the C suite.

When it comes to secure software development most organizations do the minimal effort required to meet some industry compliance standard such as PCI. They don't do it because they are trying to develop better software.

The C suite cares about one thing and one thing only, short term ROI. They are worried about their quarterly numbers and lack a long term strategy. If they did then they would know secure software development is commitment the whole company has to embrace not just development teams. Its a cultural change in how they do business and write their software.

I have seen company after company think that by performing dynamic and/or static security scans of their software they have implemented a secure software development program that is going to fix their problems. Yet they don't staff the information security teams with people who can validate the findings. They don't educate their developers on how to write secure code. They have no corporate software development policies. Those that do, their CxO has never reviewed any of the development standards to see if they comply with the development policies. They don't audit the development processes to see if they comply with the standards. Developers are left up to their own means to do whatever they want and are never questioned because the C suite would rather claim ignorance, blame technology for their lack of leadership rather than be accountable for something and make a real difference.

If you don't have a C level person in your company who is actively involved with your software development program, setting policies and holding management responsible for cutting corners to get the next version of your product out the door just so they can make their quarterly numbers then you will continue to produce insecure software and it will never get better.
Kelly Jackson Higgins
50%
50%
Kelly Jackson Higgins,
User Rank: Strategist
4/16/2014 | 8:36:15 AM
Re: It all starts with the C-Level
What you said about the C-level suite not educating programmers on writing secure code is key, @anon6230542982. It's also a cultural issue among coders that somehow needs to be shaken up. As Chris Eng said, "People are not picking languages based on security implications. That's true and will continue to be true. It's where developers have skillsets and what can get the functionality done," Eng says. "Security is going to be fifth or sixth on the list."
GonzSTL
50%
50%
GonzSTL,
User Rank: Ninja
4/16/2014 | 10:06:34 AM
Re: It all starts with the C-Level
I would extend that notion to state that the C-suite must regard all of IT security as a vital part of their organization. If that is the case, then security becomes integrated in every aspect of the organization. Nothing breaks down barriers and objections faster than the knowledge that any initiative or idea is driven down from the top. The key is conveying the message to the C-suite that IT security is vital. There are many organizations that still treat IT security as an afterthought. Look at the breached companies and you will likely find that it is sadly, and frighteningly true.


Overcoming the Challenge of Shorter Certificate Lifespans
Mike Cooper, Founder & CEO of Revocent,  10/15/2020
7 Tips for Choosing Security Metrics That Matter
Ericka Chickowski, Contributing Writer,  10/19/2020
Register for Dark Reading Newsletters
White Papers
Video
Cartoon
Current Issue
Special Report: Computing's New Normal
This special report examines how IT security organizations have adapted to the "new normal" of computing and what the long-term effects will be. Read it and get a unique set of perspectives on issues ranging from new threats & vulnerabilities as a result of remote working to how enterprise security strategy will be affected long term.
Flash Poll
How IT Security Organizations are Attacking the Cybersecurity Problem
How IT Security Organizations are Attacking the Cybersecurity Problem
The COVID-19 pandemic turned the world -- and enterprise computing -- on end. Here's a look at how cybersecurity teams are retrenching their defense strategies, rebuilding their teams, and selecting new technologies to stop the oncoming rise of online attacks.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2020-27605
PUBLISHED: 2020-10-21
BigBlueButton through 2.2.8 uses Ghostscript for processing of uploaded EPS documents, and consequently may be subject to attacks related to a "schwache Sandbox."
CVE-2020-27606
PUBLISHED: 2020-10-21
BigBlueButton before 2.2.8 (or earlier) does not set the secure flag for the session cookie in an https session, which makes it easier for remote attackers to capture this cookie by intercepting its transmission within an http session.
CVE-2020-27607
PUBLISHED: 2020-10-21
In BigBlueButton before 2.2.8 (or earlier), the client-side Mute button only signifies that the server should stop accepting audio data from the client. It does not directly configure the client to stop sending audio data to the server, and thus a modified server could store the audio data and/or tr...
CVE-2020-27608
PUBLISHED: 2020-10-21
In BigBlueButton before 2.2.8 (or earlier), uploaded presentations are sent to clients without a Content-Type header, which allows XSS, as demonstrated by a .png file extension for an HTML document.
CVE-2020-27609
PUBLISHED: 2020-10-21
BigBlueButton through 2.2.8 records a video meeting despite the deactivation of video recording in the user interface. This may result in data storage beyond what is authorized for a specific meeting topic or participant.