Stories
Slash Boxes
Comments

SoylentNews is people

posted by Fnord666 on Wednesday May 22 2019, @10:44AM   Printer-friendly
from the software-security-is-not-an-aftermarket-accessory dept.

Submitted via IRC for AnonymousLuser

Lack of Secure Coding Called a National Security Threat

The lack of secure coding is a pervasive and serious threat to national security, according to a new paper from the Institute for Critical Infrastructure Technology, a cybersecurity think tank.

Rob Roy, an ICIT fellow who was co-author of the report, suggests in an interview with Information Security Media Group that an app standards body could play an important role in improving app security.

"If there were some objective standards put in place that all software would have to abide by, then we could start to make progress," Roy says. "It may just be that there needs to be an objective standard ... and a legislative mandate that requires a certain level of assurance to provide an assured product."

The "call to action" report, "Software Security Is National Security: Why the U.S. Must Replace Irresponsible Practices with a Culture of Institutionalized Security," discusses systemic issues with the software development landscape and what needs to be done to rectify the problem of negligent coding. But solving the problem won't be easy, given the problems of speed-to-market pressures and the sheer number of IoT devices being produced, the report notes.

[Ed Note - for those Soylentils that are software developers, does your company provide training/mentoring on how to develop secure software?]


Original Submission

 
This discussion has been archived. No new comments can be posted.
Display Options Threshold/Breakthrough Mark All as Read Mark All as Unread
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
  • (Score: 0) by Anonymous Coward on Wednesday May 22 2019, @02:33PM

    by Anonymous Coward on Wednesday May 22 2019, @02:33PM (#846217)

    Your average bonehead programmer can barely write a doubly-linked list properly

    #include <list>

    std::list<int> my_list; // this is a doubly-linked list

    Done.

    let alone an input routine that doesn't suffer from buffer overflows

    My routines don't suffer from buffer overflows, they enjoy them!

    or sql injection.

    No chance. I certainly won't go to the trouble of implementing SQL for my home-grown poorly documented and poorly debugged data storage routines.

    See? My programs are perfectly secure! ;-)