Commentary

George Hulme
 

Why Software Stinks

Earlier this decade, many universities started adding cybersecurity as part of a well-rounded programming curriculum. Apparently, universities in the U.K. didn't get the memo.

Earlier this decade, many universities started adding cybersecurity as part of a well-rounded programming curriculum. Apparently, universities in the U.K. didn't get the memo.Guess what: you live in the United Kingdom, you're degreed, and you have no clue about secure development. That's just great, and probably why we continue to see the same application defects -- over and over again -- whether it was developed in C++ in 1993 or Java in 2008.

According to a survey just released by the Cyber Security Knowledge Transfer Network (KTN), established a couple of years ago by the U.K. government's Technology Strategy Board, when it comes to security training, U.K. students come up Null.


More Security Insights

White Papers

More >>

Reports

More >>

Webcasts

More >>

According to the study, available here, fewer than 20% of IT undergrads get more than five hours on how to incorporate security functionality over the entirety of their coursework.

Wow. No wonder problems with buffer overflows and poor authentication schemes keep popping up, almost daily.

Five hours isn't enough time to review the OWASP Top 10 types of Web application vulnerabilities, let alone get an overview of forensics, compensating controls, what a firewall does, explain why security should be incorporated in the design and functional requirements at the beginning of a project, or even explain how an organization should go about evaluating risk.

This is not to say that all IT students need to know IT security in-depth, but you'd think a class over a semester would be the least the universities could provide to teach IT security theory.

It looks like those who specialize in IT security in the U.K. will be busy for decades to come cleaning up the mess the universities keep churning out.


Related Reading




Currently we allow the following HTML tags in comments:

Single tags

These tags can be used alone and don't need an ending tag.

<br> Defines a single line break

<hr> Defines a horizontal line

Matching tags

These require an ending tag - e.g. <i>italic text</i>

<a> Defines an anchor

<b> Defines bold text

<big> Defines big text

<blockquote> Defines a long quotation

<caption> Defines a table caption

<cite> Defines a citation

<code> Defines computer code text

<em> Defines emphasized text

<fieldset> Defines a border around elements in a form

<h1> This is heading 1

<h2> This is heading 2

<h3> This is heading 3

<h4> This is heading 4

<h5> This is heading 5

<h6> This is heading 6

<i> Defines italic text

<p> Defines a paragraph

<pre> Defines preformatted text

<q> Defines a short quotation

<samp> Defines sample computer code text

<small> Defines small text

<span> Defines a section in a document

<s> Defines strikethrough text

<strike> Defines strikethrough text

<strong> Defines strong text

<sub> Defines subscripted text

<sup> Defines superscripted text

<u> Defines underlined text

InformationWeek encourages readers to engage in spirited, healthy debate, including taking us to task. However, InformationWeek moderates all comments posted to our site, and reserves the right to modify or remove any content that it determines to be derogatory, offensive, inflammatory, vulgar, irrelevant/off-topic, racist or obvious marketing/SPAM. InformationWeek further reserves the right to disable the profile of any commenter participating in said activities.

Disqus Tips To upload an avatar photo, first complete your Disqus profile. | View the list of supported HTML tags you can use to style comments. | Please read our commenting policy.
T-Shirt Giveaway T-Shirt Giveaway: Each week we're selecting one great comment from our readers. The author of the comment will receive an InformaitonWeek Community t-shirt. So get posting!
Subscribe to RSS

Resource Links