Nominate a Book



In order to nominate a book for the candidate list, you must submit a book review. This may seem onerous to you, at first, but bear with us. It accomplishes two things. First, the book review will get posted immediately with your byline, once approved by the committee, and we will not have to wait months for a committee member to read the book and write a review. Second, and maybe more importantly, you have to feel strongly enough about your nomination to put some skin in the game. If you feel passionately about putting your book on the candidate list, you should at least have enough passion to spend a few hours telling us why. Please submit as many nominations as you wish.


Book Review Requirements

Use this format:

  Cybersecurity Canon Candidate Book Review: "<BOOK TITLE>" <YEAR PUBLISHED>, by <AUTHOR>,” Book Reviewed by <BOOK REVIEWER NAME>, <BOOK REVIEWER TITLE>, <DATE REVIEW WAS WRITTEN>.
  Example:
  Cybersecurity Canon Candidate Book Review: "Spam Nation: The Inside Story of Organized Cybercrime - from Global Epidemic to Your Front Door (2014) by Brian Krebs," Book Reviewed by Rick Howard, Palo Alto Networks CSO, 24 November 2014.

 

Executive Summary

Write a 250-word executive summary for those readers who do not want to take the time to read your 1500 word review at the moment. You have 250 words to summarize your larger review. At the least, you want to convince readers that they should actually read the review. At the most, you want to convince readers that they should vote for this book to make it into the Canon.

Review

You are trying to make the case that the book should be inducted into the Cybersecurity Canon. Reviews will be between 800 and 1,500 words, not including the executive summary. At a minimum, it should address how well the book excels in one or more of three main categories – Fiction, Non-Fiction, and Technical – and one or more of seven sub-categories:

  • Cyber History and Culture
  • Cyber Crime
  • Cyber Espionage
  • Cyber Hacktivism
  • Cyber War
  • Novels
  • Technical

Good reviews have an introduction and a conclusion. In the introduction, talk about any background about why you picked up this book in the first place and why it is important to you specifically. In the conclusion, make your final case about why this book should be included in the Cybersecurity Canon.

Note: Consider the Executive Summary and the Review to be two stand-alone documents. It is perfectly acceptable to have the same or similar language in both the Executive Summary and the Review.

 

Submission

Combine both the executive summary and review into one document. If you are feeling scholarly, include the citation for any sources and references that you used, in addition to the book you are reviewing. Do not worry about the format. We will take care of that. Use the form below to submit the combined review. We accept Microsoft Word format and plain text files. We will take PDF files but we will edit these reviews for grammar and format. PDF files make that harder to do.

  • Reviews should be between 800 and 1,500 words.
  • Reviews should have a 4 to 10 word headline that captures the message of the book. A longer, 10-15 word sub-head should include the book's title.
  • There should follow a 1 to 2-sentence executive summary of the book in italics, below the headline and above the full review.
  • The reviewer should not have a personal connection (e.g., friend, relative) to the author.
  • At least half of each review can summarize the book, while the second half (or no less than 20%) can be opinion about the book's value.
  • The reviewer is trying to make the case that the book should be included in the Cybersecurity Canon. At a minimum, it should address how well the book excels in the specific Standard Category/Sub-category pair.

 

Fill out my online form.