| Description |
1 online resource (xx, 202 pages) : illustrations |
|
text file |
| Bibliography |
Includes bibliographical references and index. |
| Access |
Use copy Restrictions unspecified star MiAaHDL |
| Reproduction |
Electronic reproduction. [Place of publication not identified] : HathiTrust Digital Library, 2010. MiAaHDL |
| System Details |
Master and use copy. Digital master created according to Benchmark for Faithful Digital Reproductions of Monographs and Serials, Version 1. Digital Library Federation, December 2002. http://purl.oclc.org/DLF/benchrepro0212 MiAaHDL |
| Processing Action |
digitized 2010 HathiTrust Digital Library committed to preserve pda MiAaHDL |
| Summary |
Practically every day, we read about a new type of attack on computer systems and networks. Viruses, worms, denials of service, and password sniffers are attacking all types of systems -- from banks to major e-commerce sites to seemingly impregnable government and military computers --at an alarming rate. Despite their myriad manifestations and different targets, nearly all attacks have one fundamental cause: the code used to run far too many systems today is not secure. Flaws in its design, implementation, testing, and operations allow attackers all-too-easy access. Secure Coding, by Mark G. Graff and Ken vanWyk, looks at the problem of bad code in a new way. Packed with advice based on the authors' decades of experience in the computer security field, this concise and highly readable book explains why so much code today is filled with vulnerabilities, and tells readers what they must do to avoid writing code that can be exploited by attackers. Writing secure code isn't easy, and there are no quick fixes to bad code. To build code that repels attack, readers need to be vigilant through each stage of the entire code lifecycle: Architecture: during this stage, applying security principles such as "least privilege" will help limit even the impact of successful attempts to subvert software. Design: during this stage, designers must determine how programs will behave when confronted with fatally flawed input data. The book also offers advice about performing security retrofitting when you don't have the source code -- ways of protecting software from being exploited even if bugs can't be fixed. Implementation: during this stage, programmers must sanitize all program input (the character streams representing a programs' entire interface with its environment -- not just the command lines and environment variables that are the focus of most security analysis). Testing: during this stage, programs must be checked using both static code checkers and runtime testing methods -- for example, the fault injection systems now available to check for the presence of such flaws as buffer overflow. Operations: during this stage, patch updates must be installed in a timely fashion. In early 2003, sites that had diligently applied Microsoft SQL Server updates were spared the impact of the Slammer worm that did serious damage to thousands of systems. Beyond the technical, Secure Coding sheds new light on the economic, psychological, and sheer practical reasons why ... |
| Language |
English. |
| Subject |
Computer security.
|
|
Computer Security |
|
Engineering & Applied Sciences. |
|
Computer Science. |
|
Sécurité informatique. |
|
Computer security |
|
Programmeren (computers) |
|
Computerbeveiliging. |
| Indexed Term |
Core Programming |
| Added Author |
Van Wyk, Kenneth R.
|
| Other Form: |
Print version: Graff, Mark. Secure coding. Beijing ; Cambridge : O'Reilly, 2003 (DLC) 2004296887 (OCoLC)51964657 |
| ISBN |
0596522177 |
|
9780596522179 |
| Standard No. |
0596002424 |
|
More Resources