Security starts at the beginning

Security starts at the beginning

Adam Lipson, President and CEO of Network & Security Technologies

Security should be an elemental part of the application development process. Despite this basic best practice, flaws continue to be found in software, leaving enterprises exposed to worms, hackers

    Requires Free Membership to View

    Login

    SearchSecurity.com members gain immediate and unlimited access to breaking industry news, virus alerts, new hacker threats, highly focused security newsletters, and more -- all at no cost. Join me on SearchSecurity.com today!

    Michael S. Mimoso, Editorial Director

    By submitting your registration information to SearchSecurity.com you agree to receive email communications from TechTarget and TechTarget partners. We encourage you to read our Privacy Policy which contains important disclosures about how we collect and use your registration and other information. If you reside outside of the United States, by submitting this registration information you consent to having your personal data transferred to and processed in the United States. Your use of SearchSecurity.com is governed by our Terms of Use. You may contact us at webmaster@TechTarget.com.

and internal malcontents.

Why? Organizations fail to follow the best practices of software development -- spending $1 now to avoid $10 in repairs later. A few fundamental, common sense principles can greatly reduce the number of application vulnerabilities. These include:

  • Training & Awareness: Educating software designers, programmers and engineers in basic security principles will make them more aware of good security practices and help reduce the number of vulnerabilities in their code.

  • Planning: Include security at the beginning of the software development process. Make security an essential part of any application project. Remember, security is extremely difficult to bolt on the finished product.

  • Testing: Throughout the development lifecycle, test applications for security robustness and reliability. This is more than just vulnerability reviews, but ensuring that the code meets all security expectations. Also, develop a process for evaluating and testing commercial products and applications developed by third parties.

  • Assessing: When an application is being deployed, assess what level of security it requires and how to best configure it. Periodically, return to test the application to make sure no new security holes have been opened.

Correcting flaws identified during software security audits is expensive and time consuming. Worse, vast resources are spent on containing and recovering from exploits. Fortunately, providing development staff with the knowledge and tools to avoid many of these pitfalls is easy and inexpensive.

About the author
Adam Lipson is president and CEO of the infosecurity consultancy Network & Security Technologies.

For more information on this topic, visit these resources:

This was first published in September 2003

Disclaimer: Our Tips Exchange is a forum for you to share technical advice and expertise with your peers and to learn from other enterprise IT professionals. TechTarget provides the infrastructure to facilitate this sharing of information. However, we cannot guarantee the accuracy or validity of the material submitted. You agree that your use of the Ask The Expert services and your reliance on any questions, answers, information or other materials received through this Web site is at your own risk.

Back to top