From a developer point of view… secure coding
For most of us here, we are looking to hack and crack systems. But spare a thought to those poor souls who have try to ensure their code stands up to the hack attack. And coming from a developer background, I should *really* know more about the security aspects of coding.
As you may know there are a number of different programming languages out there. The most commonly used programming languages for web applications are PHP and perl. Both have potential security pitfalls as they mix the ability to send and receive data through web applications with performing system level tasks.
There are number of gotchas that coders can look for. With PHP, OWASP have their own top 5. There’s even a hardening php project. But the best guide I’ve seen so far is i-love-jack-daniels along with these brief PHP thoughts. With Perl, there is CPAN’s perlsec pod and cgisecurity has a good reference as well. One of the things you can apply whilst you code is tainting as described by developer.com, which should flag up issues with any dodgy variables and program arguments.
There some programming languages which offer a framework that handles security more implicitly but it still takes a daft developer to insert some dangerous code. Anyhow, Microsoft have a security guide for asp.net applications, whilst Java have their own.
Generally speaking, a developer should do their own code audit and code review before it is released. Naturally, there’s always pressure from sales, marketing, MD’s, etc. but in an ideal world, things should be done PROPERLY.
Comments(3)