<?xml version="1.0" encoding="UTF-8"?>
<record
    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
    xsi:schemaLocation="http://www.loc.gov/MARC21/slim http://www.loc.gov/standards/marcxml/schema/MARC21slim.xsd"
    xmlns="http://www.loc.gov/MARC21/slim">

  <leader>01644nam a2200265 a 4500</leader>
  <datafield tag="999" ind1=" " ind2=" ">
    <subfield code="c">14534</subfield>
    <subfield code="d">14534</subfield>
  </datafield>
  <datafield tag="020" ind1=" " ind2=" ">
    <subfield code="a">7111459156 (paperback)</subfield>
  </datafield>
  <datafield tag="020" ind1=" " ind2=" ">
    <subfield code="a">9787111459156 (paperback)</subfield>
  </datafield>
  <datafield tag="100" ind1="1" ind2=" ">
    <subfield code="a">Mcgraw, [ MEI ] John Viega Gary.</subfield>
  </datafield>
  <datafield tag="245" ind1="1" ind2="0">
    <subfield code="a">Building Secure Software /</subfield>
  </datafield>
  <datafield tag="260" ind1=" " ind2=" ">
    <subfield code="a">[S.l.] :</subfield>
    <subfield code="b">Machinery Industry Press,</subfield>
    <subfield code="c">2013.</subfield>
  </datafield>
  <datafield tag="300" ind1=" " ind2=" ">
    <subfield code="a">493 p</subfield>
  </datafield>
  <datafield tag="520" ind1=" " ind2=" ">
    <subfield code="a">Paperback. Pub Date :2014-03-01 Pages: 336 Language: Chinese Publisher: Machinery safety technology known as book publishers of the Yellow Emperor by the security forces to create a pro-technology guru. best-selling global. digital security technology experts jointly recommended. Comprehensive discussion on how to build a security barrier in the entire software development life cycle. software for the design of safety guidelines given farsighted. comprehensive and informative. easy to understand. For any concern about the safety of software development people. is an essential book. The book is divided into two parts. The first part introduces the code should know before writing software security knowledge on how to introduce security in software engineering practice. any person involved in software development should read. The main contents include: Introduction to the guidi...</subfield>
  </datafield>
  <datafield tag="650" ind1=" " ind2=" ">
    <subfield code="a">System design</subfield>
  </datafield>
  <datafield tag="650" ind1=" " ind2=" ">
    <subfield code="a">Computer security</subfield>
  </datafield>
  <datafield tag="650" ind1=" " ind2=" ">
    <subfield code="a">Development</subfield>
  </datafield>
  <datafield tag="650" ind1=" " ind2=" ">
    <subfield code="a">Information technology</subfield>
  </datafield>
  <datafield tag="650" ind1=" " ind2=" ">
    <subfield code="a">Security measures</subfield>
  </datafield>
  <datafield tag="650" ind1=" " ind2=" ">
    <subfield code="a">Computer networks</subfield>
  </datafield>
  <datafield tag="650" ind1=" " ind2=" ">
    <subfield code="a">Data protection</subfield>
  </datafield>
  <datafield tag="650" ind1=" " ind2=" ">
    <subfield code="a">Computer software</subfield>
  </datafield>
  <datafield tag="650" ind1=" " ind2=" ">
    <subfield code="a">Security measures</subfield>
  </datafield>
  <datafield tag="700" ind1=" " ind2=" ">
    <subfield code="a">Viega, John</subfield>
  </datafield>
  <datafield tag="856" ind1="4" ind2="0">
    <subfield code="u">http://www.amazon.com/exec/obidos/ASIN/7111459156/chopaconline-20</subfield>
  </datafield>
  <datafield tag="942" ind1=" " ind2=" ">
    <subfield code="c">BK</subfield>
  </datafield>
  <datafield tag="952" ind1=" " ind2=" ">
    <subfield code="0">0</subfield>
    <subfield code="1">0</subfield>
    <subfield code="4">0</subfield>
    <subfield code="7">0</subfield>
    <subfield code="a">QUESTCL</subfield>
    <subfield code="b">QUESTCL</subfield>
    <subfield code="d">2015-11-03</subfield>
    <subfield code="g">1181.00</subfield>
    <subfield code="l">0</subfield>
    <subfield code="o">005.1221VIE</subfield>
    <subfield code="p">53357</subfield>
    <subfield code="r">2015-11-03 00:00:00</subfield>
    <subfield code="w">2015-11-03</subfield>
    <subfield code="y">BK</subfield>
  </datafield>
</record>
