By submitting your personal information, you agree that TechTarget and its partners may contact you regarding relevant content, products and special offers.
In a forthcoming tip I'll cover what developers can and should be doing to get on board with security. In this tip I'll share what quality assurance (QA) analysts, engineers and testers can do to reduce business risks in this capacity.
As with developers, security managers and IT auditors, QA professionals have a very important role in the information security process. As an aspect of overall quality, it's part of your responsibility to ensure that code is secure before it goes into production. This fact alone validates that your role is arguably the most important among everyone involved. No pressure.
The biggest driver of secure software is that people pretty much expect it these days. Sure, the languages your applications are written in (e.g., Java and C#) can help take some of the security burden off your shoulders. But unfortunately that's a relatively small part of software security. There are still more advanced input validation concerns that have to be looked at. There are SSL and session management issues to check. Even bigger, you have to look at application logic, authentication and access control components, and more -- all things that need to be looked at using manual analysis and good tools.
Beyond these basics, how exactly are you expected to contribute to software security as a QA professional? Every situation is different and there's no best answer. That said, if you're going to make a difference beyond the basics, you're going to have to step up your game several notches. This means getting more involved in the design phase of new applications. It also means collaborating more openly with developers about the issues you're seeing on the back end that can and should be fixed up front.
One of the most profound changes you can make is to seek out and utilize a good commercial static analysis tool such as Klocwork, Checkmarx or QAInspect. These tools are essential for rooting out software vulnerabilities that would otherwise be next to impossible to find. If management is not supplying you with the budget you need, there are free tools such as FxCop and FindBugs that can certainly help fill the void, but they may not be as extensive as what you need. Based on my experience, you need to do everything you can to get management on your side and provide you with the budget for a commercial product, because in most cases you get what you pay for.
Another essential element of integrating security with QA is for you to learn how the bad guys work. Understanding their motivations (financial and self-esteem), insights (technical knowledge and understanding of breaking software) and techniques (manually exploiting application logic and using penetration testing tools to their advantage) will allow you to look at your software with a malicious mindset and fine-tune your misuse cases to uncover security issues you never knew existed.
To learn and keep up with the latest in this area I suggest reading 2600 and Hakin9 magazines as well as the numerous books on the subject such as Exploiting Software: How to Break Code and 19 Deadly Sins of Software Security. I also cover the malicious approach to testing your systems and applications in my book Hacking For Dummies. Books such as Hacking Exposed Web Applications and Hacking Exposed Web 2.0 are good resources as well.
I highly recommend you get to know -- possibly get involved with -- the Open Web Application Security Project (OWASP) and its Top 10 Project. OWASP is a great community of like-minded software and security professionals who work together to find better ways to produce higher-quality software. The recently released Top 25 Most Dangerous Programming Errors is a great resource for understanding what's being exploited -- and thus, what you should focus on. A final resource you can't afford to overlook are the Hacme and WebGoat tools. They're invaluable for learning the ins and outs of software hacks -- both the technical details and the manual analysis required -- that no QA professional should be without.
Arguably the biggest responsibility of all is for you to understand the security standards and regulations your organization is up against. If you learn the ins and outs of ISO/IEC 27002, the Payment Card Industry Data Security Standard (PCI DSS) and so on you'll definitely be at an advantage. I'm not saying you need to understand them at the level of an IT auditor or a security consultant. But familiarizing yourself with their software security components and staying current by reading about how compliance is affecting others will do wonders. The key is to expose yourself to information security concepts in every way possible.
So what's the next step? Again, generally secure code is expected as a baseline these days. You're going to have go beyond that in order to really contribute to security and start effecting change that will help minimize business risks. This is going to take a good bit of initiative and leadership on your part. Rather than waiting for someone to tell you the security requirements, why not start blazing your own trail? It will require you to learn more about security concepts as I mentioned above and will also force you to get more involved with security inside your organization. From attending security committee meetings to assisting with ongoing security assessments, there's a lot you can do.
Sure, secure software is only a component of the overall information security equation, but it's one of the most important ones, and it will make or break your business. You, as the QA professional, play a critical role in minimizing business risk. Learning the ins and outs of software security will put you in a great position to contribute in a positive and visible way. Focus on establishing yourself as an enabler of information security. Becoming a person of value will not only help your organization, it will also help make your job more fulfilling and even help your career moving forward.
About the author: Kevin Beaver, CISSP, is an independent information security consultant, keynote speaker and expert witness with Atlanta-based Principle Logic LLC, where he specializes in performing independent security assessments and information security career counseling for up-and-coming IT pros. Kevin has authored or co-authored seven books on information security, including Hacking For Dummies and Hacking Wireless Networks For Dummies (Wiley). He's also the creator of the Security On Wheels information security audio books and blog, providing security learning for IT professionals on the go. Kevin can be reached at kbeaver [at] principlelogic.com.
How to select team collaboration tools for quality assurance