Fixing an insecure software life cycle : practical techniques for building security into existing software development programs
Description
More Details
Notes
Also in this Series
Citations
Wright, A. C. (2018). Fixing an insecure software life cycle: practical techniques for building security into existing software development programs (First edition.). O'Reilly Media.
Chicago / Turabian - Author Date Citation, 17th Edition (style guide)Wright, April C.. 2018. Fixing an Insecure Software Life Cycle: Practical Techniques for Building Security Into Existing Software Development Programs. Sebastopol, CA: O'Reilly Media.
Chicago / Turabian - Humanities (Notes and Bibliography) Citation, 17th Edition (style guide)Wright, April C.. Fixing an Insecure Software Life Cycle: Practical Techniques for Building Security Into Existing Software Development Programs Sebastopol, CA: O'Reilly Media, 2018.
Harvard Citation (style guide)Wright, A. C. (2018). Fixing an insecure software life cycle: practical techniques for building security into existing software development programs. First edn. Sebastopol, CA: O'Reilly Media.
MLA Citation, 9th Edition (style guide)Wright, April C.. Fixing an Insecure Software Life Cycle: Practical Techniques for Building Security Into Existing Software Development Programs First edition., O'Reilly Media, 2018.
Staff View
Grouping Information
Grouped Work ID | 3fcf7e30-416a-9c84-4d95-74fe0a1732b5-eng |
---|---|
Full title | fixing an insecure software life cycle practical techniques for building security into existing software development programs |
Author | wright april c |
Grouping Category | book |
Last Update | 2025-01-24 12:33:29PM |
Last Indexed | 2025-01-25 03:08:52AM |
Book Cover Information
Image Source | default |
---|---|
First Loaded | Dec 22, 2023 |
Last Used | Jan 16, 2025 |
Marc Record
First Detected | Mar 21, 2023 11:45:59 AM |
---|---|
Last File Modification Time | Mar 21, 2023 11:45:59 AM |
Suppressed | Record had no items |
MARC Record
LEADER | 03054cam a2200385 i 4500 | ||
---|---|---|---|
001 | on1037354593 | ||
003 | OCoLC | ||
005 | 20230321114512.0 | ||
006 | m o d | ||
007 | cr unu|||||||| | ||
008 | 180525s2018 caua ob 000 0 eng d | ||
035 | |a (OCoLC)1037354593 | ||
037 | |a CL0500000967|b Safari Books Online | ||
040 | |a UMI|b eng|e rda|e pn|c UMI|d OCLCF|d TOH|d UAB|d MERER|d OCLCQ|d CZL|d OCLCQ|d OCLCO|d OCLCQ | ||
049 | |a MAIN | ||
050 | 4 | |a QA76.76.D47 | |
100 | 1 | |a Wright, April C.,|e author. | |
245 | 1 | 0 | |a Fixing an insecure software life cycle :|b practical techniques for building security into existing software development programs /|c April C. Wright. |
246 | 3 | 0 | |a Practical techniques for building security into existing software development programs |
250 | |a First edition. | ||
264 | 1 | |a Sebastopol, CA :|b O'Reilly Media,|c [2018] | |
264 | 4 | |c ©2018 | |
300 | |a 1 online resource (1 volume) :|b illustrations | ||
336 | |a text|b txt|2 rdacontent | ||
337 | |a computer|b c|2 rdamedia | ||
338 | |a online resource|b cr|2 rdacarrier | ||
504 | |a Includes bibliographical references. | ||
520 | |a In the race to remain competitive, development teams in many companies are under tremendous pressure to create software on tight deadlines. And in most cases, that means dealing with security bugs only after software is released. But offensive testing and incident response are poor substitutes for good code, strong architecture, and threat-based design. In this ebook, April C. Wright--security risk and compliance program advisor for a Fortune 15 company--teaches InfoSec professionals how to promote security as an integral part of an organization's software development life cycle (SDLC). You'll learn how to analyze existing development processes, gain insight into how developers and other stakeholders view software development, receive practical advice for including secure practices throughout the lifecycle, and learn how to track performance and success of your program. Get guidelines for evaluating your SDLC and rebuilding your development program Understand how developers, project managers, business execs, customers, and other key stakeholders each approach software development Gain active stakeholder participation and management support for SDLC security improvements Work directly with stakeholders to explain secure development, and push for change through policy and compliance Increase software security awareness by integrating development teams with security teams Get started through sample checklists and planning documents. | ||
588 | 0 | |a Online resource; title from title page (Safari, viewed May 23, 2018). | |
590 | |a O'Reilly|b O'Reilly Online Learning: Academic/Public Library Edition | ||
650 | 0 | |a Computer software|x Development.|9 34211 | |
650 | 0 | |a Computer networks|x Security measures.|9 68848 | |
856 | 4 | 0 | |u https://library.access.arlingtonva.us/login?url=https://learning.oreilly.com/library/view/~/9781492028222/?ar|x O'Reilly|z eBook |
994 | |a 92|b VIA | ||
999 | |c 286386|d 286386 |