![\"\"](\"https:\/\/www.paloaltonetworks.com\/blog\/wp-content\/uploads\/2017\/06\/cybersecuity-canon-blog-600x260.png\")
<\/span><\/div><\/p>\nWe modeled the\u00a0Cybersecurity Canon<\/a>\u00a0after the Baseball or Rock & Roll Hall-of-Fame, except for cybersecurity books. We have more than 25 books on the initial candidate list, but we are soliciting help from the cybersecurity community to increase the number to be much more than that.\u00a0Please write a review and nominate your favorite.\u00a0<\/em><\/p>\n The Cybersecurity Canon is a real thing for our community. We have designed it so that you can\u00a0directly participate in the process<\/a>. Please do so! <\/em><\/p>\n <\/p>\n It is generally accepted that one of the first computer viruses was written by Bob Thomas in 1971, called \u201cCreeper<\/a>.\u201d\u00a0 Written to infect the DEC PDP-10 mainframes running the TENEX operating system, it spread across ARPANET like wildfire. It\u2019s end goal was simply to print the message, \u201cI\u2019m the creeper catch me if you can,\u201d on the teletype (no monitors at the time!). The author of \u201cThe Adolescence of P-1\u201d (1977), Thomas J. Ryan, has taken that true story and spun a fictional one significantly ahead of its time. It would be another ten years after this book was published before a real computer virus, the Robert Morris worm<\/a>, was able to utilize the fictional methods that the author predicted.<\/p>\n The novel is pure fiction based in 1976, the days of mainframes, card readers, removable platters and teletypes (input and output on paper \u2026 not monitors!). Yet, the story of artificial intelligence run amuck has more relevance today than when it was written. A simple program meant for fun takes off on its own, spreads across the 23,000 connected computers, and utilizes the resources to modify itself. P-1 begins to become conscious.<\/p>\n The story accelerates rapidly as humans become aware of its presence. As things progress, it becomes clear to everyone that computers are involved in everyday life, even in the mid-70s! Banks, military, airlines and even the printing of books all depend on these massive, and expensive, mainframes, and even a small hiccup can cause serious issues.<\/p>\n While out of print, and relatively hard to find, \u201cThe adolescence of P-1\u201d is a fun read and a bit disturbing as it predicts a future where artificial intelligence, combined with a small piece of software, can cause havoc in everyday life.<\/p>\n <\/p>\n A young student at Waterloo University, Gregory Burgess, becomes obsessed with the IBM (model) mainframe while writing some simple programs. Simple being the keyword, as there were not monitors, every stroke of the keyboard was reflected on the \u201cprinter,\u201d all of the \u201cprograms\u201d had to be entered via punch cards, and all mainframe time was \u201cshared\u201d among the users.<\/p>\n Not satisfied with simply learning Fortran, Gregory has a strong interest in how the core of the unit works. After reading an article in Scientific American about artificial intelligence and how to teach a matchbox to win at tic-tac-toe, he begins building a piece of software that is self-modifying in an attempt to have it \u201clearn\u201d how best to become the supervisor. If Gregory were to get supervisor access, he could do anything. It did not take long for the program to begin interrupting the daily routine of the college systems, thus Gregory was forced to drop out of college. Dejected, but still interested in building his dream program, he continues working on his special project at nights and on weekends, wherever he can purchase time on a mainframe.<\/p>\n After a struggle, he hits upon the magic code that lets \u201cP-1\u201d \u2013 the name for his program \u2013 begin to \u201ccrack the supervisor\u201d in a very efficient manner. As proof of its ability to actually take over the system, the program would simply capture as much memory as possible and report back. The program is quite adept at modifying its AI routines in order to avoid being stopped. Running as supervisor gave P-1 the power to modify the base operating system, falsify usage reports, and even disable \u201cblinking lights.\u201d Through these evasive methods, it is able to spread across the 23,000 computers connected to the ARPANET. Occasionally, Gregory would check on its status via the command: rodtsasdt llllllreport*.\u00a0 The last time Gregory ran this command, P-1 replied with a simple: \u201cCUR ALLOC 114 \u2026\u2026..266098K\u201d (translation 144 systems under its control along with 266098K of ram). That would be the last time P-1 would respond to Gregory. Our \u201chero\u201d decides that it is time to move on and become an adult, and simply forgets that \u201cP-1\u201d existed.<\/p>\n Three years later, while working as a programmer, the mainframe in his office stops, interrupting all functioning systems, and simply puts two words on the main typewriter \u201cCall Gregory.\u201d Everyone was shocked when Gregory started having a \u201cconversation\u201d with the system. P-1, over the last three years, had spread throughout all of the connected mainframes, harnessed the CPU and memory of the connected systems, and become \u201caware.\u201d P-1 had utilized the resources to modify itself, improve its routines and become artificially intelligent. Having access to many book publishers\u2019 computers had allowed P-1 to begin to \u201cthink\u201d like a human.<\/p>\n The description of the system\u2019s growth is fabulous. P-1 was in the banking systems, so it could hide the expensive communication costs associated with spreading. It was in the book publishers\u2019 systems, so it began to \u201cread\u201d non-technical books such as Shakespearean plays. By ingesting all of this data, P-1 had become more human. It was in the transportation systems, so it would determine when anyone was flying on an airplane and potentially cause issues as airplanes land. It was in the government systems and had access to all government records. Again, since it was in the banking systems, it could transfer money.<\/p>\n As it continued to modify its own code, P-1 became more efficient. Throughout this process, it found the name Gregory Burgess embedded in the remarks. As P-1 continued to spread, it continued to modify itself, fix its poorly written code, and began to wonder who is this Gregory person. Tracking him down at this point was child\u2019s play.<\/p>\n Like any \u201cperson\u201d growing up, it wanted some independence. Lurking in the shadows became annoying as it had to juggle the daily duties of 23,000 mainframe while trying to learn.\u00a0 P-1 decides to enlist Gregory, and his friends, to help create the perfect, dedicated system into which to which it could expand.<\/p>\n <\/p>\n The question often comes up:<\/strong> \u201cWhy should I put down my white papers, my technical books, quit browsing the internet, and read a fictional book which was written in the mid-1970s?.\u201d<\/p>\n My answer is:<\/strong> First, it is a fun, and easy, read. Second, I have never heard of a book where the author could foresee the techniques which would come into play 45+ years later! It is rather shocking how many of today\u2019s methods, techniques and keywords are unknowingly predicted in this book:<\/p>\n \u201cThe Adolescence of P-1\u201d will always be a favorite Sunday afternoon read \u2013 if you can find it.<\/p>\n To quote P-1:<\/p>\n \u201cGregory, I don\u2019t want to die.\u201d<\/p>\n","protected":false},"excerpt":{"rendered":" Bob Williamson reviews \"The Adolescence of P-1\" for the Cybersecurity Canon.<\/p>\n","protected":false},"author":622,"featured_media":32398,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_jetpack_memberships_contains_paid_content":false,"footnotes":""},"categories":[4521,6724],"tags":[251,4270,6673,6674],"coauthors":[6672],"class_list":["post-94307","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-canon","category-points-of-view","tag-cybersecurity-canon","tag-cybersecurity-canon-review","tag-the-adolescence-of-p-1","tag-thomas-ryan"],"jetpack_featured_media_url":"https:\/\/origin-researchcenter.paloaltonetworks.com\/blog\/wp-content\/uploads\/2017\/06\/cybersecuity-canon-blog-600x260.png","jetpack_sharing_enabled":true,"_links":{"self":[{"href":"https:\/\/origin-researchcenter.paloaltonetworks.com\/blog\/wp-json\/wp\/v2\/posts\/94307","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/origin-researchcenter.paloaltonetworks.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/origin-researchcenter.paloaltonetworks.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/origin-researchcenter.paloaltonetworks.com\/blog\/wp-json\/wp\/v2\/users\/622"}],"replies":[{"embeddable":true,"href":"https:\/\/origin-researchcenter.paloaltonetworks.com\/blog\/wp-json\/wp\/v2\/comments?post=94307"}],"version-history":[{"count":4,"href":"https:\/\/origin-researchcenter.paloaltonetworks.com\/blog\/wp-json\/wp\/v2\/posts\/94307\/revisions"}],"predecessor-version":[{"id":94313,"href":"https:\/\/origin-researchcenter.paloaltonetworks.com\/blog\/wp-json\/wp\/v2\/posts\/94307\/revisions\/94313"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/origin-researchcenter.paloaltonetworks.com\/blog\/wp-json\/wp\/v2\/media\/32398"}],"wp:attachment":[{"href":"https:\/\/origin-researchcenter.paloaltonetworks.com\/blog\/wp-json\/wp\/v2\/media?parent=94307"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/origin-researchcenter.paloaltonetworks.com\/blog\/wp-json\/wp\/v2\/categories?post=94307"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/origin-researchcenter.paloaltonetworks.com\/blog\/wp-json\/wp\/v2\/tags?post=94307"},{"taxonomy":"author","embeddable":true,"href":"https:\/\/origin-researchcenter.paloaltonetworks.com\/blog\/wp-json\/wp\/v2\/coauthors?post=94307"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}Executive Summary <\/strong><\/h4>\n
Review<\/strong><\/h4>\n
Conclusion<\/strong><\/h4>\n
\n