Feeds

Don't blame Willy the Mailboy for software security flaws

In defense of developers

Combat fraud and increase customer satisfaction

Uncertain certification

There is Sun/Oracle's Java Certified Programmer, for example. But certification is of questionable use to the employer, as certification involves rote learning without requiring a true understanding of the subject. For programmers, certification is also risky, quickly outdated. And it can be costly. Anyone out there still have a Certified Novell Engineer docket stapled to their yellowing CV?

Then there are more general-purpose, rigor-oriented qualifications for coders: the all-encompassing SWEBOK offers an IEEE-stamped certification. But - more's the pity - employers care little for such things. Invariably, they return to the time-honored qualification - the university or college degree. But even that tends to be a guideline: hands-on experience ends up being more important for many employers.

Nevertheless, security vendors such as Fortify would like to train - and certify - your entire IT workforce to be more aware of SQL and LDAP injection attacks, cross-site scripting, and so forth. Such vendors thrive on the corporate paranoia brought about by high-profile web front-end attacks and customer data-loss snafus. Their Fortify 360 product will act as a gateway to your source control system and monitor any code commits for security vulnerabilities.

While I have some reservations about Fortify 360's usefulness, it's a good example of how management should be taking the lead to impose processes on development, rather than blaming the programmers for a breakdown in process. It's good to see that QA - which this really is - has come back into fashion, despite being re-branded in the guise of security and the paranoia of an "unseen enemy that cannot be defined".

The vulnerabilities highlighted by Fortify's Audit Workbench are good and worthy flaws, and there's a good chance that your organization will be more secure if they embrace Fortify wholeheartedly. At the very least, your chief executive will sleep better. But there's a whole category of bugs and rules that look like they really are just there to tuck your CEO in at night. For example, the following code is incredibly insecure and may bring down all of civilization, apparently:

public void login(String username, String password) {
}

First, the password is called "password," so someone scanning the compiled code could find that quite easily. Second, it's stored in a String, and Java likes to intern all its Strings in a big reusable cache - so a wily hacker will head straight for the String table and scan it for passwords. So whatever you do, store your passwords in char arrays, and obfuscate your variable names to throw hackers off the scent - "absolutelyNotAPasswordNoWay," perhaps.

There we have an example that managers will love because it seems profound, and it allows them to impose a process while still blaming programmers. But let's face it, if the user has sufficient access to the JVM to trawl the String table, then he's already pwned your organization, and it has siphoned several billion of your corporate dollars into his suburban Jacuzzi extension project.

A far more insidious problem is with insider programmers who hack the system to launder funds - the recent TJX hack case being a case in point.

But in such cases, we still have the traditional "after the event" fallback known as "the law," and preventative, compulsory regulations such as PCI Compliance, which instructs management to put barriers in their organization to prevent the wrong people from seeing credit card numbers or personal account details.

In most cases, the onus is on management to enforce regulatory procedures, which means there's no need for programmers' heads to be on the block. But as long as there are security consultants and conferences to speak at, developers will continue to be blamed for breakdowns in process and QA. ®

Matt Stephens is co-author of Use Case Driven Object Modeling with UML: Theory and Practice, and the upcoming Design Driven Testing: Test Smarter, Not Harder.

Combat fraud and increase customer satisfaction

More from The Register

next story
Ubuntu 14.04 LTS: Great changes, but sssh don't mention the...
Why HELLO Amazon! You weren't here last time
This time it's 'Personal': new Office 365 sub covers just two devices
Redmond also brings Office into Google's back yard
Next Windows obsolescence panic is 450 days from … NOW!
The clock is ticking louder for Windows Server 2003 R2 users
Half of Twitter's 'active users' are SILENT STALKERS
Nearly 50% have NEVER tweeted a word
OpenBSD founder wants to bin buggy OpenSSL library, launches fork
One Heartbleed vuln was too many for Theo de Raadt
Got Windows 8.1 Update yet? Get ready for YET ANOTHER ONE – rumor
Leaker claims big release due this fall as Microsoft herds us into the CLOUD
Microsoft TIER SMEAR changes app prices whether devs ask or not
Some go up, some go down, Redmond goes silent
Batten down the hatches, Ubuntu 14.04 LTS due in TWO DAYS
Admins dab straining server brows in advance of Trusty Tahr's long-term support landing
Red Hat to ship RHEL 7 release candidate with a taste of container tech
Grab 'near-final' version of next Enterprise Linux next week
prev story

Whitepapers

Mobile application security study
Download this report to see the alarming realities regarding the sheer number of applications vulnerable to attack, as well as the most common and easily addressable vulnerability errors.
3 Big data security analytics techniques
Applying these Big Data security analytics techniques can help you make your business safer by detecting attacks early, before significant damage is done.
The benefits of software based PBX
Why you should break free from your proprietary PBX and how to leverage your existing server hardware.
Securing web applications made simple and scalable
In this whitepaper learn how automated security testing can provide a simple and scalable way to protect your web applications.
Combat fraud and increase customer satisfaction
Based on their experience using HP ArcSight Enterprise Security Manager for IT security operations, Finansbank moved to HP ArcSight ESM for fraud management.