Cargando…

Fixing an insecure software life cycle : practical techniques for building security into existing software development programs /

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 g...

Descripción completa

Detalles Bibliográficos
Clasificación:Libro Electrónico
Autor principal: Wright, April C. (Autor)
Formato: Electrónico eBook
Idioma:Inglés
Publicado: Sebastopol, CA : O'Reilly Media, [2018]
Edición:First edition.
Temas:
Acceso en línea:Texto completo (Requiere registro previo con correo institucional)

MARC

LEADER 00000cam a2200000 i 4500
001 OR_on1037354593
003 OCoLC
005 20231017213018.0
006 m o d
007 cr unu||||||||
008 180525s2018 caua ob 000 0 eng d
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  |d OCLCO 
020 |z 9781492028215 
035 |a (OCoLC)1037354593 
037 |a CL0500000967  |b Safari Books Online 
050 4 |a QA76.76.D47 
049 |a UAMI 
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 
588 0 |a Online resource; title from title page (Safari, viewed May 23, 2018). 
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. 
590 |a O'Reilly  |b O'Reilly Online Learning: Academic/Public Library Edition 
650 0 |a Computer software  |x Development. 
650 0 |a Computer networks  |x Security measures. 
650 6 |a Réseaux d'ordinateurs  |x Sécurité  |x Mesures. 
650 7 |a Computer networks  |x Security measures  |2 fast 
650 7 |a Computer software  |x Development  |2 fast 
856 4 0 |u https://learning.oreilly.com/library/view/~/9781492028222/?ar  |z Texto completo (Requiere registro previo con correo institucional) 
994 |a 92  |b IZTAP