Ways to integrate security into the SDLC

Ways to integrate security into the SDLC

To successfully integrate security into the software development life cycle (SDLC) you need to make sure you factor time for security into the project plan. You should also consider security as added value in an application -- $1 spent up front saves $10 during development and $100 after release.

You also need to train developers, testers, architects, etc. -- anyone involved in the SDLC at different stages with software security principles because fixing the problem at right place by the right person saves a lot of time and money.

Developers must embrace secure application development. Quality is not just "Does it work" but also if the application is secure. Security vulnerabilities should be considered bugs tracked the same way as functional bugs.

Phase 1: Planning/requirements

  • Data sensitivity assessment
  • What data will you handle?
  • How is the data classified?
  • Preliminary risk assessment (RA)
  • Document assumptions and functional requirements so that the impact on security can be assessed
  • What happens if the data is disclosed, lost or changed?

Phase 2: Development/acquisition

  • Security controls in specifications:
  • Security features
  • Vulnerabilities
  • Malicious insiders
  • Contingency plan
  • Set coding standards to avoid known causes for buffer overflows
  • Using weak encryption schemes
  • Default or improper coding practices that may open doors to attackers Make available to

    Requires Free Membership to View

    Login

    When you register, you'll receive targeted emails designed to keep you informed of the most relevant information on Agile development, application security, testing & QA, software requirements, and more.

    Hannah Smalltree, Editorial Director

    By submitting your registration information to SearchSoftwareQuality.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 SearchSoftwareQuality.com is governed by our Terms of Use. You may contact us at webmaster@TechTarget.com.

  • programmers the vulnerabilities and potential exposures associated with programming languages and operating systems before getting into the implementation phase.
  • Set up regular peer review of the code.

Phase 3: Testing/implementation

  • Develop security test cases based on the requirements, and common vulnerabilities.
  • Identify all points in the source code where the program takes input from users and from another program or un-trusted source.
  • Administrative controls and safeguards
  • Remove installation programs
  • Machine content/intent
  • File and program settings and privileges
  • Contingency & disaster recovery plans

Phase 4: Operations/maintenance

  • Backup, restore, and restart instructions and procedures Cryptography keys
  • User administration and access privileges
  • Audit logs
  • Log file analysis
  • Verify documentation of access permissions
  • Review system interdependencies

Phase 5: Disposal

  • Storage of cryptographic keys
  • Legal requirements of records retention and destruction
  • Sanitize media

This was first published in May 2007

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