000 -LEADER |
fixed length control field |
01783nam a22003017a 4500 |
003 - CONTROL NUMBER IDENTIFIER |
control field |
APU |
005 - DATE AND TIME OF LATEST TRANSACTION |
control field |
20220823162635.0 |
008 - FIXED-LENGTH DATA ELEMENTS--GENERAL INFORMATION |
fixed length control field |
220215t20182018scua 000 0 eng d |
020 ## - INTERNATIONAL STANDARD BOOK NUMBER |
International Standard Book Number |
9781980901754 |
020 ## - INTERNATIONAL STANDARD BOOK NUMBER |
International Standard Book Number |
1980901759 |
040 ## - CATALOGING SOURCE |
Original cataloging agency |
YDX |
Language of cataloging |
eng |
Transcribing agency |
APU |
Modifying agency |
SF |
050 #4 - LIBRARY OF CONGRESS CALL NUMBER |
Classification number |
QA76.9.A25 |
Item number |
K56 2018 |
100 1# - MAIN ENTRY--PERSONAL NAME |
Personal name |
Kim, Peter, |
9 (RLIN) |
47845 |
245 14 - TITLE STATEMENT |
Title |
The hacker playbook 3 : |
Remainder of title |
practical guide to penetration testing / |
Statement of responsibility, etc |
Peter Kim |
250 ## - EDITION STATEMENT |
Edition statement |
Red team edition |
260 ## - PUBLICATION, DISTRIBUTION, ETC. (IMPRINT) |
Place of publication, distribution, etc |
[North Charleston, South Carolina] : |
Name of publisher, distributor, etc |
Secure Planet LLC, |
Date of publication, distribution, etc |
c2018. |
300 ## - PHYSICAL DESCRIPTION |
Extent |
ix, 271 pages : |
Other physical details |
illustrations ; |
Dimensions |
26 cm |
505 0# - FORMATTED CONTENTS NOTE |
Formatted contents note |
Introduction -- Pregame : the setup -- Before the Snap : red team recon -- The throw : web application exploitation -- The drive : compromising the network -- The screen : social engineering -- The onside kick : physical attacks -- The quarterback sneak : evading AV and network detection -- Special teams : cracking, exploits, and tricks -- Two-minute drill : from zero to hero |
520 ## - SUMMARY, ETC. |
Summary, etc |
The main purpose of this book is to answer questions as to why things are still broken. For instance, with all the different security products, secure code reviews, defense in depth, and penetration testing requirements, how are we still seeing massive security breaches happening to major corporations and governments? The real question we need to ask ourselves is, are all the safeguards we are putting in place working? |
650 #0 - SUBJECT ADDED ENTRY--TOPICAL TERM |
Topical term or geographic name as entry element |
Penetration testing (Computer security) |
Form subdivision |
Handbooks, manuals, etc |
9 (RLIN) |
47846 |
650 #0 - SUBJECT ADDED ENTRY--TOPICAL TERM |
Topical term or geographic name as entry element |
Computer networks |
General subdivision |
Security measures |
650 #0 - SUBJECT ADDED ENTRY--TOPICAL TERM |
Topical term or geographic name as entry element |
Computer software |
General subdivision |
Testing |
9 (RLIN) |
1819 |
650 #0 - SUBJECT ADDED ENTRY--TOPICAL TERM |
Topical term or geographic name as entry element |
Computer crimes |
General subdivision |
Prevention |
650 #0 - SUBJECT ADDED ENTRY--TOPICAL TERM |
Topical term or geographic name as entry element |
Hackers |
650 #0 - SUBJECT ADDED ENTRY--TOPICAL TERM |
Topical term or geographic name as entry element |
Computer programming |
655 #7 - INDEX TERM--GENRE/FORM |
Genre/form data or focus term |
Handbooks and manuals. |
Source of term |
fast |
942 ## - ADDED ENTRY ELEMENTS (KOHA) |
Source of classification or shelving scheme |
|
Koha item type |
Book |